Actions40
- Customer Actions
- Customer Group Actions
- Discount Actions
- Document Actions
- Document Payment Actions
- SEPA Payment Actions
Document → Complete Document
AI-generatedOverview
The node interacts with the EasyBill API to complete a document. It finalizes a document by marking it as done, optionally including a reason for the change. This operation is useful in scenarios where a document needs to be finalized in the billing or invoicing process, such as completing an invoice or a receipt before sending it to a customer.
Use Case Examples
- Completing an invoice document after all items and details have been reviewed and confirmed.
- Finalizing a receipt document to prevent further modifications and prepare it for archiving or sending.
Properties
| Name | Meaning |
|---|---|
| Document ID | The ID of the document to be completed. |
| Reason for Change | A string saved on the document version as the reason for completing the document. This is used if updating an already finalized document. |
Output
JSON
response- The response from the EasyBill API after completing the document, typically including the updated document status and details.
Dependencies
- EasyBill API key credential for authentication
Troubleshooting
- Ensure the Document ID is correct and the document exists in EasyBill to avoid 'not found' errors.
- If providing a reason for change, ensure it is a valid string; otherwise, the API might reject the request.
- Check API rate limits and batching options if processing multiple documents to avoid throttling issues.
Links
- EasyBill API Documentation - Official API documentation for EasyBill, including endpoints for document management.