Are PDF, e-invoice and Peppol synonymous?
A PDF invoice sent by email may be a legally valid invoice, but it is not a structured e-invoice. Peppol is not a format, but a network for sending invoices. European Commission By definition of eInvoicing is e-invoice data that is issued, sent and received in a structured format that can be automatically processed by a machine; PDF, Word, image, HTML or scanned invoices do not fall within this definition. At the same time, the current definition of a VAT invoice is broader: Article 217 of the EU VAT Directive defines an electronic invoice as an invoice issued and received in any electronic format. This also includes PDF. Peppol, in turn, is quadrilateral network structured for secure movement of invoices, not the invoice format itself or automatic obligation.
This distinction is more important than it seems. Your accountant may consider a PDF invoice to be perfectly correct for VAT purposes, but if the buyer is registered as an e-invoice recipient or requires structured data, PDF will not help with this obligation. These are two different sets of rules that accidentally use the same word „electronic”.
What is the difference between PDF, XML and Peppol in practice?
If you need to decide what to send to a specific buyer, the following table will help. A „Structured EN 16931 invoice” means a machine-readable data file (such as XML) that complies with the European e-invoice standard EN 16931.
| Feature | PDF by email | Structured EN 16931 invoice (agreed channel) | Invoice sent via Peppoli |
|---|---|---|---|
| How does the buyer get it? | As an attachment, a person opens and reads | As a data file directly to the company system | As a data file via Access Point |
| Automatic processing in the buyer's software | No, requires manual input or OCR | Yes, if it meets the standard | Yes, if the document meets the standard |
| Does it currently meet the definition of "electronic invoice" in the EU VAT Directive? | Yes, if it contains the required data | Yes | Yes |
| Meets the requirement of an Estonian registered e-invoice recipient | Usually not | Yes, if it fits EN 16931-1 or agreed standard | Mostly yes, if the buyer accepts this channel and the document meets the standard |
| Fulfills Latvia's structured invoice obligation | No | Yes, if it fits LVS EN 16931-1:2017 | Mostly yes, under the same condition |
This means: The Peppol channel itself does not guarantee anything. The structure of the document and what the specific buyer has requested decide.
Estonia: Check the e-business register before sending an invoice
From From July 1, 2025 An accounting entity that is entered in the commercial register as a recipient of an e-invoice may request an e-invoice from the seller for the goods or services purchased. An invoice is considered to be properly prepared if it complies with the standard EN 16931-1. However, the parties may also agree to use another relevant standard. The format and conditions under which machine-readable source documents are to be provided shall be agreed upon by the parties, unless otherwise provided by law or other legal act.
In practice, this means: before sending an invoice, it is worth checking the buyer's entry in the e-business register. If they are registered there as the recipient of the e-invoice, the requirement is up to them, not you. The test is machine readability, not whether the document has the word "Peppol". The law currently does not establish a single nationwide requirement that would oblige all Estonian B2B invoices to be sent via Peppol. Always check the specific buyer's requirement and the specific rules of the field.
Latvia: Structured invoices are already available in B2G
Latvia accounting law defines a structured electronic invoice as an invoice that is prepared, sent and received in a structured electronic format that can be processed automatically and electronically, and that complies with the LVS EN 16931-1:2017 standard and the EU syntax specification referenced in the law.
From From 1 January 2026 The structured invoice requirement also applies to suppliers who submit invoices to budgetary authorities based on transactions concluded before 2025. The postponement of the transition period for these contracts will end. From the same deadline, From 1 January 2026, structured invoice data submitted to budget authorities must also be transmitted to the Latvian Tax Service (Valsts ieņēmumu dienests, or State Revenue Service).
The biggest deadline for B2B entrepreneurs will come later: from From 1 January 2028 The obligation for structured electronic invoicing extends to invoices submitted to another company registered in Latvia that is not a budgetary institution. This is the moment when most Latvian customers can start demanding structured invoices from you, also outside the public sector.
Why is Peppol often the most convenient way, but not the definition?
OpenPeppol explains its In review for 2024, that e-invoicing has two distinct parts: the structured invoice data itself and the mechanism for sending and receiving it. Peppol deals with the second part. It is a four-corner network (4-corner model), where the sender and receiver use service providers, or Access Points, that exchange standardized business documents with each other.
This makes Peppol a convenient choice in practice: if your accounting software is already connected to the access point, you do not need to build a separate channel for each customer. However, using Peppol does not in itself turn an invoice into an e-invoice or automatically fulfill any legal obligations. The structure of the document and the actual requirements of the buyer are still decisive.
What will change in EU VAT rules on July 1, 2030?
The Council adopted March 11, 2025 adopted Directive (EU) 2025/516 amending the VAT Directive. The amended Article 217 replaces the current broad definition of "any electronic format" and will apply From July 1, 2030. From this date, the invoice must be in a structured electronic format that can be processed automatically, at least for certain reporting data.
This does not mean that all EU invoices must go through Peppoli in 2030. The directive gives Member States from April 14, 2025 the right to establish national rules requiring electronic invoicing for domestic transactions. However, this is a Member State choice, not an automatic EU-level Peppol obligation. Which specific channel becomes mandatory is decided by each country in its own law, as Estonia and Latvia have already done.
Five-point check before sending an invoice
- Identify the buyer and country: Check whether it is a public sector institution, a registered e-invoice recipient (in Estonia, in the e-business register), or a regular private company.
- Check the structured data requirement: In Estonia, check the commercial register entry, in Latvia, consider whether the buyer is a budget institution (the requirement is already in effect) or another company (the requirement will be added). From 1 January 2028).
- Confirm format and channel: is an agreed PDF sufficient or is a data file in the EN 16931-1 structure required? If necessary, also check whether Peppol or another agreed interface is suitable for the channel.
- Add buyer references: registry code and other identifiers requested by the buyer. Without these, even a correctly structured invoice will be rejected by automatic processing.
- Keep the original structured record: Keep the file that was actually sent, not its PDF rendering. According to the practice of the Supreme Court The following rule applies: if a party does not acknowledge the existence of a document submitted by the other party in court proceedings, of which only a photocopy has been submitted, the party that submitted the photocopy must prove its existence and must be given the opportunity to present the original document in court.
Once you have gone through these five points, you will have a clear answer to the question of what to send to a specific buyer. You will no longer be dependent on the assumption that „electronic” means the same thing everywhere.
FAQ
Is a PDF invoice the same as an e-invoice?
No. A PDF invoice may be legally valid, but it is not a structured e-invoice because it cannot be automatically processed by a machine. The e-invoice must comply with the EN 16931 standard and be in a machine-readable format.
Will Peppol be mandatory from 2025 or 2026?
No. Peppol is a network for sending invoices, not an obligation. The obligation is determined by the law of each country - in Estonia, from July 1, 2025, a structured invoice must be sent to the recipient of an e-invoice, but the channel can also be other than Peppol.
When will B2B structured invoicing become mandatory in Latvia?
Starting from 1 January 2028, all companies registered in Latvia will be required to provide each other with a structured electronic invoice. Before that, the requirement only applies to budget authorities (B2G).
What will change in the EU on July 1, 2030?
From 1 July 2030, the invoice must be in a structured electronic format, at least for reporting data. This does not mean an automatic Peppol obligation - each Member State decides on the channel itself.