Technology

Section 138 Notice Automation for Cheque Bounce at Scale

|Posted by Hitul Mistry / 13 Nov 26

Last reviewed: November 2026

Section 138 notice automation is the use of software to issue statutory demand notices for dishonoured cheques under the Negotiable Instruments Act, 1881, and to track every deadline that follows. It turns each bank return memo into a dated, provable notice and a case file that is ready for court.

This guide is for heads of collections, heads of legal and CROs at NBFCs, banks and fintech lenders that still collect post-dated or security cheques. It covers the legal clock, where manual processes break, and how to build a notice workflow that scales without losing the remedy.

Key Takeaways

  • Section 138 requires a written demand within 30 days of the bank's dishonour information, and gives the drawer 15 days to pay after receiving it.
  • A late notice cannot be fixed later, so deadline tracking matters more than drafting speed.
  • The Allahabad High Court (2024) accepted email and WhatsApp notices that meet the IT Act, but most lenders still send registered post too.
  • The Supreme Court's Sanjabij Tari judgment (September 2025) pushed electronic summons and early online payment in cheque cases.

Why Is Section 138 Notice Handling a Leadership Problem?

Section 138 notice handling is a leadership problem because a missed notice deadline permanently removes a criminal remedy that pushes many defaulters to pay. The offence carries imprisonment of up to two years, a fine of up to twice the cheque amount, or both.

That leverage only exists if every statutory step is met on time. One late notice is a small loss, but a process that misses 5% of notices across thousands of bounces quietly writes off recovery options every month.

The legal cost also scales with volume. Lenders with large books of post-dated cheques (PDCs) or security cheques can receive thousands of cheque return memos each month, and each one starts its own clock.

How Do Section 138 Notices Go Wrong?

Section 138 notices usually go wrong in five places: late receipt of the return memo, wrong drawer details, defective notice content, unprovable delivery, and lost complaint deadlines. Each one can sink a case that was otherwise strong.

Failure PointWhat HappensWhere It Shows Up
Return memo reaches legal lateDays of the 30-day window are lost in branch or courier transitNotices dated close to the deadline
Wrong name or addressNotice goes to an old address or the wrong entityReturned post, defence of non-service
Defective contentDemand differs from the cheque amount or omits key detailsDefence arguments at trial
No proof of deliveryLender cannot show when the 15 days startedWeak evidence in the complaint
Complaint deadline missedFiling after one month needs a condonation applicationExtra hearings and cost

The last two are evidence problems, not drafting problems. That is why automation has to cover dispatch, tracking and record-keeping, not just templates.

How Do Lenders Automate Section 138 Notices?

Lenders automate Section 138 notices with five layers that run from the bank feed to the court file. Each layer removes a manual handoff where deadlines usually slip.

  1. Dishonour capture: ingest return memos and bank return codes on the day they arrive.
  2. Eligibility checks: confirm the cheque, the debt and the return reason qualify.
  3. Notice generation: build the notice from approved templates and the loan record.
  4. Multi-channel dispatch: send through registered post plus email and WhatsApp, with proof.
  5. Clock and case tracking: run the 30-day, 15-day and complaint deadlines in one view.

The 30-day window starts when the lender receives information of dishonour from its bank, so the system should start the clock on that date. Pull return data electronically from the collecting bank wherever possible, instead of waiting for paper memos from branches.

Link each return to the loan account in the loan management system for NBFCs, so the notice uses the current outstanding and contact details.

Layer 2: Does This Cheque Qualify for Section 138?

Not every return qualifies. The cheque must have been presented within its validity period, and the return reason must fall within the section, such as insufficient funds or exceeding the arrangement.

The debt must also be legally enforceable. Security cheques are a contested area, so route them to counsel with the loan agreement and repayment history attached.

Layer 3: Is the Notice Content Defensible?

Generate the notice from templates your counsel has approved, with the cheque number, date, amount, bank, return memo date and reason filled from source data. Do not let users edit the demand amount freely.

Store the signed agreement alongside the case, which is easier if you already run a digital loan agreement and e-stamping process.

Layer 4: Can You Prove Delivery?

