About v1/Peppol

Options when sending to Open/Peppol:

• Main goal : include your UBL in the API and send via Billit to a Open/Peppol Receiver
• Alternative : You can also json tags without UBL (info : https://api.billit.be/swagger/ui/index#/Peppol). In case of Json tags, the v1/order endpoint is the recommended solution, more info : https://docs.billit.be/docs/quick-start#/

Specific for this v1/Peppol API endpoint:

• Basic requirement : The sender is able to include a valid Peppol UBL file :
  • The file complies with the Open/Peppol validation rules. During setup the sender will test the UBL content seperately for the relevant invoicing scenario's.
  • The customer and supplier are correctly mentionned in the UBL.
• The transport type is Open/Peppol (not other channels such as Email or non-Peppol einvoicing networks). If the receiver is not registered on Open/Peppol, then an alternative channel cannot be used via Billit.
• The "MyBillit" User Interface is not used for user tracking the success of the delivery, so you will not be able to view the invoices sent or received in My Billit. Status is obtained via API and can be integrated in the invoicing software of the sender.
• About attachments:
  • If no attachment is included as encoded object, then UBL will be sent via Peppol without any attachment (no Billit human readable generated).
  • If you want to include one or more attachments, then include them in your source UBL.