Skip to main content
GullySystem

Overdue Buckets and Weekly Monitoring

Accounts move into 1 to 30, 31 to 60, 61 to 90 and 90 plus day buckets as dates pass. The borrower list behind any figure opens in one click.

Why the bucket matters

A total overdue figure hides where the money sits. The same amount spread across last month is ordinary. Concentrated past ninety days in a few accounts, it is a different problem and needs a different conversation. Buckets separate the two.

What the review looks at

Demand against collection

What was due this week and what came in, by collector and by branch. The difference is the agenda.

Accounts that slipped a bucket

Loans that crossed into a worse bucket since the last review come up first. Discussion starts with new trouble rather than familiar names.

Promises and what became of them

A promise to pay is noted with the date it was given for. The next review shows which promises held, a fairer test of follow-up than counting visits.

Accounts nobody owns

Each overdue account can be assigned to a person for the visit. Unassigned accounts form a short list of their own.

On the loan itself

  • Every receipt, short payment and missed instalment in date order
  • Visit notes, promises to pay and the outcome of each one
  • An SMS or email reminder sent before a visit, so the date is not forgotten
  • SHG-wise outstanding, with member repayment history underneath
  • Ageing across the whole book, by product, branch and officer

How to run a weekly overdue meeting

The software supplies the list. The meeting still needs a rhythm, and small lenders that keep one catch trouble sooner.

Same day, same hour

Hold it on a fixed weekday, before collectors leave for the field. A review held whenever there is time soon stops being held.

Start with the newcomers

Open with accounts that crossed into a worse bucket. Old names can wait five minutes.

One owner per account

Leave the room with a name against every account discussed. A list without owners is only a list.

Close the loop next week

Begin the next meeting with last week’s promises. Whether they held tells you more about a borrower than a reminder count.

Weekly, fortnightly and monthly products

Repayment frequency changes how fast an account ages. A weekly loan can be a month behind in four missed instalments. A monthly loan takes four months to reach the same count. Ask your vendor to show a bucket built for each frequency, rather than one rule applied to all.

Questions to ask about overdue monitoring

  • Can I open the list behind a bucket total in one step?
  • Can buckets be drawn at the days my review uses?
  • Does the loan show who last visited and what was promised?
  • Which reminders go automatically, and which need a person?

A Monday overdue meeting, account by account

The weekly overdue meeting is where the lender’s attention goes. It works only when everyone reads from the same list. Preparation matters. Everyone arrives with the same figures.

Opening with the buckets

The manager opens the buckets and reads the totals in each one. The shift of accounts from one bucket to the next is the first topic. At this point, the meeting begins with a clear picture of the week. The week is framed.

Drilling into one bucket

The team opens the 31 to 60 day bucket and looks at the names. One click shows each borrower with the amount and last contact. The talk is about accounts, not about totals. Names replace guesses.

Assigning the calls

The manager assigns accounts to officers and collectors. Each assignment has a date for a first contact. The officers leave the meeting knowing their own list. There is no confusion about who calls whom. Ownership is clear.

Reviewing last week’s promises

Before closing, the team reads the promises made the week before. Those kept are cleared. Those broken are marked, and a different step is chosen. The meeting ends with tasks, not with hopes. Follow-through is checked.

Make an informed decision

Agree the evidence before signing off this part.

Use a representative scenario to decide what this part of the system must show and where review is still needed.

On the loan itself

Does the schedule match the agreed terms and actual release of funds?

For “On the loan itself”, use a sample already checked by your finance team. Compare due dates and the principal and interest split before relying on the resulting balance.

Background reading: Frappe Lending: repayment schedules

FAQ

Frequently asked questions

Can we set our own overdue buckets?

Yes. The 1 to 30, 31 to 60, 61 to 90 and 90 plus split is a common one, and yours is configured to whatever your review already uses. A weekly lender wants a tighter first bucket.

Does it chase the borrower on its own?

Only as far as a reminder. An SMS or email can go out on the due date and again when the account slips. The visit, the call and the conversation remain your team’s work.

What does ageing add if we already know our defaulters?

It shows the accounts drifting behind the well-known ones, and it shows them by collector. That pattern points to where follow-up starts late.

What is a bucket in loan monitoring?

A bucket is a band of days past due, such as 31 to 60. Accounts sit in one band at a time and move as the days pass, which makes the book easy to compare week against week.

Can the list be split by collector?

Yes. Overdue accounts can be assigned to a person, and demand against collection is reported per collector, so you can see whose route is slipping.

How often should overdue accounts be reviewed?

Review weekly, and weekly-repayment products may need it more often. The report reads from live records, so the cadence is a choice about people, not about software.

Does a part payment move an account back a bucket?

That depends on the rule you set for applying a receipt. Settle this during scoping, because it changes what your ageing report shows.

Can we see overdue by branch and by product together?

The ageing report cuts the same bucket totals by branch, product and officer, and each figure opens to the borrower list behind it. A branch that looks healthy in the first bucket but heavy in the last one is easy to spot.

What shows on screen when an officer visits an overdue borrower?

The loan opens with the instalments missed, the amount due, the last promise and its date, and the notes from earlier visits. The officer does not phone the office first. The outcome of the visit is added to the same record.

What is the 90 plus bucket for?

It holds every account more than ninety days behind, however far past due it has gone. Recovery effort and write-off questions are discussed there. Read its total and its account count separately, because one large loan can hide among small ones.

Where it fits

How this feature fits the system.

Loan Management System: the parts that work with this feature, the trades that use it and the ways to put it in place.

Enquiries and leads

Each loan enquiry is logged with its source and a follow-up date, and reports show which enquiries turned into applications.

Lead Management

Sanction approvals

Approval levels are set by loan amount or product, disbursement waits for the required sign-off, and the log records who approved and when.

Workflow and Approvals

Collection app for field agents

Field collectors record instalment receipts against the borrower from a phone browser, and due and received amounts appear together with collector name and date.

Receipts Management
Talk to us

Tell us what you need.

Tell us what your team does today, where work gets stuck and what you want to change.

What happens after you share your requirements

  1. We review your brief and the systems you already use.
  2. We clarify the workflow, missing information and the work to consider first.
  3. The proposed scope sets out the deliverables, responsibilities and dependencies.
  4. Review the scope and commercial terms before deciding whether to proceed.

Start with your requirements

Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.

Share your requirements