Send the notice by registered post with tracking, and add email and WhatsApp as further channels. In Rajendra v. State of U.P. (2024), the Allahabad High Court held that a notice by email or WhatsApp is valid if it satisfies Section 13 of the Information Technology Act, 2000.

That ruling is persuasive in other states, not binding. Keep registered post as the base channel, and store tracking reports, delivery receipts and message logs against each case.

Layer 5: Which Deadline Is Next?

Once delivery is recorded, the system should calculate the end of the 15-day payment period and the complaint window under Section 142. It should also suggest the court using Section 142(2), which ties jurisdiction to the payee's bank branch where the cheque was presented.

Payments received inside the 15 days should close the case automatically. Late payments should go to legal for a decision on compounding, not be ignored.

How many cheque bounce notices went out on day 29 last month, or not at all?

Talk to Our Lending Technology Specialists

Visit Digiqt to see how our custom software team builds notice workflows that run every legal deadline automatically.

How Does Section 138 Notice Automation Work on a Real Book?

On a real book, section 138 notice automation changes outcomes by protecting the deadline and starting the payment clock sooner. In this illustrative scenario, a consumer and MSME lender receives 2,400 cheque return memos a month, with an average dishonoured amount of ₹62,000.

Before automation, memos travel from branches by courier and notices are drafted by hand. About 8% of eligible cheques, or 192 a month, miss the 30-day window, which puts ₹1,19,04,000 (about ₹1.19 crore) of claims outside Section 138 each month.

After automation, return data is pulled daily and notices go out within two working days.

StepBeforeAfter
Memo to legal6–12 daysSame day
Notice dispatchDay 20–30Day 2
Missed 30-day window192 chequesUnder 10 cheques
Proof of deliveryPostal receipt onlyPost tracking plus email and WhatsApp logs

Assume 22% of drawers now pay within the 15-day period. That is 528 cheques, or ₹3,27,36,000 (about ₹3.27 crore), settled without a complaint being filed.

The lesson for leadership: the notice itself was never the hard part. The value came from starting the clock on day one and proving every step.

Which Approach Fits Your Lending Model?

The right approach depends on cheque volume, how centralised your collection account is, and how many cases end in court. High-volume lenders need full automation, while low-volume secured lenders can automate tracking and keep drafting with counsel.

SituationRecommended Approach
Under 200 bounces a month, secured loansAutomated deadline tracking, counsel-drafted notices, registered post
Thousands of PDC bounces a monthFull pipeline from bank feed to dispatch, with legal review of exceptions
Mixed cheque and NACH bookOne workflow covering Section 138 and Section 25 of the Payment and Settlement Systems Act
External law firms on panelShared case portal so firms see deadlines and upload filings

Should You Still Collect Cheques at All?

For most retail and MSME books, electronic mandates are now the primary repayment route, as our eNACH vs UPI Autopay guide explains. Cheques survive as security and in some segments.

NACH dishonour falls under Section 25 of the Payment and Settlement Systems Act, 2007, which follows a similar notice structure. A single legal workflow should handle both instruments.

How Should Notices Fit Into the Collections Workflow?

Notices work best as one step in a graded collections ladder, not as a separate legal silo. Reminders and calls come first, the notice follows a confirmed dishonour, and court filing comes only after the 15-day period ends.

Feed the notice status back to collections. An agent calling a customer should see that a statutory notice is live, so the conversation supports the legal process instead of contradicting it.

Digiqt's early-stage collections AI agent shows how outreach before and after a bounce can be sequenced. For later stages, the recovery rate prediction AI agent shows how cases can be ranked by likely recovery before you pay court fees.

Field teams also need the case status. A field collection app that shows notice dates helps agents avoid promising terms that legal has not approved.

Most lenders build this layer on top of their existing systems. Digiqt's custom software development team covers UI/UX design, web and app development and quality assurance, and starts with problem statement analysis before a dedicated team builds the workflow.

Which Metrics Show Section 138 Notices Are Working?

Five metrics show whether notices are working: memo-to-notice time, deadline breach rate, delivery proof rate, payment within 15 days and complaint filing timeliness. Together they show both legal safety and recovery impact.

