After following this walkthrough your application will be able to send an invoice via eVerbinding and check the delivery-status.
Requirement: Walkthrough: Connect your application
Step 1: Create a XML e-invoice
In the eVerbinding platform we talk about documents with templates. A document can be an invoice or an order based on a specific standard. This is determined by the template. For more information read: Overview of documents and templates.
To be able to send a invoice you now need a UBL 2.1 document that complies with Simplerinvoicing SI 1.1 standard. See simplerinvoicing-ubl-invoice for more information about the invoice and validation options.
Step 2: Determine the routing Id
For sending you need to supply a routing Id in the form of a ReferenceId and an email address of the contact person of the receiver. The ReferenceId also must be in the UBL SI 1.1 document on the proper place and the email address should be added in the document.
eVerbinding will try to deliver the document first within the eVerbinding platform by searching for the receiving party. If the receiver is not part of the eVerbinding platform a lookup is done in the Simplerinvoicing / PEPPOL network based on the ReferenceId. If the ReferenceId still can not be found an email with a private link is send to the contact person.
For selecting the prefered or best delivery, the call GetAdvisedInvoiceRecipientId can be used with all the Id’s known for the recipient. The best Id will be returned based on it’s availability in eVerbinding and the SimplerInvoicing / PEPPOL network.
Step 3: Send the document
On send via the SendDocument call the document will be validated before accepting. If a document is not valid XML, or doesn’t match the XSD or there are fatal errors based on the XSLT of the template the document will be rejected with the matching error response.
Make sure you use the correct TemplateId when sending; please read the Overview of documents and templates.
If the document is valid it is accepted and the call will return the track-and-trace code in the form of a ExternalId. Save this ExternalId for prove and to follow the status of the document. Be aware: if there is no ExternallD returned the document is not send.
Step 4: Check statuses
One of the nice things of sending documents with eVerbinding is the fact that you can see the status of the document. Use the call GetOutboxDocument with the ExternalId (one) or the call GetOutboxDocuments (all changed) with a proper filter and update the document statuses in your system.