Integration Guides
Creating an e-invoice and delivering one are two different jobs. Many invoicing products, ERP add-ons and open-source libraries already create compliant XML; delivering it over Peppol needs a certified Access Point. GoRoute is that Access Point (Peppol seat POP000991), and these guides show how to plug what you already have into it.
Pick your starting point
| You have… | Start here |
|---|---|
| Software or a library that already produces UBL invoices (Peppol BIS 3.0, XRechnung UBL, PINT) | Send XML you already generate |
| A PHP application using josemmo/einvoicing | PHP: josemmo/einvoicing |
| ZUGFeRD, Factur-X or XRechnung in CII syntax (horstoeko/zugferd, Mustang, a Factur-X PDF) | ZUGFeRD, Factur-X and XRechnung CII |
| A product with many customers who each need to send and receive e-invoices | For software vendors and resellers |
| Your own Access Point (Oxalis, phase4, Domibus, Holodeck) and want to stop running it | Migrating Access Points |
| A shop or ERP (Shopify, Wix, WooCommerce, Business Central, Odoo, Xero, QuickBooks…) | Connectors |
| Invoice data but no XML yet | Send an invoice — GoRoute builds the XML for you |
What every path has in common
- One API. Everything runs over HTTPS + JSON with an
X-API-Keyheader. There is no SDK to install; see Client libraries for a working call in Python, Node.js, C# and Java. - Test first. The test environment and the sandbox recipients (
9999:test-…) let you send end to end without reaching a real company. See Environments and Test identifiers. - Outcomes arrive by webhook. A send is accepted with
202and delivered asynchronously;transaction.deliveredortransaction.failedtells you how it ended. See Webhooks.
Once your integration works
Pass the five sandbox scenarios in Partner Verification to earn the GoRoute Verified badge, which you can show to your own customers.