Clearvo Now Covers 31 E-invoicing Countries — One API, No New Integration Work

Clearvo has expanded from 14 to 31 e-invoicing countries. The addition spans 11 European Peppol markets, 4 APAC countries on the PINT profile, Switzerland, and the UAE — which goes live with its Peppol B2G pilot in July 2026.

For existing integrations: nothing changes. Same endpoint, same request schema. Change the country field and you're done.

What's New: 17 Countries in One Release

The new markets split cleanly across two groups.

European Peppol BIS 3.0: Ireland (IE), Norway (NO), Sweden (SE), Denmark (DK), Finland (FI), Lithuania (LT), Latvia (LV), Estonia (EE), Luxembourg (LU), Slovenia (SI), Iceland (IS), and Switzerland (CH).

APAC + Middle East: Australia (AU), New Zealand (NZ), Japan (JP), Singapore (SG), and the United Arab Emirates (AE).

Every country listed here has tested XML generation against the relevant specification. That's not a small thing — and it's worth unpacking why.

"Supported" Is Not the Same as "Tested"

A common pattern in the e-invoicing market is for vendors to claim coverage of a country based on advisory knowledge of its format. They know what schema version applies, they've read the documentation, they can generate an invoice if you ask them to. But they haven't run their output through the country's official validation toolchain or submitted a test document to the network.

Clearvo draws a hard line here. A country isn't in the coverage list until its XML generation has been validated against the authority's published schematron rules and schema files. For the Peppol countries, that means running output through the OpenPeppol conformance test suite. For countries with their own submission gateway, it means a round-trip test against the sandbox or testbed environment.

The 17 countries in this release all passed that bar before launch.

PINT: Peppol's Global Extension Model

The APAC additions — Australia, New Zealand, Japan, and Singapore — use the Peppol International (PINT) profile rather than BIS Billing 3.0 directly. PINT is OpenPeppol's mechanism for extending BIS 3.0 to non-EU jurisdictions. The envelope format, AS4 transport, and participant lookup via SMP all work identically to their European counterparts.

What changes is the CIUS — the Country Implementation Specification — which defines country-specific rules layered on top of the shared core. Australia and NZ use the A-NZ PINT CIUS. Japan uses JP PINT. Singapore uses SG PINT.

From an API perspective, Clearvo handles the CIUS selection automatically based on the country field. You pass in the same structured JSON invoice, and the pipeline selects the correct profile, validates against the right schematron, and routes over AS4 to the appropriate access point.

Clearvo's Peppol AP identifier is PIE001162, registered on the Peppol production network and visible via SMP lookup.

UAE: July 2026 B2G Pilot

The UAE deserves a separate note. The country field is available now, XML generation is tested, but the UAE Peppol B2G pilot goes live in July 2026. Invoices to UAE government buyers will be routable through Clearvo from that date. For existing mandated B2B flows, the UAE operates its own framework — check your specific buyer requirements.

The Integration Picture

The expansion reinforces the core proposition of building on a single API rather than patching together country-specific solutions.

A typical country integration, done directly, involves: selecting the right schema version, implementing the submission client (often with certificate-based auth or OAuth flows specific to that country's authority), building a status poller for async acknowledgements, mapping authority error codes back to something your application can handle, and maintaining all of this across schema updates that governments push out annually.

Clearvo absorbs that surface area. The API contract is stable across all 31 countries. A request that works for Belgium works for Singapore — the payload structure, authentication method, and response format are the same. You're not learning a new protocol per country; you're consuming one.

Request Shape

For any new country, the integration looks like this:

{
  "country": "NO",
  "supplier": { ... },
  "customer": { ... },
  "lines": [ ... ],
  "totals": { ... }
}

Switch "NO" to "SG" or "JP" and the pipeline selects the correct Peppol PINT CIUS, validates the document, and routes it. No schema changes on your side. No new transport clients. No new error code mappings.

What's Next

The 31-country roster covers all currently mandated or piloting Peppol markets Clearvo has prioritised. The compliance test pipeline — the mechanism that validates XML generation before a country goes live — runs continuously against published specification updates, so schema changes from authorities propagate without requiring new integration work from customers.

Coverage details and mandate timelines for each country are documented in the Clearvo country reference.

Clearvo is a Peppol-registered Access Point (AP identifier: PIE001162) providing a unified API for B2B and B2G e-invoicing across 31 countries.