Fonoa keeps global tax determination, IDs, invoicing, and returns modular
The API-led portfolio targets digital platforms and internet businesses, with each module carrying a different fact, authority, and evidence boundary.
Editorial figure by Indirect Tax Monitor. Source context: Fonoa.
Modularity makes handoffs visible
A tax ID result, tax calculation, customer invoice, authority e-invoice, and periodic return are related but different records. An API-oriented buyer should define how identifiers, transaction facts, currency, rounding, corrections, and evidence move between them.
The architecture can be attractive to product teams that need tax close to billing and commerce. It also creates an obligation to govern API versions, latency, fallback, idempotency, retries, error states, authority credentials, and reconciliation to finance records.
Coverage should be tested as scenarios
Country lists need to become testable combinations of entity, transaction, product, customer, invoice, authority, and filing workflow. A provider may support determination in one jurisdiction and e-invoicing or returns in another without the same depth.
Buyers should require a source-backed coverage matrix and run edge cases through each selected module. The Monitor records documented scope and limitations; it does not accept broad global or automation language as evidence of a tax result.
Enterprise buyer test
Translate this change into the exact population, record type, workflow stage, decision owner, effective date, and evidence that could be affected. Ask current or prospective providers to demonstrate the named workflow with representative data and an exception—not a polished feature tour. Record what official documentation establishes, what a provider states, what the team observes, and what remains unresolved.
A defensible review also identifies the dependency outside the product. Authority interpretation, policy configuration, data quality, integrations, human judgment, approval rights, release governance, training, and retained evidence may remain customer or service responsibilities. The evaluation should preserve those boundaries instead of treating a technology claim as the complete operating model.
What we will watch next
Indirect Tax Monitor will watch the named source and affected market records for later evidence that changes status, scope, availability, implementation timing, workflow consequence, or the limits of the initial report. A later announcement does not silently overwrite this dated account; the change ledger preserves the sequence.