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 briefing · Updated October 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.
Four things to do this quarter
- List every entity, its mandates and their dates.
- Measure today's e-invoice rejection rate and master-data gaps.
- Put the ERP maintenance date next to each mandate date.
- Name one owner across Tax, Finance and IT.
Who Is Most Exposed Right Now
| Profile | Why the pressure is highest | First move |
|---|---|---|
| Multi-country groups still on SAP ERP (ECC) | Mandates keep arriving while legal updates for the ERP run out after 2027; statutory reporting in DRC needs S/4HANA. | Put both clocks side by side, entity by entity. |
| German entities above €800k turnover | Must issue structured e-invoices from 1 January 2027, and very few are ready today. | Confirm format and channel; test with top customers. |
| French, Polish and Belgian subsidiaries | Mandates are live. France and Poland have softened enforcement, which invites delay; Belgium already fines. Customers expect compliant invoices everywhere. | Measure rejections; close gaps before fines apply. |
| Spanish companies | SII already live, B2B e-invoicing from 6 October 2027 (above €8M) and 6 October 2028 (the rest), and VeriFactu in 2027 under current law, with a move to October 2028 announced: three regimes on one ERP. | Design one Spanish compliance model, not three. |
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.
Readiness is lower than confidence
37% are strongly confident in their tax master data (Vertex), only about 25% are fully deployed on S/4HANA (TJC Group) and just 6% of German firms surveyed already meet the 2027 issuing rules (Quadient). Vertex also finds that fewer than half of organisations keep a central master-data registry, and counts close to 100 countries that have implemented or announced e-invoicing mandates.
The load keeps growing
84% expect more tax disclosure within two to three years, and around 40% call rising compliance their biggest single challenge (Deloitte). 42% worry about rising technology and staffing costs (Sovos), and 61% expect senior retirements to hit the function (EY).
AI is coming, on top of weak data
86% worry about data security in AI tools and 40% plan to evaluate AI tools next year (Sovos). 85% expect AI compliance software to help (Deloitte). Yet 75% are still in the earliest GenAI phase and 80% have too little AI-ready data (EY).
From Signals to Causes
| Signal | Points to |
|---|---|
| Rules change too fast; mandates are complex | Fragmentation (cause 1) |
| Low confidence in master data; data in silos | Master data not fit for real time (cause 2) |
| ERP integration is the top barrier | Legacy ERP and integration (cause 3) |
| Compliance holds back strategic decisions | Ownership gap (cause 4) |
| Half of all time on routine tasks; retirements | Manual work, thin teams (cause 5) |
| Confidence higher than actual readiness | False comfort (cause 6) |
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. Each solved separately, often with a different provider. Result: rising run cost, inconsistent controls, no single view. First to notice: group tax and IT.
Wrong or missing VAT IDs, addresses, tax codes, units, Peppol IDs and payment terms: tolerated on paper, rejected by an automated validator in seconds. Result: rejected invoices, delayed cash, manual rework. First to notice: accounts receivable and payable.
SAP ERP (ECC) near the end of mainstream maintenance, custom middleware, point-to-point interfaces nobody wants to touch. Every new mandate becomes a development project. Result: building twice, once on the old ERP and again after migration. First to notice: IT.
Tax thinks IT owns it, IT thinks it is a tax topic, and finance operations lives with the result. Requirements are written by one team and tested by another. Result: surprises at go-live, on the legal deadline with no buffer. First to notice: nobody, until go-live.
Spreadsheet reconciliations, portal re-keying and knowledge held by one or two experts close to retirement. Result: errors, key-person risk and no time for the next mandate. First to notice: the head of tax.
'There is a grace period' is read as 'we can start later'. The obligation starts anyway; only the fine moves. Result: compressed, expensive projects and rushed testing. First to notice: the CFO, at budget time.
The pattern
Causes 1 to 3 are technical and visible; they get the budget. Causes 4 to 6 are organisational and invisible; they decide whether the project lands. That is why we treat e-invoicing as a finance operating-model change delivered through SAP, not an interface project. Every VATupdate, Vertex and INSIRE analysis we reviewed points the same way: close cooperation between finance, tax, legal and technology is the difference.
Quick test
If you cannot name one person who owns e-invoicing across all your entities, you have cause 4.
Confirmed in practice: Poland's KSeF in 2026
Poland made structured e-invoicing through KSeF mandatory for large taxpayers on 1 February 2026 and for most others on 1 April 2026. The mistakes practitioners report most often map almost one to one onto the causes above (VATupdate, July 2026):
- Master data not checked before the first submission (cause 2).
- Mapping not aligned with the official FA(3) structure (causes 1 and 3).
- ERP-to-KSeF testing too shallow, not end to end (cause 3).
- User permissions in KSeF poorly managed (cause 4).
- Processes such as approvals and document handling never adapted (causes 4 and 5).
The 2025–2030 Pressure Map
Key e-invoicing and ERP dates for European groups, as they stood in October 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) · Poland: the smallest taxpayers join and, under current law, penalties start (1 January) · Spain: VeriFactu (1 January / 1 July under current law; a move to October 2028 is announced) · France: SMEs issue (1 September) · Spain: B2B above €8M (6 October) · SAP ERP 6.0: mainstream maintenance ends (31 December).
The second wave arrives
Germany: all companies issue (1 January) · Poland: KSeF penalties (1 January, under bill UD477, not yet enacted) · Belgium: e-reporting (1 January, planned) · Spain: VeriFactu (October, announced) · Spain: B2B for all other companies (6 October).
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 have been set since Order HAC/1028/2026 was published in the BOE on 5 October 2026; the VeriFactu move to October 2028 is announced but not yet in the BOE. Dates move often: confirm them per entity.
Country by Country
| Country | Model and where it stands | Next milestone | Enforcement signal |
|---|---|---|---|
| Italy | Clearance (SdI); B2B and B2G live since 2019 | Alignment with ViDA | Mature regime; penalties apply |
| Poland | Clearance (KSeF 2.0); live for large taxpayers since 1 February 2026 and for most others since 1 April 2026 | The smallest taxpayers join on 1 January 2027 | Soft: penalties suspended through 2026; extension to 1 January 2028 proposed (bill UD477, not yet enacted) |
| Belgium | Peppol network; B2B live since 1 January 2026 for all sizes; tolerance ended on 31 March 2026 | Near-real-time e-reporting, planned from 1 January 2028 | Active: escalating fines of €1,500, €3,000 and €5,000; VAT deduction at risk |
| Croatia | Fiscalisation 2.0; B2B e-invoicing live since 1 January 2026 | — | Live |
| Romania | Clearance (RO e-Factura); B2B live since 2024 | — | Live |
| France | Approved platforms, with the public portal as directory and data hub; since 1 September 2026 all firms must receive, and large and mid-size firms must issue | SMEs and micro-businesses issue from 1 September 2027 | Soft: a 'right to make mistakes' in 2026; by statute, €50 per invoice and €500 per missed e-reporting transmission, each capped at €15,000 a year |
| Germany | Structured invoice to EN 16931 (XRechnung, ZUGFeRD); receiving mandatory since 1 January 2025 | Issuing: turnover above €800k from 1 January 2027; all from 1 January 2028 | A plain PDF no longer counts as an e-invoice |
| Spain | SII · VeriFactu · B2B e-invoicing (Crea y Crece); SII live for large taxpayers; the B2B order was published in the BOE on 5 October 2026 | B2B from 6 October 2027 (above €8M) and 6 October 2028 (the rest); VeriFactu on 1 January / 1 July 2027 under current law, with a move to October 2028 announced | Up to €50,000 a year for using non-compliant invoicing software |
| Türkiye | Clearance (e-Fatura, e-Arşiv); long established | Thresholds keep falling | Live |
| EU (ViDA) | Digital reporting of intra-EU B2B transactions; adopted in 2025 | 1 July 2030; national systems converge by 2035 | The framework every regime above will align to |
French penalty amounts as reported by vatcalc.
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; penalties are suspended through 2026, and in September 2026 an extension to 1 January 2028 was proposed (bill UD477, not yet enacted).
Tolerance ended on 31 March 2026; fines are now €1,500, €3,000 and €5,000.
VeriFactu: 2027 in the law today, with a move to October 2028 announced (not yet in the BOE); 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 obligation still applies
France asks companies to show they are actively working towards compliance; persistent non-engagement can still be sanctioned.
Cash doesn't wait
Customers' AP teams increasingly reject invoices that don't arrive through the mandated channel.
Timelines compress
A 12-month deferral used for nothing becomes a 3-month project at premium rates.
The second clock: SAP ERP 6.0 mainstream maintenance ends on 31 December 2027. Optional extended maintenance runs 2028–2030 at a surcharge; after that, customer-specific maintenance brings 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 at 20 minutes each: 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. Where it shows: AR ageing and the treasury forecast.
Unstructured inbound invoices mean manual keying, late payment, lost discounts and duplicate-payment risk. Where it shows: the AP backlog and supplier complaints.
The authority already holds your invoice data and compares it with your returns: if it doesn't match the ledger, queries, assessments and interest follow. Where it shows: tax audit files.
Reports rebuilt in spreadsheets add days to the close; new entities wait for 'the e-invoicing part', and 75% say compliance already delays decisions (Sovos). Where it shows: the close calendar, strategy and M&A timelines.
A non-compliant invoice can put the customer's VAT deduction at risk: commercial friction, credit notes and re-issuing. Where it shows: key-account relationships.
Three questions for your next finance review
- What is our e-invoice rejection rate per country, and who sees it?
- How long does it take from rejection to corrected invoice?
- Which statutory reports are still rebuilt in spreadsheets?
If the answer to the first question is 'we don't know', that is the first finding. You cannot manage a rejection rate you cannot see, and that visibility is exactly what a document-level compliance framework such as SAP DRC provides.
The Later a Gap Is Found, the More It Costs
| Where the gap is found | Who finds it | What it takes to fix | Relative cost |
|---|---|---|---|
| Diagnostic and design | The project team, on paper | A decision and a design change | Low |
| Testing | Testers, with sample invoices | Data clean-up and configuration, before anything is live | Moderate |
| After go-live | Customers, suppliers, AR and AP | Rework on live documents, credit notes, re-issuing and extended hypercare | High |
| Tax audit | The tax authority | Reconstructing history, assessments, interest and possible penalties | Highest |
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.
Monitor
The eDocument Cockpit, Manage Electronic Documents and the statutory-reporting apps: one status per document and per report.
Connect
DRC cloud edition on SAP BTP, including Peppol exchange: SAP's strategic transmission channel.
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.
The Life of One E-Invoice
Outbound e-invoice
Created, validated, sent, accepted, archived. If the authority or network rejects it, the document stops in an error status with the reason attached. AR corrects the data or the billing document and resubmits from the cockpit: no email chain, no portal re-keying.
Inbound supplier invoice
Received, checked, matched, posted, archived. Structured invoices arrive with their data already readable, so AP matches them against purchase orders and posts them in SAP, with the original eDocument linked for audit. Exceptions, not the whole volume, go to people.
What DRC Solves — and What It Doesn't
What it provides
For fragmentation: country scenarios maintained by SAP in one framework, with the Regulatory Change Manager to track upcoming legal changes. For rejected invoices: lifecycle status and reprocessing per document, outbound and inbound. For poor master data: validation before sending, and consistency checks against authority data where SAP delivers them. 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. For thin teams: automation of routine steps, with AI-supported trend analysis of statutory reports in beta for S/4HANA Cloud since December 2025.
What it does not do
Clean your master data: DRC validates data but doesn't fix it; bad VAT IDs in, rejections out, and data remediation is its own workstream. Decide tax positions: VAT treatment, invoice content rules, self-billing and exemptions stay with your tax function and advisers. Own the process: someone must watch the cockpit, fix rejections and answer the authority; without a named owner, statuses just accumulate.
What You Get Depends on Where You Run It
| Platform | eDocuments | Statutory reporting | Notes |
|---|---|---|---|
| SAP ERP 6.0 (ECC) | Partial | No | eDocument framework only, fewer scenarios, SAP GUI cockpit, no authority-data consistency checks. Legal updates stop after maintenance ends. |
| S/4HANA (on-premise / private cloud) | Yes | Yes | Both halves, Fiori apps, widest scope, full extensibility. |
| S/4HANA Cloud, public edition | Yes | Yes | Nearly all tasks; extensibility limits apply. |
| Central Finance | No | Yes | The mirror case: reporting from the central system, while documents stay in the source ERPs. |
| DRC cloud edition (BTP) | Exchange layer | Exchange layer | Transmission to authorities and Peppol; used with S/4HANA and, for some scenarios, SAP ERP. |
Country coverage
SAP's community pages list DRC scenarios across 40+ countries and regions; partners cite 55+ countries and 500+ scenarios. Coverage is defined per scenario, per product and per release, and it keeps moving. We confirm it country by country against SAP Notes and the Regulatory Change Manager, never from a headline number. 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. Large groups usually need both answers, for different entities.
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.
Five questions are a first look. For the full picture, the DRC readiness scorecard covers fifty statements across ten dimensions and returns a score out of 100 and the red flags that need action.
Five more for the working session
- Customer and supplier VAT IDs are validated automatically.
- Statutory reports are produced from the system, not spreadsheets.
- New countries use standard SAP scenarios, not custom code.
- We test end to end, including inbound invoices.
- Compliance and the S/4HANA migration share one roadmap.
KPIs worth a dashboard
- E-invoice rejection rate, by country.
- Time from rejection to corrected invoice.
- Share of inbound invoices received structured.
- Statutory reports filed on time with no manual adjustment.
- Master-data completeness: valid VAT ID, address and tax code.
- Share of countries on standard SAP scenarios.
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 the free 60-minute diagnostic.
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
SAP DRC delivery: France and Germany
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) · TJC Group, 'SAP DRC and the S/4HANA deadline'. 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) · Spanish Ministry of Finance (VeriFactu note, 5 October 2026) · Order HAC/1028/2026 (BOE, 5 October 2026) · VATupdate (KSeF common mistakes, July 2026; bill UD477) · European Commission (ViDA) · 30 Advisory briefings on Spain (Crea y Crece) and Poland (KSeF). 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 in September 2026 and updated in October 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. The VeriFactu move to October 2028 is announced but not yet published in the BOE; until it is, the legal dates are 1 January and 1 July 2027. 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.