E-Invoicing Belgian Public Bodies: Mercurius and Peppol — Odoo & ERP article by Rui Codex

Belgian public bodies receive electronic invoices through the Peppol network, with Mercurius serving as the federal platform that routes them to the right buyer. Suppliers need a Peppol-capable sending service, a structured invoice in the required format, and the buyer's correct identifier. Most rejections come from missing or wrong identifiers rather than faulty software.

Key takeaways

  • Peppol is the network that carries structured invoices between sender and receiver, and Mercurius is the Belgian federal entry point for public buyers.
  • An invoice that is only a PDF attachment is not a structured e-invoice, and public buyers may refuse to process it.
  • Most failed submissions trace back to the buyer identifier, the invoice format or a missing purchase order reference, not to the sending software.
  • Choosing between a direct access point, a managed service and an ERP add-on is a trade-off between control, effort and ongoing maintenance.

What is Peppol and why do Belgian public bodies use it?

Peppol is a network of interconnected access points that exchange structured electronic documents such as orders, invoices and credit notes. Each participant is identified by a participant identifier, and the network uses standard formats so that a sender's system and a receiver's system can process the same file without custom integration. The governing body and the technical specifications are documented on the Peppol website.

Public buyers use Peppol because it lets them accept invoices from many suppliers through one channel instead of building a separate intake for each supplier. For a supplier, the same connection can serve several public buyers, which is the main practical benefit. The network does not decide whether an invoice is correct; it only moves a valid, structured document from sender to receiver.

What role does Mercurius play?

Mercurius is the Belgian federal platform for receiving electronic invoices from suppliers, and it connects federal authorities to the Peppol network. Suppliers who sell to federal bodies therefore need to address invoices so that Mercurius can route them to the correct administration. The exact list of connected buyers and the routing details change over time, so check the current guidance from the federal authorities before you configure anything.

In practice, Mercurius is one of several entry points you must understand. A supplier may also deal with regional or local public bodies that run their own intake, and those buyers can publish different identifiers or format requirements. Treat each buyer's published instructions as the authority for that buyer, not a general rule that applies everywhere in Belgium.

What does the EU rule require?

Directive 2014/55/EU requires contracting authorities to receive and process electronic invoices that comply with the European standard for the semantic data model of core invoice elements. The directive sets the obligation for public buyers, and Belgium implemented it nationally. You can read the text of the directive on EUR-Lex. This article is general information and not legal or tax advice.

For a supplier, the practical consequence is that the format of the invoice matters as much as the channel. A PDF sent by email may be readable by a person but is not a structured invoice that the buyer's system can process automatically. For Belgian public contracts the supplier's duty is set by law, not left to each buyer: Article 14/1 of the Law of 17 June 2016 on public procurement requires suppliers to send their invoices to the contracting authority electronically, and Article 14/2 requires those electronic invoices to follow the European standard EN 16931. The duty does not apply to contracts with an estimated value of EUR 3,000 excluding VAT or less, nor to a few kinds of contract the law names, such as those placed by autonomous public enterprises or in development cooperation. It was introduced in steps by contract value; under the Royal Decree of 9 March 2022, contracts below EUR 30,000 are covered where the invitation to tender was launched, or the order sent, on or after 1 March 2024.

How do you send an e-invoice to a Belgian public body?

You send an e-invoice by creating a structured invoice in an accepted format, addressing it with the buyer's Peppol identifier, and transmitting it through a Peppol access point. The steps below describe the usual sequence. Your own sequence will depend on your accounting system and the buyer's requirements.

  1. Confirm the buyer's requirements. Check whether the public body requires a purchase order number, a contract reference or a specific format, and record these in the order data.
  2. Obtain the buyer's identifier. Use the identifier the buyer publishes in its own guidance, and do not guess it from the buyer's name or website.
  3. Generate the structured invoice. Your system must produce a file in the format that the buyer's chain accepts, with all mandatory fields filled in consistently with the purchase order.
  4. Validate the file before sending. Run it through a validator that checks the document against the applicable rules, and fix every error rather than only the warnings that look harmless.
  5. Transmit through a Peppol access point. Send the document through your access point or service provider and keep the transmission receipt.
  6. Track the status. Monitor for rejections or status messages and correct and resend invoices promptly.
Tip: Keep a test invoice for every buyer you invoice. A single validated test per buyer catches identifier and format problems before they delay real payments.

Which sending option fits your organisation?

