Inbound E-Invoicing: The Accounts Payable Mandate Most Multinationals Miss

Every e-invoicing project plan starts on the accounts receivable side: which invoices do we issue, in which countries, in which format. It's the intuitive framing — mandates are about invoices, and "our invoices" means the ones we send.

It's also how multinationals end up non-compliant in countries where they barely sell anything. Several of the most important mandates regulate the inbound side — your ability to receive structured invoices from domestic suppliers — and in Europe's two largest economies, the receiving obligation arrived before any sending obligation. If you have a legal entity in Germany or (from September 2026) France, that entity has an inbound e-invoicing obligation today, regardless of how few invoices it touches.

Why Receiving Comes First

Mandate designers phase the sending obligation by company size because issuing structured invoices requires real system changes across millions of businesses. But phased sending only works if everyone can already receive — otherwise early adopters have no one to send to. So regulators flip the sequence: receiving becomes mandatory for everyone at once, sending phases in afterwards.

The consequence for a multinational: the first date on your compliance calendar is usually an AP date, not an AR date. And because the obligation is universal — not size-gated — it lands on holding companies, dormant-ish entities, and three-person country offices that no one thought of as having a compliance project.

The Inbound Obligations, Country by Country

Germany — live since January 2025. Every business established in Germany must be able to accept structured e-invoices (EN 16931 — XRechnung or ZUGFeRD) for domestic B2B transactions. There is no turnover threshold and no phase-in: the receiving obligation applies to all German businesses, while sending obligations phase in through 2027–2028. A supplier can send you a structured invoice today, and "we only process PDFs" is not a legally valid reason to reject it.

France — 1 September 2026. All French-established businesses — every size, from day one — must be able to receive e-invoices through the new PPF/PDP infrastructure. Only the sending obligation is phased (large and mid-size companies from 2026, SMEs from 2027). If you have a French entity, its inbound capability must exist this September even if its own sending deadline is a year away. See the France September 2026 checklist.

Belgium — live since January 2026. The B2B mandate runs over Peppol, and it takes two sides: your Belgian entity must be registered on the Peppol network to receive supplier invoices. An unregistered buyer breaks its suppliers' compliance as well as its own. Learn what a Peppol Access Point does.

Poland — live since February 2026. KSeF inverts delivery entirely: suppliers don't send invoices to you at all. They submit to the government platform, and your entity retrieves its purchase invoices from KSeF using its own credentials. If nobody in your Polish entity has KSeF access configured, you are not receiving your legally valid purchase invoices — and input VAT documentation depends on them.

Italy — live since 2019. Same clearance pattern: domestic supplier invoices exist only in SDI. Your Italian entity needs a recipient code (codice destinatario) or certified channel to receive them. This has been true for seven years and still surprises new market entrants.

Romania — live since 2024. Domestic B2B invoices flow through RO e-Factura, and buyers retrieve them from the platform. Notably, Romania's regime also reaches non-established companies with Romanian VAT registrations — a US company can have Romanian inbound exposure without a Romanian subsidiary.

The Volume Trap: Why Small Entities Are the Risk

The defining feature of receiving obligations is that they don't scale with volume. A German entity processing 15 supplier invoices a month has exactly the same legal obligation as one processing 15,000. That creates a cost-benefit inversion that catches tax teams off guard:

• The entities most likely to be forgotten are the ones with the least invoice volume — and they're fully in scope.
• A traditional per-country implementation project (ERP connector, vendor onboarding, testing cycle) can't be justified for 15 invoices a month, so the fix gets deferred — and the entity stays non-compliant.
• Meanwhile the failure mode is concrete: purchase invoices you never retrieve from KSeF or SDI, input VAT you can't evidence, suppliers whose own compliance depends on your Peppol registration.

This is exactly the scenario where per-country projects fail and a platform wins. Registering an entity on Peppol, configuring KSeF retrieval credentials, or standing up French PDP receiving shouldn't be a project — it should be a configuration step on infrastructure you already have. (It's also why Clearvo's free tier — 25 invoices a month, production access, no time limit — happens to fit low-volume entities exactly: compliance for the long tail of your group structure at zero marginal cost.)

What Inbound Capability Actually Requires

Receiving is technically simpler than sending — no format generation, no clearance workflow — but it has its own checklist:

• Network registration. For Peppol countries (Belgium, and the wider network): your entity registered with an Access Point, discoverable via SML/SMP. For clearance countries (Poland, Italy, Romania): platform credentials and retrieval configured per entity.
• Format handling. Inbound documents arrive as UBL 2.1, XRechnung, FatturaPA XML, or FA(2) — your AP process needs them parsed into something reviewable and postable, not saved as attachments.
• Routing into AP. Retrieved invoices must land in the AP workflow (ERP, approval flow, archive) with their legal metadata intact — including the government-assigned identifiers that make them valid documents.
• Archiving. Most regimes require the structured original to be stored, not just the human-readable rendering.

Clearvo handles the full inbound flow — Peppol receiving through our own certified Access Point, KSeF and SDI retrieval, normalized JSON via webhook into whatever your AP process runs on — through the same API that handles outbound across 32 countries.

The Upside Nobody Mentions

Inbound mandates force something AP teams have wanted for decades: suppliers delivering machine-readable, schema-valid, tax-authority-cleared invoice data instead of PDFs. Line items, tax breakdowns, and payment terms arrive as structured fields — no OCR, no manual keying, no "the PDF total doesn't match the line sum." Companies that treat the receiving obligation as plumbing to be minimised get compliance; companies that route the structured data into their AP automation get the efficiency dividend the mandate accidentally hands them. The same data also feeds VAT reconciliation — your input VAT position, evidenced from cleared source documents.

Start with the entity list, not the invoice volume: every entity in Germany, France, Belgium, Poland, Italy, and Romania has an inbound obligation with a date attached. For the broader picture of how these mandates fit together — and where your sending obligations sit — see the US company's guide to global e-invoicing mandates.