Actions98
- AccountingContact Actions
- Category Actions
- CheckAccount Actions
- CheckAccountTransaction Actions
- CommunicationWay Actions
- Contact Actions
- Contact Address Actions
- Contact Custom Field Actions
- Contact Custom Field Setting Actions
- Credit Note Actions
- Credit Note Po Actions
- Export Actions
- Update Export Config
- Export DATEV (Deprecated)
- Start DATEV CSV Zip Export
- Start DATEV XML Zip Export
- Generate Download Hash
- Get Progress
- Get Job Download Info
- Export Invoice as CSV
- Export Invoice as Zip
- Export Credit Note as CSV
- Export Voucher as CSV
- Export Voucher as Zip
- Export Transaction as CSV
- Export Contact as CSV
- Invoice Actions
- Invoice Position Actions
- Order Actions
- Order Position Actions
- Part Actions
- Report Actions
- Tag Actions
- Voucher Actions
- VoucherPo Actions
Credit Note → Create
AI-generatedOverview
This node integrates with the sevDesk API to create a Credit Note. It allows users to specify detailed information about the credit note, including its number, associated contact, date, status, texts, address, currency, and tax rules. This node is useful in accounting workflows where automated creation of credit notes is required, such as refund processing, invoice adjustments, or financial record keeping.
Practical examples:
- Automatically generate a credit note when a customer returns goods.
- Create credit notes for partial payments or discounts applied after invoicing.
- Integrate with e-commerce platforms to reflect refunds in accounting software.
Properties
| Name | Meaning |
|---|---|
| Credit Note Number | The unique identifier for the credit note. |
| Contact | The contact associated with the credit note. Includes: - ID: Identifier of the contact. - Object Name: Should be "Contact". |
| Credit Note Date | The date when the credit note is issued. |
| Status | The current state of the credit note. Options are: - Draft (100) - Open (200) - Paid (1000) |
| Header | A header text for the credit note document. |
| Head Text | Multiline text appearing at the top of the credit note. |
| Foot Text | Multiline text appearing at the bottom of the credit note. |
| Address | The billing or delivery address related to the credit note. |
| Currency | The currency code used for the credit note amounts (e.g., EUR, USD). |
| Tax Rule | Defines the VAT rule according to sevDesk API v2.0. Options include: - Standard VAT liable transactions (0%, 7%, 19%) - Exports (0%) - Intra-community deliveries (0%, 7%, 19%) - Tax-free transactions §4 UStG (0%) - Reverse charge according to §13b UStG (0%) - Tax not levied according to §19 UStG - Small business (0%) |
| Tax Type (Deprecated) | Deprecated field for tax type; maintained only for backward compatibility. Users should use Tax Rule instead. |
| Tax Text | Custom text describing the tax situation. |
| Small Settlement | Boolean flag indicating if this is a small settlement. |
| Credit Note Pos | Positions or line items on the credit note. This is a collection that can hold multiple entries, though no specific fields are defined in the provided snippet (empty values array). |
Output
The node outputs an array of JSON objects representing the created credit note(s) as returned by the sevDesk API. Each output item corresponds to one input item processed.
- The
jsonfield contains the full response data from the API about the created credit note. - If an error occurs during creation and "Continue On Fail" is enabled, the output will contain an object with an
errormessage describing the failure.
No binary data output is indicated in the source code.
Dependencies
- Requires an API key credential for authentication with the sevDesk API.
- The base URL for API requests is
https://my.sevdesk.de/api/followed by the API version specified in credentials. - Environment configuration validation is performed before execution.
- Uses internal resource manager classes to handle API operations.
Troubleshooting
- Common issues:
- Invalid or missing API credentials will cause authentication failures.
- Incorrectly formatted dates or missing required fields may result in API errors.
- Using deprecated
taxTypeinstead oftaxRulemight lead to unexpected behavior.
- Error messages:
- Errors thrown by the API are caught and returned in the output if "Continue On Fail" is enabled.
- Typical errors include validation errors from the API, network connectivity issues, or permission denials.
- Resolution tips:
- Ensure all required fields are correctly filled.
- Use valid contact IDs and currency codes.
- Prefer using
taxRuleover the deprecatedtaxType. - Verify API credentials and permissions.
Links and References
- sevDesk API Documentation
- VAT Rules Reference (§UStG)
- n8n documentation on Creating Custom Nodes