Sending the Sales Invoice

Following the creation of your first invoice, the next step is to dispatch it to the recipient. Understanding that invoice delivery methods can vary significantly from one country to another and even among different customers, we've simplified the process to ensure ease and flexibility.

You can explore the various transportTypes available for sending invoices by visiting our documentation page Transport Types. It's important to note that not all features may be available on the test network within the sandbox environment. Therefore, we recommend regularly checking our network environments documentation for the most recent updates and changes. This proactive approach helps ensure that you're always aligned with the latest capabilities and requirements for invoice delivery.

Sending the invoices can be done by 2 options:

1. Use the commands/send API endpoint for immediate sending
   1. Content of the Json body : see example below. You can send one or many invoices with one command, alle the invoices must be for the same transporttype (e.g. Peppol).
   2. List of all TransportTypes can be found here -> Transport Types
2. No API command for sending used:
   1. Enable auto sending invoices
   2. This can be found in the company settings page (Settings/General : "Automatically send your invoices to the customer". Every day at 9 am all non-sent invoices will be sent. ii. Manual sending
   3. This can can be useful if you want to check the invoices prior to sending or if you want to add attachments.

📘

Testable request in Postman: 05 - Send Sales Invoice

{
"Transporttype" : "Peppol",
"OrderIDs" : 
  [ 
    1684998,
	  1684999
  ]
}

{
"Transporttype" : "Peppol",
"OrderIDs" : 
  [ 
    1684998
  ]
}

Validations

Per transporttype, controls are executed linked to the TransportType (e.g. Peppol). Error types can be:

• The content is not compliant with the validation rules of the network (e.g. Peppol)
• The receiver is not on the network

You will have to adjust the invoice before sending again.