How to Receive Peppol E-Invoices in Belgium Step by Step — Odoo & ERP article by Rui Codex

To receive a Peppol e-invoice in Belgium, you need a Peppol participant identifier, a connection to an access point, and a way to pass the validated UBL file into your accounting system. Since 1 January 2026, Belgian VAT-liable companies must exchange structured e-invoices with each other, and a company that only invoices consumers must still be able to receive them from its suppliers (FPS Finance and BOSA). The invoice arrives at the access point, is checked against Peppol rules, and is then booked after a matching step.

Key takeaways

  • An access point delivers and validates the invoice, but it never approves it for payment.
  • Your participant identifier must match the buyer data on every invoice you expect to receive.
  • Most rejected invoices fail on structure, missing mandatory fields or identifier mismatches, so an exception queue is essential.
  • Booking is a separate workflow of matching, approval and posting that your own systems or integration must support.

What does a Peppol access point do with an incoming invoice?

The access point receives the document from the sender's access point over the Peppol network, checks its structure and returns a technical response. It does not decide whether the invoice is correct or payable. Your business still needs a process that picks up the document and moves it into finance.

Peppol is a network of access points that follow a shared set of specifications maintained by OpenPeppol. Before a supplier sends, the network looks up where your business is registered, so the invoice reaches the right receiving point. The network basics are described on the OpenPeppol website.

The three ways to connect

In practice you have three options. You can contract an access point provider directly, use a service that bundles the access point with an ERP connector, or build and run your own connection. The last option means you own certificates, uptime and specification updates, which is rarely justified for a typical back-office flow.

A provider-based setup is the most common path for Belgian businesses. You still need someone who understands both the network and your ledger, which is where system integration services for connecting business software become relevant.

Which identifiers do you need before you can receive?

You need a participant identifier that the Peppol directory can resolve, and your ERP must recognise that same identifier on every incoming file. For Belgian companies, the usual approach is to use the enterprise number with the Belgian scheme identifier 0208, registered through your access point provider.

Before go-live, confirm the following with your provider and your finance team:

  • The enterprise number and legal name match the buyer data your suppliers already hold.
  • The participant identifier is registered in the directory and resolves to your receiving endpoint.
  • Incoming invoices route to the correct mailbox or ERP queue.
  • Test credentials work in a non-production environment.
  • The document types you accept, such as invoices and credit notes, are agreed in writing.
Tip: Ask your largest suppliers to send a test invoice before you switch off any old channel. Most identifier problems show up in the first few test files, not in production.

Why are some Peppol invoices rejected at validation?

Most rejections happen because a file fails either XML schema validation or the business rules of the Peppol billing specification. The access point returns a response that explains the failure, but the reason is often unclear to a finance clerk who never saw the XML.

Common causes include:

  • Mandatory fields that are missing, such as the buyer reference or the seller VAT identifier.
  • VAT identifiers that do not match the registered entity.
  • Currency codes or tax categories the sender has used incorrectly.
  • Document types that your endpoint has not agreed to accept.

Strict validation protects your ledger from malformed data, but it also means some legitimate invoices wait for a correction. The trade-off is acceptable only if someone owns the exception queue and resolves it within a fixed routine. Without that owner, rejected invoices quietly stop being paid.

How do you get from a validated file to an approved booking?

Once an invoice passes validation, the receiving side must still match it, approve it and post it. The network does none of these steps for you, so the workflow must be designed in your own systems. Each stage can be automated, but each one also has a failure mode.

Ingest and store the original file

Keep the original XML alongside any PDF rendering. Auditors and tax advisers often need the structured file, and a PDF alone cannot prove what the buyer received.

Match to a purchase order or contract

Matching compares supplier, amount, tax and reference fields against an existing order or contract. A two-way match checks invoice against order; a three-way match adds goods receipt. Two-way matching is simpler to set up, but it can approve charges that were never received. Three-way matching needs reliable receiving data, which many businesses do not yet have.

Approve and post

Approval routes the invoice to a budget owner, who confirms the cost. Posting then creates the supplier invoice in the ledger. Automated posting is only safe after matching rules have been tested with real supplier files. For broader work on routing and approvals, see our guidance on AI automation for document-heavy processes.

Tip: Define the matching tolerance before go-live, for example what happens when the invoice total differs from the order by a small amount. Ambiguous tolerance rules are the most common cause of silent errors in automated booking.

