E-invoicing reform simulator

How much revenue do you expose to invoice rejection?

An e-invoice sent to a third party with incorrect data (SIREN/SIRET, VAT, address) comes back to you, rejected by the platform or refused by the customer. Receiving becomes mandatory in September 2026, issuing for all SMEs in September 2027. Estimate the revenue at stake with just two figures.

Your activity

Invoices issued per month 200

Your outbound B2B invoices over a representative month.

Average amount per invoice 500 €

Average gross amount of an invoice.

Share of records that would block an invoice

Share of your third parties whose record carries a blocking anomaly (closed establishment, ceased company, missing SIRET, incorrect VAT number…). Pick the case closest to yours.

Estimate

… of revenue blocked per year

… per month

… blocked invoices / month

… invoiced revenue / month

Until these third parties are fixed, their invoices may be rejected by the platform or refused by the customer: that revenue is collected late, or even lost.

Check my third parties See plans

Method: revenue at stake = invoices/month × average amount × share of blocking records (×12 for the annual figure). The shares offered were measured by TierSafe in October 2026 on 21,409 records from 5 real customer files: on average 29% of records carried a blocking anomaly, from 24% for the cleanest file to 58% for the most degraded. A share of records is not a share of invoices: a customer who receives many invoices weighs more than another. The calculation runs entirely in your browser, no data is sent.