In this guide 6 sections
A DSA loses payout money in four places. Files go unchecked against the lender’s rate card and slab, payouts arrive short or skip files, invoices go out late, and connector shares are paid from memory. One register of disbursed files, with expected payout beside the amount received, shows each gap.
Start from the disbursal register
Every payout is worked out from a disbursal. The lender, the product, the disbursed amount and the disbursal date decide what you are owed. If those four facts sit in a WhatsApp chat, the payout cannot be checked.
So the register comes first. Each disbursed file gets one row with the sanction letter, the sanctioned and disbursed amounts and your DSA code. Part disbursals get their own rows.
Four places the money goes missing
Most leaks are not disputes. They are files nobody looked at again. Rates differ by lender, product and slab, and a short payment looks like a full one unless someone has the expected figure ready.
The leaks repeat every month. That makes them easy to find once the register exists.
- A disbursed file the lender’s payout statement simply skipped
- A payout worked out at the wrong slab
- An invoice raised weeks after the disbursal
- A connector paid twice, or paid for a file that was not his
Work out the expected payout before the lender does
Hold each lender’s rate card by product and slab, with the date it took effect. Rate cards change. A file disbursed in April is paid at April’s card, not today’s.
With the card and the register side by side, the expected payout for every file is known in advance. When the lender’s statement arrives, the comparison takes minutes. Differences become a short list to raise with the lender’s channel team.
Match receipts to invoices every month
Raise the invoice per lender soon after the payout statement, listing the files it covers. When money lands, match it against that invoice and mark each file paid, short or pending.
Do this on a fixed day. A monthly habit catches a skipped file while the banker still remembers it. Your auditor also gets a clean trail.
Settle connector shares from the same record
A connector or sub-DSA remembers the disbursal date of his files well. Your records should too. Tag each lead with its source when it first comes in, not when he calls about his share.
His share is then worked out from the same row as your payout. Record what was paid and when. When he calls about April, the answer is one filtered list, not a search through notebooks.
- Source tagged at the lead stage
- Share rule agreed and written down per connector
- Paid and pending shown per file
DSA payout check sheet
One row per disbursed file, with lender, product, slab, disbursal date, expected payout, invoice number and amount received. Add a column for the connector and his share. Filter for rows where received and expected differ, and that is the month’s follow-up list.
Open a blank worksheet to printQuestions owners ask
Will the bank’s DSA portal show all of this?
Not across lenders. Use it for login and status with that bank. It will not show your files with other lenders, or what each of them still owes you.
Can the software fetch a CIBIL score or bureau report?
No. Bureau access sits with the lender. The software records what the credit team tells you, and your executive enters eligibility notes.
Is a lender’s loan management system suitable for a DSA as it is?
Not straight out of the box. GullySystem rebuilds its Loan Management System core around the file pipeline and payouts, and drops the EMI collection parts a DSA never opens.
Who can see customers’ bank statements and ITRs?
Only the executive handling that file and the managers you name. Documents sit on a server under your own account, and every download is logged.