E-Invoice Processing Software 2026: Receiving and Rules

E-Invoicing Software: Choose by Country, Not by Brand

There is no single “best e-invoicing software” for every country. Belgium requires structured B2B invoices that can travel through Peppol. France requires an approved platform for its domestic reform. Poland routes in-scope invoices through KSeF. Germany uses an EN 16931-based model with transitional issuing rules. A product can be suitable in one market and unusable in another.

This guide therefore compares compliance routes, not a universal ranking of accounting brands. Start with the legal entity issuing the invoice, the customer type, and the destination country. Only then compare software.

Regulatory note: this page was checked against official sources on July 19, 2026. It is an operational software-selection guide, not tax or legal advice. Scope and exceptions depend on the transaction and entity; the linked authority always takes precedence.

The short answer

Your situation	Required route to verify	What the software must prove
Belgian VAT-taxable business invoicing another Belgian VAT-taxable business	Structured invoice; Peppol must be supported, unless both parties agree on an EN 16931-compliant alternative	Send and receive Peppol BIS invoices, Peppol registration, credit notes, status and accounting export
French VAT-taxable business	A platform on the French tax authority’s current approved list	Approved-platform status or a documented connection to one, receiving by September 1, 2026, issuing date for your company size, e-reporting where applicable
Polish taxpayer in KSeF scope	KSeF 2.0 and the FA(3) logical structure	Authentication, issue/receive through KSeF, KSeF number/UPO, offline modes, permissions and accounting sync
German domestic B2B invoicing	An e-invoice compliant with the applicable EN 16931 rules, subject to transition and exceptions	Receive compliant invoices now, validate structured data, preserve the original, and issue on the date that applies to the supplier
Several countries	A local route for each entity and transaction, coordinated with the ERP	Country-specific formats, identifiers, status mapping, tax reporting and a tested fallback process

Do not treat a vendor’s generic “e-invoicing ready” or “Peppol compatible” badge as sufficient evidence. Ask which legal entity, country, document type, direction and transport route the claim covers.

What counts as an electronic invoice?

An e-invoice is a machine-readable invoice whose data can be processed automatically. The European Commission defines it as an invoice exchanged in a structured electronic format. EN 16931 describes the core semantic data model; UBL and UN/CEFACT CII are two machine-readable syntaxes used to implement it.

A normal PDF attached to an email is electronic in the everyday sense, but it is not a structured invoice. A hybrid format such as Factur-X combines a human-readable PDF with embedded structured data. Whether a format is accepted still depends on the national regime and business case.

Keep these layers separate:

• Data standard: EN 16931 defines core invoice information.
• Syntax or format: UBL, CII, Factur-X, XRechnung, ZUGFeRD and Poland’s FA(3) describe how data is represented or constrained.
• Transport network: Peppol moves documents between certified service providers; it is not an invoice format by itself.
• Government platform: KSeF is Poland’s national system. France uses approved private platforms connected to its reform infrastructure.
• Business application: an accounting tool or ERP may create the invoice while another provider validates and transports it.

The European Commission’s e-invoicing overview explains EN 16931 and structured processing. OpenPeppol’s interoperability framework explains Access Points, address lookup, validation and the network’s four-corner model.

Country requirements checked for 2026

Belgium: Peppol is the default B2B route

Since January 1, 2026, structured invoices are required for transactions between Belgian VAT-taxable businesses. The Belgian administration says invoices must be capable of being sent and received through Peppol. An alternative transmission method is possible only by agreement between both parties, and the alternative format must comply with the European standard. A PDF, Word or Excel file alone does not satisfy the structured B2B rule.

Use the Belgian authority’s software-solutions page as the first filter. The authority explicitly warns that inclusion is not a qualitative assessment, certification or recommendation. The list also distinguishes tools that only send from those that send, receive and process invoices.

Before buying, verify:

• outbound and inbound Peppol BIS capability;
• registration of the correct Belgian enterprise identifier on Peppol;
• supplier invoices flowing into the accounting ledger, not only into a separate inbox;
• support for credit notes, attachments and rejection handling;
• what remains manual when an invoice falls outside domestic Belgian B2B scope;
• whether the advertised price includes the Peppol connection and invoice volume you need.

The official Belgian explanation of structured e-invoices and acceptable formats should be rechecked when the scope of a transaction is uncertain.

France: select an approved platform, not merely a compatible app

From September 1, 2026, all VAT-taxable businesses in France must be able to receive electronic invoices. Large companies and intermediate-sized companies must also issue them from that date. SMEs and micro-enterprises must issue them from September 1, 2027. E-reporting obligations can also apply to transactions outside the domestic B2B e-invoicing flow.

