Tax Compliance Under Pressure: Why Companies Struggle with E-Invoicing, and How to Get to Compliance by Design
Why e-invoicing and real-time tax reporting stall in so many companies, how SAP Document and Reporting Compliance helps, and how 30 Advisory takes you to compliance that runs as a routine, not as an emergency project.
Client dossier · September 2026 · CFOs, Tax, Finance IT
58%
of large companies call tax mandates complex for their business
Sovos, 2026 · n=300
43%
name ERP integration as the top barrier to e-invoicing
Sovos, 2026 · n=300
37%
are strongly confident in their master-data quality for tax
Vertex, 2026
6%
of German firms surveyed meet the 2027 e-invoice issuing rules
Quadient, 2026 · n=300
A grace period postpones the fine, not the consequence. France, Poland, Belgium and Spain have softened or delayed enforcement, but a rejected e-invoice is still an unpaid invoice.
Three Questions, Three Answers
Every country has its own format, platform and timeline. Master data was never built for real-time validation. ERPs are old or heavily customised, and nobody owns the problem across Tax, Finance and IT.
E-invoices and statutory reports inside the ERP, in one framework. Country content maintained by SAP. A status for every document and a cockpit to fix errors before they cost money.
We map every entity against two clocks: its mandate date and its ERP support end. We design, build and run the compliance layer in SAP, with Finance and Tax at the table, not only IT.
Execution Capacity Is the Bottleneck
Five independent surveys from 2025–2026 point the same way. Optimism about e-invoicing fell from 59% to 36% between the 2024 and 2026 editions of Deloitte's Global Tax Policy Survey (1,010 leaders, 28 jurisdictions).
Silos and weak master data break real-time validation.
Every new mandate becomes an integration project.
Half the time goes to routine work while the rules keep moving.
Three in four leaders say it holds back strategic decisions.
Six Root Causes
What we see behind almost every struggling programme.
One format, network and timeline per country: SdI, KSeF, Peppol, the French platforms, XRechnung, Verifactu. Result: rising run cost, no single view.
Wrong VAT IDs, addresses, tax codes and Peppol IDs: tolerated on paper, rejected in seconds. Result: rejected invoices, delayed cash.
SAP ERP (ECC) near the end of maintenance, custom middleware, point-to-point interfaces. Result: building twice.
Tax thinks IT owns it, IT thinks it is a tax topic, and finance operations lives with the result. Result: surprises at go-live.
Spreadsheet reconciliations, portal re-keying and knowledge held by one or two experts. Result: errors and key-person risk.
'There is a grace period' is read as 'we can start later'. The obligation starts anyway. Result: compressed, expensive projects.
Confirmed in practice: the most common Poland KSeF mistakes of 2026 were master data, format mapping, shallow ERP testing, user permissions and unadapted processes (VATupdate, July 2026).
The 2025–2030 Pressure Map
Key e-invoicing and ERP dates for European groups, as they stood on 23 September 2026.
Germany: receiving mandatory
Every business must be able to receive e-invoices from 1 January.
Belgium, Croatia, Poland and France go live
Belgium and Croatia: B2B e-invoicing live (1 January) · Poland: KSeF live (February / April) · France: all receive; large and mid-size issue (1 September).
The year the two clocks collide
Germany: companies above €800k turnover issue (1 January) · Spain: Verifactu (1 January / 1 July) · France: SMEs issue (1 September) · Spain: B2B above €8M (October, expected) · SAP ERP 6.0: mainstream maintenance ends (31 December).
The second wave arrives
Germany: all companies issue (1 January) · Poland: KSeF fines apply (1 January) · Belgium: e-reporting expected · Spain: B2B for all companies (expected).
EU ViDA
Digital reporting of intra-EU transactions (1 July); national systems converge by 2035.
Already live
Italy (SdI, 2019) · Romania (e-Factura, 2024) · Türkiye (e-Fatura / e-Arşiv, thresholds falling) · Spain's SII for large taxpayers. Spain's B2B dates depend on the ministerial order being published in the BOE. Dates move often: confirm them per entity.
Grace Periods Are Not Safety
Authorities softened enforcement in 2026; the consequences have not changed.
Live since 1 September 2026, with a 'right to make mistakes' in 2026. Statutory penalty: €50 per invoice.
KSeF live; no fines before 1 January 2028 (announced 16 September 2026).
Tolerance ended on 31 March 2026; fines are now €1,500, €3,000 and €5,000.
Verifactu moved to 2027; up to €50,000 a year for non-compliant software.
A rejected e-invoice is an unpaid invoice
From day one: the customer's system never receives or books it.
Your customer's VAT deduction is at risk
Non-compliant invoices create friction with key accounts.
The authority already has your data
Your invoice data is compared with your returns.
The second clock: SAP ERP 6.0 mainstream maintenance ends on 31 December 2027. After extended maintenance there are no new legal updates, and compliance content is a legal update.
What Non-Compliance Really Costs
Fines are the smallest line on the bill. An illustrative example, not a benchmark: 20,000 B2B e-invoices a month, €5,000 on average, 2% rejected.
400
invoices a month to investigate and resend
≈130 h
of rework a month: close to one full-time person
≈€2M
of receivables paid 10 days late, every month
Rejected outbound e-invoices raise days sales outstanding and tie up working capital.
Unstructured inbound invoices mean manual keying, late payment and duplicate-payment risk.
Invoice data that doesn't match the ledger triggers queries, assessments and interest.
Reports rebuilt in spreadsheets add days to the close; new entities wait for 'the e-invoicing part'.
None of it appears as a tax penalty; all of it shows up in working capital and headcount.
How SAP DRC Helps
SAP Document and Reporting Compliance: two halves, one framework, inside the ERP. It reads your billing documents, supplier invoices, journal entries and master data, and connects to tax-authority platforms, the Peppol network, certified providers, customers and suppliers.
Electronic documents
Create, validate, send, receive, track the status of and reprocess every e-invoice.
Statutory reporting
Select, generate, review and submit: VAT returns, SAF-T and listings.
A new country means activating a scenario, not a new build.
Accounts receivable sees rejections the same day and fixes them in SAP.
Validation and consistency checks, where SAP delivers them.
Traceable back to each document, with fewer spreadsheets.
What DRC Solves — and What It Doesn't
What it provides
For fragmentation: country scenarios maintained by SAP in one framework. For rejected invoices: lifecycle status and reprocessing per document. For poor master data: validation before sending. For manual statutory reports: guided generate-and-submit from the ledger (S/4HANA). For custom middleware: standard connectivity through the cloud edition, Integration Suite and Peppol.
What it does not do
Clean your master data: bad VAT IDs in, rejections out. Decide tax positions: VAT treatment stays with your tax function. Own the process: someone must watch the cockpit and act.
Where you run it matters
On SAP ERP (ECC), DRC covers electronic documents only, with no statutory reporting; on S/4HANA, both halves. Country coverage moves by scenario and release: SAP lists DRC scenarios in 40+ countries and regions, and partners cite 55+. Always confirm it against SAP Notes and the Regulatory Change Manager. More detail in our SAP DRC article.
Choosing a Setup: Four Routes
Decide per entity, not per group.
The entity is on S/4HANA, or will be before the mandate applies. Native DRC for both halves.
The mandate lands before the migration. DRC eDocuments on ECC, designed to lift into S/4HANA later.
Several mandates plus the 2027 maintenance end: bring that entity's S/4HANA date forward.
DRC plus a certified third-party provider, where the country requires one or coverage is missing.
The decision rule: two clocks per entity
When does the mandate apply? When does that ERP stop receiving legal updates? Mandate first: you need an answer that doesn't wait for the migration. Migration first: do it once, in S/4HANA.
Five Questions to Take Back to Your Team
Answer honestly. Your answers never leave your browser: nothing is sent or stored anywhere.
Answer all five questions to see where to start.
Uncertain answers: 0/5
You have the foundations
You know what applies, when, and who answers for it. Keep the monitoring routine and review the design before each new mandate: an independent second opinion is cheap compared with a failed go-live.
A few blind spots
Close them before your next mandate date: they are exactly where go-live surprises come from. A focused conversation about those answers is usually enough to set the priorities.
Start with the diagnostic, before any build
With three or more uncertain answers, any build starts from assumptions. A readiness diagnostic puts every entity against its two clocks and tells you where to start.
How 30 Advisory Takes You to Compliance
From exposed to compliant in five phases, with a clear deliverable in each.
We work where tax law, finance processes and SAP meet, so compliance becomes a routine your team runs, not a project it survives.
Readiness heatmap
An entity × mandate × ERP-clock map, a rejection-rate and master-data baseline, and owners and governance agreed.
Target design and roadmap
A route per entity, country scenarios confirmed in SAP, and a fit-gap across data, process and roles.
Tested solution
DRC, BTP and Peppol configuration, master-data remediation, and end-to-end tests of real rejection cases.
Live, with buffer before the deadline
Cutover and hypercare, cockpit routines for AR, AP and tax, and training by role.
Compliance as routine
KPI monitoring, regulatory watch per country, and the next country as a scenario, not a project.
Where to Start: the Readiness Diagnostic
Fixed scope and fixed price, scoped in a free one-hour session.
What you receive
A heatmap of every entity against its mandates and its ERP maintenance date. A gap list across data, process, system and ownership, with the six root causes scored. The recommended route per entity and the order to tackle them. A roadmap with effort ranges and the decisions management must take. A one-page summary for the CFO or the board.
What we need from you
The list of entities and countries. Your ERP landscape and S/4HANA plans. The mandates already live and how they were solved. Any rejection or error figures you have.
Example diagnostic output for a hypothetical group, for illustration only: dates and routes are examples.
Ways to Work with Us
From a first diagnostic to running compliance as routine.
Heatmap, gap list, route per entity and roadmap.
Design, DRC configuration, connectivity, testing and go-live.
Template design, rollout waves and alignment with the migration.
A second opinion on design, scope, plan and test coverage.
Monitoring, KPI reporting, regulatory watch and new scenarios.
Founder-led: senior people from scoping to go-live
Finance, tax and SAP in one team
Multi-country: Italy, Türkiye, Spain
One roadmap: compliance, finance and migration
Our scope, honestly: we are SAP finance and compliance advisors, not a tax law firm. Tax positions stay with your tax advisers; we turn their decisions into a working process in SAP.
Surveys: Sovos, finance leaders tax compliance survey (BusinessWire, May 2026) · Deloitte, 2026 Global Tax Policy Survey (June 2026) · EY, 2025 Tax and Finance Operations Survey · Vertex, e-invoicing compliance in 2026 (via VATupdate, July 2026) · Quadient survey of 300 German companies (2026). Regulation: vatcalc (Poland KSeF penalty deferral, September 2026; France penalties) · Sovos (France go-live) · EY Belgium and Vertex (Belgium timeline and penalties) · Avalara (Germany) · BDO (Spain Verifactu) · VATupdate (KSeF common mistakes, July 2026) · European Commission (ViDA). SAP: SAP Community DRC topic page · SAP Help Portal (DRC cloud edition) · SAP Press, INSIRE and Fink ITS on DRC scope and roadmap · ERP Research on SAP ERP 6.0 maintenance dates.
Prepared by 30 Advisory, September 2026, from public sources. Information only — not legal or tax advice. Regulatory dates, penalties and SAP scope change often and must be confirmed per entity, country and software release. Survey results are quoted as published by their authors. The cost example and the heatmap are hypothetical. SAP, SAP S/4HANA and other SAP products are trademarks of SAP SE; 30 Advisory is independent of SAP.