In this guide 6 sections
Microfinance EMI collection works best when the receipt is written at the centre meeting, against each member, by the officer who took the money. The group total then follows from the member lines. Build the instalment schedule once, mark absentees at the meeting and reconcile cash before anyone leaves the branch.
What happens at a centre meeting
In group lending, members meet at a fixed place and time, often weekly or fortnightly. A group leader gathers the instalments, and a field officer counts the cash and signs the book.
The meeting is the only moment when every member, the leader and the officer are in one place. That makes it the right moment to write the record.
Copying a paper book into the office system the next morning loses that advantage. Mistakes surface when nobody can ask the member.
Schedules and the amount due per member
Each loan needs a schedule built from principal, interest method, tenure and frequency. Flat and reducing balance methods give different instalments, so the method must be fixed per product before disbursement.
The officer should open a centre sheet that lists every member with the amount due today, any arrears and any advance paid earlier. The sheet is generated, not typed.
Check the current rules from your regulator or network on instalment frequency, fees and member protection. Those rules change, and software should follow them, not decide them.
- Principal, interest and fee split per instalment
- Arrears carried from earlier meetings
- Advance payments adjusted against the next due date
- Group leader and centre named on the sheet
Recording the receipt
Enter one receipt per member, not one lump for the group. A member who pays part of an instalment, or pays for an absent neighbour, needs that shown on the right account.
Absent members are marked at the meeting with a reason and a promised date. The promise sits on the loan so the next officer sees it.
Where the officer uses a phone, the receipt can be recorded offline and synced later. Confirm that your tool handles this before you rely on it in low-signal villages.
Closing the day
At the end of the route the officer deposits cash with the branch cashier. The cashier counts, compares with the receipts entered and signs off the difference, if any.
A small gap on day one is easier to explain than a large one on day thirty. Close each day, not each month.
Banks and mobile wallets add a second path. Bring digital payments into the same centre sheet so a member is not shown as overdue while the transfer is in transit.
Reports a branch manager reads
Start with demand against collection by centre and by officer. Then look at members who missed two meetings in a row, because that pattern often precedes a default.
Ageing buckets, such as overdue by a few days or by a month, tell the manager where visits should go. Keep the borrower list behind each figure.
A good test is whether the manager can answer a trustee’s question about one centre within a minute, without calling the officer.
Centre meeting collection sheet
A one-page sheet per centre. Rows list each member with loan number, instalment due, arrears, amount received, mode and a mark for absent or part paid. The footer holds the leader’s name, the officer’s name, total cash counted and the cashier’s sign-off with date.
Open a blank worksheet to printQuestions owners ask
Should receipts be per member or per group?
Per member. Group totals are the sum of member lines. This keeps each repayment history correct and lets you handle part payments or a neighbour paying on someone’s behalf.
Can collection work without mobile data?
It can if the app stores receipts on the phone and syncs later. Test it in your weakest signal area first, and check how conflicts are handled when two people edit one loan.
How do I handle a member who misses a meeting?
Mark the absence with a reason and a promised date on the loan. The next visit, reminder and ageing bucket follow from that record.
Does software make us compliant with microfinance norms?
No. Software records what happened and applies the rules you configure. Compliance depends on your policies and on checking current norms with your regulator or network body.