Payhawk icon

Payhawk

Interact with the Zitadel API

Actions99

Expenses → Add Payment Details To A Bank Expense And Mark Expense As Paid

AI-generated

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 with external payment systems to reflect payment status in your expense tracking tool.

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 string associated with the payment (e.g., 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 fields such as the expense's updated status, payment date, reference, and bank account information.

No binary data output is indicated for this operation.

Dependencies

  • Requires an API key credential for authenticating requests to the external expense management service.
  • The node uses a base URL configured in credentials to send HTTP requests.
  • The operation depends on the external service's API endpoint that supports updating expenses with payment details.

Troubleshooting

  • Missing Required Fields: Ensure all required properties (Account Id, Expense Id, Date) are provided; missing these will cause errors.
  • Invalid Identifiers: Using incorrect or non-existent Account Id or Expense Id will result in failed updates.
  • API Authentication Errors: Verify that the API key or authentication token is correctly configured and valid.
  • Date Format Issues: The payment date should be in a valid format accepted by the API; otherwise, the request may be rejected.
  • Network or Endpoint Errors: Check connectivity and that the base URL is correct and accessible.

Links and References

  • Refer to the external expense management API documentation for detailed information on the "Add Payment Details" endpoint.
  • Consult n8n documentation on how to configure API credentials and use HTTP request nodes for similar integrations.

Discussion