Peppol.
The common language of invoices.
One network, different applications and providers. We explain the addresses, formats and rules that make the exchange of e-invoices possible.
COMMON RULESWhat is Peppol?
Peppol combines rules for electronic business documents with a network for exchanging them. A business uses its own application and a provider of its choice; its business partner may work with a different system. The basic principle is described by OpenPeppol for users.
When preparing for e-invoicing, it helps to distinguish three questions: who you are sending the document to, what form its data takes and how it is delivered. We devote a separate article to each of them.
How is Peppol related to the Slovak eFaktúra?
Peppol is part of the Slovak e-invoicing solution. The role of the national Peppol Authority is performed by the Financial Directorate of the Slovak Republic (Finančné riaditeľstvo SR). The context is described in the Slovak profile on OpenPeppol.
For your own business, assess the legal obligations too. In the eFaktúra section you will find guidance on the document format and the legislation. When choosing a service, continue to the Digital Postman (Digitálny poštár) section. Here we focus on what makes systems work together.
Which terms are worth knowing?
| Term | Which question it answers |
|---|---|
| Peppol ID | How is the recipient identified in the network? |
| Access Point | Who handles the transfer between providers? |
| SMP and SML | How does the system find the information needed for delivery? |
| Peppol BIS Billing | What rules apply to the exchange of invoices and credit notes? |
| Validation | Which data checks must be carried out before processing? |
When asking a supplier a question, always tie it to a specific work step. Instead of a general “do you support Peppol?”, ask for example about receiving a document, identifying a partner or explaining an error message.
What do our guides explain?
- How Peppol works distinguishes the roles of providers and the lookup of the recipient.
- Peppol ID explains the address scheme and how to verify it.
- BIS Billing and XML links business data with how it is written into the document.
- E-invoice validation helps you read the result of technical checks.
- Peppol and other countries distinguishes the international network from the rules of a specific transaction.
- XML e-invoice: an annotated UBL sample shows the meaning of the fields and provides a complete training document with the result of a technical check.
- Peppol API integration describes connecting invoicing and ERP, processing statuses and retrying requests safely.
Start with the question you are dealing with right now. The articles also link to one another, so you can fill in the context you need.
Where can you find the current documentation?
The invoicing rules are in the BIS Billing documentation. You will find the network specifications and their effective dates on the Peppol eDelivery page.
When commissioning a software connection, we recommend agreeing who monitors changes in the rules and checks their impact on the software you use. Also keep the results of test sending and receiving; they will make comparison easier after a later update.
Take a closer look.
How the Peppol network works
How the sender, the recipient and their Access Points work together. An explanation of SMP, SML and looking up the address an e-invoice is delivered to.
Read the guidePeppol ID and the recipient's address
What a Peppol ID is and what the Slovak scheme 0245:DIČ means. How to verify a partner and tell apart Directory, Lookup and the data in an XML invoice.
Read the guideEN 16931, UBL and BIS Billing
How Peppol BIS Billing 3.0, UBL 2.1 and EN 16931 are related. What to check when exporting XML from invoicing or accounting software.
Read the guideValidation and troubleshooting
How an e-invoice XML is checked, what the Peppol rules mean and how to read a validation report. A practical line-total example and how to fix an error.
Read the guidePeppol and foreign partners
What to check when sending an e-invoice to a foreign partner via Peppol. Identifier, supported format, country rules and the network vs. a legal obligation.
Read the guideXML invoice with an example
A complete training XML e-invoice sample in UBL 2.1: header, Peppol ID, VAT, totals and a line. XSD, CEN and Peppol technical checks and field explanations.
Read the guideAPI and ERP connection
How to connect software to Peppol via a provider's API: UBL export, sending, receiving, statuses, webhooks, retrying requests and testing the integration.
Read the guideVerified 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 30/9/2026. For implementation, use the specifications currently in force and the requirements of the country concerned.