Load the contract population
Contracts are uploaded or imported. Draft register entries are generated with the extracted terms flagged for confirmation.
Every check cites the provision it applies. A result you cannot trace is a result you cannot defend.
Compliance Engine maintains the registers and checks that consume a disproportionate share of a close cycle: the lease inventory under GASB 87, the subscription arrangement inventory under GASB 96, fund balance classification under GASB 54, and the completeness and internal consistency of note disclosures.
It is built around a working paper model. Each check produces a result, the records it examined, the provision it applied, and a place for the preparer's conclusion — the artefacts an auditor will ask for, produced as a by-product rather than reconstructed afterwards.
Interface mockup. Values shown are illustrative and do not represent any entity.
Typical first deployment reaches steady state within one to two quarters, depending on the state of the source data.
Contracts are uploaded or imported. Draft register entries are generated with the extracted terms flagged for confirmation.
Term, options, discount rate and scope conclusions are reviewed and recorded with the reasoning. The reasoning is retained for successors.
Registers, balances and disclosures are tested. Each exception names the provision and the records involved.
Results, evidence and conclusions export as working papers with a complete change history.
We publish this section for every tool. It is the section we would want to read first.
Walk through the platform with your own chart of accounts, or start with the research library. Both routes are free to begin.