# EU ViDA E-Invoicing Readiness Checklist > Source: https://netray.co/tools/eu-vida-e-invoicing-readiness-checklist > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer A practical checklist for preparing ERP, tax codes and invoicing processes for the EU VAT in the Digital Age package. ## Category regional ## Region European Union ## Audience - Finance controller - Tax manager - ERP administrator ## Tool **Kind:** checklist **Scoring Note:** 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. **Groups:** #### Understand scope **Items:** **Text:** Identified which EU member states your entities invoice from or into **Critical:** true Read the VAT in the Digital Age package summary, covering digital reporting, platforms and single VAT registration **Text:** Noted the timeline for EU-level digital reporting of intra-EU B2B transactions and the e-invoice requirement attached to it **Critical:** true **Text:** Listed domestic e-invoicing mandates already in force or announced in your member states (for example Italy, Poland, France, Belgium) **Critical:** true Identified which cross-border flows are in scope: intra-EU supplies, reverse charge, exports and triangulation Assigned an owner in tax and an owner in IT for the programme #### Invoice data and format **Items:** **Text:** Checked whether your ERP can output structured invoices aligned with the EN 16931 semantic model **Critical:** true Compared supported syntaxes: UBL, UN/CEFACT CII and national variants or Peppol BIS profiles Verified that invoices are issued within the time limit required after supply for the relevant flows Confirmed mandatory data fields exist in the ERP: buyer VAT ID, item description, VAT category and rate, exemption reason **Text:** Mapped ERP tax codes to EN 16931 VAT category codes (S, Z, E, AE, K, G, O and others) **Critical:** true Checked that credit notes and corrective invoices are structured correctly and reference the original Tested rounding rules and totals match between invoice, ledger and return #### Connectivity and process **Items:** **Text:** Chosen a transmission route: Peppol access point, national platform, or service provider **Critical:** true Checked that customers and suppliers can receive and send structured invoices, and collected their endpoint IDs Designed handling for rejected or invalid invoices with a clear owner and turnaround time Defined how paper or PDF invoices from smaller suppliers will be processed during transition Documented outage procedures and how invoice numbering is preserved Considered how e-invoice status will be shown to AR and AP users inside the ERP #### Reporting and records **Items:** **Text:** Checked whether your VAT return process can draw on invoice-level data rather than ledger totals **Critical:** true Reviewed how transaction-level reports to tax authorities would be assembled and reconciled to the VAT return **Text:** Cleaned customer and supplier master data: legal names, addresses, VAT numbers and VIES validation status **Critical:** true Confirmed record retention periods and that archives keep the original structured invoice Considered the single VAT registration and OSS extension effects on your registrations #### Programme and change **Items:** Built an ERP and add-on roadmap with budget and a test calendar Included ERP upgrade and patch plans so e-invoicing changes are not overwritten Trained AR, AP and tax staff on the new document flow Set up monitoring of official EU and national announcements, since implementation details change ## Content **Intro:** VAT in the Digital Age (ViDA) is the EU package that moves VAT reporting toward real-time, invoice-level data, with structured e-invoicing for cross-border B2B trade at its core. This checklist helps a manufacturer with entities in several member states turn a long policy timeline into tasks the ERP team can plan. **Sections:** #### How to use this checklist **Body:** 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 **Body:** 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. **Bullets:** - 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 **Body:** 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 **Body:** 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. **Cta:** 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. **Faq:** #### When does ViDA e-invoicing start? **Answer:** 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? **Answer:** 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? **Answer:** 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? **Answer:** 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. ## Search terms vida readiness checklist, vat in the digital age checklist, eu e-invoicing 2030 preparation, en 16931 readiness, digital reporting requirements eu vat, peppol e-invoicing erp, eu e-invoicing mandate manufacturer, vida erp impact --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json