PINT is how Peppol left Europe. Where BIS Billing is bound to EN 16931, PINT is the international model that jurisdictions specialise: Australia and New Zealand, Singapore, Japan and Malaysia each have their own billing specification on the same shared core. InvoiceXML creates and validates PINT documents, and reads the CustomizationID to tell you exactly which jurisdiction you are looking at.
curl -X POST https://api.invoicexml.com/v1/validate/ubl \ -H "Authorization: Bearer YOUR_API_KEY" \ -F "[email protected]"
{
"valid": true,
"data": {
"profile": "pint",
"customizationId": "urn:peppol:pint:billing-1@aunz-1"
}
}
EN 16931 was written for Europe, so OpenPeppol built PINT to carry the rest of the world without fragmenting into incompatible national formats. Every PINT invoice is layered:
The jurisdiction is declared in one place: the CustomizationID (PINT calls it ibt-024), of the form urn:peppol:pint:billing-1@{jurisdiction}-1. Read that field and you know the rule set.
<cbc:CustomizationID> urn:peppol:pint:billing-1@aunz-1 </cbc:CustomizationID> # the jurisdiction suffix decides the rules @aunz-1 Australia & New Zealand @sg-1 Singapore @jp-1 Japan @my-1 Malaysia
Each jurisdiction has its own specification identifier. We recognise all of them on validation today; the jurisdiction-specific rule packs are rolling out behind the same endpoint.
| Jurisdiction | CustomizationID (ibt-024) | Local programme | On InvoiceXML |
|---|---|---|---|
| Australia & New Zealand | urn:peppol:pint:billing-1@aunz-1 | ATO and MBIE, shared A-NZ specification | Detected today, rule pack rolling out |
| Singapore | urn:peppol:pint:billing-1@sg-1 | IMDA InvoiceNow, the GST e-invoicing route | Detected today, rule pack rolling out |
| Japan | urn:peppol:pint:billing-1@jp-1 | Digital Agency, JP PINT | Detected today, rule pack rolling out |
| Malaysia | urn:peppol:pint:billing-1@my-1 | MDEC Peppol, alongside the LHDN MyInvois clearance | Detected today, rule pack rolling out |
| European Union | urn:peppol:pint:billing-1@en16931-2017@eu-3 | EU PINT, the European profile of the model | For EU billing, see Peppol BIS |
PROFILE-DETECTION notice naming what it recognised, never a false rejection.
The same endpoints that power every profile, set to the international model. Each has a free in-browser companion tool, the same auth, and the same jurisdiction detection behind it.
JSON in, validated PINT out, stamped against the international model.
Open toolDrop any PINT file; the jurisdiction is read from the CustomizationID and named in the verdict.
Open toolSame invoice, other syntax, revalidated on the way out.
Open toolA human-readable preview of any PINT file, for approvals and archives.
Open toolTurn a received PINT invoice into clean JSON your ERP can import.
Open toolLet AI agents draft, validate, and fix international invoices over MCP.
Open toolYou should not have to parse a URN to know whether an invoice is Singaporean or Japanese. The verdict reads ibt-024 and reports the recognised jurisdiction in data, alongside any findings in the same shape every profile uses.
pint for the international model.Detect first, route with confidence, never on a guess from the country code.
{
"valid": true,
"data": {
"profile": "pint",
"customizationId": "urn:peppol:pint:billing-1@sg-1"
},
"warnings": [
{
"rule": "PROFILE-DETECTION",
"layer": "cius",
"message": "Recognised PINT Singapore (sg-1).
Validated against the base PINT and
EN 16931 rules; the SG jurisdiction
rule pack is rolling out."
}
]
}
Each jurisdiction runs its own programme and its own timeline. PINT is the common thread that keeps them interoperable.
Malaysia is the one to read carefully: the national mandate runs on LHDN's MyInvois clearance model, while Peppol PINT is the interoperability layer on top. The two are distinct, and we keep them that way. See the Mandate Map for each country's timeline.
PINT specifications move per jurisdiction: A-NZ, Singapore, Japan and Malaysia each publish on their own release calendar. We track every one, vendor the artifacts as they become mandatory, and slot the jurisdiction rule packs in behind the same pint profile. Detection is live now; the per-jurisdiction validation deepens without you changing a line.
Every PINT jurisdiction is recognised on validation today. The A-NZ, Singapore, Japan and Malaysia rule packs land behind the same endpoint as each is finalised.
Validate, convert and embed compliant e-invoices through one API. Start your 30-day free trial. No credit card required.