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
- Cards Actions
- Suppliers Actions
- Fund Accounts 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.
- Marking expenses as paid in bulk after reconciliation with bank statements.
- Integrating payment status updates into automated bookkeeping processes.
Properties
| Name | Meaning |
|---|---|
| Account Id | Identifier of the account related to the expense. |
| Expense Id | Identifier of the specific expense to update with payment details. |
| Date | Date when the payment was made. |
| 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 and payment information fields reflecting the changes made by this operation.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential for authenticating requests to the external service managing expenses (referred generically as "an API key credential").
- The node uses a base URL configured in credentials to send HTTP requests.
- The operation depends on the external expense management API to update expense records.
Troubleshooting
- Common issues:
- Invalid or missing
Account IdorExpense Idcan cause the update to fail. - Incorrect date format for the
Dateproperty may result in validation errors. - Network or authentication failures if the API key credential is not set up correctly.
- Invalid or missing
- Error messages:
- "Expense not found" indicates the provided
Expense Iddoes not exist; verify the ID. - "Unauthorized" or "Authentication failed" suggests issues with the API key credential.
- "Invalid date format" means the
Dateproperty value does not meet expected formatting; use ISO 8601 format (e.g.,YYYY-MM-DD).
- "Expense not found" indicates the provided
Links and References
- Refer to your expense management system’s API documentation for details on the expense update endpoint.
- Use ISO 8601 standard for date formatting: https://en.wikipedia.org/wiki/ISO_8601