sevDesk icon

sevDesk

Consume the sevDesk API
Join our community

Actions41

Overview

This node integrates with the sevDesk API to create a new check account transaction. It is useful for automating bookkeeping tasks by programmatically adding transactions to a specified check account in sevDesk. Typical use cases include recording payments, deposits, or any financial movements related to a bank or checking account managed within sevDesk.

For example, an accountant or finance team can use this node to automatically log transactions imported from other systems or payment gateways, ensuring that the accounting records stay up-to-date without manual entry.

Properties

Name Meaning
Value Date The date when the check account transaction was booked (required).
Amount The monetary amount of the transaction (required).
Check Account ID The identifier of the check account to which this transaction belongs (required).
Payee / Payer Name The name of the payee or payer involved in the transaction (required).
Status The status of the transaction. Options: Created (100), Linked (200), Private (300), Booked (400).
Additional Fields Optional extra fields to provide more details about the transaction:
- Entry Date Date when the transaction was imported.
- Payment Purpose Description or purpose of the payment.
- Enshrined Date when the transaction was enshrined (made immutable). Use with caution.
- Source Transaction ID ID of the source transaction if this is a rebooking.
- Target Transaction ID ID of the target transaction if this is a rebooking.

Output

The node outputs JSON data representing the created check account transaction as returned by the sevDesk API. This typically includes all properties of the newly created transaction such as its unique ID, dates, amounts, status, and linked account information.

If the API supports binary data for this resource (not indicated here), it would be summarized accordingly, but this node primarily deals with JSON transaction data.

Dependencies

  • Requires an active sevDesk API key credential configured in n8n.
  • Depends on the sevDesk REST API endpoint at https://my.sevdesk.de/api/v1/.
  • The node sends HTTP requests with JSON payloads to create transactions.

Troubleshooting

  • Missing Required Fields: Ensure all required properties (Value Date, Amount, Check Account ID, Payee/Payer Name, Status) are provided; otherwise, the API will reject the request.
  • Invalid Check Account ID: Using a non-existent or incorrect check account ID will cause errors. Verify the ID by fetching check accounts beforehand.
  • Status Value Errors: Only the predefined status codes (100, 200, 300, 400) are accepted. Using invalid values may result in API errors.
  • API Authentication Failures: Confirm that the API key credential is valid and has sufficient permissions.
  • Date Format Issues: Dates must be correctly formatted as ISO 8601 strings; improper formatting can cause request failures.
  • Rebooking IDs: When using source or target transaction IDs for rebooking, ensure these IDs exist and belong to valid transactions.

Links and References

Discussion