France distinguishes an approved platform from a compatible solution. Only an approved platform can perform all regulated transmission and reporting functions. An accounting or invoicing application can remain in the workflow if it connects to an approved platform, but “compatible” does not make the application an approved platform.

Use the tax authority’s live list of approved platforms, not a vendor roundup or an old list of provisional registrations. The authority says final approval follows technical and interoperability testing.

The buying checklist is different from Belgium’s:

• identify the approved platform that will legally carry the flow;
• if buying a compatible application, obtain the name of its approved-platform partner and the contractual responsibility of each provider;
• confirm the issue date that applies to your company size and the September 1, 2026 receiving path;
• test UBL, CII and/or the hybrid format used by your workflow, including Factur-X where supported;
• map invoice lifecycle statuses back into accounting and collections;
• verify e-reporting coverage for relevant B2C, international and payment data;
• keep Chorus Pro in the analysis for public-sector invoicing rather than assuming the domestic B2B route replaces it.

The French tax authority describes the platform roles and reform scope on its electronic invoicing and approved platforms page.

Poland: KSeF is not a Peppol substitute

Poland’s mandatory KSeF rollout began on February 1, 2026 for businesses whose gross 2024 sales exceeded PLN 200 million. It expanded on April 1, 2026 to other in-scope businesses. The smallest taxpayers can remain outside mandatory issuing until January 1, 2027 when the gross value of sales documented by invoices does not exceed PLN 10,000 per month. Mandatory receipt through KSeF began on February 1, 2026, subject to statutory exclusions.

KSeF issues, sends, receives and stores structured invoices using Poland’s logical structure. A Peppol connector on its own does not meet this workflow. Software should support the current FA(3) structure and the relevant KSeF 2.0 authentication, permissions, receipt and contingency processes.

Use the Ministry of Finance’s current KSeF scope and implementation dates as the source of truth. For software evaluation, verify:

• KSeF 2.0 rather than a retired or test-only integration;
• successful submission and retrieval of the KSeF number and official receipt confirmation;
• inbound invoice retrieval from February 1, 2026;
• permissions for staff, accountants and service providers;
• handling of offline24, offline and system-failure modes;
• corrections, QR verification and invoices with attachments where relevant;
• export of the authoritative KSeF data into the accounting system without duplicate posting.

The Ministry also provides free KSeF tools. That can suit a simple workflow, but it does not remove the need to assess accounting integration, permissions and operational controls.

Germany: receiving readiness came before universal issuing

Since January 1, 2025, domestic businesses must be able to receive e-invoices. The German Federal Ministry of Finance says an email inbox is sufficient for receipt, but the invoice still needs to meet the applicable structured requirements and be handled correctly downstream.

Transitional rules allow all issuers to use other invoices through the end of 2026. If the issuer’s prior-year turnover is no more than €800,000, that transition extends through the end of 2027. That means software selection should not reduce the rule to a misleading “mandatory for everyone in 2025” or a single universal 2028 date.

Check the Federal Ministry of Finance’s transition summary and obtain tax advice for exceptions. In a product review, test:

• receipt and validation of the structured formats used by your suppliers;
• preservation of the original structured invoice, not only a rendered PDF;
• correct ingestion of tax, payment, reference and line-item fields;
• issuing readiness for the date that applies to the supplier;
• treatment of rejected, corrected and out-of-scope invoices;
• compatibility with the accounting and archiving controls already in use.

How to shortlist software without trusting marketing claims

1. Write a one-page scope matrix

List each issuing legal entity, VAT registration, customer type and destination. Separate domestic B2B, B2G, B2C and cross-border flows. Record monthly inbound and outbound volume, currencies, invoice formats, credit-note volume and ERP owner.

This prevents a common procurement error: choosing a product for an entire group after seeing one country’s logo on a vendor page.

2. Verify the regulated route

For Belgium, check the official software information and the actual Peppol registration path. For France, check the current approved-platform list. For Poland, verify KSeF 2.0 and FA(3). For Germany, verify EN 16931 processing and the applicable transition.

Ask the supplier to demonstrate the route live. A screenshot of a settings page or a roadmap item is not proof of production availability.

3. Test the complete invoice lifecycle

A connector that can send one valid invoice may still fail the operational workflow. Test creation, validation, transport, acknowledgement, rejection, correction, receipt, posting, payment status and export. Include one invalid invoice to see whether the error message is usable.

4. Calculate total cost for your real volume

Do not compare only monthly subscription prices. Request a written quote that separates:

• base software and required plan;
• setup, implementation and country activation;
• Access Point or approved-platform fees;
• included inbound and outbound volume;
• overage and archive charges;
• ERP connector, sandbox and API access;
• support level and additional legal entities;
• exit costs and data export.

