Audit

Audit analytics and assurance over the accounting estate. It reads the general ledger through Connector's canonical model, proves the books reconcile (Dr = Cr, trial balance, statement identities), finds gaps between business areas rather than inside them — sales × inventory, sales × cash, purchases × inventory — runs configurable journal-entry tests with Benford analysis, validates financial-statement metrics against the figures the accounting system itself prints, traces entities through the ledger, and closes findings through a PDCA cycle where closure is a clean re-run of the procedure that found the issue, never an email saying "fixed".

Important decision-use notice. Audit output is an analytical indication, not an audit opinion, review conclusion, attestation or certification. A run is not an audit under ISA/GAAS or the IIA framework and does not replace professional judgement. Completeness of the data supplied, sampling and scope judgements, materiality settings and every decision remain the Customer's; independent human review is required before any material or adverse action. Purchase and trial require separate acceptance of the Audit Plugin Special Terms and Assurance Limitation Acknowledgment.

What separates it: it refuses to answer what it did not measure. A period that does not balance turns every metric off with the reason; unmapped accounts are named, not netted away; a reconciliation whose grain the model cannot measure says which axis is missing; a measured zero and an unreported value never share a representation. An account carries a role assigned by a chart-of-accounts pack — the same screens work on a Russian, US, SAP or NetSuite chart of accounts, and a role read from the system is stamped differently from one inferred from a name. Access to the source system is read-only, always.

With Compliance installed the two exchange signals over the event bus: a detector hit is answered with how much money actually flowed through that party, and a blacklisted counterparty's postings are tested against the ban window. Audit works without Compliance and simply loses those loops.

Requires the Connector module for data: audit consumes the canonical ledger entities Connector publishes on the event bus (accounts, postings, printed balances) — plan for both line items. Priced per tenant (company) per month on flat Basic / Pro / Max tiers; capability fences are enforced in the plugin itself, and the scope disclosure is never gated on any tier.