E-invoice receiving and processing software takes your suppliers' invoices in as structured data instead of PDF attachments in a shared mailbox. GoRoute is an electronic invoice receiving platform built on a certified Peppol access point: it registers your business as an addressable participant, accepts what suppliers send, records what each document was validated against, and delivers it to the portal, to a connector, or to your own endpoint. Nobody retypes an invoice, and every arrival is on one register with its status.
Four steps, none of them manual
E-invoice receiving and processing software makes a business addressable on an e-invoicing network, takes delivery of supplier invoices on its behalf as structured documents, records what each one was validated against, and passes it to the system that will pay it. Sending software answers “did my invoice arrive”; receiving software answers “what arrived, from whom, and is it complete”.
The distinction matters because receiving is the half most businesses do not plan for. A mandate is usually read as an obligation to issue invoices in a particular format, so the sending side gets a project. Then trading partners begin sending structured invoices back, and there is no address for them to send to. An enterprise e-invoice receiving software decision is really three decisions: who holds your address on the network, what happens to a document the moment it lands, and where it ends up so that someone can approve and pay it.
GoRoute answers all three from one platform. The sending side has its own page — e-invoice sending and tracking software covers what happens between pressing send and a delivery receipt — while the country coverage and the compliance scope are set out on the global e-invoicing platform page, and the interface and the endpoints on the API services page. This page is about what the platform does with an invoice that someone sends to you.
If you would rather watch it than read it, the video walkthroughs cover the portal and the ERP connectors end to end, and the portal recording is also written out screen by screen — how a supplier invoice arrives and what is recorded against it afterwards.
You are registered once. After that, arrivals are automatic.
GoRoute registers your participant identifier and publishes the entry in its SMP, so other access points can find you
Invoices, credit notes and any other document type you are willing to take are declared on that entry
The supplier's access point delivers into your account and the invoice appears as a structured document, not a scan
A document.received webhook fires, so an ERP learns of the invoice without anyone opening the portal
Step one is the step people skip. Until your participant entry is published, a supplier's provider has nowhere to deliver to, and the invoice falls back to email — which is the outcome the whole exercise was meant to remove. The getting-started steps in the help centre cover the account profile and the identifier, and the SMP service is where the entry itself lives.
Purchase documents have their own list in the portal, sales documents have theirs, and both sit together in one combined register. The separate lists answer directional questions — did this invoice reach this customer. The combined register answers chronological ones: what moved on this account, in order, over a given period.
Each entry carries what the document was validated against and how far it got, so a query that used to mean searching mailboxes becomes a query against one list: which documents came from a given counterparty, what each was checked against, and when it was acknowledged. The archive holds the original UBL XML alongside the record rather than a rendering of it, with validation results, delivery receipts and audit logs — which is what an auditor asks for, and it is the same archive on both directions of traffic.
For an integrated team the same events are available as webhooks: GoRoute posts document.received, document.validated, document.sent, document.failed and document.delivered to the URL you set, with HMAC-signed payloads, retries using exponential backoff and dead-letter logging. That is what lets an accounts-payable queue show an arrival without polling for it.
The address on the network is the same in all three. Only the destination changes.
No integration, no ERP. Arrivals are worked in the browser, with the register and the archive in the same place. This is where most businesses start, and it is a complete answer for a team receiving tens of invoices a month.
See the portal walkthrough →Into the system you already run. Odoo, TallyPrime, SAP, Oracle and Microsoft Dynamics 365 each have a documented path, and Connect for Excel exists for teams with no ERP at all.
All connectors →Your own endpoint, your own queue. The REST interface and the webhook events are described on the API services page and in the documentation, and the developer programme issues a sandbox to try it against.
Peppol API integration →Receiving over Peppol depends on two pieces of infrastructure: an access point that takes delivery for you, and a Service Metadata Publisher — an SMP, the directory entry that tells another provider which documents you accept and where to deliver them. GoRoute is certified for both under POP000991, so your entry is published as part of receiving rather than being someone else's dependency.
That distinction is worth putting to any provider you are comparing. A reseller can connect you through another company's access point, which works, but it means the record of your address, and the ability to change it, sits one party further away. If you are a provider or a group that needs to hold your own customers' entries under your own identity, SMP-as-a-Service does that, and the SMP itself is where registrations are managed.
If the terms are new, what a Peppol access point is explains the four-corner arrangement in plain terms, and how to choose one sets out what to compare between providers.
Most receiving software demonstrates well and differs in the places a demo does not reach. These are the questions that separate them, and they are worth asking of us as much as of anyone else.
On the last one, the country rulebook belongs on the country page rather than here: which profile applies where, and whether a tax authority also has to see the document, is set out per market on the global platform page and the country pages it links to.
A demo covers registration, an arrival, the register and the webhook in one pass. If you would rather look first, the walkthroughs and the API documentation are open.
E-invoice receiving and processing software takes supplier invoices in as structured data instead of PDF attachments. It registers your business as an addressable participant on a network such as Peppol, accepts what arrives on your behalf, records what each document was validated against, and hands it to your portal, connector or webhook so nobody retypes an invoice.
Two things: an account with a completed organisation profile, and a registered Peppol participant identifier with the document types you accept. The identifier is your address on the network — you choose a scheme such as VAT or GLN, GoRoute registers it as a certified access point and publishes the entry in its SMP. Until that entry exists, a supplier's provider has nowhere to deliver to.
No. Arrivals can be worked entirely in the portal, which is the usual starting point for a business with no integration at all. A connector into an existing accounting system, or the REST API with a webhook, are routes in rather than requirements, and you can add one later without changing your address on the network.
Where an integration is listening, the arrival fires a document.received webhook, which is how an ERP learns about a supplier invoice without anyone opening the portal. GoRoute posts document.received, document.validated, document.sent, document.failed and document.delivered to the URL you set, with HMAC-signed payloads, retries with exponential backoff and dead-letter logging.
Yes. Sales and purchase documents each have their own list, and both sit together in one combined register. The separate lists answer directional questions — did this invoice reach this customer — and the combined register answers chronological ones: what moved on this account, in order, over a given period. The portal walkthrough shows both.
The document itself as structured data, what it was validated against, its status, and the timestamps around it. The archive keeps the original UBL XML alongside the record rather than a rendering of it, with validation results, delivery receipts and audit logs, so an audit request becomes a query against one register instead of a search through mailboxes.
No. Your entry is published in GoRoute's SMP as part of receiving, and GoRoute is a certified Peppol Access Point and SMP provider under POP000991. A provider or group that wants its own SMP — usually to hold its customers' entries under its own identity — can run one through SMP-as-a-Service instead.
The developer programme issues a 14-day sandbox with an sk_test_ key, the full validation gate, and four deterministic 9999:test-* receivers that reproduce success, timeout, validation failure and recipient-not-found end to end. That lets you exercise the arrival and webhook path before anything is wired to a live account.
The mechanics are the same wherever delivery is over Peppol: an addressable identifier, a published set of accepted document types, and an access point that takes delivery. What differs is the country's own rulebook — which profile applies, and whether a tax authority also has to see the document. Those requirements are set out on each country page rather than here.
Whether it is a certified access point in its own right or resells someone else's, whether it publishes your participant entry and can show it, what it records about each arrival, whether you can work without an ERP, what the arrival event looks like to an integration, how long the archive holds the original document, and whether you can test the whole path in a sandbox first.
What a business must receive, and by when, is set by its own tax authority and changes over time. This page describes how receiving works on the GoRoute platform; confirm the current obligation for your market on the relevant country page and with the authority itself.
