Lead story: ViDA moves from adoption into a decade of implementation work
The EU package now has an official implementation program, but its e-invoicing, digital-reporting, platform, and single-registration measures still land on different dates.
Follow the mandate. Reconcile the transaction.
The EU package now has an official implementation program, but its e-invoicing, digital-reporting, platform, and single-registration measures still land on different dates.
All covered businesses must be able to receive electronic invoices from 1 September 2026, while issuance and e-reporting obligations remain phased by company size.
Poland's 2026 system makes invoice receipt compulsory from the first phase even for businesses whose own issuance date arrives later.
All covered businesses must be able to receive electronic invoices from 1 September 2026, while issuance and e-reporting obligations remain phased by company size.
Poland's 2026 system makes invoice receipt compulsory from the first phase even for businesses whose own issuance date arrives later.
The March 2026 finance-ministry FAQ draws a firm line between machine-processable invoice content and information that exists only in an attachment.
IRAS now publishes a phased path that reaches existing GST businesses by annual supplies after earlier cohorts of new voluntary registrants.
The government has chosen the destination and start date, while architecture, scope, standards, transition, and technical operation still require detailed design.
For the stated turnover population, invoices reported after 30 days cannot be posted to the e-invoice portal, making queue monitoring and escalation material.
Jurisdiction, registration, product, customer, location, exemption, price, currency, and timing drive treatment. A tax engine can apply configured content only to the facts it receives.
Read the market record →Clearance, post-audit, digital reporting, network exchange, schema, signatures, archive, status, and correction models vary by jurisdiction and phase.
Read the market record →Determination, invoicing, ledger entries, adjustments, exemptions, returns, remittance, and authority acknowledgments need a reconstructable chain of evidence.
Read the market record →Tax programs need to distinguish proposals, enactment, technical specifications, pilots, transition windows, taxpayer phases, and enforcement posture before changing production logic.
Read the market record →Inbound and outbound programs need platform, directory, transaction classification, reporting, status, correction, and archive readiness with the applicable company-size phase preserved.
Buyers should require exact edition, syntax, country profile, participant identifiers, access-point role, validation, response, and archive evidence.
Enterprise evaluations should map each product, edition, jurisdiction, data model, integration, service, and accountable owner rather than infer a unified workflow from portfolio breadth.
Buyers should test country coverage and the handoffs, versions, failures, reconciliation, and evidence across each selected module rather than accept a general global-automation claim.
The product should be evaluated as an invoice connectivity and transformation layer with explicit boundaries for tax determination, source data, authority rules, network partners, status, archive, and exit.
Programs should maintain measure-level dates and source status and should not convert implementation work into a claim that every technical interface or Member State rule is final.
The research connects the provider market, normalized capabilities, authority records, operating domains, and source limitations rather than presenting a score or universal winner.
Read the report →