Business Central app · Peppol
Peppol e-invoicing, built into Business Central.
Posted sales invoices and credit memos travel the Peppol network from the page you already work on. Supplier documents come back in through Business Central’s own E-Document framework. Belgium’s B2B mandate has been live since January 2026 — this is how you meet it without a portal alongside your ERP.
- Peppol BIS 3.0 · UBL
- Self-Billing 3.0
- Belgian mandate
What it does
Sending, receiving, and knowing where a document is.
Sending
One, a selection, or nobody
Send a posted invoice on its own, select rows and send them together, or let a job queue sweep pick them up unattended. A batch does not stop on a bad row — fifty documents with two bad customers still delivers forty-eight, and the two are written to the log with their reason.
Receiving
Supplier documents, coded and routed
Incoming documents are matched to the vendor they came from, become a purchase invoice or a purchase order as you decide, and can be routed into your existing approval workflow. Their own PDF is attached to the purchase document alongside the structured data.
Knowing
Sent is not the same as delivered
The log records what Business Central did. Check Delivery asks the network whether the receiving side confirmed arrival. Download UBL gives you the XML exactly as it was exchanged — which is what you want on the day a customer says nothing came.
How it works
From posted document to the network, in one flow.
Nothing happens on a schedule that a person has not switched on first.
-
1
You post as you always did
A sales invoice or credit memo is posted in Business Central. No separate entry, no export, no second system.
-
2
It becomes a compliant document
The app builds a Peppol BIS 3.0 document in UBL, applies Belgian reverse charge where your VAT setup calls for it, and can attach a PDF rendering so the receiver still sees the invoice as you designed it.
-
3
It travels the network
The document goes out through your access point to your customer’s. The send is recorded, and the status sits on the document itself.
-
4
And the same in reverse
Supplier documents arrive through Business Central’s E-Document framework, are recognised, and wait wherever you decided they should wait.
Inside the app
Ten tiles that count what needs a person.
The app adds an E-Invoicing band to the Business Manager and Accountant role centers. Every tile is off until you switch it on, and the choice is per user — ten tiles on everybody’s home page would be noise for most of them.
Role center · Business Manager
Supplier Bank Details
Bank Accounts
5
IBAN Changes
2
Incoming Documents
No Supplier
1
Will Not Import
0
Invoice or Order
3
Approval
Awaiting Approval
4
Request Failed
0
Outgoing Documents
Failed Sends
0
Delivery Unconfirmed
7
Connection
Issues
0
If you show only two, make them IBAN Changes and Failed Sends. One is money going somewhere it should not; the other is money not arriving.
Why you would trust it
The parts that exist because something can go wrong.
Fraud
Bank details are a claim, not a fact
Every account an incoming document proposes waits on a list for a person to accept or reject it. Nothing reaches a vendor card until somebody approves it. When a document changes details you already hold, the confirmation says so in as many words — and tells you to call the supplier on a number you already had.
Identity
A document cannot leave under the wrong company
Each Business Central company is mapped to its own identity on the platform, and a company whose mapping has not passed its identity check cannot send at all. That is deliberate: sending under the wrong legal entity is worse than not sending.
Evidence
The log cannot be emptied
The day-to-day permission set can add to the send log and update it, never delete from it. A user who can delete rows can make a failed send disappear — which is precisely the evidence you want when a customer says an invoice never arrived.
Exit
It comes out as cleanly as it went in
Uninstall Impact reports exactly what the app has written into standard tables, and changes nothing while it does. That answer is as useful before you buy as before you leave.
What it covers
Which documents travel, and what it plugs into.
Two questions with short answers. The first table is scope: which documents move, in which direction, and which of them a job queue can handle unattended. The second is where the app sits inside Business Central — because the useful answer to “does it do approvals” is that it does not do approvals at all. It routes into yours.
| Send | Receive | Unattended | Delivery confirmed | |
|---|---|---|---|---|
| Posted sales invoice | Covered | Not applicable | Covered | Covered |
| Posted sales credit memo | Covered | Not applicable | Covered | Covered |
| Supplier invoice | Not applicable | Covered | Covered | Not applicable |
| Supplier credit memo | Not applicable | Covered | Covered | Not applicable |
| Self-billed invoice | Covered | Not applicable | Not applicable | Covered |
| Self-billed credit note | Covered | Not applicable | Not applicable | Covered |
Unattended sending sweeps posted sales invoices and credit memos only — a self-billed document is always sent by a person. Incoming documents arrive on Business Central’s own inbox poll, and a credit memo always becomes a purchase credit memo, whatever the supplier is set to.
One more thing the readiness box tells you before you post: Intercompany appears when the other side turns out to be one of your own companies on the platform — on the customer when you sell, on the vendor when you self-bill. Blank means an outside party. It posts nothing on your behalf; it saves you finding out afterwards.
What it integrates with
- Approval workflow
- Purchase documents go for approval through Business Central’s own routines. Standard Business Central does not send a purchase invoice created from an incoming e-document for approval — that import path never raises the event the workflow listens to — so an electronically received invoice would arrive postable while the same invoice typed by hand would need approving first. Approval for Incoming Documents closes that gap. With no workflow enabled the app leaves the document alone and writes down why; it does not invent an approval.
- E-Document framework
- Receiving registers as a connector on the standard Service Integration enum, with the app’s own vendor resolution plugged into E-Doc. Proc. Customizations. The import path itself is not replaced.
- Text-to-account mapping
- Incoming lines without an item are coded by description through Business Central’s own mapping: this vendor first, then any vendor, then the fallback account on Purchases & Payables Setup. The app reads that setup and never writes it — it only tells you in advance which descriptions resolve to nothing.
- Document attachment
- A supplier’s own PDF is attached through the standard framework, so external file storage keeps working exactly as it did.
- VAT posting setup
- Belgian reverse charge is applied from your own VAT setup. No table of ours decides what your VAT looks like.
- Report selections
- The PDF that travels alongside the structured invoice is your own invoice report, so the receiver still sees the document as you designed it.
- Job queue
- Unattended sending is an ordinary job queue entry — scheduled, monitored and stopped like every other one on the list.
- Guided experience
- The setup page registers itself, so it turns up in Manual Setup and under Set up this app rather than somewhere only we know about.
- Isolated storage
- The platform secret is held in isolated storage, where no page and no API can project it.
- Customer and vendor
- One field added to each, Peppol Endpoint, plus three on the vendor that record whether a person really chose Receive E-Document To. All of them are removed when the app is uninstalled with Delete Extension Data.
- Role centers
- An E-Invoicing tile band on the Business Manager and Accountant role centers, with every tile off until a user switches it on.
The full inventory — nineteen page extensions, everything the app writes, and the standard data it can only read — is in Standard Business Central Features This App Uses.
What you need
Before it can do anything.
- Business Central
- 2026 release wave 1 (version 28) or later, with Microsoft’s E-Document Core app, which ships with Business Central.
- A platform account
- An account with an e-invoicing platform provider, for network access. Sold separately — we help you get set up on it.
- Outbound calls
- Allowed for the extension. A newly installed extension has this switched off, and reinstalling switches it off again.
- Company identity
- A VAT registration number or, in Belgium, an enterprise number on Company Information.
- Where it applies
- The app is built for the Belgian B2B mandate, which has been in force since January 2026. Sending is not limited to Belgium: identifier schemes for the Netherlands, France and Germany are supported as well, plus GLN, so you can address trading partners abroad.
Several features lean on standard Business Central that has to be configured — approval workflows, text-to-account mapping, report selections. What Business Central Must Have in Place lists every one of them.
Documentation
Everything the app does, written down.
Get started
Set it up
Connect Business Central to the platform, map your companies, and give customers and vendors a Peppol address.
Day to day
Send and receive
Sending posted invoices, self-billing in a supplier’s name, recognising suppliers on incoming documents, and approving the bank details they propose.
When something breaks
Error messages, explained
Every error the app can raise, with what caused it and what to do — searchable by the exact text on your screen.
Full documentation: E-Invoice Platform help. It is also reachable from inside Business Central, through the Learn more links on tooltips. And it is what Chat with Copilot reads: the app manifest points Copilot at these pages, so a question you ask in Business Central is answered from this manual rather than from the internet at large. English only — that is the language Copilot’s chat is validated in.
How you start
It is a conversation, not a download.
The app is on its way to Microsoft AppSource and is not listed yet, so there is no install button to press today. Tell us which Business Central version you are on and what you invoice, and we will tell you honestly whether this fits — and what it would take.
Already using it? Product support answers within one working day.