Why we plan to build it
Most finance controls are tested after the fact. At the end of a quarter or a year, someone takes a sample of transactions, checks them by hand and records the result. It is slow, it only covers the sample, and it tells you about problems long after they happened.
The weakest point is usually the handover between systems. A control can be well designed inside your ledger and still miss the activity that never reached it. Compliance Assurance is being designed to close that gap.
What Compliance Assurance will do
Compliance Assurance will check that operational activity matches your policies and controls, continuously rather than by sample, and record the outcome of each check. The planned capabilities include:
- Continuous control tests mapped to your control framework.
- An evidence record for each check: what was compared, why it passed or was flagged, and how confident the match was.
- A review log showing who reviewed each flag and what they decided.
- Audit-ready exports, so evidence for a period is collected as the period happens.
Built on the engine that is live today
Compliance Assurance will reuse the three-layer matching engine and human-in-the-loop review that already run Revenue Assurance for HubSpot and Xero. Every flag Revenue Assurance raises today already carries a confidence score, the evidence behind it and a record of who reviewed it.
Access will stay read-only. Auditor Alpha is hosted on SOC 2 Type II–audited cloud infrastructure; Auditor Alpha itself has not yet completed a SOC 2 audit. You can read the full detail on our security page.
Where things stand
Compliance Assurance is on our roadmap and is open to design partners. It is not generally available, and we won't give a release date until it's ready. Join the waitlist below to shape what we build and be told when it launches.
If you run HubSpot and Xero, Revenue Assurance is available now, and its flag history already gives you an evidence trail for the CRM-to-ledger control.