One foundation, many applications
Every tax on this page shares one root cause: the execution logic beneath it. Fix that layer once and each tax becomes an application on the same foundation.
That is why the same foundation shows up in application after application. The four building blocks stay constant. What changes is the input: an invoice, a wagering transaction, a time record, an agent's mandate. Each application feeds a different economic event into one real-time verification layer, and gets back proof instead of a copy of the data.
The applications below sit at honest, different stages. One is a working prototype. One is an R&D track. One is a proposal. One is on the horizon. Each runs alongside the others, and every phase carries its own go or no-go.
Real-time VAT
Invoice and POS events → real-time VAT routing and proof.
VAT is the first and most tangible application. It is a working prototype, developed and tested with the Netherlands Tax Administration in an R&D setting, where market parties participated in the trials.
In the pilot, VAT splits off to the tax authority at the moment of payment, the rest goes to the business. No separate filing, because the proof sits inside the transaction itself. What used to be a return filed weeks later becomes a verification that happens as the payment clears.
That shift is easiest to see rather than describe. Watch the split happen in the live demo, and read how the four building blocks fit together in the architecture. The mechanism has a name of its own: split payment.
Gambling tax
Transaction events from operators → compliance proof without raw data.
An R&D track exploring real-time database audit for gambling tax.
A real-time database audit is a way to confirm that the figures inside an operator's own systems are correct as transactions occur, rather than requesting and copying the underlying records to check them afterwards. The authority gains certainty that the tax base is right, and the operator's raw data stays where it is.
The foundation is the one already carrying VAT. Only the input changes: instead of invoices, the events are the transactions flowing through an operator's platform. The output keeps the same shape, proof that the amount owed is correct, verifiable without the detail behind it ever leaving the operator. This track runs alongside the VAT pilot, at its own earlier stage, with its own go or no-go. The building blocks are shared in the architecture, where real-time reporting is defined.
Construction
Time-registration events → continuous permanent-establishment detection.
A proposed application: continuous permanent-establishment detection.
When a foreign company works on a site long enough, it can create a taxable permanent establishment. Today that threshold is reconstructed after the fact from paperwork and site records. With time-registration events feeding the same verification layer, the count can be watched continuously and flagged the moment it is crossed, rather than surfaced in an audit a year later.
The timing gives this application its urgency. The Dutch Wtta takes effect on 1 January 2027, with enforcement by the Netherlands Labour Authority from 1 January 2028. Continuous detection turns that obligation into something a business can satisfy at source. This is a proposal, running alongside the live tracks at its own stage, with its own go or no-go. It rests on the same architecture and the same principle of compliance by design.
Agentic commerce
Agent-mandate-bound transactions → proof of mandate compliance.
Horizon: agent-mandate-bound transactions.
As autonomous software agents begin to transact on behalf of people and businesses, one question comes with them. How do you prove an agent stayed inside the mandate it was given? The building block already exists in the foundation: digital identity that establishes who, or what, is acting, with certainty and without exposing the file behind it.
This is a horizon application, not a current capability. It marks where the same foundation could reach as agents enter commerce, and it is framed as direction rather than a product on offer today. The glossary carries the full vocabulary, and the common questions this raises sit in the FAQ.
The pattern underneath
Across all four, the pattern is the same. The economically relevant moment is the right moment to verify for tax. A payment, a wager, an hour worked, a mandated purchase, each is an event, and each event can carry its own proof. That is why one foundation stretches across domains that look unrelated on the surface, and why a new application means a new input rather than a new system.
See the split happen in the live demo, or book a demo to walk your own domain through the foundation.