Multi-Country E-Invoicing API: Buy or Build?

A multi-country e-invoicing API abstracts transport and format conversion, but not legal meaning: each country decides which fields are reportable, how an issued invoice is corrected or cancelled, and what happens to its number. Buy when your roadmap includes countries that put a licensed intermediary in the invoice path or keep moving their mandate dates. Build when you serve few countries, already run a tax engine and need control over invoice states. For most SaaS products the realistic answer is a hybrid, and the deciding variable is the number of intermediary walls on the roadmap, not the number of countries.

Last reviewed: 23 October 2026. What changed this year: Poland’s KSeF became mandatory on 1 February 2026 for taxpayers with 2024 turnover above PLN 200 million and on 1 April 2026 for other VAT-registered businesses, with micro-entrepreneurs following on 1 January 2027. Greece started its first B2B group on 2 March 2026, a month later than first set. France made e-invoice reception mandatory for all VAT-registered businesses on 1 September 2026, and issuance and transaction-data reporting mandatory for large and mid-size companies the same day. On 30 September, a day before its start date, Greece postponed the second B2B group again; the new start is reported as 2 November 2026.

What “one API” really abstracts: transport and format, not legal meaning

A global invoicing compliance API can hide three things: how a document travels, which syntax it is written in, and how you authenticate to each network. It cannot hide what the law says the document means.

Peppol is the clearest case of transport standardisation. It is not a platform for invoice exchange but a set of technical specifications. In its four-corner model, the sender’s and the receiver’s certified service providers (corners two and three) exchange documents in the Peppol BIS format, and a central registry tells the sending provider where to deliver.

On the format side, EN 16931-1:2017 defines the semantic model of a core invoice, and CEN/TS 16931-2 lists UBL and UN/CEFACT CII as the two syntaxes that satisfy it, as the European Commission’s guide to the standard explains. Directive 2014/55/EU obliges public contracting authorities to receive invoices in those syntaxes. Whatever a country needs beyond the core enters through a Core Invoice Usage Specification (CIUS), which stays compliant with the standard, or through an extension, which does not.

That is the part a provider can honestly hide: you send one canonical invoice and it produces the Peppol envelope or the national XML. What the standards leave out, namely which fields an authority wants, when it wants them and what a failure does to the invoice, is where country logic comes back into your code.

What doesn’t abstract away: four places your code still carries country logic

Each of the following survives behind a unified endpoint, because each is a fact about the law rather than about the transport.

Reportable fields differ by country and by party

Under Council Directive (EU) 2025/516 (ViDA), from 1 July 2030 the replaced Article 264 of the VAT Directive sets what each side of an intra-EU transaction reports, and the two sides report different things. A supplier of goods under Article 138(1), or of a reverse-charged supply, transmits ten of the data points in Article 226: points 1 to 4, 6, 7, 8, 11, 16 and 17, plus point 11a where relevant. The customer reporting an intra-Community acquisition transmits twelve: points 1 to 4, 6 to 11, 16 and 17. The clocks differ too. Supplier data goes out when the invoice is issued or should have been issued; customer data goes out within five days of receiving the invoice.

National regimes add their own layers. Greece’s myDATA record carries income and expense classification data on top of the invoice, and invoices to public bodies add contract and contracting-authority details under Joint Ministerial Decision 63446/2-6-2021. One canonical invoice model needs country-specific and party-specific slots for the same reason the standard has CIUS and extensions.

Correction and cancellation follow different state machines

India’s e-invoice system lets you cancel an invoice on the Invoice Registration Portal (IRP) only within 24 hours, and only as a whole: partial cancellation is not possible. After that window the fix happens outside the IRP, through a credit note or a correction in the GST return. Italy’s Sistema di Interscambio (SdI) works differently. A file that fails its checks is discarded (scarto) and the invoice counts as never issued, so the correction is a resend rather than a cancellation. A single “cancel invoice” endpoint therefore has to mean a portal call in one country, a credit note in another and a resend in a third, and your product has to tell the user which of the three just happened.

