A thousand loan accounts arrive as a spreadsheet. They should leave as served notices, tracked deadlines, and a raised invoice—not as a merge field someone got wrong at 11pm.
Opt-in module · Professional AI & Enterprise
Illustrative run — sample data
Bulk is the primary path, and every step leaves an audit event. The lender stays your client; the borrower never becomes one.
Track, template, serial prefix, fee schedule, signatory, and retention—set once per lender engagement.
Upload the lender's file, map the headers once, commit the accounts. The profile is saved for next month.
Template merge with continuous serials and the signatory block. Preview before anything is produced.
Edit while pending, then approve in bulk. PDFs materialise and the print pack is ready to run.
Postal manifest and print pack come out in the same serial order, so the counter never resequences.
PODs file to the account. Returns open a task. Redispatch is recorded, deemed service applied nightly.
Windows land in your Calendar with reminders, and the mandate dashboard shows what has breached.
GST invoice from the batch, MIS returned with status columns, and one action to escalate to court.
The document and the despatch are produced together—so what the post office takes matches what the file says you sent.
Serials run continuously across the batch and the signatory block is applied from the mandate—so a run of a thousand reads like a run of one.
Post remains the evidentiary primary; email and WhatsApp are supplementary. Every return becomes somebody's task rather than somebody's problem.
Platform defaults for the tracks recovery counsel run most. Deemed-service and reminder days are per-track and can be overridden on the mandate.
Background reading: filing a cheque bounce case under s.138, the s.138 NI Act amendment, and filing a securitisation application before the DRT.
Service you cannot evidence, and a window nobody was watching. Collections is built around both.
Proofs file against the borrower account, not the monthly batch—so the trail survives refresh cycles and staff changes.
Every track carries staged deadlines. They land in the same Calendar you already run your hearings from.
The commercial follow-through sits on the same mandate as the legal file—so what you invoice matches what you actually sent.
Documents file by loan account, so a refreshed monthly batch never orphans last quarter's notice trail.
Raise the invoice from the run you just dispatched, hand the lender back their own file, and escalate what is ready.
Your matters, documents, calendar, and clients stay exactly where they are.
It is the system a recovery practice uses to run lender mandates at volume—importing delinquent loan accounts, generating and approving statutory notices, dispatching and proving service, tracking the statutory windows that follow, and invoicing the lender. LawSathi Collections does all of that against the same matters, documents, and calendar your practice already runs.
Panel counsel and recovery practices acting for banks and NBFCs. The lender is your client and stays on your Clients record; the borrower is the adverse party and lives inside Collections. It is built for the advocate side of the mandate, not for the lender's in-house collections floor.
Five tracks ship with staged defaults: NI Act s.138, SARFAESI s.13(2) through s.13(4), arbitration invocation under s.21 and appointment under s.11, recall and demand notices, and vehicle repossession. Each track carries its own stages, deemed-service days, and reminder days, which you can override per mandate.
Yes—bulk is the primary path. Upload the lender's file, map the headers once, and commit the accounts. Serials, the signatory block, and the mandate's template are applied on generate, and you can preview the merge before anything is produced. Mapping profiles are saved so the next month's file lands in a single pass. A single loan file can be entered manually against the same notice engine.
Post remains the evidentiary primary; email and WhatsApp are supplementary channels. Proofs of delivery upload to the borrower account's Service-proofs folder, so the trail sits with the account rather than with a monthly batch. A return opens a Task to trace the address, and redispatch is recorded against the same account.
Deemed service is applied on a nightly sweep using the track's default, and the resulting deadlines sync into your LawSathi Calendar alongside the rest of your diary. Reminders fire ahead of the window, and each mandate dashboard lists both upcoming deadlines and anything that has already breached.
Yes. A GST invoice is raised directly from a dispatched batch and keeps its provenance back to the mandate, and the lender's MIS file can be re-exported with LCM status columns added. When an account is ready for court, one action opens a full LawSathi litigation matter from the borrower account.
