Sell accountants an exception-management layer for the EU e-invoicing mandate wave instead of trying to replace their accounting stack.
One-line thesis: Build a lightweight exception-management and client-readiness layer for SMB accountants and multi-entity finance teams facing the 2026-2027 EU e-invoicing mandate wave.
Small and mid-sized accounting firms, outsourced CFO/bookkeeping shops, and finance managers who oversee many small legal entities across Belgium, France, and Poland.
The underlying mandate is real and dated, not speculative. The European Commission page for Belgium says B2B eInvoicing became mandatory from 1 January 2026 for Belgian VAT-registered businesses. The European Commission page for France says all businesses must be able to receive eInvoices from September 2026, with phased B2B rollout. The Poland KSeF guide says the largest taxpayers were pulled in from 1 February 2026 and every VAT-registered business from 1 April 2026, with schema and authentication requirements.
The buyer pain is not “we need another ERP.” It is operational readiness and exception handling. Banqup’s Belgium article frames penalties up to €5,000 plus VAT deduction and payment-delay risk for non-compliance. Reddit threads in Belgian freelancer communities show confusion about which invoicing software actually works with Peppol and how accountant-led workflows should be set up. Microsoft Dynamics and SAP community posts show concrete implementation breakage: Peppol/XML format issues, address-field problems, export failures, and country-specific compliance edge cases.
That combination matters: hard deadline plus multi-client operational mess. Accountants are the natural aggregation point because one accountant may need to drag dozens or hundreds of small clients through compliance at once.
This is a timing trade, not an evergreen workflow idea. Belgium is already live, France is in phased rollout during 2026, and Poland’s KSeF deadlines are now active. That means buyers are moving from “we should prepare” to “we are already behind” and implementation bugs are surfacing in real production environments.
Start with an accountant dashboard, not invoice transport itself. Core v1:
This is much easier than replacing ERP/accounting systems. It is a coordination and failure-management layer.
Direct outreach to bookkeeping/accounting firms serving Belgian and French SMBs; accounting LinkedIn; local accountant associations; integration consultants posting about Peppol/KSeF problems; communities already discussing Winbooks, Odoo, Dynamics, and SAP rollout issues.
Today the substitute is a mix of ERP vendor modules, Peppol access providers, email, spreadsheets, and the accountant manually chasing each client. Existing e-invoicing vendors validate budget, but most positioning is transport/compliance infrastructure or enterprise workflow, not accountant-first exception management for many small clients.
This could collapse into a feature inside existing accounting software or Peppol providers. Country-by-country nuance can expand scope fast. If the buyer really wants end-to-end filing and transport rather than readiness/exception handling, a small standalone tool may be too narrow. The opportunity is strongest if the product stays in the “orchestration and exception resolution” lane rather than trying to become another invoicing network.