Five-corner model: five roles, one invoice

In the five-corner model the invoice does not travel directly from supplier to buyer: it passes through each side's accredited access point and the Peppol network, with validation at the edges.

Try it on your own invoice

5 documents free. PDF, photo or XML — data out as CSV, Excel or JSON.

The five corners

Corner 1: the supplier, who issues the invoice from their system.

Corner 2: the supplier's access point (ASP), which validates and transmits.

Corner 3: the Peppol network, which routes by Peppol ID.

Corner 4: the buyer's access point, which receives and validates.

Corner 5: the buyer, who books the invoice.

Where errors are caught

At corners 2 and 4: format validation happens before and after transport, so a malformed invoice is stopped at the edge rather than in someone's inbox.

That is the practical gain: fewer documents bouncing back days later.

What it means for your team

You do not build the network: you connect to an access point.

You do keep responsibility for content — validation checks structure, not whether the amount is right.

Where the data work remains

Received invoices still need to be read into the ledger: TRN, number, VAT per category, totals.

The model moves documents; it does not do your books.

Frequently asked

Do I need a Peppol ID?

Your access point typically issues and manages the identifier you are addressed by.

Is the five-corner model mandatory?

It is how the UAE framework is built on Peppol; the obligation is to exchange invoices in the required format.