Glossary Term

DRR (Digital Reporting Requirements)

Digital Reporting Requirements (DRR) are the ViDA pillar that, from 1 July 2030, obliges EU businesses to issue structured EN 16931 e-invoices and report transaction data to tax authorities in near real time for cross-border intra-Community B2B and B2G trade, replacing recapitulative statements.

Quick Facts

Scope
Intra-Community B2B and B2G transactions
Format
EN 16931 structured e-invoice
Part of
ViDA, Pillar 1
Replaces
Recapitulative statements (EC Sales Lists)
Full name
Digital Reporting Requirements
Reporting window
10 days (relaxed from 2 working days)
Cross-border start
1 July 2030
Domestic alignment deadline
1 January 2035

Definition

What are Digital Reporting Requirements?

Digital Reporting Requirements (DRR) are the first and most technically significant pillar of the EU's ViDA package. DRR replaces today's periodic, aggregated VAT reporting for cross-border trade with structured e-invoicing plus near-real-time, transaction-level digital reporting. In effect, DRR is the EU's harmonised Continuous Transaction Controls (CTC) layer for intra-Community commerce.

The headline date is 1 July 2030: from then, EU VAT-registered businesses must issue structured e-invoices conforming to EN 16931 for cross-border intra-Community B2B and B2G transactions, and report the underlying data to their tax authority within a short window. The long-standing recapitulative statements (EC Sales Lists / ESL) are abolished for transactions in scope.

What DRR actually requires

Three obligations sit at the core of DRR:

1. Structured e-invoice issuance. A cross-border intra-Community B2B/B2G invoice must be a structured electronic document compliant with EN 16931 (Directive 2014/55/EU). PDFs and unstructured formats no longer satisfy the requirement. Invoices must be issued within 10 days of the chargeable event for the transactions in scope.
2. Near-real-time digital reporting. Transaction data must be transmitted to the tax authority within a defined window — set at 10 days in the adopted text (relaxed from the original proposal of 2 working days). Both the supplier and the customer have reporting obligations, drawn from the same structured invoice.
3. Abolition of recapitulative statements. Because the authority now receives transaction-level data continuously, the aggregated ESL becomes redundant and is removed for in-scope flows.

A handful of summary fields previously not required on invoices (for example, bank account details and certain references) become part of the mandatory data set so that reporting can be automated end to end.

DRR and domestic mandates

DRR is the cross-border layer, but it interacts tightly with national mandates. From ViDA's entry into force on 14 April 2025, member states may impose domestic e-invoicing mandates without an EU derogation and without buyer consent — which is why France, Germany, Belgium and Poland are rolling out national systems well before 2030. Crucially, member states that run a domestic digital real-time reporting system must align it with the EU DRR model and standards by 1 January 2035. So DRR sets both the 2030 cross-border obligation and the 2035 convergence target for national CTC regimes.

Why DRR matters for ERP vendors

DRR is the moment e-invoicing stops being only about producing an invoice and starts being about reporting it. For an ERP or invoicing platform this means:

  • The product must emit clean EN 16931 structured output, not just a printable invoice.

  • A reporting extraction must be derived reliably from the same invoice data — the report and the invoice cannot disagree, or the business is exposed.

  • Timeliness becomes a compliance property: a 10-day window turns invoicing latency and system downtime into tax risk.

  • The same document must satisfy the EN 16931 core, any applicable national CIUS, and the DRR reporting schema simultaneously.
  • This is exactly the kind of multi-ruleset, high-stakes constraint where a compliance safety layer earns its place: catching a defect before it propagates into both the invoice the customer receives and the report the tax authority ingests.

    Relation to EN 16931, ViDA and CTC

    DRR is a ViDA pillar; EN 16931 is the format it mandates; and conceptually it is the EU's implementation of CTC for cross-border trade. Understanding DRR therefore means understanding all three together: the regulation (ViDA), the data model (EN 16931), and the control philosophy (CTC). For developers, the practical preparation is identical to ViDA readiness — build to EN 16931 with clean CIUS separation now, and add reporting extraction as the 2030 date approaches.

    XML Examples

    UBL (Peppol, XRechnung)

    <!-- DRR mandates EN 16931-conformant structured output; the customization ID anchors conformance -->
    <cbc:CustomizationID>urn:cen.eu:en16931:2017</cbc:CustomizationID>
    <cbc:ProfileID>urn:fdc:peppol.eu:2017:poacc:billing:01:1.0</cbc:ProfileID>
    <cbc:ID>INV-2030-CB-0007</cbc:ID>
    <cbc:IssueDate>2030-07-03</cbc:IssueDate>
    <cac:AccountingSupplierParty>
      <cac:Party>
        <cbc:EndpointID schemeID="9925">BE0123456789</cbc:EndpointID>
      </cac:Party>
    </cac:AccountingSupplierParty>

    Related Content