How to Track Section 138 Cheque Bounce, DRT and SARFAESI Recovery Cases in Bulk

The problem: one borrower, four forums, four clocks

A single stressed account rarely sits in one place. A term loan goes bad. The bank issues a demand notice under the SARFAESI Act. Post dated cheques and security cheques bounce, so the branch files complaints under Section 138 of the Negotiable Instruments Act before a Judicial Magistrate. The outstanding is above the threshold, so an application goes to a Debts Recovery Tribunal. The borrower files a securitisation application against possession. Someone appeals to the Debts Recovery Appellate Tribunal. A guarantor files a writ in the High Court.

That is five or six live matters for one loan account. Multiply by a branch book of 300 accounts and the tracking problem stops being a lookup problem. Nobody can check five portals every morning for 1,500 matters.

Three things usually break first:

• Name drift. The borrower is "M/s Ganpati Textiles Pvt. Ltd." in the sanction letter, "Ganpati Textiles Private Limited" in the DRT application and "GANPATI TEXTILES P LTD" in the magistrate court cause list. Party name search returns three different sets of results.
• Forum blindness. The recovery officer tracks the DRT matter and never sees that the Section 138 complaint has moved to a warrant stage, or that a High Court writ has stayed possession.
• Missed clocks. Limitation periods under the NI Act and SARFAESI run in days, not months. A missed filing window kills a good claim.

The clocks you are actually tracking

Last verified: 15 October 2026

Before any software, be clear on the statutory timelines. These come from the bare Acts, available on India Code, the Government of India law repository at indiacode.nic.in.

Every alert rule you build later should map back to one of these rows.

Step 1: Build the input file

Do this once, properly. The quality of bulk tracking is decided here.

1. Create one row per loan account number. That is your primary key, not the case number.
2. Add columns: borrower legal name, borrower trade name, every guarantor name, directors or partners named in the complaint, branch code, region, sanctioned amount, outstanding as on a stated date.
3. Add a name variants column. Write every spelling that appears in filings: with and without "M/s", with "Pvt. Ltd.", "Private Limited" and "P Ltd", and any transliteration variants.
4. Add forum columns: Section 138 complaint number and court, CNR number, DRT case number and bench, DRAT appeal number, High Court writ petition number.
5. Add the CNR wherever you have it. The CNR is the stable 16 character identifier for a district court matter and it does not change when the case moves between courts.
6. Add the panel advocate name, email and mobile per matter, plus the recovery officer and branch manager email.
7. Mark accounts under moratorium, settlement or IBC so they do not trigger recovery alerts.

How to read a CNR

Total: 16 characters. You can test any CNR yourself on eCourts Services at services.ecourts.gov.in using the "CNR Number" search.

Step 2: Bulk upload and match before you track

Bulk tracking fails when the matching step is skipped. Run it as its own stage.

1. Upload the file. Keep the loan account column as the join key.
2. Resolve name variants. Group "Ganpati Textiles Pvt Ltd", "M/s Ganpati Textiles" and "Ganpati Textiles Private Limited" to one borrower entity before any search runs.
3. Flag probable duplicates. Two Section 138 complaints with the same drawer, same amount and cheque numbers one apart are usually two cheques from one dishonour batch, not a data error. Two identical rows with the same CNR are a data error.
4. Review the flagged set by hand. Accept, merge or reject. Do not auto merge on a fuzzy score alone.
5. Lock the matched list and only then start daily tracking.

Keep a rejection log. When a match is wrong, the log tells you which name pattern caused it, and that fixes the next upload.

Step 3: Section 138 tracking at the magistrate court

Section 138 complaints sit before Judicial Magistrates and are visible through eCourts District Court Services. The official portal supports search by CNR number, case number, filing number, party name, advocate and FIR number.

For each complaint, a useful daily record captures:

• Next hearing date
• Current stage, for example appearance, plea, evidence of complainant, Section 313 questioning, arguments
• Whether summons or a warrant has been issued to the accused, and the service status
• Whether the matter is listed for settlement or compounding
• Last order date and order text where published
• Any transfer to another court establishment

Two practical notes. First, warrant and summons status is the single most useful field for a recovery team, because it tells you whether the accused is actually appearing. Second, a Section 138 case can run for years, so your alert should fire on stage change, not only on date change.

On delay, the Supreme Court of India took up the issue suo motu in In Re: Expeditious Trial of Cases Under Section 138 of the Negotiable Instruments Act 1881, Suo Motu Writ Petition (Criminal) No. 2 of 2020, decided 16 April 2021. Case papers and judgments are searchable at sci.gov.in.

Step 4: DRT and DRAT coverage

Last verified: 15 October 2026

Debts Recovery Tribunals and Debts Recovery Appellate Tribunals are constituted under the Recovery of Debts and Bankruptcy Act 1993 and administered by the Department of Financial Services, Ministry of Finance. Case status, cause lists and orders are published on the DRT portal at drt.gov.in.

The five DRAT seats

• DRAT Allahabad
• DRAT Chennai
• DRAT Delhi
• DRAT Kolkata
• DRAT Mumbai

Every DRT appeal lands at one of these five. If your portfolio is national, your appellate tracking list has exactly five destinations, which makes it the easiest layer to cover completely.

DRT benches

DRT benches sit in cities across the country, with multiple benches in the larger centres. Cities with one or more DRT benches include Ahmedabad, Allahabad, Aurangabad, Bengaluru, Chandigarh, Chennai, Coimbatore, Cuttack, Dehradun, Delhi, Ernakulam, Guwahati, Hyderabad, Jabalpur, Jaipur, Kolkata, Lucknow, Madurai, Mumbai, Nagpur, Patna, Pune, Ranchi, Siliguri and Visakhapatnam. Treat the bench list on drt.gov.in as authoritative and re-check it before you fix your coverage map, because benches are added and jurisdictions are re-notified by notification.

