The method below is the one articled trainees learn on their first audit — formalised so it can be documented and reviewed. Applied honestly to every significant ledger, it catches more misstatements per hour than almost any other fieldwork procedure.
Every ledger starts where last year’s audited statements ended. An opening balance that does not tie to the prior-year closing is the first exception to log — before reading a single entry.
The most common finding in practice: entries that do not belong to the head — a capital item sitting in repairs, a director’s personal expense in staff welfare, a loan routed through a supplier account. Ask of each significant entry: does this belong here?
A trade receivable with a credit balance is usually an advance, a wrong posting or an unadjusted receipt; a creditor with a debit balance is an advance to supplier or a debit note story. Wrong-direction balances change Schedule III classification, so they are audit adjustments, not curiosities.
Round sums, period-end and post-close postings, weekend or holiday entries, reversals, entries with vague narrations ("being amount adjusted"), and seldom-used account pairings. These are the entries that earn voucher-level testing.
For each expense head: was TDS deductible, and deducted at the right section and rate? For each purchase/expense with GST: is the ITC claim consistent with the nature (blocked credits under Sec 17(5))? Ledger scrutiny is where 40(a)(ia) disallowances and ITC reversals are caught before the return is filed.
Names recur — directors, their firms, group companies. Flag transactions with them for Sec 188 / AS 18 / Ind AS 24 evaluation and for the Form 3CD clauses. A ledger read is the cheapest related-party discovery tool an auditor has.
Entries in the last week of March and the first week of April decide whether income and expense sit in the right year. Match them to documents — GRNs, invoices, bank dates — not narrations.
Balances that matter get external evidence: confirmations, bank statements, GST portal data, 26AS. Then write the conclusion per ledger — clean, or exceptions listed with resolution — so the working paper stands on its own.
The checklist template turns the method into a per-ledger sheet — header block, the checks, an exceptions table with voucher references, and a conclusion line a reviewer can sign against.
When the client has four thousand ledgers, CORAA reads all of them — deterministic checks across the full population, exceptions explained in plain English, every number drilling to its voucher. See AI ledger scrutiny or start free: your first audit is on us.
Ledger scrutiny is the systematic examination of each ledger account — its opening balance, every significant entry, and the closing balance — to check that entries belong to the account head, are supported by evidence, comply with tax law, and land in the right period. It sits between the trial balance review (too summary) and voucher testing (too granular): scrutiny is where the auditor reads the books as books.
Vouching starts from a transaction and checks its evidence — invoice, approval, payment. Scrutiny starts from the account and checks its story — does the pattern of entries make sense for this head, is the balance direction right, do the totals reconcile. Vouching proves individual entries; scrutiny catches mispostings, missing entries and wrong classifications that no single voucher would reveal.
Risk-first: cash and bank (fraud surface), loans and advances (Sec 185/186 and deemed-dividend exposure), related-party accounts, expense heads with TDS applicability, purchase ledgers with heavy ITC, and any account with a wrong-direction balance or heavy period-end activity. In a small entity, scrutinise everything — the population is readable in a day.
Reading every ledger and every entry rather than a risk-based selection. Manually that is impractical beyond small entities, which is why software now does the reading: deterministic checks sweep the full population — balance directions, mispostings, tax applicability, period-end patterns — and surface only the exceptions for the auditor’s judgment. The auditor still concludes; the machine just never gets tired on ledger 4,000.
No ICAI-prescribed format exists; the convention is a per-ledger sheet: header (ledger, group, opening/debits/credits/closing), the checklist applied, an exceptions table with voucher references and resolutions, and a conclusion. The free template on this page follows that convention and is editable in Word.
