Embed compliance or build it: the maths for ERPs and accounting firms
Updated 2026-08-01 · 7 min read
Building compliance looks like a bounded project until the second country. Then it becomes a permanent team, because rules move and someone has to watch them.
The costs people forget
The initial build is the cheap part. The recurring costs are regulatory monitoring, format versioning, per-country certification, support load when an export is rejected, and the opportunity cost of engineers not working on your actual product.
- One engineer permanently allocated to format and rule maintenance
- Re-testing every profile whenever an authority publishes a revision
- Support tickets that require tax knowledge to triage
- A compliance defect in production is a customer's legal exposure, not just a bug
What integrating once looks like
You keep your invoicing UI, your customer relationship and your pricing. You call one export endpoint with a canonical invoice and a jurisdiction profile, and receive a compliant document plus an audit record.
New country support arrives as a new profile identifier, not as a project in your roadmap.
The commercial shape
A master account holds your client workspaces. Usage is metered per exported invoice with idempotency, so a retried API call never double-bills. Sandbox keys let your team integrate and test without generating charges.