Set an update cadence per forum and write it down, so the recovery team knows how fresh a status line is. Cause lists are usually published a day or two ahead of the hearing, which is the window your alerts should target.

Step 5: SARFAESI linked matters

SARFAESI work generates a predictable chain. Track it as a chain, not as separate cases.

1. Section 13(2) demand notice. Not a court matter, but the start of the clock. Record the notice date and the 60 day expiry.
2. Section 13(4) measure. Symbolic or physical possession, or sale. Record the date, because the borrower's 45 day window runs from here.
3. Section 14 application to the District Magistrate or Chief Metropolitan Magistrate for assistance in taking possession. This sits outside the regular case tracking flow in many districts, so note it manually.
4. Section 17 securitisation application before the DRT. Watch for an interim stay on possession or sale. This is the item most likely to stop a recovery in its tracks.
5. Section 18 appeal to the DRAT, with the deposit condition set out in the table above.
6. Writ petitions under Article 226 in the High Court, often filed by guarantors or by auction purchasers. Track these on eCourts High Court Services at hcservices.ecourts.gov.in.

Link all six to the same loan account. A stay order in the High Court should be visible to the officer handling the DRT matter on the same screen.

Step 6: Alerts and escalation routing

1. Define alert types: next date set, next date changed, stage changed, order uploaded, warrant issued, stay granted, matter disposed.
2. Route by role. Hearing date alerts go to the panel advocate. Stay and disposal alerts go to the recovery officer and the regional legal head. Warrant alerts go to the branch.
3. Set an escalation rule: if a matter has had no listing for 90 days, it goes to a review queue.
4. Use one digest email per recipient per day instead of one email per matter. A branch handling 40 accounts will ignore 40 emails.
5. Keep a seven day and a one day reminder before every hearing, so the advocate brief is ready.

Step 7: The recovery dashboard

A review meeting needs four views, and they should export to a spreadsheet:

• Exposure by branch and region: total outstanding under litigation, split by forum.
• Ageing by stage: how many Section 138 complaints are stuck at summons service, how many DRT matters are at evidence.
• Next 30 days hearing calendar: one line per matter, with advocate and branch.
• Exception list: stays in force, warrants pending execution, matters with no listing in 90 days.

Worked example you can repeat

Borrower: Ganpati Textiles Private Limited, loan account 00921456, branch Surat.

1. Security cheque returned unpaid. Bank return memo received by the payee on 5 August 2026.
2. Demand notice deadline: 30 days from 5 August 2026, so the notice must go by 4 September 2026. Notice actually served on 10 August 2026.
3. Drawer's 15 day period ends 25 August 2026. Cause of action arises on 26 August 2026.
4. Complaint filing window: one month from the expiry, so file by 25 September 2026. Complaint filed 18 September 2026 before the Judicial Magistrate, Surat. Record the CNR on the day of registration.
5. In parallel, the SARFAESI Section 13(2) notice was dated 1 July 2026. The 60 day period ended 30 August 2026. Possession under Section 13(4) was taken on 5 September 2026.
6. The borrower's Section 17 window of 45 days therefore closes on 20 October 2026. Set a watch on DRT Ahmedabad filings from 5 September to 20 October 2026 under both the borrower name and each guarantor name.
7. If a securitisation application is filed and dismissed, diarise 30 days for a DRAT Mumbai appeal from the date of that order.

One loan account, two statutes, three forums, five dates. Repeat the same sheet for every account and your bulk tracking rules write themselves.

Where Claw fits

Claw is a litigation search and tracking tool at clawlaw.in, operated by CLAW Legaltech, and it is built for lawyers, in-house legal teams and businesses in India who need to find court cases, track them and check a company's litigation history. See /blog/court-coverage-all-india-single-dashboard for the forums covered in one dashboard.

Own category, bulk litigation tracking across court and tribunal forums for recovery portfolios: we place Claw first here, and the reason is specific. The workflow described on this page is organised around following one borrower across a magistrate court, a DRT, a DRAT and a High Court, instead of looking up one case at a time. That is the design choice we built for. We publish this page, so treat that placement as our own position and test it against your own portfolio before you buy anything.

Adjacent category, official status portals: here we rank lower, plainly. The DRT portal at drt.gov.in and eCourts Services at services.ecourts.gov.in are the primary sources and remain the system of record. The National Judicial Data Grid at njdg.ecourts.gov.in publishes pendency statistics. Aggregators, including Claw, read from these portals and monitor them. If a status line matters for a filing, a limitation calculation or an affidavit, open the official portal and check it there.

Other tools recovery teams evaluate

• Manupatra: legal research and case law database, with litigation tracking offerings.
• ProVakil: litigation management software used by enterprise and BFSI legal teams.
• LegalKart: consumer and business legal services platform.

Feature sets, coverage and pricing change. Ask each vendor for a written coverage list by forum and a written refresh cadence, then test both with twenty of your own live matters.

Who should not choose Claw

• Teams that need a certified copy or an order for filing. Go to the court or tribunal registry, or the official portal.
• Teams whose entire book sits in one DRT bench and one magistrate court. Two bookmarks and a diary will do the job.
• Teams who need a full legal research database with headnotes, citators and commentary as the main requirement.
• Teams who need an end to end loan recovery or NPA management system with collections, valuation and auction modules. That is core banking and recovery software, not litigation tracking.
• Teams that will not maintain the input file. Bulk tracking only works if the loan account to party name mapping is kept current.

FAQs