The provider's user API and AS4 between Access Points are different interfaces. Test receiving, sending, duplicates and errors; an HTTP success alone does not confirm delivery.
How does software connect to Peppol via an API?
A typical integration connects your invoicing or ERP system with the interface of a delivery provider. The software prepares the data, hands over the document and picks up the results or received invoices. The provider performs its role in the delivery network.
The customer API and the transfer between Access Points are different layers. Peppol AS4 describes communication between providers. The specific API addresses, authentication method and response format for your software are set by the documentation of the provider you choose.
Before programming starts, confirm the scope: sending only, receiving only, or both directions. Also state any multiple companies, corrective documents, attachments and the required link to accounting.
Which tasks should be divided between the ERP and the provider?
| Task | What to agree |
|---|---|
| Creating the invoice | Where the data source is and who approves the document |
| UBL export | Who creates the XML and which profile or release it supports |
| Addressing | Where the Peppol ID is taken from and how the recipient is verified |
| Validation | Which layers are carried out and how errors are returned |
| Delivery | What message identification and result the ERP receives |
| Receiving | How the original XML, attachments and time of receipt are obtained |
| Reporting | How the result of the data for the Financial Administration of the Slovak Republic (Finančná správa SR) is tracked |
The provider may accept a finished XML or offer to create it from other data. In both cases, check that the business meaning of the fields is preserved. The mapping is explained in the annotated XML sample.
How should sending and the return of the result be designed?
First save the document and check it technically. When handing it over, record your own reference and the provider's message identification. The API response has an explained meaning: acceptance of the request may come before the final result of the transfer.
With asynchronous processing, the result may arrive by webhook, or the software may find it out by repeated polling as described in the documentation. Do not treat these options as a mandatory feature of every API. Agree how the result is returned to the correct document and what a staff member will see in the event of an error.
An illustrative integration flow:
ERP prepares and saves the invoice
→ checks the XML and assigns its own reference
→ hands the document over to the provider
→ saves the message identification
→ picks up the result of the transfer
→ shows the status or a correction task
The diagram is not a definition of a specific API. Take the status names and available confirmations from the service's documentation. Distinguish technical delivery from business approval by the customer.
What happens during an outage or a repeated request?
If a timeout occurs after sending, the result may be unknown: the provider may have accepted the document. Resending must have agreed protection against duplicates. Check whether the API supports an idempotent request or looking up a message by your reference.
With webhooks, allow for a repeated event and verify its origin as described in the documentation. When receiving, store both the message identifier and the identity of the invoice; do not base the check on the file name alone. A technical duplicate of a transfer and two documents that are similar in business terms are different situations.
Also prepare a manual way of resolving a case that has been left without a clear result. Do not automatically mark a result as successful just because error codes have stopped coming in.
How should receiving and access for several companies be set up?
Keep the XML you have obtained and compare its data with the import into the correct company. Subsequent approval, account assignment and payment belong to your own workflow. The official UBL structure will help you determine where business data belongs.
Keep test and production accounts separate. Store keys on the server and make them available only to the processes that need them. With several entities, verify the scope of each authorisation so that a request from one company cannot process the documents of another.
Also define how access is restored and how credentials are exchanged when the service changes. An operational log should help to trace a problem without needlessly copying the entire content of invoices into every log.
What must pass testing before going live?
Test ordinary sending and receiving, an invalid document, an unknown recipient, a correction and a repeated import. Add a timeout after handover, a repeated event and temporary unavailability of the service. For each scenario, define the expected result and the procedure for the operator.
Record the rules release used and the connector version. When updating, compare them with the eDelivery specifications in force. Checking the document is explained in e-invoice validation.
For Slovak operations, also add an agreement on data reporting. The Financial Administration describes the automatic transfer via the Digital Postman (Digitálny poštár); the integration should allow the user to trace its result. The general flow is described in invoice delivery.
The organisation of work and testing with the software supplier is complemented by the guide to connecting accounting software. Converting existing documents is covered by the PDF to eFaktúra procedure.
Verified sources
We rely on official materials. You will find the original documents under the links below. When the rules change, we update this guide too.
Content verified 1/10/2026. In a specific tax case, the applicable wording of the law and the circumstances of the supply are decisive.