Number reuse points in opposite directions

The same withdrawal can burn an invoice number in one country and leave it free in another. In India, once an invoice has received an IRN and that IRN is cancelled, the document number cannot produce another IRN; the replacement needs a new number. A submission rejected at validation never receives an IRN, so nothing has been cancelled and the number is untouched. In Italy a discarded invoice is treated as not issued. Circular 13/E of 2 July 2018 from the Agenzia delle Entrate says the corrected invoice should be re-sent within five days of the discard notice and that it is preferable to keep the original date and number. Its fallbacks are a new number linked to the discarded document, or a separate numbering section such as “1/R”. Gapless-sequence logic that is correct in one country breaks in the other.

The certified-provider wall: in some countries “build” still means “integrate a provider”

Greece does not require a provider as such. A taxpayer can issue through a provider certified by the tax authority (AADE) or through AADE’s free applications, timologio and myDATAapp, and ERP software is allowed only in parallel during the transition, as AADE’s 17 February 2026 announcement sets out for the first group. That group’s transition ran from 2 March to 3 May 2026. For the second group, AADE’s decision A.1197/2026 of 30 September 2026 postpones the timetable; reports of its text put parallel ERP issuance through 31 January 2027, with issuance and myDATA transmission going only through a provider or the AADE apps from 1 February 2027. AADE’s FAQ is reported to say that business software on its own is not an accepted issuing channel, so a SaaS product that issues invoices on behalf of customers needs a provider underneath it, either through its own certification or a partner’s. Invoices to public bodies already have to travel through a certified service provider under Law 4601/2019.

France puts the same wall in a different place. Under article 289 bis of the Code général des impôts, issuing, transmitting and receiving in-scope e-invoices runs through an accredited platform, a plateforme agréée (PA), and a central directory lets an invoice be addressed to the recipient’s PA. Large and mid-size companies issue and report from 1 September 2026; smaller companies follow on 1 September 2027. The tax administration’s practical guide of July 2026 adds a nuance that matters for risk: a genuine invoice that arrives by email, PDF or paper should not be rejected on that ground alone, and VAT deduction is not automatically lost. The same guide states that this tolerance does not postpone or suspend the obligation.

Poland shows the other pattern. The integration target is the Ministry of Finance’s own KSeF API, and the Ministry’s KSeF 2.0 manual lists tokens, KSeF certificates and qualified signatures or seals as authentication methods; in August 2026 the Ministry removed the end date for tokens. So “build” in Greece or France means integrating or becoming a licensed intermediary, while in Poland it means writing a client for the authority’s API.

When to build, when to buy a multi-country e-invoicing API

The build vs buy e-invoicing decision turns on counting walls, not countries. A roadmap of several countries that expose an API you can authenticate to is a smaller problem than two countries that each require a licensed intermediary, because the second roadmap forces you to hold a certification or depend on someone who does.

Option Best when What you still carry Where it breaks
Build direct Few countries, none behind an intermediary wall, and an existing tax engine with an owner Every country’s field set, state machine, numbering rules, error handling and mandate tracking The first wall country; every date change lands on your roadmap
Buy a provider API Many jurisdictions, a wall on the roadmap, no appetite to track moving mandates Mapping to the provider’s schema, numbering and lifecycle states in your own product, per-country onboarding Coverage that is resold or shallow; semantics leaking through a flattened API
Hybrid A mix of open-API countries and wall countries Direct clients for the open countries plus a provider integration for the rest Two integration styles to maintain behind one invoice model

Build when the control is the product: you must show a customer exactly why an invoice was rejected, you already run a tax engine, and the countries you serve let you talk to the authority directly. Buy when coverage speed and mandate tracking matter more than control. The analyst view has long leaned that way. As Bruno Koch of Billentis wrote in 2017, “Clarifying legal requirements for all trading parties (located in dozens of countries) is extremely challenging or almost unsolvable for them. Such projects typically never succeed.” He was writing about in-house projects driven by IT teams at large companies, nine years ago, but the mechanism he points at, legal clarification multiplying with every country, is the one described above.

