PPAE-001critical severity
Asset capitalised without commissioning evidence
Quantom
Forensic ledger engine
The audit, run against every row.
Quantom reads a client’s general ledger where it already lives, runs a library of rules built for Indian audit over every line, and returns flags an auditor can act on. The reasoning behind each flag stays in the file, so a finding questioned months later still has an answer.
General ledger · 10 of 1,04,281 rows shown
04-04-2025Steel plate — Meenakshi Metals₹18.45 L
04-04-2025Depreciation — plant & machinery₹9.62 L
07-04-2025Freight inward — cashSTLA-007₹38,000
09-04-2025Finished goods — Coimbatore depot₹41.20 L
11-04-2025CWIP transfer — line 3 commissioningPPAE-001₹1.24 Cr
14-04-2025Consumables — Sri Vaari TradersINV-031₹2.15 L
16-04-2025Collection — Anand Auto ComponentsTR-022₹28.60 L
18-04-2025Professional fees — retainerCACE-004₹1.75 L
21-04-2025Provision — warranty₹6.40 L
23-04-2025Packing material — monthly₹96,300
6 questions returned
₹1.24 Cr
CWIP-014high severity
CWIP ageing beyond one year with no movement
TR-022high severity
Receivable outstanding past 180 days, unprovided
STLA-007medium severity
Cash payment to a single party crossing the day limit
INV-031medium severity
Negative stock on a closing date
CACE-004low severity
Round-sum expense booked on the last day of the period
Illustrative product data. No client ledger is shown.
The buyer problem
A ledger this size cannot be read.
A statutory audit ledger now runs past a lakh of rows. Reading through it, or sampling a slice and hoping the rest holds, was never really an audit method — it was a limit on how much attention one file could get.
-
Volume outgrows sampling.
Testing a few hundred entries out of a lakh does not scale to what an Indian statutory audit now has to cover, and it never surfaces the exception sitting in row eighty thousand.
-
Reasoning that is never recorded does not survive review.
A balance gets cleared over a call and the file moves on. When the question returns at review or inspection, the reasoning behind it is gone with the person who gave it.
How it runs
From the client’s Tally to a signed report.
-
Tally
A desktop connector runs on the client machine and streams the ledger across. Nothing is mailed, nothing is re-keyed.
-
Ingest
Ten lakh rows and more, normalised into a columnar store built for scanning rather than browsing. Every voucher — date, number, party, both legs — is in the app from here on; nobody goes back to Tally for reference.
-
Rules
Declarative rules compile down to analytical SQL and run across the whole ledger, not a sample.
-
Findings
Each hit carries a rule id, an amount, a severity and a reason an auditor can read without opening the ledger.
-
Review
An auditor opens the evidence behind a finding, shares it with the client or proposes the adjustment from it, and the trail stays on the file against the person who acted.
-
Report
What was tested, what fired, what did not, and what the auditor concluded — as one document.
The rules library
Built for the Indian balance sheet, not a generic anomaly feed.
Rules are grouped by where they sit in the Schedule III balance sheet and profit and loss statement, and each is parameterised per engagement so thresholds match the client in front of you rather than an average. Where a rule tests a specific section or Standard on Auditing, it says which. Journal-entry tests cover unusual timing, round numbers and high-value entries, including the year-end entries SA 240 asks about. A firm writes its own rules in the builder — filters, aggregations, duplicates, sequence gaps, Benford — and tests them against its own books before saving.
- PPAE
- Property, plant and equipment
- CWIP
- Capital work in progress
- INV
- Inventory
- TR
- Trade receivables
- CI
- Cash and investments
- STLA
- Short-term loans and advances
- LTLAA
- Long-term loans, advances and assets
- CACE
- Current assets and current expenses
- OCFA
- Other current and financial assets
- NCI
- Non-controlling interests
Actual Quantom interface · Demonstration data
Review
A junior can work it. A partner can defend it.
Flags arrive sorted by severity and amount, so the biggest exposure is read first. Every action — a finding shared with the client, an adjustment proposed from it, a review recorded — is logged against the user who took it, with the reasoning attached.
Review trail
- PPAE-001 Shared with client
No commissioning certificate on file. Sent to the client for the certificate before sign-off.
- TR-022 Reviewed
Ageing verified against the balance confirmation received from the client.
- CACE-004 Adjustment proposed
Provision short by the amount tested. Proposed the journal from the finding for the partner to approve.
The output
A report that survives being questioned.
The deliverable states what was tested and what was not. Rules that did not fire, rules that were disabled, and rules that had no data to run against are all disclosed, because being able to prove the scope of testing is the point of the exercise.
What the report discloses
- Tested
PPAE — property, plant and equipment. Every rule ran across the full ledger.
- Tested
TR — trade receivables. Every rule ran across the full ledger.
- Not tested
NCI — non-controlling interests. No qualifying balance existed in this ledger.
- Disabled
OCFA-014 — turned off for this engagement; the threshold does not apply to this entity type.
Actual Quantom interface · Demonstration data
Actual Quantom interface · Demonstration data
From findings to financials
Every figure traces back to a voucher.
The audit does not stop at a list of flags. The same file carries the statements, the notes, the policies and the adjustments, and each of them can be opened down to the entry it came from.
-
Drill from a statement line to the voucher.
A figure on the balance sheet opens to its note where one is bound, then to the account groups and ledgers that make it up, then to the voucher with both legs showing. Four hops, one panel, no export in between.
-
The ledger, month by month.
Any ledger charts its debit, credit and net movement across the year. Click a month and it opens day by day, so an unusual run of entries is seen rather than searched for.
-
Adjustments proposed from the finding.
An audit journal can be raised directly from a flag, or uploaded in bulk from an Excel template with a preview before anything posts. Quantom never writes back to the client’s Tally — the connector is read-only by design.
-
Statements in the format the entity requires.
Schedule III Division I under AS, Division II under Ind AS, and the ICAI non-corporate format. The entity type decides which applies, and the notes regenerate from the live trial balance rather than being typed in.
-
Accounting policies that belong to the client.
A framework-aware set of policies, worded for the standard in force, that the auditor edits per client and per year. What was changed stays changed the next time the file opens.
-
Out as Excel or PDF.
Statements, notes, the findings workbook and the journal register download as Excel; statements and the findings report as PDF. Nothing is retyped to leave the system.
Before day one
What a firm needs to start.
Nothing here asks a client to change how they keep their books, and nothing asks the firm to open a port.
-
The books.
Tally Prime, reached across your own network. Tally does not have to sit on the machine running the connector — both the host and the port are set in the connector itself. The link out to Quantom is outbound only: nothing is exposed to the internet, no port forwarding, no static IP.
-
The machine.
Windows 10 or 11. The connector installs like any Windows application and sits in the tray, or runs as a Windows service where IT would rather it did. Its one dependency is Microsoft’s WebView2 runtime, already present on Windows 11 and on most maintained Windows 10 machines.
-
Or simply an export.
A firm that would rather not install anything — or whose client runs SAP, Oracle or another ERP — uploads the books instead: .xlsx, .xls or .csv. There is no template to fill in. Quantom reads the columns it is given and maps them; where it is not confident, it offers a suggestion and waits rather than deciding on your behalf. A trial balance needs ledger names and closing balances. A general ledger needs dates, vouchers, amounts and narration.
One practice
The engagement is the bridge.
Klok carries the client, team and deadline. Quantom carries the ledger, finding and conclusion. Raukon keeps the context between them intact.
A clearer practice
Run it against your own ledger.
Start the trial and see what Quantom finds in a live engagement, not a demo file.