MetricFormulaWhat a Weak Number Signals
Memo-to-notice timeAverage days from dishonour information to dispatchBranch or courier delays eating the window
Deadline breach rateNotices sent after day 30 ÷ eligible dishonoursLost remedies and weak process control
Delivery proof rateCases with delivery evidence ÷ notices sentCases that may fail at trial
Payment within 15 daysCheques paid in the window ÷ notices deliveredWeak notice content or wrong contact data
Timely complaint filingComplaints filed within one month ÷ complaints filedCondonation costs and adjournments

Review these monthly with collections, legal and panel law firms, split by branch and by firm.

Which Mistakes Weaken Section 138 Cases?

Four mistakes weaken most Section 138 cases, and they are process failures rather than legal ones.

  • Starting the clock late. If the return memo sits in a branch, part of the 30-day window is already gone.
  • Relying on one delivery channel. Registered post alone leaves gaps when addresses are stale, so add electronic channels and keep the logs.
  • Filing everything. Court fees and lawyer time should go to cases with a realistic chance of recovery.
  • Disconnecting legal from collections. Settlements agreed on calls should update the case, or the lender may prosecute a borrower who has already paid.

What Is Changing Next?

Courts are moving cheque cases online. In September 2025, the Supreme Court's Sanjabij Tari judgment directed electronic and dasti service of summons, a synopsis with each complaint, and online payment links so accused persons can pay at the initial stage.

That raises the bar for lenders' data, because complaints will need clean electronic records, correct contact details and payment reconciliation from day one.

For a wider view of recovery operations, see our guide to collection efficiency, or build these controls into a digital lending platform from the start.

Want every dishonoured cheque tracked from return memo to court filing without spreadsheets?

Talk to Our Lending Technology Specialists

Visit Digiqt to see how our custom software team builds legal and collections workflows for lenders.

Sources

Read our latest blogs and research

Featured Resources

Technology

Collection Efficiency for Lenders: Formulas and Levers

Collection efficiency explained for lenders: formulas with worked arithmetic, bucket metrics, why public benchmarks mislead, and the levers that improve it.

Read more
Technology

Field Collection App for Lenders: Routes, Receipts, Conduct

Field collection app guide for NBFCs and banks: route planning, digital receipts, cash control and the RBI recovery agent rules that apply from January 2027.

Read more
Technology

eNACH vs UPI AutoPay: Choosing a Loan EMI Mandate Rail

eNACH vs UPI AutoPay for loan EMIs: limits, RBI e-mandate rules, NPCI execution windows, bounce drivers and a hybrid routing model for lenders.

Read more

About Us

We are a technology services company focused on enabling businesses to scale through AI-driven transformation. At the intersection of innovation, automation, and design, we help our clients rethink how technology can create real business value.

From AI-powered product development to intelligent automation and custom GenAI solutions, we bring deep technical expertise and a problem-solving mindset to every project. Whether you're a startup or an enterprise, we act as your technology partner, building scalable, future-ready solutions tailored to your industry.

Driven by curiosity and built on trust, we believe in turning complexity into clarity and ideas into impact.

Our key clients

Companies we are associated with

Life99
Edelweiss
Aura
Kotak Securities
Coverfox
Phyllo
Quantify Capital
ArtistOnGo
Unimon Energy

Our Offices

Ahmedabad

B-714, K P Epitome, near Dav International School, Makarba, Ahmedabad, Gujarat 380051

+91 99747 29554

Mumbai

C-20, G Block, WeWork, Enam Sambhav, Bandra-Kurla Complex, Mumbai, Maharashtra 400051

+91 99747 29554

Stockholm

Bäverbäcksgränd 10 12462 Bandhagen, Stockholm, Sweden.

+46 72789 9039

Malaysia

Level 23-1, Premier Suite One Mont Kiara, No 1, Jalan Kiara, Mont Kiara, 50480 Kuala Lumpur

Lewes

16192 Coastal Highway, Lewes, Delaware 19958, USA

software developers ahmedabad
ISO 9001:2015 Certified

Call us

Career: +91 90165 81674

Sales: +91 99747 29554

Email us

Career: hr@digiqt.com

Sales: hitul@digiqt.com

© Digiqt 2026, All Rights Reserved