Skip to main content
GullySystem

Daily dues follow-up for farmer credit

Dues follow-up turns the seasonal credit book into a list of whom to call today, what the farmer promised and what was said last time. Each call is noted when it ends. The owner, the counter and the accountant all read one trail instead of three memories.

What the dues follow-up list keeps

A dues list is a working list. It is drawn from the credit book each morning and added to after every call. Four pieces of information sit against each farmer, so the person phoning never starts from a blank page.

Whom to call today

Farmers whose promised date has passed, or falls today, appear on the day’s list, ordered by promised date. The oldest broken promise comes first. No farmer reached today comes up a second time. One call per day is enough.

What was promised

Beside each name stands the amount due, the bills it covers and the date the farmer gave. A promise to pay after the paddy is sold is written as that, with the date. Nothing depends on remembering.

What was said last time

The last conversation shows in a line or two, with who spoke and when. Anyone who said the cotton buyer had not paid is not asked the same question again. Calls build on each other. Nobody starts cold.

The next call and its owner

Every call ends with a next step: a new promised date, a visit or a pause. The next call is assigned to one person. A due that belongs to everyone ends up belonging to no one.

Dues follow-up through a collection week

Calls are made between customers, in a shop that is busy with sowing. The list has to fit those gaps. Four scenes show how a morning list turns into payments, promises and notes that the next caller can read the same day.

The morning list is opened for dues follow up

Before the counter fills, the owner or a clerk opens the day’s list. Farmers past their date appear with the oldest first. Calls are shared out so nobody hears from two staff members. Sharing keeps it short.

A call that reaches a promise

A grower answers and says the harvest money arrives after market day. Staff enter a new date and a short note. That farmer drops off today’s list and returns on the new date. The wait is recorded.

A farmer pays at the counter

A farmer walks in with part of the dues. The clerk records the payment, which clears the oldest bill. The follow-up list refreshes. The call planned for the afternoon is no longer needed, and nobody makes it.

A message instead of a call

For a farmer who seldom picks up, the shop sends a text or a WhatsApp note about the balance close to its date. Staff note that it went. The next person knows the message was sent. Duplicates stop.

Who sees the follow-up list and what they do

Collection is shared work in a small shop. Four people take part, each with a different piece of the same list. Shared access keeps them from tripping over one another. It also keeps them from calling one grower twice in an afternoon.

For the owner

Reads credit past its promised date by farmer and village, assigns calls and decides when to extend. Sees whose promise has been broken twice. Holds the final say on who gets more credit. That say is the owner’s alone.

For counter staff

Check the list when a farmer on it walks in and raise the payment on the spot. See the last note before saying a word. A clerk who knows the history needs no awkward opening. The conversation stays kind.

For the accountant

Reads dues and promised dates beside sales and payments. Notes on calls stay with the farmer, and the books receive only the figures. The accountant sees how much is due and how old it is. Age matters here.

For delivery crews

Do not collect or chase. They can pass on a note from a village visit, such as a farmer away until market day. The note goes to the record, and the caller reads it before dialling.

Decisions to settle before the list is used

Rules decide the tone of a follow-up list. Four decisions settled with the owner keep it fair to farmers and useful to staff. Each one is quicker to agree before the first overdue balance than during a busy sowing week.

Who calls and who may extend

Decide which staff phone farmers and who may grant a new promised date. A clerk may note what the farmer says. An extension belongs with the owner. The rule is written down so every caller says the same thing.

What the list leaves out for dues follow up

Agree which farmers stay off the list, such as those in a dispute or with a note from the owner. Leaving someone off is a deliberate step. It carries a reason, which the owner can read later on.

How earlier promises come across

Promises written in the old ledger margin are keyed as the opening notes against each farmer, with dates. Your office checks them against the credit book. Without this, the first week of calls starts cold.

Which report matters first for dues follow up

Begin with seasonal credit by farmer and village, oldest balance first, and read it as the call list. Test it for one morning. If the order feels wrong, change the rule before the second day.

How follow-up connects to the product

This list is a view of credit, made practical. It reads balances, promises and payments from other features and writes only the notes of the calls. Five links tie it in. A payment at the counter and a call on the phone never clash on the same farmer.

  • Seasonal credit book supplies balances, bills and promised dates
  • Farmer records hold phone numbers and crop for each call
  • Payments at the counter remove a farmer from today’s list
  • Text, email and WhatsApp notes are logged on the record
  • Accounting export carries dues and ages to the accountant

Where dues follow-up stops

The list says whom to call and what was said. It makes no call. It does not decide how firm to be with a neighbour either. Recovery steps, notices and any legal action stay with the owner and an adviser. A shop with a handful of credit farmers can keep the names on a single sheet.

FAQ

Frequently asked questions

How does the list know not to call twice?

Each call is noted against the farmer with its date and outcome. A farmer reached today, or promised a later date, drops off the list until that date arrives. Two staff cannot dial one person by accident. Duplicate calls end.

Can a caller see what was said last time?

Yes, in a line or two beside the farmer’s name, with who spoke and when. Callers read it before dialling. Opening with the right question saves a minute and some patience on both sides of the call.

Does it send reminders on its own?

A balance close to its due date can trigger a text, email or WhatsApp note. Wording and timing are agreed at set-up here. Phone calls remain with staff, who read the list and decide whom to ring.

What order does the list follow?

It follows promised date, oldest broken promise first. The credit report orders balances oldest first as well. The owner can change the order for a village or a crop if a trip is planned. Plan the route.

How do we mark a farmer as disputed?

Add a note with the reason and take the farmer off the list. The owner sees the note and decides when to put the farmer back. The balance stays in the credit book meanwhile, visible to all. Nothing is deleted.

Where it fits

How this feature fits the system.

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

Truck receipt and bag count

The count at the gate is booked against the company invoice by grade, and shortages or wrong grades are recorded before the driver signs.

Goods Receipt (GRN)

Grade and warehouse stock

Stock is held by grade, bay and stack, so the counter knows which shed to send a loader to for forty bags.

Warehouse Management

Company allotments and indents

Allotments, lifted quantities and pending balances sit beside each indent, so the next order to the company is placed against real figures and not a remembered total.

Purchase Order 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