A posted invoice leaves Dynamics 365 Business Central through its E-Document framework as structured data, is converted and validated, and travels to your customer over the Peppol delivery network through a certified access point. The same path serves Finance & Operations and the wider global e-invoicing networks.
Watch the 10-minute walkthrough: how the GoRoute connector for Microsoft Dynamics ERP works — Dynamics 365 Business Central and its E-Document framework, through validation and Peppol delivery to Oman Fawtara readiness. Running Dynamics in Oman? Oman e-invoicing from Microsoft Dynamics 365 walks the same path against Oman’s own rules, and names the four fields in your Dynamics master data that decide whether a document is accepted.
Dynamics 365 business applications
Certified Peppol Access Point
Business Central posts the invoice as it always has. Its E-Document framework hands that document out as structured data; GoRoute renders it as UBL 2.1 XML, validates it against the receiving country’s rules, and delivers it over Peppol to your customer’s own access point.
That is the whole shape of it, and the part worth holding on to is what does not change. Your finance team raises and posts a sales invoice the way it does today. There is no second system for them to learn, no export-and-upload step, and no PDF emailed to a shared mailbox at the other end. What changes is what happens after they press post: instead of a document rendered for a human to read, a structured document leaves the system, is checked before it goes anywhere, and is handed to the buyer’s provider over a network both sides already trust.
Peppol is a delivery network rather than a portal. Your access point and your customer’s access point exchange the document between them; neither of you logs into anything to make it happen, and the addressing is resolved from a directory rather than from an email address someone typed. GoRoute is a certified Peppol Access Point and SMP provider, service provider ID POP000991, so the certified half of that pair is the part we run.
| Step | Where it happens | What your team does |
|---|---|---|
| Raise and post the invoice | Business Central | Nothing new — the same posting routine |
| Hand the document out as data | The E-Document framework in Business Central | Configured once, during setup |
| Convert to UBL 2.1 and validate | GoRoute | Fix what the errors name — usually master data |
| Deliver over Peppol | GoRoute, as a certified access point | Nothing — delivery and status are tracked |
| Report to the tax authority, where a country requires it | Depends on the country | Confirm which regime you fall under |
The last row is the one that surprises people. In some countries the buyer and the tax authority receive the same thing; in others they do not. Oman is the clearest example: the buyer receives the invoice, and a separate tax data document, derived from that invoice, is what reaches the Tax Authority. If Oman is your market, the regulatory detail belongs on Oman e-invoicing from Microsoft Dynamics 365 rather than here — that guide names the four fields in your Dynamics master data that decide whether a document is accepted, and the two mandate dates.
Six things this connection gives a Microsoft estate. Each one is written out in full below the cards.
Built on Azure platform with Logic Apps, Functions, and Service Bus integration. Scales with your Microsoft infrastructure.
Power Apps connectors for e-invoicing workflows. Power BI dashboards for compliance reporting and analytics.
SharePoint document management and Teams notifications. Outlook email integration for invoice delivery confirmations.
Native Business Central extension with AL language customizations. Seamless sales order to e-invoice automation.
Azure AD integration with multi-tenant isolation. Company-specific compliance rules and e-invoicing configurations.
Support for Azure Government Cloud deployments. FISMA, FedRAMP compliance for public sector e-invoicing.
A card can assert “Business Central ready” in two words. What a project needs to know is which part of Business Central is involved, what runs where, and which of these six matter to the estate you actually have. Taken in the order the cards appear:
The Azure side of this is deployed into your subscription, not ours. An ARM template — Azure’s own deployment file, which describes a set of resources so they can be created in one operation — establishes Logic Apps, Key Vault and Service Bus with the permissions they need, using an Azure AD service principal and a managed identity so no secret has to be copied anywhere by hand. Logic Apps carry the workflow, Key Vault holds credentials, and Service Bus is what keeps a burst of invoices from being lost when something downstream is briefly slow.
The practical consequence is about ownership rather than technology: the resources sit inside your own tenant, under your own cost centre and your own monitoring, and the network path between them and GoRoute is one your infrastructure team can see. If your organisation would rather not host any of it, say so early — that is a design decision, not a late configuration switch. The hosted infrastructure options are the alternative.
Power Apps connectors put e-invoicing steps inside the workflows a business already runs, and Power BI reads the same delivery and compliance data for compliance reporting and analytics. This is the part most often underestimated in a good way: the question “which invoices went out, which were rejected and why” is a reporting question, and a finance team that can answer it without opening a support ticket will trust the system months earlier than one that cannot. Power Platform usage is typically covered under existing Office 365 E3 or E5 subscriptions, so for most estates this adds capability rather than licence cost.
Outlook carries delivery notifications, SharePoint holds archived documents, and Teams carries workflow alerts, with Power BI dashboards available in the same Office portal people already have open. The point of listing them is not that these are exotic integrations — they are not — but that e-invoicing status has to land somewhere a human looks. A status that only exists in an integration console is a status nobody reads, and the first month of live running is when that difference is felt.
This is the card that matters most, and it is the one the recorded walkthrough opens on. The E-Document framework is the point at which a posted sales document leaves Business Central as structured data rather than as a rendered PDF. GoRoute starts there deliberately, rather than reading the database or scraping a report, because a document handed out by the framework is the document Business Central considers posted — with the same numbering, the same amounts and the same customer record behind it.
A native Business Central extension, written in AL, is what carries the configuration inside the system, and sales order to e-invoice runs as automation rather than as a daily human task. If you would rather watch it than read it: the framework itself is explained at 02:15 in the walkthrough, and the invoice leaves Dynamics at 03:00. The whole recording runs ten minutes and twenty-three seconds, in thirteen chapters, and needs nobody’s permission to watch: the GoRoute connector for Microsoft Dynamics ERP.
Azure AD integration with multi-tenant isolation means several companies can run through one connection while their data stays separated, and compliance rules and e-invoicing configuration are held per company rather than globally. That matters more than it sounds for a group: the Omani subsidiary, the UAE entity and the UK company do not have the same rules, the same identifiers or the same go-live date, and a single shared configuration forces the strictest one on everybody. Per-company configuration is what lets a group go live in stages instead of all at once.
Azure Government Cloud deployments are supported for public-sector customers with their own e-invoicing requirements. If you are in that position, treat the specifics as something to confirm in writing against your own authorisation boundary before it becomes a design assumption — that is true of any provider, and it is a cheaper conversation in week one than in week nine.
Dynamics is not one product, and this is the first thing the walkthrough says out loud. Business Central, Finance & Operations, Sales and Customer Service, and older on-premise systems each take a different integration path. Treating a Dynamics estate as one thing is how integration projects arrive at the wrong estimate, and it is why the published walkthrough starts with Business Central and its E-Document framework rather than claiming every Dynamics installation behaves alike.
So the honest answer to “do you have a Peppol solution for Dynamics” is: which Dynamics? Ask any provider to answer that in writing, naming the product and the version they support, before the question becomes an assumption inside a plan. Ours is answered on this page and demonstrated in the recording.
Three steps, in the order they actually happen.
Deploy GoRoute.ai Azure ARM template to your subscription. Establishes Logic Apps, Key Vault, and Service Bus resources with proper permissions.
Install Business Central extension or configure Dynamics 365 data connections. Map invoice entities to UBL format with Power Platform connectors.
Use Power BI dashboards for e-invoicing analytics. Monitor Azure costs and performance with built-in telemetry and alerting.
By validating a real one, early. GoRoute checks a document against the full rule set for the profile it is being sent under and returns a compliance score with human-readable errors, rather than a bare pass or fail. An error that names the field and the rule is a ticket someone can act on; a rejection code is a conversation.
Two things make validating properly cheap, and both change how a project is sequenced. Validation-only calls carry no per-call charge, so validating the same Business Central invoice forty times while a mapping is being corrected costs nothing. And you can validate long before you can send, so the technical work and the commercial work run in parallel rather than in sequence — which is usually where a compliance deadline is won or lost.
For volume, batch submission takes between 1 and 1,000 invoices in a single request, with separate validate and process stages. That shape matters at month-end, when a month of Business Central invoices arrives in an hour rather than across a day, and it is the point at which a design that sends one invoice per call tends to fail.
What usually fails validation is not the integration. It is master data — a customer with no usable tax identifier, an item without the classification its destination country requires, an amount carried to more decimal places than the local currency allows. Those values live in ordinary Business Central records, they are entirely within your control, and counting the gap is much better done in week one than in week nine. The developer sandbox and the API services page are where a technical team starts; the documentation has the request and response shapes.
Book a working session against your own Dynamics estate, or watch the recorded walkthrough first — it needs no form.
The six asked most often before a Dynamics project starts
Yes, through a certified access point. Business Central raises and posts the invoice exactly as it does today. Its E-Document framework hands the posted document out as structured data; GoRoute renders it as UBL 2.1 XML, validates it and delivers it over Peppol to the buyer’s access point. Nobody in the finance team works differently.
It is the point at which a posted sales document leaves Business Central as structured data rather than as a PDF. GoRoute’s recorded walkthrough starts there: the framework is explained at 02:15 and the invoice leaves Dynamics at 03:00, then goes through validation, Peppol delivery and transaction tracking.
Dynamics is not one product. Business Central, Finance & Operations, Sales and Customer Service, and older on-premise systems each take a different integration path, which is why the walkthrough starts with Business Central and its E-Document framework rather than treating every Dynamics estate the same way. Which product and version apply to you is a question to ask and get answered in writing.
No. The ARM template automates the Azure deployment into your own subscription, establishing Logic Apps, Key Vault and Service Bus with a service principal and managed identity. We provide guided setup and can handle the initial deployment for enterprise customers with managed services options.
By validating a real one. GoRoute returns a compliance score with human-readable errors naming the rule that fired, rather than a bare pass or fail. Validation-only calls carry no per-call charge, so validating the same Business Central invoice repeatedly while a mapping is corrected costs nothing, and batch submission takes between 1 and 1,000 invoices in a single request.
Azure consumption costs scale with usage. Business Central extensions may require additional user licenses. Power Platform usage is typically covered under existing Office 365 E3/E5 subscriptions.