Which connection option fits your business?

The right option depends on how many suppliers send through Peppol, how much your ERP can do natively, and who will maintain the connection. The table below compares the options qualitatively, because the real effort depends on your systems and not on a generic figure.

OptionSetup effortControl over workflowTypical failure point
Access point provider onlyLow to moderateLimited to the provider interfaceManual re-keying into the ledger
Provider with ERP connectorModerateGood for standard flowsConnector limits on document types
Custom integration on a providerHigherHigh, tailored to your processesMaintenance after specification changes
Self-built access pointHighFull, but you carry all operationsCertificates, uptime and updates

A provider-only setup works while volumes are modest and the team can handle manual posting. It starts to fail when the ledger needs automatic matching, because the provider interface rarely knows your purchase orders. A custom integration fixes that gap, but it adds a maintenance cost that must be budgeted from the start.

Belgium has introduced electronic invoicing rules for business-to-business transactions, and the scope and timing are set by the Belgian authorities. Check the current requirements in the official publications of the Belgian FPS Finance before you plan. EU-level rules and the European standard for electronic invoices are available through EUR-Lex, the official EU law database.

This article is general information and not legal or tax advice. Rui Codex offers technical implementation support only, not legal, tax or compliance advice, audits or certification, so confirm your obligations with qualified advisers.

Retention of the original structured file, and the ability to show what was received and when, are practical points to raise with your advisers early. Those questions shape how you design storage and archiving in your integration.

Hypothetical examples of incoming Peppol invoices

Here are two hypothetical scenarios:

In the first scenario, a trading company receives invoices that fail validation because supplier records use a trade name instead of the registered legal name. The fix is master data cleanup on both sides, followed by a rule that rejects new supplier records without a matching identifier.

In the second scenario, a services firm receives valid invoices that cannot be matched because suppliers omit the purchase order reference. The fix is a mandatory reference field in supplier onboarding, plus a clear routing rule for invoices that still arrive without one.

Neither scenario is a measured result. They show where the work usually sits: in data quality and exception handling, not in the network connection itself.

Frequently Asked Questions

What is a Peppol access point?

An access point is a service provider authorised within the Peppol network to send and receive electronic invoices on behalf of a business. It validates the document structure, returns an acknowledgement to the sender and makes the file available to your systems through a secure channel. It does not approve invoices, match them to orders or decide on payment, so those steps still need your own workflow.

Do you need Peppol to receive invoices in Belgium?

You need a Peppol connection when your trading partners send invoices through the network or when Belgian rules require it for your transactions. Whether a given invoice must use Peppol depends on the parties and the rules in force, so check the official Belgian guidance first. Plan for the channel your key suppliers and customers actually use, and confirm the rules with the authorities before setup.

Can your ERP receive Peppol invoices without an access point?

Most ERP systems cannot join the Peppol network on their own, so they need an access point or a provider that connects to one. Some vendors offer ready-made connectors, and a custom integration can also pass validated files into your ledger. Either way, check which document types the connector supports and how it reports rejections back to your team.

Why is my incoming Peppol invoice rejected?

Most rejections come from a file that fails schema or business-rule validation, or from buyer data that does not match your registered identifier. Missing mandatory fields, incorrect VAT identifiers, unsupported currencies and wrong document types are common causes. Set up an exception queue that shows the rejection reason, so the supplier can correct and resend the invoice quickly.

Does Rui Codex connect Peppol access points to ERP systems?

Rui Codex provides technical implementation support for system integrations, including connecting ERP and CRM systems with the software that receives invoices. It does not provide legal, tax or compliance advice, audits or certification. The scope depends on your systems and is agreed in a project consultation.

Conclusion

Receiving Peppol e-invoices in Belgium is a chain of four steps: the access point delivers the file, validation checks it, your team or system matches and approves it, and the ledger posts it. Most delays come from identifiers, rejected files and unclear matching rules rather than from the network itself. Start by agreeing identifiers and an exception owner, then automate matching once real supplier files have been tested. Rui Codex is led by a founder with 200+ projects delivered, and can help scope the integration. Request a project consultation at ruicodex.com to discuss your setup.

Sources

Tags: Peppol e-invoicing Belgium access point ERP integration accounts payable workflow automation API integration

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