Interoperability Standard
What Is Peppol PINT?
The international invoice specification that enables structured, validated invoice exchange across the Peppol network worldwide. PINT extends BIS Billing 3.0 with a formal framework for jurisdiction-specific rules, making Peppol a truly global e-invoicing infrastructure.
What is Peppol PINT?
Peppol PINT (Peppol International Invoice) is a specification that defines how invoices must be structured and validated for exchange on the Peppol network across jurisdictions worldwide. PINT extends the original European-focused Peppol BIS Billing 3.0 to accommodate tax rules, business practices, and regulatory requirements from non-European countries, enabling a single global invoice specification with jurisdiction-specific extensions.
How Peppol PINT Works
PINT builds on established standards and adds a layered validation architecture that separates universal rules from jurisdiction-specific requirements.
Built on UBL 2.1
PINT uses Universal Business Language (UBL) 2.1 as its underlying data model. UBL defines the XML schema for business documents, including invoices and credit notes. Every PINT invoice is a valid UBL 2.1 document, which means existing UBL-capable systems can process PINT invoices without requiring a fundamentally different parser.
Extends BIS Billing 3.0
BIS Billing 3.0 defined the European rules for Peppol invoicing. PINT takes the BIS Billing core and adds a formal extension framework, allowing non-European countries to participate in the Peppol network while maintaining interoperability with European trading partners. The core business terms from BIS Billing carry forward into PINT.
Country-Specific Extensions (CIUS)
Each country that joins Peppol can define a Core Invoice Usage Specification (CIUS) that adds mandatory fields, tax-specific rules, and business terms required by its domestic regulations. These extensions layer on top of the PINT core without modifying it, so a PINT invoice with a Japan extension is still a valid PINT invoice at its core.
Layered Validation Rules
Validation in PINT occurs in layers. First, the invoice is validated against the UBL 2.1 schema. Then, the PINT core business rules are applied. Finally, the country-specific extension rules are checked. An invoice must pass all three layers to be considered PINT-compliant for a given jurisdiction.
PINT vs BIS Billing 3.0
BIS Billing 3.0 served as the European Peppol invoicing standard. PINT is its global successor, designed to support any country that joins the Peppol network.
Scope
BIS Billing 3.0
Designed for European invoicing within the Peppol network. Business rules and validation reflect EU VAT requirements and European business practices.
PINT
Designed for global invoicing across the Peppol network. Accommodates tax regimes, business practices, and regulatory requirements from any participating country.
Extension Mechanism
BIS Billing 3.0
Limited accommodation for non-European requirements. Country-specific rules were handled through informal adaptations or workarounds.
PINT
Formal extension framework (CIUS) that allows each country to define additional mandatory fields and validation rules without modifying the core specification.
Tax Regime Support
BIS Billing 3.0
Primarily supports EU VAT structures, including standard rates, reduced rates, zero-rating, and reverse charge mechanisms.
PINT
Supports EU VAT, GST, consumption tax, and other tax models through the extension framework. Each country extension defines how its tax regime maps to PINT fields.
Migration Path
BIS Billing 3.0
Current standard for European Peppol invoicing. Will be superseded by PINT as OpenPeppol completes the transition.
PINT
Backward-compatible with BIS Billing core elements. Designed so that existing BIS Billing implementations can transition without rebuilding from scratch.
PINT Architecture
PINT uses a two-layer architecture: a universal core specification and jurisdiction-specific extensions. This separation is what enables global interoperability without forcing every country into a single set of rules.
Core Specification
The PINT core defines the universal business terms, data types, and validation rules that apply to every PINT invoice regardless of jurisdiction. This includes seller and buyer identification, line item structure, tax summary format, document totals, and payment information. The core is based on the European Norm (EN 16931) semantic model and is expressed in UBL 2.1 syntax.
Country Extensions
Extensions add jurisdiction-specific requirements on top of the core. An extension can make optional core fields mandatory, add new validation rules, define country-specific code lists, and require additional business terms. Critically, extensions cannot remove or contradict core rules. This constraint is what preserves interoperability: any PINT-compliant system can process the core of any PINT invoice, even if it does not support a specific country extension.
Country Extensions
Each country that joins the Peppol network can define an extension that adds mandatory fields, tax-specific rules, and business terms required by domestic regulations. The core specification remains shared and unchanged.
Japan (PINT JP)
The Japan extension adds fields for the Qualified Invoice System (QIS), including the registered invoice issuer number, consumption tax calculations at the line level, and specific formatting requirements mandated by the National Tax Agency (NTA). Japan adopted Peppol as its national e-invoicing infrastructure, making PINT JP the standard for digital invoicing.
Singapore (PINT SG)
The Singapore extension supports InvoiceNow, the national e-invoicing framework operated by IMDA. PINT SG includes GST-specific fields, Unique Entity Number (UEN) validation requirements, and formatting rules aligned with IRAS (Inland Revenue Authority of Singapore) compliance expectations.
Australia / New Zealand (PINT A-NZ)
The A-NZ extension covers both Australia and New Zealand under a shared specification. It includes ABN (Australian Business Number) and NZBN (New Zealand Business Number) validation, GST handling specific to each country, and fields required by the ATO (Australian Taxation Office) and Inland Revenue New Zealand.
Malaysia (PINT MY)
Malaysia is adopting Peppol as part of its national e-invoicing initiative. The PINT MY extension addresses SST (Sales and Service Tax) requirements, TIN (Tax Identification Number) formatting, and compliance fields required by the Inland Revenue Board of Malaysia (LHDN).
PINT and the Four-Corner Model
Peppol uses a four-corner model for document exchange. PINT defines the content and validation rules for the invoice that travels through this network.
Sender creates PINT invoice
The seller or their system generates a UBL 2.1 invoice that conforms to the PINT core specification and the relevant country extension. All mandatory fields are populated, tax calculations are completed, and the document is ready for transmission.
Sender Access Point validates and transmits
The sender's access point (Corner 2) performs PINT validation, checking schema conformance, core business rules, and applicable extension rules. If the invoice passes validation, the access point transmits it to the receiver's access point via the Peppol network.
Receiver Access Point validates and delivers
The receiver's access point (Corner 3) may perform its own validation before delivering the invoice to the buyer. This second validation layer provides additional assurance that the document conforms to the expected PINT specification and country extension.
Receiver processes PINT invoice
The buyer's system (Corner 4) receives a structured, validated invoice that conforms to known rules. Because PINT standardizes the format and business terms, the receiver can automate processing without manual interpretation of the invoice structure.
Where PINT Is Adopted
PINT adoption is expanding as more countries join the Peppol network and existing Peppol members transition from BIS Billing 3.0.
Japan
Japan adopted Peppol as its national e-invoicing standard in connection with the Qualified Invoice System (QIS). PINT JP is the specification used for digital invoice exchange between Japanese businesses and their trading partners.
Singapore
Singapore's InvoiceNow initiative uses Peppol as its e-invoicing infrastructure. PINT SG aligns with IRAS requirements and supports GST-compliant invoice exchange through the nationwide Peppol network.
Australia and New Zealand
Both countries share the PINT A-NZ extension. The Australian Taxation Office (ATO) and New Zealand Inland Revenue support Peppol e-invoicing, and adoption is growing across government agencies and the private sector.
Malaysia
Malaysia is adopting Peppol as part of its broader e-invoicing strategy managed by LHDN (Inland Revenue Board). PINT MY is being developed to accommodate SST requirements and local business practices.
European Union
EU member states that already use Peppol for cross-border invoicing are transitioning from BIS Billing 3.0 to PINT. The transition aligns with the broader ViDA (VAT in the Digital Age) initiative and moves toward a unified global specification.
Growing Network
OpenPeppol is actively onboarding additional countries and regions. As each new jurisdiction joins, it defines a country extension that layers onto the PINT core, expanding the global reach of the specification without fragmenting it.
Who Uses PINT
Multinational Corporations
Businesses operating across multiple Peppol-connected countries benefit from PINT's unified core specification. Instead of implementing a different invoice format for each country, multinationals can use PINT core with the relevant country extensions, reducing integration complexity and maintenance overhead.
Access Point Providers
Peppol certified access points must support PINT to transmit and validate invoices on the network. Access point providers implement the core specification and add country extensions based on the jurisdictions they serve, ensuring their customers can exchange invoices with any Peppol participant globally.
ERP and Accounting Software Vendors
Software vendors that support Peppol invoicing are building PINT into their platforms. This includes generating PINT-compliant UBL documents, applying the correct country extension rules, and validating invoices before transmission. PINT support is increasingly a competitive requirement for vendors expanding beyond European markets.
Governments Joining Peppol
Governments adopting Peppol for public procurement or national e-invoicing define their country extension and require suppliers to submit PINT-compliant invoices. This applies to both government-to-business (G2B) procurement and, in some jurisdictions, business-to-business (B2B) invoicing broadly.
Common Misconceptions
Myth: PINT replaces BIS Billing 3.0
Reality: PINT is the evolution of BIS Billing 3.0, not a replacement that discards the original. The core business terms and structure from BIS Billing carry forward into PINT. Existing BIS Billing implementations form the foundation for PINT migration. OpenPeppol is managing a gradual transition, not an abrupt replacement.
Myth: PINT requires a separate implementation per country
Reality: The PINT core specification is shared across all jurisdictions. Country extensions add only the jurisdiction-specific rules on top of this shared core. A system that supports PINT core needs only to add the relevant country extension rules, not rebuild from scratch for each new country.
Myth: PINT is only for Asia-Pacific countries
Reality: While PINT was initially driven by the need to onboard non-European countries such as Japan, Singapore, and Australia, it is designed to be the global standard for all Peppol invoicing. European countries are transitioning from BIS Billing to PINT as the unified specification. PINT is jurisdiction-agnostic at its core.
Myth: PINT changes the Peppol network infrastructure
Reality: PINT is a document specification, not a network change. The Peppol network infrastructure (access points, SMP, SML, the four-corner model) remains the same. PINT defines what the invoice looks like and how it is validated. How the invoice is transported across the network is unchanged.
How AutoFact AI Supports Peppol PINT
AutoFact AI is designed to support businesses and their advisors in working with PINT-compliant invoices across jurisdictions.
PINT-Aware Validation
Validates invoices against the PINT core specification and applicable country extensions, checking schema conformance, business rules, and tax-specific requirements in a single pass. Validation results identify which layer (core or extension) generated each finding.
Country Extension Detection
Automatically identifies which country extension applies to an incoming PINT invoice based on document metadata, participant identifiers, and tax-specific fields. This allows the system to apply the correct validation rules without manual configuration for each trading partner.
Jurisdiction Mapping
Maps invoice fields to the requirements of the relevant jurisdiction, identifying which fields are mandatory under the applicable country extension, which tax codes are valid, and which formatting rules apply. This supports both invoice creation and incoming invoice processing.
Multi-Specification Support
Supports PINT alongside other invoice specifications including UBL, Factur-X, and legacy BIS Billing 3.0. This allows businesses transitioning from BIS Billing to PINT to validate both formats during the migration period without switching between separate tools.
Regulatory Authority Mapping
Peppol PINT requirements are shaped by OpenPeppol governance and the national authorities of each adopting country.
OpenPeppol
International Association
- What they govern: PINT specification governance and versioning
- What AutoFact AI maps to: PINT-compliant document validation
- What risk this removes: Non-conformance with current PINT specification
National Tax Agency (NTA)
Japan
- What they regulate: Japan e-invoicing via Peppol PINT JP
- What AutoFact AI maps to: Japan PINT extension field mapping
- What risk this removes: Missing Japan-specific tax fields
Inland Revenue Authority of Singapore (IRAS)
Singapore
- What they regulate: Singapore InvoiceNow (Peppol PINT SG)
- What AutoFact AI maps to: Singapore PINT extension compliance
- What risk this removes: Invalid GST treatment codes
Australian Taxation Office (ATO)
Australia / New Zealand
- What they regulate: Australia/NZ Peppol PINT A-NZ
- What AutoFact AI maps to: A-NZ extension field validation
- What risk this removes: Non-compliant ABN/NZBN formatting
AutoFact AI is not certified by, affiliated with, or endorsed by any regulatory authority listed above. References describe technical alignment with published regulatory requirements only.
Frequently Asked Questions
PEPPOL PINT & International E-Invoicing Resources
Validate PINT Invoices Across Every Jurisdiction
AutoFact AI supports PINT core validation, country extension detection, and jurisdiction-specific field mapping. Start your free trial and ensure every invoice aligns with the correct PINT specification before it reaches the network.
14-day free trial · No credit card required · Setup in minutes