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 tax engine and e-invoicing APIs 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
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.
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.
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.
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.
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 tax engine and e-invoicing APIs 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
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.