Define the operating boundary
A useful definition names the triggering event, required inputs, governing source, accountable owner, decision or action, exception path, evidence retained, and downstream handoff. Buyers should adapt those elements to their own population, jurisdictions, policies, systems, and control model before writing requirements.
The most important distinction is between a label and an operational capability. A provider may document mandate content effective-date and change management while depending on customer-supplied policy, licensed content, third-party data, integration partners, manual review, or services. The demonstration should expose those dependencies rather than hiding them behind a completed interface.
What a demonstration should prove
- Begin with representative source records and a named policy, standard, or controlled rule.
- Show the normal path, an ambiguous case, missing data, an exception, an override, and a material source change.
- Identify who can change rules, who can approve or reject, and how accountability is preserved.
- Trace every output back to inputs, versions, timestamps, user actions, and governing evidence.
- Export the resulting record and reconcile it with downstream systems and retained obligations.
Authority and operating context
EU ViDA
ViDA modernizes EU VAT through phased digital reporting based on e-invoicing, platform-economy measures, and single VAT registration reforms. The package uses several dates rather than one universal compliance deadline. Programs need an EU roadmap that preserves measure, taxpayer, transaction, member-state implementation, and application date. Technology designs must remain edition-aware as implementing specifications and domestic systems evolve.
OECD VAT/GST Guidelines
The Guidelines provide internationally agreed principles for applying VAT or GST to cross-border trade, including neutrality and destination-based taxation. They do not replace domestic place-of-supply, registration, invoice, return, or recovery rules. Global tax logic should preserve domestic rules while explaining how common destination and neutrality principles shape product design. A normalized rule model cannot erase jurisdictional differences.
Wayfair
Wayfair removed the federal constitutional requirement for a seller to have physical presence before a state may require sales-tax collection. Sellers must still analyze each state's enacted thresholds, sourcing, included sales, marketplace rules, dates, and administrative guidance. Nexus-monitoring software needs a state-by-state, time-aware record rather than a universal threshold. A threshold alert is a research trigger, not an automatic registration conclusion.
UK VAT e-invoicing mandate 2029
The UK government selected mandatory e-invoicing for VAT invoices from April 2029 and committed to detailed collaboration and a roadmap. Scope, architecture, standards, transition, exceptions, and technical rules require future official records. Programs can establish governance and invoice-data readiness now, but should not hard-code an assumed clearance or network model before official design and legislation are complete.
France e-invoicing reform
France requires covered businesses to receive structured electronic invoices from September 2026 and phases issuance and e-reporting duties by company size through September 2027. Accredited platforms, the recipient directory, transaction reporting, and payment data are distinct parts of the model. Buyers need entity and size phasing, B2B invoice flow, B2C and cross-border e-reporting, payment-status data, platform selection, directory routing, rejection, correction, and archive evidence.
Germany B2B e-invoice
Germany revised VAT invoice rules so domestic businesses must be able to receive structured e-invoices from 2025 and phases issuance requirements through transition periods. EN 16931-compatible formats such as XRechnung and qualifying ZUGFeRD profiles are addressed in official guidance. The receiving requirement, issuance transitions, structured data, hybrid formats, invoice corrections, attachments, archive, and B2G distinction need separate test cases.
KSeF 2.0
KSeF 2.0 is Poland's official system for issuing, receiving, assigning identifiers to, and storing structured invoices. Issuance is phased, while receipt became mandatory from the first phase; exceptions, consumer invoices, offline modes, QR access, and attachments have specific rules. KSeF requires exact entity, document, authorization, schema, authentication, submission, status, receipt-date, offline, correction, and archive workflows. A generic XML export is not sufficient evidence.
FATOORA
FATOORA first required compliant electronic invoice generation and then introduced authority integration in waves. Tax and simplified invoices use different workflows, fields, security, clearance or reporting, and timing requirements. Providers must demonstrate the correct invoice type, XML or PDF/A-3 treatment, cryptographic and QR elements, clearance or reporting path, authority response, retry, and historical evidence for the taxpayer's assigned wave.
India 30-day e-invoice reporting rule
The GST e-Invoice system applies a 30-day reporting limit from invoice date to taxpayers with annual aggregate turnover of INR 10 crore and above. The portal restriction affects operational timing, backlog handling, corrections, and controls. Systems need transaction-date controls, queue monitoring, rejection handling, IRN and QR evidence, cancellation logic, and escalation before an invoice becomes ineligible for portal reporting.
Operating domains
Jurisdiction, registration, and nexus
The operating process for identifying where an entity may have transaction-tax obligations, measuring applicable thresholds or establishment facts, deciding whether registration is required, and maintaining authority accounts and effective dates.
E-invoicing and continuous transaction controls
The jurisdiction-specific process for producing structured invoice data, validating legal and technical rules, exchanging or clearing the document, reporting data to an authority, receiving status, correcting failures, and preserving an accepted evidence record.
Returns, reconciliation, and remittance
The process for assembling source transactions and adjustments into jurisdiction returns or reports, reconciling books and invoices to declared amounts, submitting through authority channels, managing payments, and preserving acknowledgments.
Purchase-side use tax and VAT recovery
The review of supplier invoices and employee or corporate spend for tax charged, use-tax accrual, deduction or recovery eligibility, documentation, adjustments, and reconciliation to accounts and claims.
Mandate content and change control
The governed process for monitoring authority change, classifying source status and dates, assessing applicability, updating content and configuration, testing affected workflows, releasing changes, and preserving historical decisions.
Evidence and comparison limits
Official provider documentation can establish product positioning. Provider confirmation can clarify package or availability. Independent observation requires a disclosed scenario, environment, date, inputs, and reproducible result. None of those sources alone establishes buyer-specific legal, clinical, regulatory, quality, or operational fitness.
Buyer questions
- What exact outcome and evidence should mandate content effective-date and change management produce?
- Which source, version, and customer facts govern the workflow?
- Which decisions remain human and who is accountable for them?
- What is native, configured, integrated, service-delivered, or planned?
- How does a changed source affect open and historical records?
Recent changes
Avalara's maintained catalog spans determination through e-invoicing — Enterprise evaluations should map each product, edition, jurisdiction, data model, integration, service, and accountable owner rather than infer a unified workflow from portfolio breadth.
European Commission publishes 2026 ViDA implementation work — 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.
German finance ministry updates B2B e-invoice FAQ — Provider mappings and buyer tests should preserve structured required fields, format profile, validation, correction, readable rendering, and archive rather than accepting a format-name claim.
Singapore extends GST InvoiceNow to all registered businesses by 2031 — Entity records need registration path, annual-supplies population, implementation date, exclusions, solution readiness, network status, and IRAS data-transmission evidence.
UK government chooses mandatory VAT e-invoicing from April 2029 — Organizations can improve invoice data and governance now but should keep architecture, scope, standards, exceptions, and technical implementation in not-established status until official design records are issued.