Peppol International Invoice Model
A Peppol international invoice model with jurisdiction-specific specialisations for markets such as Australia and New Zealand, Japan, Malaysia, Singapore, the UAE and Oman.
Current version and implementation status
How to recognize the profile
Do not rely on the file extension alone. Inspect the root namespace, customization/profile identifiers, version values and authority-specific envelope.
- PINT profile identifiers
- Jurisdiction-specific CustomizationID
- Peppol endpoint identifiers
Production validation stack
- 1UBL schema
Confirm that the document is well formed and structurally compatible with the intended PINT syntax.
- 2PINT core rules
Apply semantic and business-rule checks rather than accepting a file merely because it parses.
- 3Jurisdiction rules
Validate currencies, countries, tax categories, units, payment means and other controlled values against the correct release.
- 4Peppol transport capability
Apply the national, network or authority restrictions that narrow the base syntax.
Common errors and corrective action
Locate the relevant field and rule, correct the source mapping, rerun every validation layer, then preserve the final response.
Locate the relevant field and rule, correct the source mapping, rerun every validation layer, then preserve the final response.
Locate the relevant field and rule, correct the source mapping, rerun every validation layer, then preserve the final response.
Locate the relevant field and rule, correct the source mapping, rerun every validation layer, then preserve the final response.
Countries using or referencing this profile
Questions people ask
What is PINT?
A Peppol international invoice model with jurisdiction-specific specialisations for markets such as Australia and New Zealand, Japan, Malaysia, Singapore, the UAE and Oman.
How is PINT validated?
A production check normally applies UBL schema, PINT core rules, Jurisdiction rules, Peppol transport capability. Local browser preflight cannot replace the official validation artefacts or authority outcome.
Which version should I use?
The current research note is: Jurisdiction releases have separate release cycles. Confirm release notes at the official source before production deployment.
Inspect and prepare PINT files
Technical invoice preflight
Check parseability, core fields, identifiers and arithmetic before submission.
E-invoice schema and version finder
Find the country system, structured format family, likely active version markers and official technical source.
Peppol participant directory lookup
Validate participant syntax and continue to the official Peppol Directory to check registration and document capabilities.
Invoice profile ID finder
Locate CustomizationID, ProfileID and guideline identifiers and connect them with likely format profiles.