Mandate dates are the other cost of building. Greece moved its first group’s start from 2 February to 2 March 2026 and its second group’s from 1 October to a reported 2 November 2026, the second change published the day before the original date. If you build, each move is a roadmap change on your side. If you buy, it is a commitment you should have in writing.

My rule of thumb is to buy the wall countries and keep the semantics layer either way. Whatever you buy, keep the invoice model, numbering and lifecycle states in your own product, because that is the part a flattened API leaks. Do not buy a multi-country e-invoicing API if you serve one or two open-API countries and have no one to own the integration; do not build if any country on your roadmap routes invoices through a licensed intermediary and you do not want to hold the licence.

Questions to put to a global e-invoicing provider

A demo shows the happy path. These questions force the country-specific answers.

  1. Which countries do you cover first-party, and which do you resell? First-party means the provider itself holds the certification, accreditation or platform registration: the AADE certification in Greece, a PA accreditation in France. Ask for the name of the entity that holds each one. In Greece, a taxpayer using a provider also files a start declaration, so the chain of responsibility is visible from day one.
  2. How are corrections and cancellations exposed? Ask for a state diagram per country and for the transitions your own system must perform. A single cancel call that becomes a portal cancellation, a credit note or a resend depending on the country needs documenting, not hiding.
  3. Who owns the number sequence, and what happens to a number when a submission fails? The answer differs between a cancelled Indian IRN and a discarded Italian file. Get the behaviour for each country in writing.
  4. How do validation errors reach you? Ask for the authority’s original error code and message next to the provider’s normalised one, and whether rejection comes back inside the API call or arrives later as a status change. That decides how you build retries.
  5. What happens when a mandate date moves? Greece changed two start dates in 2026. Ask how much notice you get, how quickly the provider ships changes, and whether a postponement leaves your integration running in parallel mode.
  6. What is the exit? Ask how invoices, identifiers and authority registration numbers, such as the MARK and UID that Greece’s myDATA assigns, can be exported if you change provider.

Frequently asked questions

Can one API cover all of the EU?

For transport and format, yes: Peppol and EN 16931 are EU-wide. For compliance, not fully by 2030. From 1 July 2030 Article 218 requires electronic invoices to follow the European standard, with other standards allowed only for domestic supplies, and Article 264 harmonises intra-EU reporting. Member States can still require domestic reporting under Article 271a, and those with real-time systems already running have until 2035 to align, so expect national layers on top.

Does a provider remove my compliance liability?

No. A provider takes over the connection, not the legal obligation. In Greece the fine for not issuing an e-invoice where VAT applies is 50% of the tax, and it falls on the taxpayer; in France, non-compliant issuance is fined per invoice under article 1737 of the Code général des impôts. How much of that risk a provider takes back is a matter for the contract, not the statute.

What is left to build if I buy a provider API?

Your canonical invoice model with country-specific and party-specific slots; the numbering sequence and its behaviour on failure; the mapping from provider statuses to your own states and screens; per-country customer onboarding, such as Greece’s start declaration; and monitoring for rejections.

How do providers keep up with changing mandates?

Each change is a release, not an automatic update. Greece changed two start dates in 2026, and Poland changed its token authentication plan in August. Ask what notice period the provider commits to and what a late change means for your customers’ deadlines.

How to integrate e-invoicing in SaaS without rewriting it for every country?

Keep an internal invoice model aligned with the EN 16931 core, add typed slots for country-specific and party-specific data, and keep numbering, lifecycle states and the audit trail in your product. Put each authority or provider behind an adapter that translates in both directions and reports statuses back. That is the shape of an e-invoicing integration SaaS companies can maintain, and it lets you switch between building and buying one country at a time.