Key takeaways

• Tax authorities now hold three records of every transaction the VAT return, SAF-T, and e-invoicing and reconcile them automatically.
• A mismatch between the VAT return and CTC e-invoice totals is the single most common audit trigger in CTC countries.
• Unreconciled data causes audits, per-invoice penalties, blocked VAT refunds, and formal non-compliance.
• Romania requires an explanation to ANAF within 10 days when discrepancies exceed the greater of 20% of VAT due or RON 1,000 (about €200).
• Spain's B2B e-invoicing mandate begins phasing in from July 2027 for companies with turnover above € 8 million.
• The fix is a single golden record plus monthly three-way matching at transaction level, not just on totals.

What are VAT returns, SAF-T, and e-invoicing reports?

VAT returns, SAF-T, and e-invoicing reports are three tax-reporting systems that describe the same transactions from different angles and at different moments. A VAT return is the periodic summary, filed monthly or quarterly, that reports total output VAT, total input VAT, and the resulting net liability. SAF-T, the Standard Audit File for Tax, is the detailed audit file that gives authorities transaction-level data on invoices, payments, ledgers, and inventory; Portugal, Poland, and Norway already use it, while Spain, France, and Germany are expanding comparable Continuous Transaction Control (CTC) models. E-invoicing reports are real-time or near-real-time transmissions of each individual invoice and its status to the tax office, through systems such as Spain's VERI*FACTU, Italy's SDI, and France's Chorus Pro.

Why are tax authorities now reconciling these systems automatically?

Tax authorities reconcile the three systems automatically because Continuous Transaction Control and SAF-T mandates have given them three independent records of every transaction, and their systems cross-check those records without human involvement. The shift is away from periodic, "declare and explain" audits toward continuous, real-time monitoring. A mismatch is raised, for example, when an invoice is reported through e-invoicing but missing from the SAF-T ledger, when SAF-T shows €100,000 of output VAT while the VAT return declares only €90,000, or when an e-invoice is marked as paid but the SAF-T payment data disagrees. When the three feeds do not tell the same story, it is the business that has to account for the difference.

What happens when VAT returns, SAF-T, and e-invoicing don't match?

When the three systems do not match, reconciliation gaps feed automated risk scores and trigger fast consequences. In CTC countries, a discrepancy between the monthly VAT return and CTC e-invoice totals is the most common audit trigger. Penalties can apply per invoice: Spain's anti-fraud legislation already sanctions discrepancies between SIF invoicing systems and declarations. Cash flow is hit just as directly, because where the input VAT claimed in a return does not match the e-invoices reported by suppliers, authorities freeze refunds until the figures are shown to reconcile. There is also direct compliance exposure  under Spain's forthcoming B2B mandate, recipients must report acceptance or rejection of an invoice within four days, and any misalignment makes the filing non-compliant.

Where do the three systems most often diverge?

The three systems most often diverge because they serve different purposes, run on different timetables, and fail in different ways. The table below summarises the typical mismatch causes for each.

A common example is a credit note issued on 28 December but only applied in January's VAT return: e-invoicing records it as issued on 28 December, SAF-T shows it posted on 5 January, and the fourth-quarter VAT return omits it. Each system is internally correct, yet together they appear to contradict one another. Prefilled VAT returns raise the stakes further, because they are generated from the data already submitted to the authorities; any correction a taxpayer makes therefore signals a discrepancy in an underlying obligation such as SAF-T or e-invoicing, and points to non-compliance.

Once an authority detects an inconsistency, the responsibility for investigating its root cause and correcting it rests entirely with the taxpayer, and that is rarely straightforward. Resolution becomes complex and time-consuming when the underlying issue is unclear, and the involvement of multiple vendors across different reporting obligations adds to the difficulty of keeping submissions consistent, diverting resources from core operations and raising compliance costs. Romania illustrates the trend: taxpayers continue to file regular VAT returns, but where discrepancies exceed the greater of 20% of the VAT due or RON 1,000 (approximately €200), they must explain the difference to ANAF within ten days through the Virtual Private Space (VPS) platform, or risk fines and audits.

What are the benefits of reconciling the three systems?

Reconciliation protects both cash flow and reputation. Clean reconciliation means refund claims are processed without follow-up questions, so VAT is returned to the business faster. A reconciled audit trail lowers the risk score an authority's algorithm assigns, reducing the likelihood of an audit. The discipline of reconciling also forces the correction of poor master data invalid VAT codes and incorrect customer NIF or VAT numbers, improving overall data quality. And when SAF-T is requested, the ledger already matches what the authority received through e-invoicing, leaving the organization genuinely audit-ready.

How do you reconcile VAT returns, SAF-T, and e-invoicing efficiently?

The most efficient approach is to build everything on a single golden record and run a monthly three-way match. The ERP or invoicing system should be the single source of truth, so every figure traces back to a common origin. The central control is to confirm each month that the sum of e-invoices issued equals the SAF-T sales ledger total, which in turn equals the output VAT on the VAT return. That match must operate at transaction level rather than on totals alone comparing invoice number, date, and VAT amount across all three systems so offsetting errors cannot hide inside an aggregate. Corrections need the same rigor: credit notes and adjustments should update all three systems using the same reference. Finally, all of this should be tested before mandate deadlines, such as Spain's B2B mandate, which begins phasing in from July 2027 for companies with turnover above € 8 million.

Frequently asked questions

Bottom line

Each system answers a different question for the authority: the VAT return states how much tax is owed, SAF-T proves every transaction behind that figure, and e-invoicing confirms the authority saw each invoice when it happened. When the three narratives align they corroborate one another; when they do not, authorities assume error or evasion. Reconciliation is how a business proves that all three are telling the same story.

Disclaimer: This article is for general information only and is not tax, legal or financial advice. Tax rules differ by jurisdiction and change frequently. Consult a qualified professional about your organisation’s specific circumstances.