Why it exists

Across nineteen years of indirect tax implementations, the same failure kept appearing. A tax engine returns a rate, the ERP posts it, and six months later nobody can explain why a particular cross-border line was treated the way it was. The rate was rarely the hard part. The place of supply, the liable party, the registration status and the evidence behind the decision were.

Aurevat is built around that gap. Every determination carries the provision it rests on and the facts it used, so a reviewer can argue with the reasoning rather than accept an output. That is the whole idea, and it is why the demo shows the rule, not just the number.

Where we actually are

Pre-revenue, with no customers. The determination logic for India GST and EU-27 VAT is working and testable today. Export-based ERP connectors (SAP, Oracle, D365, NetSuite, Tally, Zoho) are live today. Scheduled API pulls and statutory report formats are in build. Live filing submission is not built at all, and we do not pretend otherwise on the pricing page.

The earlier version of this site carried outcome statistics and a customer logo strip that we could not substantiate. Both are gone. If you saw them, they were wrong, and removing them cost us less than keeping them would have.

How we work with early partners

Small, written, reversible. A scoped pilot on a real transaction export, a fixed duration, and a clear deliverable — the flagged lines with the reasoning beside them. Nothing about a pilot depends on you committing to an annual contract first.