One JSON Invoice, Every Format: GoRoute’s Multi-Country E-Invoicing API

You write the invoice once, as JSON, and send it with one call to POST /api/v1/invoices. GoRoute reads the buyer’s country, asks the Peppol network what that buyer can receive, and renders and checks the invoice in that format: Peppol BIS 3.0, PINT A-NZ, PINT OM, XRechnung or ZUGFeRD / Factur-X, or a filing with the tax authority in Spain and Nigeria.

The recording runs 3 minutes 22 seconds in thirteen chapters: the request, how the format is chosen, a quick quiz, the six routes one by one, a cheat sheet, and three things to know before promising this to a customer. The same walkthrough is written out on a page of its own, if you would rather read it than watch it.

Chapters

0:00 — One JSON invoice, every format
0:19 — One call, the same fields everywhere
0:40 — How GoRoute decides the format
0:58 — Quick quiz: your buyer is in Sydney
1:13 — Stop one: Europe, the UK and Norway (Peppol BIS 3.0)
1:25 — Stop two: Australia and New Zealand (PINT A-NZ)
1:33 — Stop three: Oman (PINT OM and the Tax Data Document)
1:41 — Stop four: Germany's public sector (XRechnung)
1:51 — Stop five: Germany and France by email (ZUGFeRD / Factur-X)
2:03 — Stop six: Spain and Nigeria, straight to the tax authority
2:13 — The cheat sheet: six routes
2:23 — Three things worth knowing
3:09 — Recap and where the docs are

Prefer to read it?

Every chapter is written out, with the format table and the questions people ask about it answered, on a page of its own.

Read the written guide →

One JSON Invoice, Every Format: GoRoute’s Multi-Country E-Invoicing API

Chapters

Prefer to read it?

Where to go next