Resource: salesinvoicebatch.nv
HTTP-method: POST
This resource can be used to import sales invoices as a batch, sales orders must be imported individually with the resource salesinvoice.nv.
Please note that when importing sales invoices using salesinvoicebatch.nv, any potential errors in the import must be queried using the query get batch status getbatchstatus.nv. The query also returns the error type returned by the Netvisor API. Errors are not otherwise notified.
| Level | Element | Format and length | Occurs | Description | Example |
| Root | root | Aggregate | 1 | ||
| 1 | salesinvoicebatch | Aggregate | 1 | ||
| 2 | sharedattachments | Aggregate | 0...1 | ||
| 3 | attachment | Aggregate | 1...n | ||
| 4 | mimetype | String, max. 50 | 1 | MIME-type of the attachment | application/pdf |
| 4 | data | String | 1 | Base64 encoded data of the attachment | |
| Attr. | type | String | 1 | finvoice or pdf | finvoice |
| 4 | filename | String, max. 255 | 1 | Attachment file name | attachment.pdf |
| 4 | description | String, max. 100 | 1 | Attachment description | Description |
| 4 | printbydefault | Integer | 0...1 | NOTE! Not given if the attachment type is finvoice. Otherwise, the request is rejected. 1 = true, 0 = false | 1 |
| 4 | itemlink | Aggregate | 1 | ||
| 5 | itemidentifier | String, max. 50 | 1 | ||
| 2 | items | Aggregate | 1 | ||
| 3 | item | Aggregate | 1...n | ||
| 4 | identifier | String, max. 50 | 1 | Identifier of one invoice in invoice batch. Defined by you. | |
| 4 | itemdata | XML | 1 | Valid SalesInvoice XML | See the resource description: Import Sales Invoice |
This article has been translated using an AI-based translation tool. The contents or wording of these instructions may differ from those in other instructions or in the software.
Did you find it helpful? Yes No
Send feedbackSorry we couldn't be helpful. Help us improve this article with your feedback.