Detection procedure · STX-002
Which entries need a closer look?
After the auditor checks the extract against the declared totals, Verilekh evaluates the selected procedure across the uploaded population. This rule looks for two conditions in the same row.
Download the 45-row sample (CSV) ↓
Rule applied to each entry
- TDS amount is greater than zero
- Deposit date is empty
- Both match → stage a draft exception
1 of 45 entries matched (2.2%).
Source evidence · EX-7002
What triggered the flag?
BuildRight’s contractor entry records a deduction of ₹4,000. The deposit date field is empty. Verilekh attaches the original row so the reviewer can trace both fields back to the extract.
Selected fields from the sample row
- Document
- EX-7002
- Posting date
- 11 May 2026
- Contractor charges
- ₹2,00,000
- TDS deducted
- ₹4,000
- Deposit date
- Blank in extract
Auditor review · EX-7002
Was the tax actually deposited?
The blank field raises a question. The auditor checks the deposit receipt (challan) and reconciliation, then decides whether to confirm or discard the exception.
What if the auditor finds a matching receipt?
The receipt could support discarding the suspected non-deposit. The auditor can assess why the extract lacked the date as a separate question.
Path in the documented example
- Auditor confirms the finding
- Verilekh drafts the observation from the finding and its linked risk
- Auditor documents the root cause and reviews the wording
Reporting · Risk R-STAT-001
What reaches the committee?
A second reviewer signs the observation. The Report Centre, management reporting and Audit Committee Pack then draw on that signed record. The team tracks the action owner and due date through follow-up.
Trace back to EX-7002 ↗
Sample observation · condition
Of 45 entries examined, one recorded a TDS deduction of ₹4,000 with no deposit date in the extract.
Supporting record EX-7002 · Procedure STX-002