Five-bucket ledger aging + exception detection — suspense account aging automation in under 30 seconds per ledger.
| Voucher No | Date | Narration | Debit (Rs) | Credit (Rs) | Posted By |
|---|---|---|---|---|---|
| JV-2026-00412 | 09 Mar 2026 | Bank charges - Acme Bank Mar 2026 | 4,250 | — | acme.user |
| JV-2025-08891 | 14 Aug 2025 | Unidentified inward remittance - awaiting trace | — | 87,500 | acme.ops |
| JV-2026-00501 | 15 Mar 2026 | Adjustment - to be confirmed | 5,00,000 | — | acme.admin |
| JV-2026-00478 | 25 Jan 2026 | (blank) | 12,340 | — | system.batch |
Manual suspense account aging breaks down the moment a ledger exceeds 40 open items. Finance teams at Indian mid-market companies processing 200–600 journal vouchers per month carry a suspense account that accumulates unclassified entries throughout every period.
Controllers building ageing buckets with DATEDIF formulas in Excel, scanning narrations to guess reclassification accounts, and formatting working papers by hand for a ledger of 80–120 open items. A fresh spreadsheet is built from scratch every period — with no systematic carry-forward or escalation logic.
Round-amount entries (amounts ending in 00,000) and weekend postings are listed indicators of manipulation under ICAI SA 240, yet a pivot table does not check posting-day-of-week and does not flag round totals. Entries that should route to supervisory review reach the close pack unchecked.
Under Companies Act 2013 Schedule III, any material balance in a suspense or “other liabilities/other assets” line requires separate disclosure in the notes. A credit of Rs 87,500 sitting unidentified for 220+ days will appear without explanation unless it is surfaced before the balance sheet date — and manual review routinely misses it.
A standard spreadsheet does not validate that a suspense entry carries either a debit or a credit — not both. An entry with non-zero values in both columns violates the fundamental single-sided posting rule for suspense accounts. Without a programmatic check, such entries are silently bucketed and the balance overstated.
The scale-break point for manual suspense account aging. Beyond 40 open items across multiple cost centres and originating users, the ad-hoc spreadsheet cannot reliably enforce narration completeness, detect weekend postings, or build the exception queue the auditor expects under ICAI SA 315 (Identifying and Assessing the Risks of Material Misstatement) — without rebuilding the entire triage from scratch each period.
Indian companies preparing financial statements under Ind AS or the Companies Act are bound by four overlapping frameworks that treat uncleared suspense balances as disclosure and control failures — not just housekeeping items.
Balances that cannot be classified into the primary head-of-account categories in Schedule III must be disclosed separately in the notes to financial statements. Any material amount parked in suspense at the balance sheet date without a written explanation creates an emphasis-of-matter risk during the statutory audit and, if material, a basis-for-qualified-opinion risk.
SA 315 (Identifying and Assessing the Risks of Material Misstatement through Understanding the Entity and Its Environment) requires auditors to evaluate the entity’s process for clearing control-account balances. A suspense account with uncleared items beyond 90 days is routinely identified as a significant risk area that requires increased substantive procedures, extending the audit cycle and raising fieldwork cost.
SA 240 (The Auditor’s Responsibilities Relating to Fraud in an Audit of Financial Statements) lists unusual journal entry characteristics — round amounts, entries posted outside business hours or on weekends, and entries with vague narrations — as specific fraud risk indicators that should be selected for substantive testing. The workflow surfaces both flags before fieldwork, giving the internal audit team documented evidence of supervisory review.
SA 230 (Audit Documentation) requires the auditor to prepare documentation that is sufficient to enable an experienced auditor, having no prior connection with the audit, to understand the work performed and the conclusions reached. An Excel working paper that captures voucher number, posting date, ageing bucket, validation flags, and the reviewer’s accept/override decision with timestamp directly satisfies this standard and eliminates the supplementary documentation step that currently adds one to two days to the close-pack assembly.
Seven deterministic passes from suspense ledger upload to audit-ready working paper — in under 30 seconds per ledger, with every validation rule applied consistently and every exception documented without manual input.
Reads the uploaded XLSX file (sheet “Suspense Ledger - Open Items”) and extracts every open-item row: voucher_no, posting_date, narration, debit_amount, credit_amount, posted_by, and cost_center. Rows missing a voucher_no or with a non-parseable posting_date are flagged immediately and excluded from downstream bucket counts until corrected.
Before any ageing calculation, applies the debit_credit_exclusive rule: an entry must carry either a non-zero debit or a non-zero credit — never both. Any row violating this constraint receives a FAIL severity validation, is rejected from all five ageing buckets, and is surfaced in the exception queue with an instruction to correct the source voucher before re-upload.
For each valid row, computes calendar days from posting_date to the analysis run date and assigns the entry to one of five buckets: 0–30 days, 31–60 days, 61–90 days, 91–180 days, or 180+ days. Entries with a null posting_date are excluded from bucket counts and flagged separately. Bucket assignments are deterministic and reproducible for any given run date.
Entries older than 90 days receive a WARNING severity flag (ageing_within_90_days). Entries older than 180 days receive a FAIL severity flag (ageing_within_180_days), are added to the exception queue, and are tagged for write-off review and Schedule III disclosure narrative. The 90-day and 180-day thresholds map directly to the materiality escalation logic most internal audit charters apply for suspense balances.
Evaluates two WARNING-severity rules concurrently: round_amount_check (debit or credit amount ending in 00,000) and weekend_posting_check (posting date falling on Saturday or Sunday). Both flags are raised simultaneously where applicable — as with JV-2026-00501, a Rs 5,00,000 debit posted on Sunday 15 March 2026 — consistent with the fraud-risk indicators listed in ICAI SA 240 · Para A26.
Any row with a null or blank narration field triggers a FAIL severity validation (narration_required). The entry is blocked from the auto-reclass step and added to the exception queue with a manual-review tag. JV-2026-00478 (Rs 12,340, 95 days old, posted by system.batch) illustrates this path: it receives both a narration FAIL and a 91–180 day WARNING simultaneously, and no reclass suggestion is generated.
For entries with valid narrations, matches narration keywords against a configured keyword-to-GL-account table (e.g., “bank charges” → GL 5610; “TDS” → GL 1450) and appends a suggested reclass account to the reviewer inbox row. Then assembles the full ageing working paper — per-entry ageing bucket, severity flags, and reviewer decisions with timestamps — as an Excel export formatted for the period-close pack and audit file under ICAI SA 230.
A battery of synthetic test scenarios that exercise every failure mode observed in real-world suspense ledger data. Each scenario produces a deterministic, auditor-verifiable outcome.
debit_credit_exclusive; row rejected from all ageing buckets and surfaced in exception queue; instruction to correct the source voucher before re-upload.Four seeded suspense ledger files — each engineered to exercise a different failure mode. Three process cleanly. One is deliberately constructed to trigger the maximum severity exception path.
Demonstrates the happy-path flow: narration keyword match triggers an automatic reclass suggestion to GL 5610 and the entry lands in the 0–30 day green bucket with no exception flags.
FAIL severity ageing breach, 180+ day red badge, write-off review queue routing, and Schedule III disclosure narrative tag — the most operationally significant catch in the demo set.
Two concurrent WARNING flags raised simultaneously per SA 240 · Para A26 fraud-risk indicators. Entry routed to supervisory exception queue; no reclass accepted until reviewed.
FAIL for missing narration plus WARNING for 91–180 day ageing raised simultaneously. Auto-reclass blocked; entry added to exception queue with manual-review tag.
A suspense ledger with 80–120 open items typically requires one to two days of manual triage per close cycle — building ageing formulas, scanning narrations, drafting the exception list, and formatting the working paper. Cadel runs all seven passes in under 30 seconds and produces an audit-ready document that drops directly into the close pack with no additional formatting.
The 180-day FAIL threshold automatically queues unidentified credits (like the Rs 87,500 inward remittance in the demo data) for write-off review before the balance sheet date, eliminating the most common source of Schedule III non-disclosure that auditors identify during fieldwork and that results in late adjustments and emphasis-of-matter paragraphs.
Round-amount and weekend-posting detection per SA 240 · Para A26 runs on every row, every cycle — not just when the internal auditor selects a sample. Finance teams that ran this across a full quarter’s ledger reported eliminating suspense-account-related audit queries by removing the two most common missed exceptions: stale balances not escalated in time, and round-amount weekend postings not documented before fieldwork.
The Excel export carries voucher number, posting date, ageing bucket, all severity flags, the reviewer’s accept/override decision with timestamp, and the suggested reclass account — every field an experienced auditor needs under ICAI SA 230 to understand the work performed without supplementary documentation or email-thread reconstruction.
The questions controllers, CFOs, and statutory auditors ask most often before deploying suspense account aging automation.
Under Schedule III of the Companies Act, 2013, balances that cannot be immediately classified must be disclosed separately, and auditors routinely cite uncleared suspense balances as a key risk area during the Statutory Audit under SA 315 (Identifying and Assessing the Risks of Material Misstatement). The ICAI Guidance Note on Audit of Miscellaneous Expenditure and COSO Internal Control — Integrated Framework require that suspense accounts be reviewed and cleared within a defined period — typically 90 days — with write-off or reclassification approvals documented in working papers.
Each row in the uploaded suspense ledger carries a cost_center column (e.g., CC-FIN-01), and the workflow groups ageing buckets and exception flags at the cost-centre level in addition to the overall entity view. For a multi-entity close pack, controllers can upload separate ledger extracts per legal entity, and the Excel working-paper export includes a cost-centre summary tab that maps directly to the intercompany and segment disclosures required under Ind AS 108.
The engine matches narration text against a keyword dictionary — for example, entries containing “bank charges” are mapped to GL account 5610, and entries containing “TDS” are mapped to 1450 — and displays the suggested account alongside a confidence indicator in the reviewer inbox. The controller must explicitly confirm or override the suggestion before any journal entry is posted; the workflow does not write to the GL directly. Entries with blank or ambiguous narrations receive no suggestion and are routed to the exception queue, ensuring no unreviewed reclassification reaches the books.
The workflow accepts a standard XLSX tabular export of the suspense ledger with seven columns (voucher number, posting date, narration, debit amount, credit amount, posted-by user, cost centre), which every major accounting system — Tally Prime, SAP S/4HANA via transaction FBL3N, and NetSuite via Saved Search — can produce without customisation. The Excel working-paper export produced by the workflow can be imported back as a journal entry template in each of these systems after reviewer sign-off.
The exported Excel working paper includes, for each entry: the original voucher number, posting date, narration, debit/credit amount, posted-by user, cost centre, computed ageing bucket, all validation flags with their severity levels (WARNING or FAIL), and the reviewer’s accept/override decision with a timestamp. This trail satisfies the documentation requirements of ICAI SA 230 (Audit Documentation) and supports the internal auditor’s test of controls over journal entry authorisation under SA 315.
No. The round-amount check (amounts ending in 00,000) and weekend-posting check are WARNING-level indicators designed to direct human attention to entries that warrant additional scrutiny; they do not constitute a finding of fraud or misstatement. Any entry flagged by these rules should be escalated through the company’s existing internal-audit or forensic-accounting process in accordance with ICAI SA 240 (The Auditor’s Responsibilities Relating to Fraud) and, where applicable, reported under Section 143(12) of the Companies Act, 2013.
A manual spreadsheet approach requires building DATEDIF formulas each period, visually scanning narrations to guess GL accounts, and formatting the working paper by hand — typically one to two days for a ledger of 80–120 open items. Cadel’s suspense account aging automation runs all six validation rules deterministically in under 30 seconds, builds the exception queue without manual input, and produces an audit-ready working paper that drops directly into the close pack with no additional formatting. The keyword-driven reclass engine removes the most time-consuming manual step — matching narration text to GL accounts — for every entry with a well-formed narration.
The ageing buckets, exception thresholds, and auto-reclass logic are accounting-framework-agnostic — they operate on the ledger data regardless of whether the entity reports under Ind AS, IFRS, or US GAAP. The Schedule III disclosure tagging and SA 230/SA 315 audit-documentation references are most directly applicable to Indian statutory audit contexts, but the working-paper output satisfies the documentation requirements of IAS 37 (provisions and contingent liabilities review) and PCAOB AS 1215 (audit documentation) for IFRS and US GAAP audits respectively.