ViDA is here: what changes for your invoices, ERP and accounting

If your company still sends invoices as PDF attachments, this regulation applies to you. On March 11, 2025, the EU Council adopted the VAT in the Digital Age package (ViDA). Starting April 14, 2025, member states can require businesses to issue invoices in a structured electronic format. Not PDFs. Not scanned paper. Machine-readable files your systems can process without anyone retyping data.

For most companies, nothing changes overnight. But the direction is set and the deadlines are real.

What actually changes

ViDA introduces three mechanisms that will affect every business trading within the EU:

Structured e-invoicing. An invoice stops being a document someone opens and reads. It becomes a data message in a defined format (typically UBL or CII) that systems send and receive automatically. The goal: eliminate manual processing. A company will no longer be able to email a PDF and call it an e-invoice. The format must comply with the European standard EN 16931, or the receiving party can simply reject it.

Digital VAT reporting. Member states will be able to require businesses to transmit invoice data directly to tax authorities, either in real time or with a short delay. Several countries already operate this way. Poland rolled out KSeF, Hungary has been running RTIR for years, and Italy made e-invoicing mandatory back in 2019. Italy reported a multi-billion euro reduction in the VAT gap within two years. Those numbers are exactly why other countries are moving fast.

OSS/IOSS changes. From January 2027, rules for One Stop Shop and Import One Stop Shop get updated. Businesses selling goods or digital services to end consumers in other EU countries will need to adjust their invoicing and reporting processes. This affects e-commerce sellers, SaaS companies, and digital content providers most directly.

What this means for your ERP

This is where it gets practical. Most ERP systems generate invoices as PDFs. Moving to structured e-invoicing requires changes across several layers:

Invoice format. Your system needs to generate XML in the UBL 2.1 or EN 16931 standard. Adding an export button is not enough. The data structure must include mandatory fields (scheme identifiers, country codes, VAT category codes) that many systems don't collect today. For example, most invoices currently lack a Buyer Reference or Order Reference field, even though these are standard in structured formats.

Pre-send validation. A structured invoice goes through automated validation. Missing or malformed data means the invoice is rejected. This requires validation logic inside the ERP, not downstream in the accounting system. The validation must cover both XML schema correctness and business rules: for instance, that the total matches the sum of line items plus VAT.

Approval workflows. If invoice approvals happen over email or shared folders, that process needs to move into a system. Who approved, when, and what changed becomes part of the audit trail. Companies with multi-level approvals (department head, CFO, managing director) need defined workflows with clear roles and deadlines.

Archiving. Electronic invoices must be stored in their original format for the legally required retention period. A PDF copy does not qualify. The archive must preserve the XML file alongside metadata and guarantee data integrity over the full retention window.

Payment integration. If your ERP generates payment orders, these need to align with the e-invoice. References, variable symbols, and identifiers must map to structured fields. Banks are migrating to ISO 20022 payment message formats, and the link between invoice and payment will need to work automatically.

Timeline

• March 2025: EU Council adopted ViDA
• April 2025: Member states can mandate domestic e-invoicing
• January 2027: Updated cross-border reporting rules, OSS/IOSS clarifications
• July 2030: Mandatory VAT reporting for cross-border transactions across the EU

Individual countries will set their own implementation schedules within this framework. Companies waiting for national legislation will have less time for system adjustments once deadlines are announced. Experience from Italy and Poland shows that real-world implementation takes companies 12 to 18 months, depending on system complexity.

How accounting workflows change

The shift to e-invoicing is not just an IT project. It changes how the finance team works on a daily basis.

Accountants who currently retype data from received invoices will get structured data directly. This reduces errors but requires new controls for automated import: matching against purchase orders, duplicate detection, flagging unusual line items. If someone today manually reviews every invoice before posting, that check needs to move into the system with defined exceptions that still require human review.

Invoice approvals will need defined workflows with roles, deadlines, and escalation paths. For smaller companies where one person approves everything, the change is minor. For companies with multiple departments and revenue above a million euros, it requires careful process design.

Monthly VAT closes will rely on data the system already transmitted to authorities. Any mismatch between reported and declared figures will be visible immediately. This shifts the accounting team's role from monthly "invoice gathering" to ongoing monitoring of automatically processed data.

Smaller companies are not exempt

ViDA is often framed as a concern for large enterprises processing thousands of invoices per month. But smaller businesses will feel the impact too, just differently.

A company issuing 50 outgoing invoices per month can probably get by with a module in their existing accounting software. But that module still needs to produce the correct format. If your current accounting program does not support ViDA-compliant output, you will need to switch. And migrating accounting data under deadline pressure is not something you want to experience.

For sole traders and micro-businesses, tax authorities will likely provide simplified interfaces or free tools, as Italy did with its SDI system. Even so, you need to understand what data the system requires and where it comes from in your workflow.

What to do now

Don't wait for legislation. Map your current invoice journey from issuance to posting. Find the spots where data gets retyped manually, where unstructured formats are used, where validation is missing. Count how many invoices you process per month and how much time your team spends on manual handling.

If you're planning an ERP upgrade, include UBL/EN 16931 support and e-invoice receiving APIs in your requirements. If you run custom software, start with a data model analysis of your invoice entities. Check whether your system can generate valid XML, validate it against the standard, and archive it in the correct format.

Want us to look at how your invoice processing handles the shift to ViDA? Get in touch, we can walk through it together.