Glossary Term

Real-Time Reporting

A Continuous Transaction Controls (CTC) model in which invoice data is transmitted to the tax authority within minutes or hours of invoice issuance — but after the invoice has already been exchanged with the buyer. Unlike clearance, real-time reporting does not block or pre-approve the invoice; it runs in parallel.

Quick Facts

Category
CTC model
Definition
Transaction data reported to tax authority shortly after invoice issuance
Data format
Country-specific (NAV XML, SII XML, etc.) — not EN 16931
Contrast with
Clearance (pre-issuance) and post-audit (on-demand)
Typical latency
Minutes to days (country-dependent)
Invoice blocking
No — invoice is valid without authority approval
Primary EU examples
Hungary RTIR, Spain SII, Spain Verifactu (optional mode)
Future EU-wide equivalent
ViDA DRR (mandatory July 2030)

Definition

What is Real-Time Reporting?

Real-time reporting is a category of Continuous Transaction Controls (CTC) where businesses must transmit invoice data to the tax authority immediately after — not before — an invoice is issued and delivered to the buyer. The reporting happens in near real-time (typically within minutes to a few days), but the invoice itself is already legally binding between seller and buyer at the moment it is reported.

Real-time reporting contrasts with two other major CTC models:

  • Clearance — the tax authority must approve the invoice before it is considered legally issued (e.g., Italy's SDI).

  • Post-audit — the tax authority only sees invoices during a periodic audit, not routinely.

    • Real-time reporting sits between these two: more intrusive than post-audit, less intrusive than clearance.

    How Real-Time Reporting Works

    The canonical flow:

    1. Seller issues the invoice to the buyer (via email, PDF, structured XML, or a private network).
    2. Invoice becomes legally valid the moment it is issued and accepted. No tax-authority approval needed.
    3. Seller (or their ERP/billing software) transmits the invoice data to the tax authority's reporting endpoint, usually in XML or JSON format, within the required window.
    4. Tax authority acknowledges the submission — but this acknowledgement does not change the invoice's legal status.
    5. Tax authority uses the data for VAT reconciliation, risk analysis, and pre-filled VAT returns.

    The key design property: the invoice is not delayed. The buyer gets the invoice immediately; the authority gets a copy shortly after.

    Real-Time Reporting Systems in Europe

    Hungary — RTIR (Real-Time Invoice Reporting)

    Launched in 2018, extended to all B2B invoices in 2020 and to B2C in 2021. Hungary's NAV Online Számla system is the flagship real-time reporting regime in Europe:

  • All invoices must be reported immediately (practically, within 24 hours, but typically within minutes).

  • Reporting is done via XML submission to NAV's API.

  • Includes invoices below VAT thresholds and foreign-currency invoices.

  • Heavy enforcement — non-reporting triggers immediate VAT audit flags.

    • Spain — SII (Suministro Inmediato de Información)

    Launched in 2017 for large taxpayers (revenue > €6M). Spain's SII requires:

  • Invoice data transmission within 4 working days of issuance.

  • XML payload submitted to the AEAT's SII web service.

  • Applies to both issued invoices and received invoices (incoming).

  • Companies on SII are exempt from the upcoming Verifactu mandate.

    • Spain — Verifactu (optional mode)

    Verifactu, Spain's newer certified billing regime (mandatory from Jan 2027 for CIT payers, Jul 2027 for self-employed), includes an optional real-time mode: Verifactu invoices can be transmitted to AEAT within 8 days. Non-Verifactu mode stores records locally.

    Portugal — SAF-T(PT) + ATCUD

    Portugal's model is hybrid: invoices must be generated by certified software with unique ATCUD codes, and a SAF-T accounting file is submitted monthly — not instantaneously. This is closer to periodic reporting than true real-time, but often grouped under real-time models in CTC literature.

    Germany — no real-time reporting (yet)

    Germany currently has no real-time reporting regime. The 2025 B2B e-invoicing mandate is structured as exchange of EN 16931 invoices between parties; real-time reporting is planned as a second phase under ViDA but is not yet implemented.

    Real-Time Reporting vs. Clearance

    This distinction matters operationally:

    Aspect Real-Time Reporting Clearance
    ----------------------------------------
    When tax authority gets data After issuance Before issuance
    Does authority block invoice? No Yes
    Invoice legally valid without authority action? Yes No
    Latency impact on issuer Near-zero (async) Direct (synchronous)
    Example Hungary RTIR, Spain SII Italy SDI, Turkey e-Fatura

    For ERP developers, real-time reporting is technically easier: failed submissions don't break business flows. Clearance is harder: if the tax authority is down, invoices cannot be issued.

    Real-Time Reporting vs. Post-Audit

    Real-time reporting replaces post-audit in jurisdictions that adopt it:

  • Post-audit: invoices stay private until a specific audit is triggered. Tax authority has limited visibility; fraud detection is reactive.

  • Real-time reporting: tax authority has continuous visibility; fraud detection becomes proactive.

    • Real-time reporting is widely seen as more efficient for tax authorities — it provides near-immediate VAT transaction data without the disruption of clearance.

    Relevance to ViDA and the Future of EU E-Invoicing

    ViDA (VAT in the Digital Age), adopted in March 2025, mandates Digital Reporting Requirements (DRR) for intra-EU B2B transactions by July 2030. DRR is effectively real-time reporting: transaction-level data transmitted to the tax authority within 10 days of issuance.

    For Member States that currently operate post-audit (Germany, Netherlands, Austria, Ireland), this is a major shift. For countries already running real-time reporting (Hungary, Spain), DRR is closer to their existing model — though compliance will still require adjustments to match the EU-level data format.

    What ERP Developers Need to Know

    1. Real-time reporting is an additional integration, not a replacement for invoicing. You still issue the invoice to the buyer; you also transmit data to the tax authority. Both must happen.

    2. Data format differs from invoice format. Real-time reporting payloads (e.g., NAV XML, SII XML) are usually tax-authority-specific, not EN 16931. Don't assume your Peppol-ready UBL will satisfy Hungarian RTIR.

    3. Design for idempotency and retries. Reporting endpoints occasionally fail or return transient errors. Track submission status per invoice and implement retries with deduplication.

    4. Track acknowledgements. Most real-time reporting systems return a confirmation with a unique reference number. Store it with the invoice — you'll need it in audits.

    5. Decouple issuance from reporting. If the reporting endpoint is down, the invoice should still go to the buyer. Queue reporting submissions asynchronously and reconcile later.

    6. Monitor per-country deadlines. Reporting windows vary (Hungary: immediate; Spain SII: 4 days; Verifactu: 8 days; Portugal SAF-T: monthly). Build country-specific timers into your compliance engine.

    7. Prepare for DRR. If you operate in Member States without current real-time reporting, the ViDA DRR mandate arrives July 2030. Architect now for the fact that every cross-border B2B invoice will need to be reported.

    Related Content

    Glossary
    Post-Audit ModelVerifactu
    Compare
    Peppol vs Italy’s SDI: Federated Network vs Centralized System
    Answers
    What is CTC (Continuous Transaction Controls) reporting?What is ViDA and when does it take effect?
    Blog
    E-Invoice Validation Rules ExplainedE-Invoice Schematron Rules Explained: What ERP Developers Need to Know
    Validators
    XRechnung Validator