Peppol vs PINT: The Difference in E-Invoicing Explained

Peppol vs PINT in one sentence

Peppol is the network; PINT and BIS Billing 3.0 are formats that travel on it. That single distinction resolves most of the confusion around Peppol vs PINT. Peppol is the governance framework and four-corner delivery network; Peppol BIS Billing 3.0 and Peppol International (PINT) are two invoice specifications you can send across it.

If the four-corner concept is new, start with how e-invoicing works over Peppol and what is a Peppol Access Point. This article compares the two document specifications.

What Peppol BIS Billing 3.0 is

BIS Billing 3.0 is the long-established Peppol billing profile, aligned to the European standard EN 16931. It is:

A structured UBL 2.1 invoice/credit note.
The default across the EU, and used by Australia and New Zealand as the A-NZ specialisation.
Governed by CEN EN 16931 plus Peppol BIS Schematron rules.

It was designed first and foremost for the European single market. For the finance-team rollout view, see the Peppol onboarding checklist for finance teams.

What PINT is

PINT (Peppol International) is a newer, globally oriented billing model. Its design goal: provide a common core that any jurisdiction can extend, so countries adopting Peppol outside the original European scope don't each invent an incompatible format. PINT ships as a base plus country specialisations, for example:

PINT OM — Oman (urn:peppol:pint:billing-1@om-1).
PINT A-NZ, PINT MY, PINT JP and others.

Each specialisation adds jurisdiction-specific rules — tax handling, identifiers, mandatory fields — on top of the shared PINT base. Oman's implementation is dissected in the PINT OM CustomizationID reference.

The key differences

Dimension	Peppol BIS Billing 3.0	Peppol PINT
Scope	EU baseline; A-NZ specialisation	Global base for non-EU jurisdictions
Aligned to	EN 16931	UBL core + PINT base + local rules
Example users	EU, Australia, New Zealand	Oman, Malaysia, Japan, others
Identifier	BIS Billing CustomizationID	e.g. `urn:peppol:pint:billing-1@om-1`
Validation	CEN EN 16931 + Peppol BIS Schematron	PINT base + jurisdiction Schematron
Transport	AS4 over Peppol	AS4 over Peppol (identical)

The row that matters most operationally is the last one: transport is identical. The profile only changes the document and its rules, never how it moves.

When each applies

You do not choose a profile by preference — you use the one the receiving jurisdiction mandates:

Selling into the EU, Australia or New Zealand → BIS Billing 3.0 (A-NZ specialisation for the Tasman). See Peppol e-invoicing in Australia.
Selling into Oman → PINT OM, plus the Tax Data Document for CTC. See the Oman Fawtara 5-corner model.
Other PINT jurisdictions → their respective PINT specialisation.

A well-built Access Point selects the profile automatically from the receiver and document type — the sending business shouldn't have to hard-code it.

How CustomizationID tells them apart

Every Peppol invoice declares a CustomizationID (and ProfileID). That value is how a validator knows which rule set to apply:

A BIS Billing 3.0 document carries the BIS Billing CustomizationID → routed to CEN EN 16931 + BIS Schematron.
A PINT OM document carries urn:peppol:pint:billing-1@om-1 → routed to the PINT OM Schematron, and it skips the European baseline.

Getting this value wrong is a classic failure mode — the document either fails validation or gets checked against the wrong rules. See invoice validation errors you can prevent.

Why it matters for multi-country rollouts

If you bill across several countries, the temptation is to standardise on one format. You can't — a German buyer and an Omani buyer need different profiles by law. The right architecture is a single integration to an Access Point that:

Emits the correct profile per destination automatically.
Runs the matching validation before transmission.
Adds any CTC step (like Oman's TDD) where required.

That is exactly the model behind a single global integration — see the multi-country e-invoicing API.

How GoRoute helps

GoRoute (POP000991) is a certified Peppol Access Point and SMP that supports both BIS Billing 3.0 and PINT — compiling official Schematrons per jurisdiction and selecting the right profile per receiver — across 50+ countries from one REST API. Book a demo or read how to choose a Peppol Access Point.

Sources: Peppol BIS Billing 3.0; OpenPeppol PINT; EN 16931.

Frequently asked questions

What is the difference between Peppol and PINT?

Peppol is the overall network and governance framework for exchanging e-invoices. PINT (Peppol International) is a billing specification within Peppol designed as a common base for country-specific invoice profiles outside the original European scope. In short, Peppol is the network; BIS Billing 3.0 and PINT are formats that travel on it.

What is Peppol PINT?

PINT — the Peppol International model — is a UBL-based billing specification that provides a shared core plus jurisdiction-specific extensions (for example PINT OM for Oman, PINT A-NZ, PINT MY). It lets each country add its own rules while keeping a common, interoperable base.

How is PINT different from Peppol BIS Billing 3.0?

BIS Billing 3.0 is the EN 16931-aligned European profile used across the EU and by A-NZ as a specialisation. PINT is a newer, globally oriented base model for countries beyond that original scope. Both are UBL and both travel over Peppol, but they use different CustomizationIDs and different Schematron rule sets.

When should I use PINT instead of BIS Billing 3.0?

Use the profile the receiving jurisdiction mandates. Oman, for example, requires PINT OM; the EU and Australia/New Zealand use BIS Billing 3.0 (A-NZ as a specialisation). Your Access Point should select the profile automatically based on the receiver and document type.

How does CustomizationID distinguish Peppol and PINT?

The CustomizationID (and ProfileID) in the invoice declares which specification and rules apply. BIS Billing 3.0 uses its own CustomizationID; PINT profiles use identifiers such as urn:peppol:pint:billing-1@om-1. Validators route the document to the correct Schematron based on that value.

Is PINT replacing Peppol BIS Billing 3.0?

No. PINT is not a wholesale replacement. BIS Billing 3.0 remains the European and A-NZ baseline, while PINT provides the base for jurisdictions adopting Peppol beyond that original scope. The two coexist, and a good Access Point supports both.

Does the choice of profile change how the invoice is transmitted?

No. Transmission is identical — AS4 over the Peppol four-corner network with SMP/SML discovery. The profile only affects the document's structure, CustomizationID and validation rules, not the transport.