Custom e-invoicing and digital reporting software development
ViDA is often summarised as a new invoice format. That is the smallest part. What really changes is that the same data goes to the tax authority per transaction instead of aggregated in a return. That removes the room most administrations live in today: the weeks between booking and filing, in which errors are quietly put right.
What changes and when
The Council of the European Union adopted the ViDA package on 11 March 2025, following the European Parliament's approval. The package has three pillars, of which e-invoicing with digital reporting is the most far-reaching. From 1 July 2030, an invoice for an intra-Community B2B transaction must comply with the European standard EN 16931, and the data of that transaction goes digitally to the tax authority.
In 2026, the Netherlands published a proposal for the first phase. Under this timeline, 1 January 2030 applies to domestic e-invoicing, 1 July 2030 to the European obligation and 1 January 2032 to domestic digital reporting. The government wants the legislation finalised at least two years before the European date, so by 2028 at the latest.
The real change is not the format but the timing. Today you book an invoice, later discover an error in a VAT number or a rate, and correct it before the return goes out. With per-transaction reporting, the invoice has already been reported. You can still correct it, but it becomes a visible correction rather than an unnoticed one. That means data quality has to move forward, to the moment the invoice is created.
How we build this
Here the unit is the invoice line, not the return. If every line is correct the moment it is created, reporting becomes a technical step.
We analyse your current invoicing to find which fields are often missing or wrong: VAT numbers, country codes, units, rates. That list is almost always shorter than feared and more concrete than a standards analysis.
Every check that now happens at the return stage, we move to the moment of creation. There it costs a second, whereas afterwards it costs a correction.
EN 16931 describes what has to be on the invoice. We structure your data so that the standard follows from it, because the standard will still be extended in the years up to 2030.
We have the system reprocess a closed month and show which invoices would have been rejected under per-transaction reporting. That number is your actual workload.
What the software actually does
Data quality on the invoice line underpins everything. Which components you need depends on how much cross-border trade you have and on what your current software can already handle.
Checks at the moment of creation
Missing or invalid fields are flagged before the invoice goes out. That is the only moment when correcting is still free.
Invoice built to EN 16931
The structured invoice follows from your data, not from a template. If the standard changes, the mapping changes, not your accounting.
Per-transaction reporting ready
The data that goes to the tax authority is compiled per transaction and stored exactly as it was sent. If questions arise later, what you reported at the time is what counts.
Deviations with follow-up
A rejected invoice, a VAT number that is no longer valid, a counterparty that does not respond. Each becomes an action with an owner, because an error list without follow-up only grows.
Connecting to your own software
The invoice originates in your ERP or accounting software. We build the layer in between using integrations instead of replacing your software, and connect to your Peppol integration if you have one.
Recording what was sent
For each invoice and each report: what was sent, when, and with what outcome. With per-transaction reporting, that is your only defence if a dispute arises later.
Who we build for
How much work this involves depends on your transaction flow. Four situations.
Trade within the EU
You supply customers in several member states, and those are precisely the transactions that fall under the obligation first. Your biggest risk is incorrect or expired VAT numbers of counterparties.
Manufacturing with cross-border deliveries
Your invoices contain lines with units, weights and sometimes partial deliveries. Translating those into a standardised invoice is the real work, and it gets harder as soon as there are customer-specific agreements.
Sales through multiple channels
Invoices originate in different systems, each with its own assumptions. As long as these don't come together in one place, you will end up reporting different versions of the truth about the same business. The purchasing side, with receipts created outside the office, is covered on the ViDA app page.
Bookkeeping and accountancy firms
You do this for dozens of clients at once, so an overview per client is more useful to you than a separate system for each one. The VAT return side itself is covered on VAT compliance software.
Test your idea first: a working prototype in 1 day
With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.
View OneDayBuild →Technology and integrations
The exact details of the Dutch legislation and of the reporting messages have not yet been settled. Everything connected with them should be configurable and stored per version.
To submit VAT data per transaction to the tax authorities, there is our real-time VAT reporting integration.
Why Appfront
The deadline seems far off, but your invoice flow is slow to change
Changing an invoicing process affects sales, logistics and finance all at once. If you start in 2029, you will find that the data the standard requires is not recorded anywhere.
Correcting afterwards stops being an option
We move checks to the moment of creation, because that is the only point where they still cost nothing.
Your software stays in place
We build the layer in between using integrations. Replacing your ERP to meet a standard is the most expensive route to the same result.
Honest about what is still changing
The Dutch legislation has not yet been finalised and the message definitions are still being added to. We build these as a setting and make no claims about what they will say in the end.
Security and privacy
Invoicing data is both commercially sensitive and tax evidence. Anyone who can view your invoice flow knows your customers, your margins and your volumes; anyone who can change it can make your records unusable. We therefore keep read permissions strictly separate from edit permissions, and record every change to a sent invoice as a correction rather than an amendment.
With per-transaction reporting, a requirement comes into play that does not apply today. You must later be able to show what you reported and when, even if the invoice was corrected afterwards. We therefore store the message as it was sent, with its timestamp and outcome, and not just the invoice's current state. A system that only knows the latest version cannot explain to the tax authority what was reported at the time. How we handle security ourselves is set out in our information security policy; reports from outside go through our coordinated vulnerability disclosure policy.
Frequently asked questions about ViDA and e-invoicing
For intra-EU B2B transactions from 1 July 2030, in line with the European standard EN 16931, together with digital reporting of those same transactions. In the Dutch timeline, domestic e-invoicing is set for 1 January 2030 and domestic digital reporting for 1 January 2032. These national dates have not been finalised yet; check the status of Dutch legislation before you fix your plans.
Not in the sense that ViDA means. It refers to a structured invoice that a system can read without human intervention, built according to EN 16931. A PDF is an image of an invoice; what the standard requires is the data itself.
Peppol is the network the invoice travels over, whereas ViDA is about what the invoice contains and what must be reported to the tax authority alongside it. If you already send via an access point, the transport is sorted but the data quality is not. See Peppol integration for that side.
VAT compliance is about the return chain: rate determination, the reverse-charge mechanism, EC Sales List and One Stop Shop. ViDA is about the invoice as a data carrier and about per-transaction reporting. The two interlock, because the data comes from the same source; see VAT compliance software.
Rarely. Most packages can create and export an invoice; what's missing is line-level validation and the reporting side. An intermediate layer that connects to those is cheaper and less risky than a migration, and you can still replace it later with a package feature once your supplier delivers one.
Then it hasn't been sent and your delivery stalls on the administrative side. That is exactly why validation belongs up front: a rejection at creation takes a second, a rejection after sending costs you a conversation with your customer. That's why we build a list of deviations with an owner and a deadline instead of an error message.
Commercial arrangements remain possible, but they must be expressible in a standardised invoice. Discounts, tiered pricing and surcharges that currently sit in a free-text line become fields. For most companies this is the underestimated part of the work, and the reason to start early.
That depends on the number of invoicing sources, the state of your master data and whether the reporting side needs to be included. The validation layer on existing invoices is usually usable quickly and delivers the most, because it makes your actual error rate visible. We give a substantiated estimate after the discovery phase.
Preparing for e-invoicing?
Take a closed month and count how many invoices had a missing or invalid field that was corrected later. That number is what will become visible soon. We build this as a standalone application and as part of a broader custom software project.