Peppol inbound inbox — receiving supplier invoices

Receiving becomes as important as sending

Belgium's structured B2B e-invoicing obligation, effective from 1 January 2026, reshaped how VAT-liable businesses exchange invoices. Much early guidance focused on outbound compliance: generating UBL documents and sending them through a Peppol Access Point. Equally critical is the inbound side: your organisation must reliably receive supplier invoices over Peppol, process them, and integrate them into accounting workflows.

Before the mandate, many SMEs treated supplier invoices as email attachments — PDFs filed manually or scanned into accounting software. Under the Belgian e-invoicing obligation, domestic B2B invoices between Belgian VAT-liable parties must travel as structured electronic documents on Peppol. The legal and operational centre of gravity shifts from the mailbox to a Peppol inbound inbox: a controlled reception point where network-delivered documents are validated, stored, and made available for business processing.

What the Peppol inbound inbox is

In Peppol terminology, inbound documents arrive at your organisation's Access Point and are forwarded to your business application. The inbox is the user-facing layer where those received documents appear before they are booked, approved, or archived.

Conceptually, the inbound inbox differs from a traditional email inbox in three ways:

1. Network delivery — Documents are routed through Peppol's four-corner model (sender Access Point → recipient Access Point → your software), not as arbitrary email attachments.
2. Structured payload — The primary artefact is a machine-readable XML document (typically UBL conforming to EN 16931 and Peppol BIS Billing), not an unstructured PDF.
3. Traceability — Delivery status, timestamps, and technical validation results are recorded at network level, providing an audit trail distinct from email headers.

A well-designed inbound inbox surfaces received invoices with their Peppol metadata: sender participant identifier, document type, delivery timestamp, and processing status. Users can review, approve, export, or link documents to existing accounting records without re-keying line items from a PDF.

Structured data versus PDF attachment

A common misconception is that Peppol invoices are "PDFs sent differently." In practice, the structured XML is the legally relevant payload under the mandate; a PDF, when present, is typically a human-readable rendering or supplementary attachment, not a substitute for the structured document.

See PDF versus structured invoice for a fuller comparison. The inbound inbox should expose both views where useful: structured fields for automation, and a rendered PDF or HTML preview for human verification.

When a supplier sends a Peppol invoice, your Access Point receives the XML, validates it against the declared document profile, and delivers it to your inbox. Accounting systems can then extract supplier name, VAT number, invoice number, dates, line items, tax breakdown, and payment references without transcription errors.

Matching inbound documents to accounting

Receiving a document into the inbox is only the first step. The operational value lies in matching it to your accounting workflow:

• Supplier recognition — Linking the Peppol sender identifier (often a Belgian enterprise number in scheme 0208) to a known supplier record in your chart of accounts.
• Purchase order or contract matching — Associating line items with expected purchases where your process requires it.
• Duplicate detection — Checking invoice number and supplier combination against already-booked documents.
• Approval routing — Forwarding to the responsible cost centre or manager before payment authorisation.

Structured data makes matching more reliable than OCR on PDFs because fields are unambiguous: amounts, VAT categories, and references are encoded, not inferred from layout. Mature Peppol integrations attempt automatic matching on arrival and flag exceptions for manual review.

Unmatched and orphaned inbound documents

Not every inbound document lands cleanly in accounting. Two failure modes deserve attention:

Unmatched documents arrive in the inbox but cannot be automatically associated with a supplier, purchase order, or expected transaction. Causes include unknown sender identifiers, incomplete supplier master data, or invoices for goods not yet recorded in the system. These documents remain visible in the inbox and require manual intervention: create or update the supplier, assign a cost centre, or reject the invoice with a formal response.

Orphaned documents are a more severe edge case: the Peppol network delivers a document to your Access Point, but your business application cannot associate it with any company account or tenant. This can happen when registration metadata points to the wrong Access Point endpoint, when a multi-entity setup lacks proper routing rules, or when a document arrives before onboarding is complete. Orphaned documents are received at network level but suspended from normal inbox processing until an administrator resolves the routing.

Both situations illustrate why inbound reception is not "set and forget." Monitoring the inbox, maintaining accurate supplier records, and reviewing unmatched or orphaned queues are part of compliant Peppol operations.

Discoverability: the prerequisite for inbound reception

You cannot receive Peppol invoices if counterparties cannot find you on the network. Discoverability depends on correct Peppol registration in Belgium: your enterprise number published in the SMP with the correct document types and Access Point endpoint.

Before the mandate, some businesses registered only for sending or ignored registration altogether. After 2026, suppliers look up your participant identifier — via Peppol participant lookup or their own software — and send structured invoices to the Access Point listed in your SMP entry. If you are not registered, or if your metadata is outdated, suppliers may fall back to non-compliant channels or encounter delivery failures.

Registration is therefore not a one-time checkbox. Changes of Access Point provider, company restructuring, or addition of document types (for example credit notes) require updated SMP metadata. Inbound reception starts with being correctly listed on Peppol.

Peppol inbound inbox

The reception layer where structured documents delivered over the Peppol network appear for review, matching, and integration into accounting workflows.

Relationship to OrdoGrid

OrdoGrid provides a Peppol inbound inbox where Belgian businesses receive supplier invoices as structured documents, with automatic supplier matching where possible and clear handling of unmatched or orphaned items requiring attention.