GL-to-voucher matching + fraud indicator detection — ledger voucher scrutiny working paper in under 30 seconds.
| Posting Date | Voucher No | Account Head | Party Name | Narration | Debit (Rs) |
|---|---|---|---|---|---|
| 2026-02-10 | JV-0142 | Professional Fees | Acme Corp LLP | Audit retainer Q4 | 85,000 |
| 2026-02-14 | JV-0143 | Repairs & Maintenance | Acme Corp Services | AC servicing Feb | 50,000 |
| 2026-02-17 | JV-0144 | Conveyance | Cash | — | 12,500 |
| 2026-02-28 | JV-0146 | Legal Fees | Acme Corp LLP | Retainer Nov 2025 | 1,75,000 |
For a mid-market company running 50–500 active general ledger accounts, the monthly ledger voucher scrutiny exercise is one of the most labour-intensive tasks a finance team faces before each statutory audit.
A senior accountant must open the GL extract, locate the corresponding voucher in a separate register, verify amounts agree, confirm a supporting document reference exists, check for self-approvals, and flag date gaps — 300–800 vouchers per month, entirely in spreadsheets. The task cannot be delegated without risk and cannot be skipped without regulatory exposure.
Amount mismatches, missing supporting bills, self-approvals, out-of-period vouchers, and blank narrations each require a different lookup pattern across two separate Excel files. Missing even one class in a manual pass creates a gap the statutory auditor will find — and document — during fieldwork under ICAI SA 500 (Audit Evidence) requirements.
A manually assembled spreadsheet comparison has no audit trail: it does not record who ran which check, when, or on which version of the files. ICAI SA 230 (Audit Documentation) requires that working papers be sufficiently detailed to allow a second auditor, with no prior connection to the engagement, to understand the evidence gathered and conclusions reached — a standard a manually annotated Excel file does not meet.
Round-sum entries posted on weekends are among the most reliable fraud risk indicators in the ICAI Guidance Note on Audit of Expenses and ICAI SA 240 (The Auditor’s Responsibilities Relating to Fraud) — yet detecting them requires comparing every posting date against a calendar and every amount against a divisibility rule across hundreds of rows. No manual reviewer does this systematically under time pressure at period close.
The cost of manual GL voucher matching before each statutory audit for a company with 300–800 monthly journal entries. Controllers at Acme Corp Pvt Ltd and similarly-sized mid-market entities report this as the single largest controllable time drain in the pre-audit period close cycle — and the one most likely to produce an auditor observation when rushed.
Ledger voucher scrutiny sits at the intersection of four mandatory obligations in Indian financial reporting. Each card below represents a distinct regulatory anchor that this workflow’s output directly satisfies.
The statutory auditor must report whether the company has kept proper books of account as required by law. This test depends directly on whether every ledger entry is traceable to an authorised, documented voucher. An untraceable entry is a reportable deficiency — it appears in the audit report and becomes public in the annual filing with MCA.
Working papers must be sufficiently detailed to allow an experienced auditor with no prior connection to the engagement to understand work performed, evidence obtained, and conclusions reached. A manually annotated spreadsheet with no process timestamp or version control does not satisfy this standard; a Cadel working paper with an immutable run-log does.
SA 315 (Identifying and Assessing Risks of Material Misstatement) requires the auditor to understand and test internal controls over financial reporting, including the two-person authorisation principle for journal entries exceeding a materiality threshold. Self-approved vouchers above Rs 10,000 are a direct indicator of segregation-of-duties failure requiring documentation and follow-up.
Ind AS 8 (Accounting Policies, Changes in Accounting Estimates and Errors) requires prior-period items to be disclosed separately or corrected in the current period’s financial statements. A voucher dated in one financial period but posted to the ledger in the next — the JV-0146 scenario (100-day gap) — is a prior-period item that must be detected at period close, not discovered during fieldwork.
For mid-market companies without a dedicated internal audit team, these four checks are typically performed — if at all — by the CFO or controller personally, in a compressed two-day window before audit fieldwork begins. A gap in any one of them triggers a qualified observation or emphasis-of-matter paragraph under ICAI SA 705 that becomes part of the public annual report.
Seven deterministic passes from a GL ledger extract and vouchers register to a statutory-grade audit working paper — in under 30 seconds per document pair regardless of file size.
Accepts the GL ledger extract (ledger_*.xlsx) and vouchers register (vouchers_*.xlsx) as two structured document types, automatically parsing all columns — posting date, voucher number, account head, party name, narration, debit, credit, voucher type, approver, and supporting document reference — without any column-mapping configuration from the user.
Joins every GL entry to its counterpart in the vouchers register using voucher_no as the primary key (exact match, case-insensitive after trim). Unmatched ledger entries (GL entry with no voucher) and unmatched voucher entries (voucher with no GL entry) are each flagged as separate Unmatched Entry exceptions with the identifier value preserved for quick investigation.
For every matched pair, compares the GL debit or credit amount against the voucher register amount. Any difference greater than Rs 1 raises an Amount Mismatch exception that quantifies the exact rupee variance — as demonstrated by JV-0143 (GL Rs 50,000 vs voucher Rs 45,000, variance Rs 5,000 flagged for controller review before period close).
Checks whether the supporting_doc field in the vouchers register is blank or whitespace-only; a missing reference raises a Missing Supporting Bill exception. Where the approver field contains a self-approval indicator or matches the preparer, a concurrent Self-Approval Risk exception is raised for the same voucher — directly targeting the ICAI SA 315 para A81 segregation-of-duties control.
Compares voucher_date (from the vouchers register) against posting_date (from the GL). Any gap that crosses a financial period boundary raises an Out-of-Period Voucher exception with both dates displayed side-by-side for Ind AS 8 / AS 5 period-cut review. Demonstrated by JV-0146: voucher date 2025-11-20, GL posting date 2026-02-28, a 100-day cross-period gap.
Evaluates each GL entry’s posting date against a calendar; entries posted on Saturday or Sunday raise a Weekend Posting risk indicator consistent with ICAI SA 240 fraud risk factor guidance. Entries whose debit or credit amount is an exact multiple of Rs 50,000 with no paise component raise a Round-Sum risk indicator for auditor review.
Checks every GL narration field; any entry with a blank or whitespace-only narration raises a Blank Narration exception, marking the row incomplete pending controller annotation. All seven checks run in a single deterministic pass and produce a scrutiny working paper with each exception categorised, a status badge per voucher (Cleared / Exception / Risk Indicator), and an Excel export formatted for direct attachment to the statutory audit file under ICAI SA 230.
A battery of synthetic test scenarios that exercise every failure mode observed in real-world GL data. Each scenario produces a deterministic outcome an auditor or controller can verify in seconds.
Ten seeded file pairs that together exercise every exception class. Each pair consists of one GL Ledger extract and one Vouchers Register, engineered to produce a deterministic outcome.
Approver: CFO · Supporting doc: INV/SA/2026/0871 · Narration: “Audit retainer Q4”. Baseline test confirming zero false positives on correctly documented entries.
Acme Corp Services · Supporting doc: INV/CR/2026/0214 · Amount difference triggers Amount Mismatch exception with quantified variance. Controller must reconcile before audit.
Two concurrent exceptions: Missing Supporting Bill and Self-Approval Risk. Demonstrates ICAI SA 315 segregation-of-duties failure detection on cash conveyance entries.
Acme Corp LLP · Rs 1,75,000 · Supporting doc: INV/KH/2025/4421. Triggers Out-of-Period Voucher exception for Ind AS 8 / AS 5 prior-period disclosure review.
Running the five demo file pairs against the workflow produced the following outcomes. All results are deterministic — re-running with the same inputs returns identical exception counts and categories every time.
The clean pair (ledger_clean.xlsx + vouchers_clean.xlsx, JV-0142, Professional Fees, Acme Corp LLP, Rs 85,000, approver CFO, supporting doc INV/SA/2026/0871) returned zero exceptions and one Cleared status — confirming that a correctly documented entry passes all seven checks with no false positives. This is the most important result in the demo dataset: the workflow does not over-flag correctly prepared entries, which is the primary reason manual reviewers resist automation.
The amount-mismatch pair (JV-0143, Repairs & Maintenance, Acme Corp Services) produced one Amount Mismatch exception with a quantified Rs 5,000 variance (GL Rs 50,000 vs voucher Rs 45,000). The missing-supporting-doc pair (JV-0144, Conveyance, Rs 12,500) produced two concurrent exceptions: Missing Supporting Bill and Self-Approval Risk — both in a single workflow run, with the two exception categories surfaced separately in the working paper for distinct disposition paths.
The date-mismatch pair (JV-0146, Legal Fees, Acme Corp LLP, Rs 1,75,000) produced one Out-of-Period Voucher exception displaying the 100-day gap between voucher date 2025-11-20 and posting date 2026-02-28 — the exact gap that triggers a prior-period disclosure requirement under Ind AS 8 paragraph 41. Across all five document pairs in a single session, the workflow raised a total of eight distinct findings across four exception categories, with zero false clears on the exception-carrying pairs and zero false positives on the clean pair.
The most operationally significant finding in the demo dataset is the concurrent Missing Supporting Bill + Self-Approval Risk double-exception on JV-0144. A cash conveyance of Rs 12,500 with no supporting document and no independent approver is precisely the entry class that Section 143(3)(b) of the Companies Act, 2013 requires the statutory auditor to report on — and it is also the entry most likely to be overlooked in a manual review of a 400-row GL extract under period-close time pressure.
Replacing the manual ledger voucher scrutiny process with this workflow reduces a three-to-five working day task to under 30 seconds of processing and a short controller review of the flagged exception queue — without reducing the thoroughness or reproducibility of the working paper.
The Excel export produced by each workflow run includes exception category, voucher number, account head, variance amount, run timestamp, and an auditor-annotation column. It drops directly into the statutory audit file as a Schedule to the workpapers, satisfying ICAI SA 230 para 8–11 documentation requirements without reformatting. The in-platform audit trail records every exception status change — from Flagged to Cleared — with timestamp and reviewer email, immutably.
A manual reviewer checking 400 rows for round-sum amounts and weekend postings will miss entries. This workflow checks every row against the calendar and the divisibility rule in a single deterministic pass, consistent with the comprehensive journal-entry testing required by IIA Standard 2320 (Analysis and Evaluation) and the fraud risk documentation standard of ICAI SA 240. Risk indicators that pass through manual review become audit observations; this workflow prevents that.
The same GL extract and vouchers register always produce the same exception list. A second controller, an internal auditor, or the statutory auditor can re-run the workflow on the same files and verify that no exceptions were suppressed or overlooked. This reproducibility satisfies the ICAI SA 230 para 11 requirement that working papers be sufficient to allow an experienced auditor with no prior connection to the engagement to understand and verify the evidence gathered.
The questions finance controllers and audit teams ask most often before deploying automated ledger scrutiny.
The scrutiny working paper is structured to satisfy the documentation requirements of ICAI SA 230 (Audit Documentation) and supports the risk-assessment procedures described in ICAI SA 315 (Identifying and Assessing Risks of Material Misstatement). The Excel export includes exception category, voucher number, account head, variance amount, and an auditor-annotation column — all fields typically required by a statutory auditor’s firm file. The in-platform audit trail records every status change with a timestamp and reviewer email, satisfying SA 230 para 8 evidence-retention requirements.
The workflow compares the voucher date in the vouchers register against the GL posting date; any gap that crosses a financial period boundary is flagged as an Out-of-Period Voucher exception. This directly supports period-cut reviews required under Ind AS 8 (Accounting Policies, Changes in Accounting Estimates and Errors) and the equivalent AS 5 under Indian GAAP, both of which require prior-period items to be disclosed or corrected separately. The working paper displays both dates side-by-side with the number of days between them, giving the controller exactly what is needed for the disclosure assessment.
The workflow ingests a standard XLSX ledger extract with columns for posting date, voucher number, account head, party name, narration, debit, and credit — a format that Tally ERP 9 / Tally Prime, SAP S/4HANA GL line-item reports (transaction FBL3N), and NetSuite’s General Ledger saved search all produce natively. No ETL or API integration is required; export the report from your ERP, upload the file, and the workflow maps columns automatically. The vouchers register follows a matching XLSX format with voucher number, voucher date, type, amount, approver, supporting doc ref, and account head.
Any debit or credit amount that is an exact multiple of Rs 50,000 with no paise component is classified as a round-sum entry — a pattern associated with estimated or fabricated transactions in fraud literature and in the ICAI Guidance Note on Audit of Expenses. The flag is a risk indicator, not a hard exception; the auditor reviews flagged entries in the exception queue and can clear them with an annotation if a legitimate round-figure invoice exists. The threshold of Rs 50,000 is configurable per engagement if your organisation’s materiality threshold differs.
Each workflow run processes one entity’s ledger and vouchers register. For groups with multiple subsidiaries, controllers run a separate instance per entity and combine the exported working papers offline into the consolidated audit file. Multi-currency support — where ledger amounts are in a foreign currency and voucher amounts are in INR — is on the product roadmap; currently, both files must carry amounts in the same currency denomination for the amount-comparison check to be meaningful.
Every status change — from Flagged to Cleared or Escalated — is logged with a timestamp, the reviewing user’s email, and a free-text annotation field. The full audit trail is included as a separate sheet in the Excel export and is immutable within the Cadel platform, satisfying the evidence-retention requirements of ICAI SA 230 paragraph 8 and internal audit charter documentation standards. An auditor querying a cleared exception can see exactly who cleared it, when, and why.
A VLOOKUP matches on one key field and returns one value. This workflow matches on voucher_no, then simultaneously checks amount agreement (within Rs 1 tolerance), account head alignment, supporting doc presence, approver validity, narration completeness, date-gap size, and round-sum / weekend-posting risk indicators — all in a single deterministic pass that produces a structured working paper with exception categories and status badges, not a column of #N/A errors. It also catches unmatched rows in both directions: ledger entries with no voucher, and voucher entries with no GL counterpart.
Yes. For any voucher where the Approved By field contains a self-approval indicator — or where the preparer and approver names are identical — the workflow raises a Self-Approval Risk exception. This directly targets the segregation-of-duties control described in ICAI SA 315 paragraph A81 and is one of the checks that the IIA Standard 2320 journal-entry testing program requires. The exception is flagged independently of whether the amount and supporting document checks pass, so a self-approved voucher with a valid bill still surfaces for secondary review.
