M-sheet tightening called off? What companies need to know now
The planned July 2026 M-sheet tightening is expected not to apply after all. What does this mean for eVAT M2M and your company's VAT compliance readiness?
In brief: M-sheet relief may be coming, but eVAT preparation cannot stop
Based on the government's communication, the stricter M-sheet rules planned from 1 July 2026 will likely not need to be applied in practice. This is an important development for businesses that were already preparing for the expanded data content of the domestic summary report (M-sheet).
The announcement may bring short-term administrative relief, but it does not change the fact that the long-term direction of VAT return processes continues to point towards eVAT, NAV M2M, and automated data reporting.
The most important message for companies is therefore: it is worth re-evaluating transitional M-sheet developments, but it is not advisable to postpone preparation for eVAT M2M.
The key points in 5 bullets
According to the government's communication, the stricter M-sheet rules planned from 1 July 2026 will likely not need to be applied in any single filing period.
The current M-sheet obligations do not automatically cease as a result of this.
The announcement may reduce transitional development and administrative burdens.
The eVAT M2M and NAV M2M direction remains of unchanged strategic importance.
Companies should now focus on eVAT-compatible data structures, tax code mapping, and VAT return processes.
What has changed now?
Under the previously adopted regulation, stricter data content requirements would have applied from 1 July 2026 to invoice-level data reporting related to received invoices.
However, according to the Ministry of Finance's latest statement, the government plans to submit a proposal that would ensure the stricter rules do not need to be applied in any single filing period.
In practice, this means that businesses should re-evaluate any development or reporting tasks they had initiated solely because of the M-sheet tightening planned for 1 July 2026 (the new rules would have first applied to the July filing period, which is submitted in August).
It is important to note, however, that this does not represent a change in the direction of VAT return digitalisation. It is much more a matter of avoiding an expected transitional administrative burden.
What does this mean on the corporate side?
The announcement may be favourable in the short term for companies where meeting the stricter M-sheet data content would have required system development, new reporting logic, manual additions, or ERP-side modifications.
The additional workload could have been particularly significant for businesses where the VAT return is currently compiled from multiple sources, Excel-based reconciliations, or subsequent manual corrections.
Based on the current announcement, it is worth reviewing the necessity of those developments that served solely a transitional compliance purpose.
At the same time, it is also important that the expected practical absence of the M-sheet tightening does not resolve the data quality and process management issues that will equally arise during the introduction of eVAT M2M.
Why does eVAT M2M remain important?
eVAT M2M is not simply a new technical submission channel. Successful operation requires high-quality source data, well-structured VAT analytics, well-thought-out tax code mapping, and a controlled VAT return process.
If the VAT return at your company currently relies on significant manual steps, if the logic of tax codes is not fully documented, or if the return data is compiled from multiple systems, then preparation for eVAT M2M remains justified.
NAV has already published the eVAT M2M 2.0 interface specification, which will be available in the test environment from July 2026. This also shows that the direction of M2M-based VAT return operations remains current.
For companies, the question is therefore not whether to address the digitalisation of VAT return processes, but at what pace and along what focus points it is worth preparing.
What should you focus on now?
In the current situation, it is not necessarily justified to allocate resources to short-term developments that would have served solely the M-sheet tightening planned from 1 July 2026.
Instead, it is worth concentrating on eVAT-compatible operations that are also useful in the longer term.
1. Assessing VAT analytics
It is worth examining what level of detail and quality the current VAT analytics are available in. For eVAT M2M operation, it is not sufficient for data to be compilable after the fact; it is important that they can be produced in a structured, repeatable, and verifiable manner.
2. Preparing tax code mapping
The tax codes used in the ERP or accounting system should be compared against the eVAT logic. This is one of the most important professional and technical preparatory tasks, because tax codes determine how individual line items appear in the VAT return.
3. Identifying manual corrections
Where the VAT return is currently prepared with manual modifications, Excel-based reconciliations, or subsequent corrections, it is especially important to clean up the process before introducing eVAT M2M.
4. Checking source system data
A key question from the eVAT M2M perspective is whether the necessary data is available in the appropriate form from the source systems. If a piece of data can only be produced with manual additions or by merging multiple systems, this may pose an error risk later.
5. Establishing a testing and error-handling process
The introduction of the M2M connection does not end with establishing the technical link. Test data, validation rounds, an error-handling process, and clearly defined responsibilities are also required.
What does this mean for finance, tax, and IT teams?
The current announcement provides an opportunity for companies to focus not on a short-term M-sheet modification, but to examine the operation of their VAT return processes more comprehensively.
For finance and tax teams, this is primarily a matter of data quality, controls, and processes. For IT and ERP teams, it is a task of system integration, data structure, and automation.
The introduction of eVAT M2M can be successful if both sides work together: behind the technical solution there is clear tax professional logic, and behind the professional requirements there is a feasible and sustainable system-side operation.
Frequently asked questions
Is it certain that the M-sheet tightening from 1 July 2026 does not need to be applied?
Based on the government's communication, the aim is that the stricter M-sheet rules do not need to be applied in any single filing period. However, the final situation can only be assessed once the legislative amendment has been adopted.
Is the M-sheet being abolished?
No. The announcement is not about abolishing the M-sheet, but about the expected practical non-application of the stricter data content planned from 1 July 2026.
Does the M-sheet still need to be dealt with?
Yes. The current M-sheet obligations may still be relevant for businesses that submit their VAT returns in the traditional way.
If the tightening does not come, is it still worth preparing for eVAT M2M?
Yes. The expected practical absence of the M-sheet tightening does not change the fact that VAT return processes are heading in the long term towards digital, data-driven, and M2M-based operations.
What should be the first step now?
As a first step, it is worth assessing how well the current VAT analytics, tax code structure, manual correction processes, and source system data are suited to supporting eVAT M2M operations.
Summary
The government's announcement may be a favourable development for businesses that would have devoted significant resources to the M-sheet tightening planned from 1 July 2026.
However, the expected relief does not mean that the digitalisation of VAT return processes will take a back seat. The long-term direction remains data-driven, automated, and M2M-based operations.
Companies should therefore not sit back now, but prioritise wisely: less focus on transitional M-sheet developments, more focus on eVAT-compatible, long-term sustainable VAT return operations.