One read of the books, and the season’s work comes off it.
Most audit software asks you to prepare the data for it. Audcrix reads the client’s books once, straight from Tally, and every module works from that same read — which is a different thing from importing the same file into six places.
01
The books are read once, over a channel the client never opens a port for
A small agent on the client's machine dials out to Audcrix and holds the line open, waiting for work. Nothing dials in. There is no inbound port, no port forward and no firewall exception, because the direction of the connection is a property of how it is built rather than a setting somebody has to maintain.
02
Everything is classified on that one read
Ledger groupings, party identity, TDS sections, GST heads — all settled once, against the books as they actually are rather than against an assumed chart. Every module downstream inherits that single classification, which is why the tax audit, the statutory audit and the GST workbench agree with each other rather than having to be reconciled to each other.
03
The population is tested, not a sample drawn from it
51 accounting checks and 40 fraud tests, run on every voucher — never a sample Sampling exists because reading everything used to be impossible. It is not impossible any more, so the engine reads everything and the sample becomes a choice rather than a constraint.
04
Every figure carries the vouchers underneath it
A number on a face is a link to its composition, and from there to the entry in the client's books. The reviewer's question — where did this come from — is answered on the page rather than by reopening the file. A correct figure with no visible basis is indistinguishable from a wrong one, and gets queried like one.
05
Where it cannot tell, it refuses rather than guesses
An allocation the books do not settle is not quietly assigned to whichever party looks likeliest. It is flagged for a decision, with the reason stated. A silent guess that happens to be wrong is the one failure an audit file cannot absorb, because nothing in the file records that a guess was made.
What runs on every engagement
- 51 accounting checks and 40 fraud tests, run on every voucher — never a sample
- Filing-ready Form 3CD, all 21 CARO clauses, and GST returns matched to the books
- Tally read over a paired outbound channel — no inbound port opened on the client's machine
Those are counts taken from the engines themselves rather than round numbers chosen for a brochure, and a harness re-counts them on every deploy so the page cannot drift from the product.
Where the work goes next
Each module is described on its own page — what it reads, what it tests and what it refuses to assume. See all modules, or read how a client’s books are handled in Assurance.