Evidence-led policy analysis: earlier and more detailed data is not simply another copy of a periodic return.

Slovakia is not moving from a world in which the tax administration knows nothing about invoices to one in which it finally receives transaction information. The VAT control statement already provides a reporting framework. Its existence creates a fair question: what additional value will the new collection produce, and which existing work will it replace?

That question should not be turned into the claim that the state already possesses a complete, immediate picture of every business transaction. It does not follow from the existence of a control statement. A proper comparison must separate coverage, timing, detail and the actions made possible by the information.

Begin with the actual baseline

The Financial Administration’s 2023 methodological guidance traces the control-statement obligation under section 78a of the VAT Act to 1 January 2014.9 It explains reporting by tax period and the deadline of 25 days after the end of the period.9 That is a different timing model from reporting closely associated with invoice issuance or receipt.

The same guidance distinguishes several sections with different purposes. A.1 concerns specified supplier invoices; B.2 concerns received invoices from which the recipient claims deduction in the relevant period.9 There are also arrangements for reverse-charge transactions, corrections and simplified invoices, including forms of aggregation.9 This is not a uniform copy of every invoice in the economy.

These distinctions matter analytically. A supplier’s reported transaction and a customer’s deduction do not necessarily describe the same VAT-reporting event or reporting period. A comparison process must understand period rules, corrections and exceptions rather than assuming that any unmatched entry is evidence of misconduct.

The 2023 guidance is used here to describe the established baseline, not as an exhaustive statement of every later legislative amendment. A business making a filing decision should use the rules applicable to its own period and circumstances.

What the new reporting adds

The Financial Administration’s January 2026 explanation of the transitional domestic regime lists reportable supplier information including identifiers, invoice number, relevant dates, quantity and type of goods or extent and type of services, unit prices, discounts and tax information.8 It states that only the listed information relevant to the particular taxable transaction is reported.8 The comparison should therefore concern the defined report, not an assumption that every possible attachment or internal business document is transmitted.

Timing changes as well. In the described transitional delivery-service reporting scenario, the supplier reports at issuance; the guidance gives a five-day period from receipt for the domestic VAT-registered recipient’s reporting and specific treatment for self-billing.8 A headline about “real time” should not erase those distinctions or suggest that every participant performs an identical action at an identical instant.

The reporting duty in that transitional explanation is tied to invoices sent through the specified delivery service.8 That scope matters because the guidance elsewhere addresses delivery by other agreed means.8 A policy article should not convert a conditional description into a universal rule for every document.

The administration also explains that the control-statement obligation is abolished from 1 July 2030, with transitional treatment for earlier periods.8 It would therefore be wrong both to promise its immediate disappearance in 2027 and to accuse the design of necessarily keeping it forever.

Compare three changes, not one

For the transitional regime beginning on 1 January 2027, section 85o(11) also provides that the reporting obligation is deemed fulfilled by handing the electronic invoice to the delivery service. Distinguishing delivery and reporting statuses should not imply an additional separate filing step for the business, or confuse that statutory rule with the customer’s acceptance of the transaction.10

The first change is earlier availability. Even if two systems collected identical fields, receiving them sooner could make a difference where intervention is time-sensitive. This is the strongest conceptual argument for transaction-oriented reporting over waiting for a period-end submission.

The second change is granularity. Information about the kind and quantity of goods or the scope of services may help explain a transaction that invoice-level tax figures alone cannot. But more detail does not automatically mean more reliable knowledge. A description can be inaccurate, vague or dependent on a contract that the reporting system does not possess.

The third change is business workflow. A structured invoice can help a buyer import and match a document, while a control statement is a tax report. The automation benefit to businesses should be evaluated separately from the information benefit to the state. Combining both into one vague promise makes it harder to verify either.

For each change, ask what would happen without it. Could better matching of existing data solve the problem? Would earlier receipt of a smaller set of fields be enough? Does the additional detail improve an investigator’s decision, or merely enlarge the database?

A hypothetical invoice shows both opportunity and limits

Imagine a hypothetical engineering company buying materials for a customer’s installation. The invoice contains several product lines, quantities and negotiated prices. The company later disputes one line and receives a correction. This is an illustration, not a documented tax case.

