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 transaction ingestion normalization and reconciliation 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
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.
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.
Operating domains
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.
Invoice interoperability and network exchange
The technical and operational layer that maps source invoice data to structured formats, discovers recipients, transports documents through networks or platforms, returns statuses, and preserves business meaning across systems.
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 transaction ingestion normalization and reconciliation 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?