Before retrieving a sales invoice, a sales invoice list must be retrieved, from which the identifier of the sales invoice is picked. With the identifier, detailed information of one sales invoice at a time can be retrieved. When importing sales invoices, sales orders and credit notes, the up-to-dateness of customer and product registers must be taken into account. Read tips for data processing here.
Sales invoices can be imported in larger batches with batch import. Instructions for batch import can be found here.
Sales invoices' handling operations are divided into the following resources:
Endpoint | HTTP-method | Resource | DTD | Schema | Example |
GET | salesinvoicelist.nv |
|
| ||
GET | getsalesinvoice.nv / getorder.nv |
|
| ||
POST | salesinvoice.nv |
| |||
GET/POST | deletesalesinvoice.nv |
|
| - | |
GET/POST | deletesalesinvoiceproductline.nv | ||||
POST | updatesalesinvoicestatus.nv |
|
| - | |
GET | deletedsalesinvoices.nv | ||||
GET | deletedsalesorders.nv | ||||
POST | salesorderinvoicing.nv | ||||
POST | salesinvoicecomment.nv | ||||
POST | matchcreditnote.nv | ||||
GET | contractinvoicingreport.nv | ||||
GET | paymenttermlist.nv | ||||
GET | salespersonnellist.nv |
Sales payments' handling functions are divided into the following resources:
Endpoint | HTTP-method | Resource | DTD | Schema | Example |
GET | salespaymentlist.nv |
|
| ||
POST | salespayment.nv |
| |||
POST | deletesalespayment.nv |
| - | ||
GET | deletedsalespayments.nv | ||||
POST | masspayments.nv | ||||
POST | matchpayment.nv |
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.