The three common options differ in who holds the connection and who maintains it. A managed service takes most of the technical work but adds a dependency on the provider. A direct access point gives full control but requires you to maintain certificates, updates and monitoring. An ERP add-on can be the simplest path if your accounting system already supports Peppol, but its coverage depends on your version and configuration.

OptionControlSetup effortMain risk
Managed Peppol serviceMediumLowDependency on the provider's roadmap
Direct access pointHighHighOngoing maintenance and monitoring burden
ERP add-onMediumLow to mediumLimited coverage of buyer-specific rules

If your invoices flow out of an ERP or an e-commerce platform, the integration work often matters more than the choice of access point. Mapping invoice fields correctly from your system is where most of the effort sits. For organisations that need that mapping built and tested, the team at Rui Codex offers technical implementation support for Peppol e-invoicing, and the wider ERP and CRM integration work covers the data flow behind it.

Where does the setup usually fail?

Failures cluster in a few predictable places. The buyer identifier is the most common, because a typo or an outdated identifier sends the invoice to a participant that cannot accept it. The second is format: a file that looks complete to a person can miss a mandatory field that the receiving chain checks automatically. The third is process, where the invoice references no purchase order or contract number that the buyer requires.

Use this checklist before you go live with a new public buyer:

  • The buyer identifier matches the buyer's published guidance exactly.
  • The invoice passes validation with no errors against the buyer's applicable rules.
  • Purchase order or contract references are present wherever the buyer requires them.
  • Tax amounts and totals are consistent across the header and line items.
  • Rejections are routed to a named person who can correct and resend them.
  • Test invoices have been accepted for each buyer, not only for one reference buyer.

Rejections also reveal process gaps. If the same error appears repeatedly, the fix is usually in the data your ERP sends, not in the transmission step. Tracing the error back to the field mapping is faster than adjusting the access point settings.

Hypothetical examples

Here are two hypothetical scenarios:

  • A mid-sized supplier in Flanders invoices three public bodies. Two accept invoices without a purchase order reference, and one requires it. The supplier adds the reference field to its ERP export and runs a test invoice for each buyer before the first live submission.
  • A software vendor in Wallonia sends invoices through a direct access point. A certificate renewal lapses on a weekend and transmissions fail silently. The vendor adds monitoring that alerts a named engineer on any failed status, so the next lapse is caught the same day.

Neither scenario describes a real organisation. They show that the cause of a delay is often a small configuration detail, and that a simple test and a monitoring step prevent most of them.

Frequently Asked Questions

Do I need Peppol to invoice Belgian public bodies?

Peppol is the most common route for structured e-invoices to Belgian public buyers, but the buyer's own guidance decides which channel it accepts. Check each buyer's published instructions before you set up a connection. Some buyers may accept other structured formats through their own intake, so confirm this rather than assuming one channel works for all.

Is a PDF invoice sent by email acceptable?

A PDF sent by email is generally not a structured e-invoice, and many public buyers route only structured files into automated processing. For Belgian public contracts covered by Article 14/1 of the Law of 17 June 2016 on public procurement, it is not the buyer's choice: suppliers must send electronic invoices that follow the European standard EN 16931. The article does not apply to contracts of EUR 3,000 excluding VAT or less or to a few kinds of contract it names; for those, check the buyer's contract documents before sending a PDF.

What is the most common reason an invoice is rejected?

The most common reason is an incorrect or outdated buyer identifier, followed by missing mandatory fields and absent purchase order references. A validator run before sending catches many of these. Keep the rejection messages and trace each one to the data field that caused it so the same error does not repeat.

Can a small supplier handle this without a developer?

Many suppliers manage Peppol invoicing through a managed service or an ERP feature without writing code. The work becomes harder when invoices come from a custom system or must map fields in an unusual way. In those cases, technical support for the mapping and testing is usually the deciding factor, and a short consultation can clarify which path suits your setup.

Conclusion

Invoicing Belgian public bodies electronically depends on three things: the Peppol network, Mercurius for federal buyers, and a structured invoice that each buyer's chain accepts. Choose your sending option based on control and maintenance, test every buyer before going live, and track rejections to their root cause. If you want help mapping invoice data and testing it against real buyer requirements, request a project consultation at Rui Codex or email info@ruicodex.com to discuss your project.

Sources

Tags: e-invoicing Peppol Mercurius Belgium public procurement API integration ERP integration compliance

Need Help Implementing This?

Our team can help you put these insights into practice. From AI automation to custom software development, we build solutions that deliver real results.

Send a project request