Actions29
- Article Actions
- Contact Actions
- Credit Note Actions
- File Actions
- Invoice Actions
- Payment Actions
- Profile Actions
- Quotation Actions
- Recurring Invoice Template Actions
- Voucher Actions
- Voucherlist Actions
Voucher → Create
AI-generatedOverview
This node operation creates a voucher in LexwareOffice. It is useful for automating the creation of various types of vouchers such as sales invoices, sales credit notes, purchase invoices, and purchase credit notes. Typical use cases include generating invoices for sales orders, recording refunds or returned sales orders, and managing purchase-related documents. Users can specify detailed voucher information including organization ID, voucher number, type, status, dates, amounts, tax details, contact information, remarks, voucher items grouped by tax rate, and associated files.
Use Case Examples
- Automatically create a sales invoice voucher when a new order is placed in an e-commerce system.
- Generate a purchase invoice voucher upon receiving a supplier invoice to streamline bookkeeping.
- Create a sales credit note voucher to process a refund for a returned product.
Properties
| Name | Meaning |
|---|---|
| Organization ID | Unique ID of the organization generated on creation by lexoffice. |
| Voucher Number | Number of the voucher, typically the order's identification reference number. |
| Voucher Type | Type of the voucher, such as sales invoice, sales credit note, purchase invoice, or purchase credit note. |
| Voucher Status | Status of the voucher. Only 'open' and 'unchecked' are writable via the API. |
| Voucher Date | Date when the voucher was issued. Only the date part is required. |
| Shipping Date | Date when the purchased item/service is to be shipped or supplied. Only applicable for sales invoices and sales credit notes. |
| Due Date | Date when the voucher's payment must be settled. |
| Total Gross Amount | Total gross amount of the voucher, matching the sum of all positions including tax amounts. |
| Total Tax Amount | Total tax amount of the voucher, matching the sum of all positions' tax amounts. |
| Tax Type | Tax type of the order, either net (taxes added) or gross (tax included). |
| Use Collective Contact | Whether to use the collective contact within lexoffice, ignoring the optional contact ID. |
| Contact Name | Name of the recipient or invoicing party if the collective contact is used. |
| Contact ID | Existing contact ID to assign to the voucher if not using the collective contact option. |
| Remark | Comments or remarks for the order, searchable within lexoffice. |
| Voucher Items | Positions of the voucher grouped by tax rate, including amount, tax amount, tax rate percent, and category ID. |
| Files | List of voucher image file IDs assigned to the voucher. |
Output
JSON
id- Unique identifier of the created voucher.organizationId- ID of the organization the voucher belongs to.voucherNumber- Number assigned to the voucher.type- Type of the voucher.voucherStatus- Status of the voucher.voucherDate- Date when the voucher was issued.shippingDate- Date when the item/service is to be shipped or supplied.dueDate- Due date for payment of the voucher.totalGrossAmount- Total gross amount of the voucher.totalTaxAmount- Total tax amount of the voucher.taxType- Tax type of the voucher (net or gross).useCollectiveContact- Indicates if the collective contact is used.contactName- Name of the contact if collective contact is used.contactId- ID of the contact if collective contact is not used.remark- Remarks or comments on the voucher.voucherItems- Array of voucher items with details such as amount, tax amount, tax rate, and category ID.files- Array of file IDs assigned to the voucher.
Dependencies
- An API key credential for LexwareOffice to authenticate requests.
Troubleshooting
- Ensure that the organization ID and contact ID (if used) exist in LexwareOffice before creating a voucher.
- Voucher amounts must match the sum of all positions and tax amounts; otherwise, the API may reject the request.
- Only 'open' and 'unchecked' voucher statuses are writable; using other statuses may cause errors.
- Shipping date can only be specified for sales invoices and sales credit notes; specifying it for other types may cause errors.
- File IDs assigned to the voucher must be unique and existing; omitting existing file IDs during updates deletes them permanently.