Actions99
- Expenses Actions
- Group Accounts Actions
- Group Account Codes Actions
- Accounts Actions
- Purchase Orders Actions
- Get A List Of Purchase Orders
- Create A New Purchase Order
- Get A Purchase Order
- Update A Purchase Order
- Open A Purchase Order
- Get A List Of Purchase Orders Items For A Specific Purchase Order
- Create A Purchase Order Item
- Get A Purchase Order Item
- Update A Purchase Order Item
- Delete A Purchase Order Item
- Get A List Of Goods Received Notes For A Specific Purchase Order
- Create A Goods Received Note
- Attach A File To A Goods Received Note
- Delete A Goods Received Note
- Suppliers Actions
- Fund Accounts Actions
- Cards Actions
- Expense Categories Actions
- Tax Rates Actions
- Amortizations Actions
- Account Teams Actions
- Account Codes Actions
- External Teams Actions
- Custom Fields Actions
- Get Custom Fields
- Create A New Custom Field
- Get Custom Field
- Update Custom Field
- Delete A Custom Field And All Its Values
- Get Custom Field Values
- Create A Custom Field Value
- Delete Custom Field Values
- Get A Custom Field Value
- Update A Custom Field Value
- Delete A Custom Field Value
- Get Managers For A Specific Custom Field Value
- Adds Managers For A Specific Custom Field Value
- Replaces Managers For A Specific Custom Field Value
- Removes Managers For A Specific Custom Field Value
- Webhook Subscriptions Actions
- Group Teams Actions
Overview
This node operation allows you to add payment details to a specific bank expense and mark that expense as paid. It is useful in financial workflows where expenses need to be updated with payment information after the payment has been made, ensuring accurate tracking of paid expenses within an accounting or expense management system.
Practical examples include:
- Automatically updating an expense record with payment confirmation details once a payment transaction completes.
- Integrating with banking or payment systems to reflect the payment status of expenses in real-time.
- Streamlining bookkeeping by marking expenses as paid directly from automated workflows.
Properties
| Name | Meaning |
|---|---|
| Account Id | Identifier of the account associated with the expense. |
| Expense Id | Identifier of the specific expense to update with payment details. |
| Date | Date when the payment was made. |
| Payment Reference | Reference string for the payment, such as a transaction ID or note. |
| Account Number | Bank account IBAN or number from which the payment was made. |
Output
The node outputs JSON data representing the updated expense object after adding the payment details and marking it as paid. This typically includes the expense's updated status, payment date, reference, and related account information.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential or similar authentication token configured in n8n to connect to the external service managing expenses.
- The node interacts with an external API endpoint (likely a financial or expense management API) to update expense records.
- Proper base URL and authentication credentials must be set up in n8n for successful API communication.
Troubleshooting
- Common issues:
- Missing or incorrect
Account IdorExpense Idcan cause the API call to fail or update the wrong record. - Invalid date format for the
Dateproperty may result in errors or rejected requests. - Authentication failures if API credentials are not properly configured or expired.
- Missing or incorrect
- Error messages:
- "Expense not found" or similar indicates the provided
Expense Iddoes not exist or is inaccessible. - "Unauthorized" or "Authentication failed" suggests issues with API credentials.
- Validation errors on fields like
DateorAccount Numberrequire checking input formats and values.
- "Expense not found" or similar indicates the provided
Resolving these usually involves verifying input values, ensuring correct API credentials, and confirming the existence of referenced accounts and expenses.
Links and References
- Refer to your expense management system’s API documentation for detailed field requirements and error codes.
- n8n documentation on setting up API credentials and HTTP request nodes for further customization.