ViDA Digital Reporting Requirements outstanding questions

At the core is the need to align the revised VAT Directive provisions—particularly Articles 218, 218a, 232 and the new EU e-invoicing standard—with the practical realities of cross-border trade, procurement flows, legacy ERP architecture and national e-invoicing regimes. Much of this was discussed at the Group Future of VAT.

1. Definitions and scope

Problems identified by Member States:

• No common definition of invoice issuance, transmission or acceptance.

• Unclear correction cycles, rejection flows, and timing of late invoices.

• Ambiguity over “days”: working or natural?

• Lack of clarity on scope: intra-EU B2B only? What about domestic Reverse Chard cases?

Work on definitions, uniform deadlines and scope of mandate

• Define issuance as the moment the invoice is finalised and sent; transmission as confirmed delivery to the buyer.

• Define real-time reporting as submission within a short, fixed number of calendar days.

• Apply a uniform number of dats  supplier deadline and number of days buyer deadline EU-wide.

• Clarify scope: DRR covers intra-EU B2B plus domestic reverse-charge analogues, but not B2C.

2. Invoice formats, standards and content

Problems identified:

• Acceptance of non-structured formats still debated.

• Status of EDIFACT unclear; hybrid formats (German ZUGFeRD/ or French Factur-X) inconsistently treated.

• No shared definition of “compliant” vs “conformant”.

• CEN schema lacks certain VAT codes (e.g. triangulation indicator).

• Inconsistent expectations on attachments, IBAN fields, VAT-related additional data.

Enforce EN 16931; ban PDFs; IBAN rules and harmonise terminology 

• Enforce one mandatory EU e-invoice format (EN 16931) for all in-scope transactions.

• Prohibit national deviations or extra data fields for cross-border invoices.

• Treat PDFs only as visualisations, not compliant invoices.

• Clarify content rules: credit/debit notes must reference the original invoice; IBAN generally required; standard VAT phrases mandatory (“Reverse charge”, “Triangular transaction”, etc.).

• Ensure hybrid formats remain acceptable only if the embedded XML is fully compliant.

3. Treatment of special VAT scenarios

Problems identified:

• No harmonised method for corrections, rebates, cash-accounting adjustments.

• Triangulation inconsistencies; missing CEN code.

• Multi-party chains treated differently across Member States.

• No shared rule on Fixed Establishment (FE)  involvement and VAT ID usage.

Standard corrects; rebates; Fixed Establishment definition

• Require corrections via credit/debit notes, never by overwriting original invoices.

• Require year-end rebates, bulk discounts and transfer-pricing adjustments to be documented with formal VAT credit notes.

• Standardise triangulation with mandatory wording and EU-wide coding.

• Clarify FE rule: use the FE VAT ID when the FE is involved in making the supply.

4. Cross-border transmission, validation and competent authority

Problems identified:

• No agreement on whether supplier’s or buyer’s Member State rules apply.

• Divergent national validation criteria and error codes.

• Customer refusal, validation failures and platform-to-platform transmission poorly defined.

Row back on supplier reporting; Peppol adoption

• Adopt a “report once” model: submission in the supplier’s country automatically populates the buyer’s tax authority.

• Harmonise validation rules, error structures, and acknowledgements across all Member States.

• Use common transmission channels – Peppol – to ensure consistency in cross-border acceptance/refusal flows.

• Recognise software certified in one Member State as certified everywhere.

5. Technical interoperability

Problems identified:

• National systems risk becoming incompatible, duplicating reporting.

• Hybrid XML-PDF formats inconsistently interpreted; EDIFACT legacy processes remain.

• No common framework for handling attachments, translations, FX, rounding.

Single data platform for reporting and domestic regimes

• Build national platforms as part of an interconnected EU data-exchange grid, enabling automatic routing of cross-border invoices.

• Establish common rules for FX rates, rounding and multilingual content.

• Require Member States to integrate domestic e-invoicing regimes into the DRR architecture rather than running them separately.

6. Data security, burden reduction and SME support

Problems identified:

• Businesses concerned about exposure of sensitive commercial data.

• Fear of heavier administrative burden, especially for SMEs.

Encryption; grace periods

• Guarantee end-to-end encryption, GDPR-aligned storage and restricted access.

• Introduce a soft-landing period like France or Belgium: penalties waived for minor early-stage errors and continued right to deduct.

7. Transition and governance

Problems identified:

• Multi-year rollout with uneven national readiness.

• Coexistence of domestic e-invoicing mandates and new EU cross-border rules.

• Risk of divergent national guidance pre- and post-go-live.

Set coordinated preparation, testing, pilot and governance

• Push single EU-wide rollout with mandatory consultations, pilots and test environments.

• Align all national guidance with the Explanatory Notes for a single message across the EU.

• Establish an ongoing EU governance body (VAT Committee / task force) to resolve divergences post-implementation.

Other DRR issues

Questions were also raised about self-billing, invoice numbering, cash vs credit disclosures, and the management of foreign currency, translations and rounding. These points link directly to the DRR requirement to define what constitutes a “transaction” for reporting: is it the issuance of an invoice, the underlying taxable event, or another legally determinative moment? This matters acutely where the DRR obliges customer-side reporting—including cases where the customer has no invoice at all, such as certain intra-group or reverse-charge situations.

Taken together, the current debates highlight the scale of the technical alignment still required. The DRR’s success will depend not only on legislative clarity but on reconciling national e-invoicing models, legacy standards, supply-chain practices and multi-jurisdictional VAT rules into a single, interoperable EU-wide system.

EU VAT in the Digital Age reforms