Calculate annual total cost / annual processed invoices, but keep fixed implementation cost visible. A low per-invoice number can hide a large first-year deployment cost.

A manual acceptance test to run with every finalist

Clearpick has not opened vendor sandboxes or sent live regulated invoices for this page. The protocol below is a scenario for your finance and accounting team to execute during a trial or supplier-led demonstration. Supplier demonstrations should be labelled as such; they are not independent hands-on tests.

Use a fictional company and fictional counterparties in a non-production environment:

1. Create: enter a multi-line B2B invoice with tax, payment terms, buyer reference, discount and one attachment.
2. Validate: inspect which rule fails when a mandatory buyer identifier is removed.
3. Send: submit through the country’s actual test route, not by emailing a PDF.
4. Track: record timestamps and all lifecycle statuses. Confirm the external acknowledgement or government identifier where the regime provides one.
5. Reject and correct: reject the invoice, fix it, then issue the correct document or credit note without overwriting the audit trail.
6. Receive: retrieve an inbound structured invoice and post it to a test ledger. Compare supplier, tax, line, reference and payment fields with the source data.
7. Export: export both the original structured file and a readable rendering, plus the event history.
8. Interrupt: simulate an unavailable API or network and document the permitted fallback, resubmission and duplicate-prevention process.

Run the scenario separately for each country and transaction type in scope. Record the product version, environment, date, tester, result and anything the supplier performed on your behalf.

Evidence to request from a vendor

Claim	Evidence worth accepting	Evidence that is insufficient alone
“Peppol ready”	Named certified service provider, supported country, send/receive directions, document types and production demonstration	A Peppol logo without scope
“Ready for France”	Appearance on the current approved-platform list, or a named approved partner and documented connection	“PDP-ready” copy written before final approval
“KSeF compliant”	Current KSeF 2.0/FA(3) documentation, successful test submission, receipt and contingency workflow	A connector for KSeF 1.0 or a roadmap
“EN 16931 compliant”	Supported syntax and CIUS, validation report and sample structured file	A PDF invoice template
“End-to-end automation”	Demonstrated inbound posting, status sync, correction, exception and export	Sending one happy-path invoice

Common selection mistakes

• Buying PDF invoicing instead of structured invoicing. A polished PDF editor does not provide a regulated transport route.
• Confusing Peppol with universal compliance. Peppol is a network and specification ecosystem; national tax platforms, reporting and country rules still apply.
• Checking only outbound invoices. Receiving became mandatory earlier than issuing for some businesses, and inbound accounting can be the larger workload.
• Assuming listing means endorsement. The Belgian authority says its software list is not a certification or recommendation.
• Ignoring exceptions and fallback modes. Consumer, foreign, public-sector and system-outage flows can follow different rules.
• Trusting a future roadmap. A mandate date requires production capability, contractual support and an implemented internal process.
• Letting the provider own the only copy. Confirm how original structured files, acknowledgements and audit history can be exported when the contract ends.

Which route should you choose?

Choose a lightweight invoicing application connected to the required route when one small entity has simple invoices and no complex approval process. Choose an accounting platform with an embedded country connection when the ledger is the operational source of truth and the connection covers both directions. Choose a specialist e-invoicing provider when several ERPs, countries or formats must be orchestrated. Use a broader AP automation platform only when approval, matching and supplier operations justify the extra implementation work.

The winner is therefore not the provider with the longest feature list. It is the smallest reliable architecture that passes every in-scope country test, returns usable statuses to accounting, survives an outage and allows a complete export.

Frequently asked questions

Is a PDF invoice an e-invoice?

A normal PDF is not a structured e-invoice. Some hybrid formats, including Factur-X, combine a readable PDF with embedded structured data. Acceptance depends on the relevant national rules and profile.

Does Peppol make software compliant across Europe?

No. Peppol provides interoperable document specifications and a network between certified service providers. Each country can add identifiers, validation rules, reporting or a different government platform. Country scope still has to be verified.

Must every French business issue e-invoices in September 2026?

No. All in-scope businesses must be able to receive them from September 1, 2026. Large and intermediate-sized businesses issue from that date; SMEs and micro-enterprises issue from September 1, 2027. Scope and e-reporting need transaction-level review.

Is KSeF the Polish version of Peppol?

No. KSeF is Poland’s national system for structured invoices. It has its own logical structure, identifiers, permissions and operational modes. A generic Peppol connection is not evidence of KSeF support.

How should a company compare prices?

Ask for a quote based on legal entities, countries, inbound and outbound volumes, ERP connectors, implementation, support, overages and archive/export. Compare first-year and recurring annual cost separately, then calculate cost per processed invoice.

For how Clearpick distinguishes official documentation, supplier claims and hands-on evidence, see our comparison methodology.