India Audit Lens
Run automated audit and Ledger Scrutiny checks
Use Ledger Scrutiny for deterministic exception checks over imported records. Use Audit (Beta) to create a versioned automated-audit run across the agents enabled for your firm. Both surfaces produce review…
By India Audit Lens product team · Updated 2026-08-26
Before you begin
Open the correct client and engagement and confirm the period under examination. Make sure the latest books, mappings, materiality, and relevant source evidence are available. Confirm who will prepare the work and who will review it. Do not conclude from a dashboard count alone; inspect the underlying records and evidence.
Run the Ledger Scrutiny review
Confirm that the engagement's books have been imported and normalised. Open Examination → Ledger Scrutiny. Confirm the dataset identity, source/import batch, period, import counters and active normalized record populations shown on Overview. Review the factual totals for checks performed, checks not performed, procedures with exceptions and affected records. These are results, not an automated audit-readiness conclusion. Work through the six CA-facing views: Overview, Accounting, Period & cut-off, Master data, Transactions, and Evidence. Select a procedure and review Population, Tested,…
Exception-table columns are generated from the check and therefore vary. Typical fields include party, PAN/GSTIN, invoice/voucher reference, date, amount, narration, HSN/rate, payment reference and the reason the record was flagged.
Dataset provenance is not a separate work area. Overview retains the exact source, import batch, period, counters, active populations and evaluation fingerprint. Structural checks also continue to run, but appear where the CA reviews their consequence: journal, sales, purchase and payment linkages under Transactions; GL and trial-balance account references under Accounting; and canonical classifications under Master data.
Capture or escalate a data exception
Run and review Audit (Beta)
Availability and output depend on the firm's enabled feature settings. If no agents are enabled, a run may complete without workpapers or findings.
Open Audit (Beta) in the engagement. Confirm the intended engagement and that the required imported data is complete. Click Run Audit once. Leave the run in progress; do not start a replacement simply because it takes time. When complete, note the new audit version and review Workpapers and Findings. Use Search, Risk, Domain and Data quality only to triage the list. Click a finding to review the affected population, supporting transactions, what to verify, why it matters and linked workpaper/review state. Open Company Health for a high-level orientation and follow its linked finding chips…
Do not compare counts across versions without also considering data snapshot, feature configuration and run time. Do not copy a health status or Doctor narrative into a signed conclusion without review and corroboration.
Expected result
The deterministic check population and the selected automated-audit version are reviewed; evidence supporting real exceptions is preserved; false positives and data gaps are documented; and only human-reviewed matters progress to Findings, issues, document requests or conclusions.