EU ViDA E-Invoicing Readiness Checklist (Free)

0%

0 of 28 items complete

8 critical items still open - these are the highest-risk gaps.

Download checklist:

Understand scope

Identified which EU member states your entities invoice from or intoCRITICALRead the VAT in the Digital Age package summary, covering digital reporting, platforms and single VAT registrationNoted the timeline for EU-level digital reporting of intra-EU B2B transactions and the e-invoice requirement attached to itCRITICALListed domestic e-invoicing mandates already in force or announced in your member states (for example Italy, Poland, France, Belgium)CRITICALIdentified which cross-border flows are in scope: intra-EU supplies, reverse charge, exports and triangulationAssigned an owner in tax and an owner in IT for the programme

Invoice data and format

Checked whether your ERP can output structured invoices aligned with the EN 16931 semantic modelCRITICALCompared supported syntaxes: UBL, UN/CEFACT CII and national variants or Peppol BIS profilesVerified that invoices are issued within the time limit required after supply for the relevant flowsConfirmed mandatory data fields exist in the ERP: buyer VAT ID, item description, VAT category and rate, exemption reasonMapped ERP tax codes to EN 16931 VAT category codes (S, Z, E, AE, K, G, O and others)CRITICALChecked that credit notes and corrective invoices are structured correctly and reference the originalTested rounding rules and totals match between invoice, ledger and return

Connectivity and process

Chosen a transmission route: Peppol access point, national platform, or service providerCRITICALChecked that customers and suppliers can receive and send structured invoices, and collected their endpoint IDsDesigned handling for rejected or invalid invoices with a clear owner and turnaround timeDefined how paper or PDF invoices from smaller suppliers will be processed during transitionDocumented outage procedures and how invoice numbering is preservedConsidered how e-invoice status will be shown to AR and AP users inside the ERP

Reporting and records

Checked whether your VAT return process can draw on invoice-level data rather than ledger totalsCRITICALReviewed how transaction-level reports to tax authorities would be assembled and reconciled to the VAT returnCleaned customer and supplier master data: legal names, addresses, VAT numbers and VIES validation statusCRITICALConfirmed record retention periods and that archives keep the original structured invoiceConsidered the single VAT registration and OSS extension effects on your registrations

Programme and change

Built an ERP and add-on roadmap with budget and a test calendarIncluded ERP upgrade and patch plans so e-invoicing changes are not overwrittenTrained AR, AP and tax staff on the new document flowSet up monitoring of official EU and national announcements, since implementation details change

ViDA is implemented in stages and national rules vary, so treat dates and details as items to verify with your tax adviser and member state authority. Critical items are those with the longest lead time.

Check invoice data quality before the mandate

We can outline a read-only data quality scan of tax codes, VAT IDs and credit notes in your ERP. Optional.

Optional. The tool and every export work without this. No spam.

How to use this checklist

Start with the scope group, because ViDA sits on top of national rules that already differ widely. Then work through invoice data, connectivity, reporting and programme management. Tick the items you can evidence, export the list and assign owners. Because national implementation is still moving, use this as a living document and re-score it every quarter. Critical items are those with the longest lead time, such as master data cleansing and the choice of a transmission route.

What ViDA covers

The package has three broad pillars. First, digital reporting requirements for transactions, which for intra-EU B2B supplies rely on structured e-invoices aligned with the European standard EN 16931, with an EU-wide start planned toward the end of the decade. Second, updated VAT rules for the platform economy. Third, a move toward a single VAT registration for cross-border trade. Member states can also keep or introduce their own domestic e-invoicing obligations, so dates differ by country.

EN 16931 defines the data model, not one single file format
UBL and CII are the main permitted syntaxes
Peppol is a common transmission network, not the only one
Domestic mandates continue alongside EU-level rules

ERP considerations

The practical work sits in the tax code and master data layers. Each ERP tax code should map to an EN 16931 VAT category and exemption reason, and each customer needs a validated VAT ID and routing identifier. Check how credit notes, advance payments and mixed-rate invoices are represented, because these produce the most validation errors. If your ERP lacks native support, a certified add-on or an e-invoicing service provider can build and send documents, but the data still originates in your system, so quality at source matters.

Common mistakes

Teams often wait for a single final rule and lose time, assume that a PDF with a QR code counts as a structured invoice, or treat the project as only a tax issue when it changes AR, AP and customer onboarding. Another trap is cleaning data late. Start with VAT numbers and addresses now, because it benefits every other compliance process, including Intrastat and the EC Sales List.

Frequently Asked Questions

When does ViDA e-invoicing start?

The package sets a staged timeline, with EU-level digital reporting for intra-EU B2B transactions planned for the end of the decade, while some member states already require domestic e-invoicing. Confirm dates with the official EU texts and your national authority.

Is a PDF invoice acceptable under ViDA?

For in-scope transactions, the invoice must be in a structured electronic format that supports automatic processing, aligned with EN 16931. A plain PDF is a visual document and normally does not meet that definition.

Do we need Peppol?

Not necessarily. Peppol is widely used and mandated in some countries, but ViDA does not require one network. You need a route that delivers compliant documents and meets the national rules in each country you serve.

Does this affect businesses outside the EU?

It can. Non-EU manufacturers selling into the EU through an EU entity or VAT registration may need to issue or receive compliant invoices. Check how your registrations and customer contracts are set up.

If you need to find which invoices in your ERP would fail EN 16931 validation today, Netray can help build a read-only check over your invoice and tax code data.

Talk to an Expert Explore More Free Tools

Related Tools

Country & Tax

More Country & Tax tools

See all

EU ViDA E-Invoicing Readiness Checklist