The GoRoute E-Invoicing agent brings GoRoute into Microsoft 365 Copilot. You ask in plain language, inside Teams, and the agent looks a customer up on the Peppol network, drafts and validates an invoice, or reports what was sent and what failed, all against your own GoRoute account and within your role. Nothing is created or sent without your confirmation.
This page is the recording written out, chapter by chapter, for anyone who would rather read than watch. Watch the recording on its own page.
It puts e-invoicing where your team already works. Instead of opening the GoRoute dashboard, a finance user asks Copilot in Microsoft Teams, and the agent answers from GoRoute’s records: who can receive an e-invoice, whether an invoice is right, and whether it arrived.
Can this customer receive an e-invoice at all? Is the invoice right for the customer’s country? And did it actually arrive? Each one is a thing GoRoute already knows how to do: a lookup on the Peppol network, a validation against the buyer’s country rules, and a delivery status. The agent gives Copilot those three tools, and a few more, and nothing else.
Copilot in Teams, then Agents, then GoRoute E-Invoicing. The first time you ask it something that needs GoRoute, it opens GoRoute’s sign-in page; from then on it acts as you, within the permissions of your GoRoute role. How an administrator allows it and how each user connects is on the Copilot page.
Give it a Peppol identifier or a company name. The agent looks the identifier up on the live Peppol network and says whether it is registered and which documents it can receive, invoices and credit notes for example. It also finds the customers and suppliers saved in your GoRoute account. Every answer comes from the network or from your records; the agent never invents a Peppol ID.
“Draft an invoice to Acme for …” is enough to start. The agent collects what is missing, the invoice number, the date, the lines and the VAT treatment, builds the draft in your GoRoute account, and runs GoRoute’s validator for the buyer’s country. If something is wrong it says what to fix rather than guessing.
Creating a draft writes to your account, so Copilot shows what it is about to create and asks before it does. The two actions that change anything, creating a draft and sending one, always ask; everything else is read-only and asks for nothing.
The agent lists what was sent in a period, counts it by status, names the failures with their reason, and gives the status history and a PDF link for any single document. It can also show the purchase invoices you received over Peppol, most recent first.
Nothing. A draft is sent only after you explicitly confirm that specific draft. The agent never resends on its own, never changes a VAT category or rate on its own, and never acts on data it has inferred rather than read.
Twelve things, and nothing else. Every capability maps to one GoRoute tool, and every answer is grounded in what that tool returned.
| You ask | The agent does | Asks first? |
|---|---|---|
| Is this company on Peppol? | Looks the identifier up on the network and says which documents it accepts | No, read only |
| Find my saved customer Acme | Searches the parties saved in your GoRoute account | No, read only |
| What did we send this month, and what failed? | Lists sent documents and counts them by status | No, read only |
| What is the status of INV-2026-0042? | Returns the transaction, its status history and a PDF link | No, read only |
| Show the purchase invoices we received this week | Lists received documents and opens one in full | No, read only |
| Validate this invoice | Runs GoRoute’s validator for the buyer’s country and reports what to fix | No, changes nothing |
| Draft an invoice to Acme for … | Creates a draft in your account after collecting what is missing | Yes, before creating |
| Send that draft | Sends it over the Peppol network | Yes, every time |
Create a GoRoute account, so the agent has something to connect to. In the Microsoft 365 admin center, an administrator allows the GoRoute E-Invoicing agent for the users or groups who invoice; each user then opens the agent, asks it something, and signs in to GoRoute when prompted. The agent’s Agent Store listing is in Microsoft’s review, and the Copilot page is updated the day it goes live. The recording uses sample data from a GoRoute demo account.
Registering Peppol identities, deleting drafts, sending raw XML and GoRoute’s general API are deliberately not in the agent; they stay in the GoRoute dashboard. The GoRoute app for Business Central, which shares the same account, has its own recording. Pricing is on the pricing page.
To use the agent inside Microsoft 365 Copilot (Word, Outlook, Teams, Business Central), yes. In Copilot Chat the agent can be used where your tenant allows third-party agents. Your administrator decides which agents are available.
Your own. The first time you ask Copilot something that needs GoRoute, it opens GoRoute's sign-in page; you sign in and approve the connection. Copilot then acts as you, within the permissions of your GoRoute role. You can disconnect it from GoRoute at any time.
No. Sending is a confirmed action: Copilot shows you the draft and asks before it calls the send tool, every time. It never resends, never changes a VAT category or rate on its own, and never acts on data it has inferred rather than read.
Only what the tools you use need: the identifiers, invoice data and status you ask about. Those go to GoRoute over TLS. GoRoute does not receive your Microsoft password and Microsoft does not receive your GoRoute password.
Its listing is in Microsoft's review. The Copilot page on goroute.ai is updated the day it goes live; a GoRoute account can be created now so the agent has something to connect to.
