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 product service and customer taxability classification 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
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.
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.
Tax master data and classification
The governance of legal entities, registrations, products, services, customers, suppliers, locations, exemptions, accounts, document types, and mappings that tax engines and invoice systems rely on.
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.
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 product service and customer taxability classification 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?