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 VAT and GST determination 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.
Canada digital-economy GST/HST
Canada's digital-economy measures address nonresident digital suppliers, platform operators, qualifying goods, and short-term accommodation through simplified and normal GST/HST regimes. Several tests can apply to one business. Systems must represent supplier role, platform role, customer status, supply type, location, registration regime, and province rather than applying one digital-services tax flag.
MTD for VAT
MTD for VAT requires covered businesses to keep specified digital records and submit VAT returns through compatible software. It is a digital record and return framework, not the same as the announced future UK e-invoicing mandate. Buyers need to separate digital records, links, return submission, invoice exchange, and the forthcoming 2029 invoice mandate when assigning products and controls.
Operating domains
Tax determination, taxability, and sourcing
The transaction-time decision that combines seller and buyer entities, registrations, locations, product or service classification, exemptions, price, currency, date, sourcing, place-of-supply, and maintained rules to produce tax treatment and evidence.
Exemptions, tax IDs, and customer evidence
The collection, validation, application, expiry, and retention of resale certificates, exemption documents, VAT or GST identifiers, location evidence, and customer-status records used in transaction treatment.
Marketplace and platform liability
The determination of when a marketplace, digital platform, or merchant-of-record is treated as supplier, facilitator, collector, reporter, or transaction party and how responsibilities divide with the underlying seller.
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.
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 VAT and GST determination 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.
Fonoa documents a modular global tax API portfolio — 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.
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.