E-invoicing in Business Central: what if your invoices told your other systems themselves?
- 3 days ago
- 3 min read
E-invoicing is no longer a distant project. For many companies, receiving and issuing invoices electronically through an approved platform is becoming mandatory, in phases, over the coming regulatory milestones. (Check the exact timeline that applies to your situation — it has shifted several times.)
Among Microsoft Dynamics 365 Business Central users, one question comes up again and again as soon as the topic is raised: "An invoice has just arrived in Business Central. How do my other tools know?"
That is exactly the problem our new Webhook DyXit feature solves.
The real problem: the data arrives, but no one is notified
Thanks to the iopole connector for Business Central, e-invoices received through the platform land automatically in Business Central's native E-Document module. So far, so good.
But in real life, Business Central is rarely alone. There is often:
a legacy environment (for example an old Navision still running during migration),
another ERP in a subsidiary,
an automated approval or archiving flow,
an in-house business tool that must react to every invoice.
Without a notification mechanism, these systems have to poll Business Central constantly to find out whether a new invoice has arrived. It is heavy, slow, and fragile.
The solution: the webhook, or the problem turned around
A webhook flips the logic. Instead of your systems constantly asking "is there anything new?", Business Central tells them as soon as an event occurs — for example the arrival of a supplier invoice.
Concretely, with Webhook DyXit:
An e-invoice arrives through iopole in Business Central.
Business Central automatically generates a notification.
The DyXit platform relays it to the destination system(s) you have configured.
Each system retrieves the invoice and triggers its own processing.
All of this without manual intervention, and without your third-party systems needing direct access to Business Central.
Designed for how companies actually work, not just for the demo
We built this feature starting from the situations we genuinely encounter with our customers.
Several destinations for the same event. A received invoice can, at the same time, be notified to a legacy ERP and trigger a Power Automate flow. Each destination is delivered and tracked independently: if one is momentarily unavailable, the others are not blocked.
No loss, even during an outage. If a destination system is unreachable, the notification is not lost: it is retried automatically, with progressive delays. A tracking board clearly shows the state of each delivery — delivered, pending, failed — for oversight with no blind spots.
Simple configuration, on the administrator side. Adding a destination, choosing the events it cares about, enabling or suspending a delivery: everything is done from Business Central, without code.
Compatible with your no-code tools. A Power Automate flow can be connected in minutes: the notification arrives, the flow triggers, the invoice is retrieved. Business automation within reach, no development required.
A foundation built to last
Webhook DyXit is not limited to iopole. It is built on the DyXit for BC365 technical foundation, shared across our various integrations. In other words: the same reliable notification mechanism will be able to serve other use cases tomorrow, as your ecosystem grows. You are investing in a building block, not a throwaway workaround.
In summary
At a time when e-invoicing is imposing new flows between platforms, ERPs and business tools, the real question is no longer just "how do I receive my invoices" but "how does my information system react, automatically, to each of them."
Webhook DyXit provides a simple, robust, no-code answer to that question — at the heart of Business Central, and as close as possible to your regulatory obligations.
Do you use Business Central and are preparing your move to e-invoicing? Let's talk about your context: we'll show you how to connect your systems in minutes.
