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 audit trail document archive and evidence export 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 eInvoicing and EN 16931
The EU framework established structured electronic invoicing in public procurement and a common semantic data model. Country rules, CIUS profiles, transports, routing, archives, and business-to-business mandates remain separate implementation layers. A claim of EN 16931 support does not establish country-profile conformance, legal invoice validity, routing, authority reporting, or acceptance. Buyers need format, profile, validation, transport, and status evidence.
Peppol BIS Billing 3.0
Peppol BIS Billing defines business terms, syntax bindings, rules, code lists, and validation artefacts for invoice and credit-note exchange over Peppol. It does not by itself establish tax treatment or every country mandate requirement. Peppol support needs edition, document type, country profile, participant discovery, access-point role, validation, response, and archive evidence. A network connection is not a universal authority clearance connection.
SSUTA
The Streamlined Sales Tax program coordinates specified definitions, registration, rate, sourcing, filing, and certified service-provider arrangements among participating states. Coverage and seller eligibility require direct review. Provider participation can affect services and economics, but a certified-provider label does not establish every state, product, transaction, or seller obligation.
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.
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.
Singapore GST InvoiceNow
Singapore requires phased populations of GST-registered businesses to transmit invoice data to IRAS using InvoiceNow-ready solutions and the Peppol-based national network. Population and implementation date depend on registration path and annual supplies. A buyer must establish population, date, exclusions, solution readiness, Peppol exchange, data transmitted to IRAS, due dates, corrections, and operating responsibility rather than treating network onboarding as the complete tax control.
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.
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.
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.
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.
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.
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 audit trail document archive and evidence export 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
France begins universal e-invoice reception and first issuance phase — Inbound and outbound programs need platform, directory, transaction classification, reporting, status, correction, and archive readiness with the applicable company-size phase preserved.
Peppol BIS Billing 3.0 remains the base profile for network invoice exchange — Buyers should require exact edition, syntax, country profile, participant identifiers, access-point role, validation, response, and archive evidence.
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.
Storecove documents one API for network and country e-invoicing routes — 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.
ZATCA refreshes the FATOORA phase and invoice-type record — Country coverage claims need taxpayer wave, invoice type, schema, security, clearance or reporting path, authority status, rejection, and archive evidence.
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.
Poland starts KSeF 2.0 mandatory receipt and first issuance phase — AP receipt, authentication, invoice retrieval, identifiers, statuses, source posting, outbound issuance, fallback, and archive need a unified but phase-aware operating record.
India applies 30-day e-invoice reporting limit to INR 10 crore population — Invoice-age monitoring, rejection response, escalation, IRN evidence, cancellations, corrections, and reconciliation must operate before the portal window closes.