Actions99
- Group Accounts Actions
- Group Account Codes Actions
- Accounts Actions
- Expenses 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 bank transfer is completed.
- Integrating with accounting software to reflect the payment status of expenses in real-time.
- Streamlining bookkeeping by marking expenses as paid when payment data is received from a banking API.
Properties
| Name | Meaning |
|---|---|
| Account Id | Identifier of the account related to the expense. |
| Expense Id | Identifier of the expense to update with payment details. |
| Date | Date of the payment (required). |
| Payment Reference | Reference text or code associated with the payment transaction. |
| 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 bank account information.
If binary data were involved (e.g., receipts), it would be summarized here, but this operation focuses on JSON updates only.
Dependencies
- Requires an API key credential for authenticating requests to the external expense management or banking API.
- The node uses a base URL configured in credentials to send HTTP requests.
- Depends on the external service's API supporting updating expenses with payment details and changing their status.
Troubleshooting
- Missing Required Fields: Ensure all required properties (
Account Id,Expense Id, andDate) are provided; otherwise, the API call will fail. - Invalid Identifiers: Using incorrect or non-existent account or expense IDs will result in errors indicating resource not found.
- Authentication Errors: Verify that the API key or authentication token is correctly set up in the node credentials.
- API Endpoint Issues: Confirm the base URL and endpoint paths are correct and accessible.
- Date Format: The payment date should be in a valid format accepted by the API; invalid formats may cause request rejection.
Links and References
- Refer to your expense management or banking API documentation for details on updating expenses and payment statuses.
- n8n documentation on creating and using custom nodes: https://docs.n8n.io/integrations/creating-nodes/