Glossary

Compliance by design

Definition. Compliance by design is an approach in which regulatory requirements are built into the systems and processes that carry out an activity, so that compliance is produced automatically as the activity happens, rather than checked and corrected afterwards.

Context

Compliance by design borrows its logic from privacy by design, the principle that data protection should be engineered into a system from the outset rather than added as a control on top. Applied to tax, it means that the rules, the right VAT rate, the correct split, the required report, are embedded in the accounting, invoicing and payment flow itself. When compliance is a property of the system, the default outcome is the correct one, and getting it wrong requires deliberately working against the design rather than simply making an ordinary mistake.

This reframes the relationship between business and authority. The traditional model is file-then-check: the taxpayer submits a declaration and the administration verifies it later, often through audits that reconstruct events long after they happened. Compliance by design moves the assurance forward in time, so correctness is established as value changes hands. The paradigm shift is from more data after the fact to more certainty up front.

Compliance by design matters because it lowers cost and friction on both sides. Businesses spend less effort proving they did the right thing, and authorities spend less effort catching those who did not, because the system makes the compliant path the path of least resistance. It is the organising idea behind seamless taxation and behind the OECD's Tax Administration 3.0 vision.

The honest nuance is that building compliance into a system concentrates responsibility in the design of that system. If the embedded rules are wrong, opaque or hard to audit, errors scale automatically too. Credible compliance-by-design systems therefore pair automation with verifiability and privacy safeguards, so that the fact of compliance can be proven without exposing everything and without asking anyone to simply trust the box.

Source

  • Four reusable building blocks (event streaming, digital identity, cryptographic proof, privacy-preserving verification) underpin this approach, as set out on the architecture page and in the Netherlands Tax Administration real-time VAT work.