The Peppol five-corner model

The five-corner model is what the Peppol four-corner architecture becomes once the tax authority joins the picture. It is the European answer to continuous transaction controls (CTC) and the basis of the next wave of e-invoicing mandates. Below is an original SVG diagram, free to embed.

By Peppol Validator · Last updated

Peppol five-corner modelDiagram showing the Peppol five-corner model. Corner 1 (Seller) sends an invoice to Corner 2 (Sender Access Point), which transmits it over AS4 to Corner 3 (Receiver Access Point), which delivers it to Corner 4 (Buyer). At the same time, the Access Points report a copy or summary of the invoice to Corner 5, the Tax Authority, for near real-time e-reporting (used by Belgium from 2028 and by the EU VAT in the Digital Age reform). Source: https://peppolvalidator.com/diagrams/five-corner-modelPeppol five-corner modelPeppol Validator (peppolvalidator.com)© Peppol Validator. Free to embed with attribution link to peppolvalidator.com.https://peppolvalidator.com/diagrams/five-corner-modelPeppol networkCORNER 5Tax Authoritynear real-time e-reportingCORNER 1SellerERP / accounting systemCORNER 4BuyerERP / accounting systemCORNER 2Sender Access Pointvalidates, signs, reportsCORNER 3Receiver Access Pointdecrypts, validates, reportsUBL invoiceAS4 over HTTPSsigned & encryptedUBL invoicereportreportSML & SMP discoveryfinds the recipient endpointand certificate© peppolvalidator.com
The Peppol five-corner model. The four trading corners exchange invoices through Access Points; both Access Points also report to the tax authority (corner 5).

From four corners to five

The Peppol four-corner model gives a buyer and a seller a clean way to exchange a structured invoice without bilateral integration. It works because every Access Point on the network speaks the same standard format (Peppol BIS Billing 3.0 on top of UBL 2.1) and shares the same discovery layer (SML and SMP). When a tax authority is added, two things change.

A fifth corner appears in the architecture: the national tax administration. In Belgium this is FPS Finance; in France a central public portal sits behind the network of certified PDPs; in other EU member states, ViDA-aligned authorities will play a similar role.

The Access Points gain a reporting responsibility. As an invoice flows from corner 2 to corner 3, both Access Points also send a copy or a structured summary of the invoice to the tax authority. The reporting message is separate from the trading message: the buyer still receives the original invoice the way they always did, and the tax administration receives its own near real-time view in parallel.

The trading partners themselves do not need to integrate with the tax authority directly. From the seller's and buyer's point of view, the e-invoicing experience is unchanged. The new responsibility lives with the certified Access Points.

Why governments are moving to the five-corner model

Tax authorities want timely, structured visibility into B2B transactions to fight VAT fraud, accelerate refunds and reduce the administrative burden on businesses (in theory, by replacing periodic VAT returns with what they call "pre-filled" reports). The classic answer in countries like Italy or Brazil has been to route invoices through a central government portal: every invoice passes through a state-run system before reaching the buyer.

The five-corner model is the European alternative. Instead of building a central portal and forcing every business to integrate with it, it reuses the Peppol delivery infrastructure that is already in place and adds a reporting flow on top. Trading partners stay on the network they already use; the tax authority becomes one more endpoint that the Access Points talk to.

This is the architecture that Belgium has chosen for its 2028 e-reporting layer. France has chosen a closely related architecture through PDPs and a central portal. Both approaches preserve the four-corner core. The EU's VAT in the Digital Age (ViDA) reform will require near real-time digital reporting for cross-border B2B transactions across all member states by 2030, and is broadly compatible with the five-corner approach.

What this means for trading partners

In most cases the migration from four corners to five is transparent for the seller and the buyer. The Access Point handles the reporting flow; the seller's ERP keeps producing invoices the same way; the buyer's system keeps receiving them. What does change in practice is that data quality matters more. If a business term is missing or wrong, the tax authority sees it immediately, not three months later when the periodic return is filed.

That makes pre-flight validation essential. Running every outgoing invoice through a Peppol BIS 3.0 validator before it reaches the network catches the schematron failures that would otherwise show up as a rejection or a tax-side correction request. The Peppol Validator on this site does exactly that, for free, with no signup.

Embed this diagram

Copy the snippet below into any HTML page, blog post or wiki. The image is served as an SVG so it scales to any size and stays sharp on retina screens. Please keep the attribution line below the image.

<a href="https://peppolvalidator.com/diagrams/five-corner-model">
  <img src="https://peppolvalidator.com/diagrams/five-corner-model/svg"
       alt="Peppol five-corner model diagram"
       width="800" height="540" />
</a>
<p><small>Diagram by <a href="https://peppolvalidator.com">Peppol Validator</a></small></p>

The SVG file also carries a Dublin Core copyright block (RDF metadata), so the attribution travels with the image when it is downloaded or screenshotted.

Related references

Validate your Peppol invoices

Drop a UBL XML invoice and check it against every EN 16931 and Peppol BIS Billing 3.0 rule. Free, instant, no signup.

Frequently asked questions

What is the Peppol five-corner model?

An extension of the four-corner model. The seller (corner 1), sender Access Point (corner 2), receiver Access Point (corner 3) and buyer (corner 4) still exchange invoices the same way. A fifth corner is added: the national tax authority. As an invoice flows through the network, a copy or a summary is also reported to the tax administration in (near) real time.

Which countries use the five-corner model?

Belgium will introduce a Peppol five-corner model on 1 January 2028 for tax e-reporting via FPS Finance. France is implementing a similar architecture through Plateformes de Dématérialisation Partenaires (PDPs) connected to a central public portal. The EU's VAT in the Digital Age (ViDA) reform will require near real-time digital reporting for cross-border B2B transactions across all member states by 2030. Italy already runs a centralised version (Sistema di Interscambio, SDI) since 2019, although SDI is not strictly Peppol.

How is the five-corner model different from continuous transaction controls?

Continuous transaction controls (CTC) is the umbrella term for any system that requires invoices or invoice data to pass through (or be reported to) a tax authority in or near real time. The Peppol five-corner model is one specific way to implement CTC: rather than rerouting invoices through a central government portal, the existing four-corner Peppol delivery is preserved and a reporting copy is sent to the tax authority in parallel. This keeps trading partners on the same network they already use.

Does the buyer or seller change anything to support the five-corner model?

Not in most cases. The reporting to the tax authority is handled by the Access Points (corners 2 and 3), not by the trading partners themselves. As long as your Access Point is certified for the relevant national e-reporting profile, your existing Peppol setup keeps working. You may need to add a few extra business terms to your invoice (for example a tax category code) so the report is complete.

Can I embed this diagram on my own site?

Yes. The diagram is an original SVG, free to embed with an attribution link back to peppolvalidator.com. The embed snippet on this page gives you the exact HTML to paste. The SVG file also carries a Dublin Core copyright block so the attribution stays with the image when downloaded or screenshotted.