Earlier structured information could allow the administration to identify a mismatch sooner than period-based reporting alone. Line-level information could help distinguish a supply of materials from a service description. But the invoice does not by itself show where the materials were installed, whether the customer accepted the work or whether a disputed quantity was eventually returned.

The correction is especially important. A system that counts the original document and the correction without understanding their relationship can generate a misleading picture. A useful reporting design therefore needs identifiers and correction logic, not just rapid ingestion.

The same invoice may reveal commercially sensitive prices and purchasing relationships. It does not necessarily reveal a complete bill of materials for the customer’s finished product. A bill of materials is a production specification, not a synonym for invoice lines. We should recognise genuine confidentiality concerns without exaggerating what a particular document proves.

The strongest argument for collecting more

The strongest defence of richer, earlier data is that it may help distinguish suspicious chains or inconsistent descriptions while there is still time to investigate. Waiting until a later reporting period can reduce that opportunity. The European Commission itself describes granular, timely cross-border reporting as a tool against VAT fraud, especially carousel fraud.7

That is a reason to evaluate the new capability seriously. It is not proof that a particular Slovak implementation will generate a specified revenue increase. It does not show that every collected detail contributes equally. EU-level policy expectations and national operational performance are different types of evidence.

A fair evaluation should also recognise that the existing system has limitations. Aggregation, scope exclusions and period-based reporting mean that “the state already has everything” is not a sound premise.9 Rejecting all new collection on that basis would be as weak as claiming that more data necessarily eliminates fraud.

Turn the promise into a test

The state should publish a field-by-field comparison between the existing statement, the business invoice and the tax report. Specify the versions of both regimes being compared. For each field or justified group, publish purpose categories, access and retention—not detection thresholds or an evasion manual. Detailed effectiveness testing belongs with authorised independent oversight under protected conditions. This would help identify both justified collection and unnecessary duplication.

Assign responsibility by function: the reporting business sponsor should justify the information need and evaluate its public benefit; the technical implementer should demonstrate reliable collection and transmission; the competent rulemaker should define the obligation and its limits. These roles need not be separate institutions, and this is a proposed accountability map, not an assertion about named officials. The provider demonstrates service outcomes; the business measures its own work. Neither interoperability nor successful transport establishes the fiscal effect of the reform. Proposed measures include time to a usable signal, signals requiring correction, investigator effort and clarification work for compliant businesses. No evaluation results are asserted here.

Revenue comparisons need particular care. A change in receipts can reflect economic activity, tax rules, enforcement resources or timing. A before-and-after total alone cannot establish that new invoice fields caused the difference. An evaluation should set out its comparison method and limitations, including how it avoids counting the same recovery under several initiatives.

Data protection and commercial confidentiality should be addressed through the actual fields, purposes and controls. I do not infer a violation merely from the existence of detailed reporting. Nor does the absence of a demonstrated violation remove the need to justify necessity and restrict access.

Retire work, not only forms

Abolishing a form is valuable only if the underlying work genuinely disappears or becomes easier. If accountants must repeatedly reconcile two representations of the same transaction, the burden may persist under another name. The transition should therefore track manual tasks as well as the formal list of returns.

Businesses can prepare by documenting where invoice data originates, who approves corrections and which records explain differences between commercial documents and tax treatment. Providers should expose understandable statuses and preserve evidence of what was submitted, rather than offering only a generic success notification.

My conclusion is conditional, not dismissive. The control statement’s existence does not make every new report redundant. It makes the obligation to demonstrate incremental value stronger. Collect earlier information where timing matters, justify extra detail where it improves decisions, remove superseded work on a clear schedule and measure the result. The objective should be better tax administration and less unnecessary business effort—not simply a larger collection of invoices.

Sources

[10] Slov-Lex — VAT Act 222/2004, section 85o(11), published version for 1 January 2027–30 June 2030

[7] European Commission: VAT in the Digital Age

[8] Financial Administration: 1/DPH/2026/I, January 2026

[9] Financial Administration: 5/DPH/2023/MP, VAT control statement