Fatture in Cloud icon

Fatture in Cloud

Interact with Fatture in Cloud API

Overview

This node integrates with the "Fatture in Cloud" API to create a new Received Document record. It is designed for users who need to automate the entry of received financial documents such as expenses, passive delivery notes, or passive credit notes into their accounting system.

Typical use cases include:

  • Automatically logging supplier invoices or expense receipts received by a company.
  • Managing and tracking payments related to these documents.
  • Keeping detailed records including tax, currency, and amortization information.

For example, a company could use this node to automatically create an expense document when a new invoice PDF is received via email, including all relevant payment terms and amounts.

Properties

Name Meaning
Company ID The numeric identifier of the company for which the received document is being created.
Document Type The type of received document. Options: Expense, Passive Delivery Note, Passive Credit Note.
Description A textual description of the received document.
Entity The supplier entity associated with the document. Includes:
• Entity ID (number)
• Entity Name (string)
Date The date of the document (date/time).
Amount Net The net amount (before VAT) of the document (number).
Amount VAT The VAT amount of the document (number). Optional.
Amount Gross The gross amount (net + VAT) of the document (number). Optional.
Additional Fields A collection of optional fields including:
• Amortization (number)
• Other Withholding Tax amount (number)
• Withholding Tax amount (number)
• Attachment Token (string, password)
• Currency details (ID, exchange rate, symbol)
• E-Invoice flag (boolean)
• Invoice Number (string)
• Is Detailed flag (boolean)
• Is Marked flag (boolean)
• Next Due Date (date/time)
• Revenue/Cost Center (string)
• Tax Deductibility percentage (number)
• VAT Deductibility percentage (number)
Payments List A list of payments related to the document. Each payment includes:
• Amount (number)
• Due Date (date/time)
• Paid Date (date/time, optional)
• Payment Account details (ID, name, virtual flag)
• Payment Terms (days, type: Standard or End of Month)
• Status (Not Paid, Paid, Reversed)

Output

The node outputs JSON data representing the created received document as returned by the Fatture in Cloud API. This typically includes all the input fields along with additional metadata such as unique document IDs assigned by the system, timestamps, and status information.

No binary data output is produced by this node.

Dependencies

  • Requires an active connection to the Fatture in Cloud API using OAuth2 authentication.
  • The user must configure appropriate API credentials within n8n to authorize requests.
  • Network access to the Fatture in Cloud service endpoint is necessary.

Troubleshooting

  • Common Issues:

    • Invalid or missing company ID can cause errors.
    • Incorrect or incomplete entity (supplier) information may lead to validation failures.
    • Providing inconsistent amounts (e.g., net, VAT, and gross not matching) might cause API rejections.
    • Missing required fields like description, date, or amounts will result in errors.
  • Error Messages:

    • Errors from the API are captured and reported with details including HTTP status and error messages.
    • Validation errors often indicate which field is problematic.
    • Authentication errors suggest checking the configured API credentials.
  • Resolution Tips:

    • Ensure all required fields are provided and correctly formatted.
    • Verify that the API credentials are valid and have sufficient permissions.
    • Use the "Continue on Fail" option in n8n to handle individual item errors gracefully during batch operations.

Links and References

Discussion