Skip to main content
GullySystem
Financial services

Collections and Payment Follow-Up for Chit fund companies

Turn unpaid customer balances into assigned follow-up actions.

Sales and Distribution

Does this function belong in your operation?

Use when customer credit creates balances that require organised follow-up.

An invoice becomes due or a payment promise needs checking.

Agents on rounds see the subscription due per ticket and the amount already paid. Late subscribers are called in order of how long they have been behind. Promises to pay carry a date.

Bring the records the workflow depends on.

  • Outstanding invoices
  • Customer contacts
  • Follow-up ownership and rules

Outputs to check

  • Assigned collection action list
  • Payment-promise and dispute history
  • Overdue balance follow-up report

Follow the collections and payment follow-up workflow.

Use this sequence to compare your current process with the proposed module. Agree the owner, permission and exception at each step.

  1. 1. Prepare balances

    Use current invoices, credits and allocated receipts.

  2. 2. Prioritise action

    Assign due accounts and separate disputed amounts.

  3. 3. Contact the customer

    Record the discussion, promise and next date.

  4. 4. Check the outcome

    Confirm whether payment arrived or another decision is needed.

  5. 5. Close or escalate

    Remove settled items and route unresolved exposure to the authorised owner.

Who uses the module, and who approves?

Keep responsibilities distinct even when one person holds more than one role.

Accounts assistant

Works the list from the top and keeps the notes current.

Field collector

Carries the day’s route on a phone and records what was actually brought back.

Sales executive

Knows what the customer owes before asking for the next order.

Owner

Reads promises broken twice, and decides who stops getting goods.

Decide how exceptions are handled.

These business rules belong in configuration and testing. A normal transaction alone does not demonstrate that the workflow is ready.

Customer disputes invoice

Separate the dispute owner and action from routine payment reminders.

Promise date missed

Record the failed promise and route the next action under the agreed policy.

Payment received during follow-up

Reconcile it before sending another demand for the same amount.

Can this work independently?

Collections can use a reviewed outstanding-balance import. Invoice and receipt connections keep the amount current, while credit control decides whether further orders are held. Follow-up records do not post payments; settlement must come from the authorised receipt or accounting process.

Systems and records it connects with

  • Invoice management: Issued invoice references, line amounts and outstanding balances.
  • Receipts management: Recorded customer payments and invoice allocations.
  • Credit control: Customer limits, current exposure and authorised order releases.
  • WhatsApp and SMS: Permitted message content and channel delivery responses.

Configure, test and introduce the workflow.

  • We go through your receivables and the way calls are made now. You send a recent outstanding statement. A note comes back on how accounts are grouped.
  • Timing before and after the due date, tone of messages and escalation limits are agreed. You approve the wording for each stage. Open bills are imported from your accounting software. The accounts team checks a sample against the ledger. Mismatches are corrected.
  • Collectors and the accounts assistant use the list beside their old method. Notes go in. Gaps in the list are fixed. Collectors are trained on the phone screens. The diary is set aside. From then on the daily list is the working tool.

Check the result before rollout.

Apply these checks to a sample from the agreed workflow, then repeat with an exception. Keep the expected result beside the test record.

  • Follow-ups use current balances.
  • Payment promises retain dates.
  • Settled invoices leave the active collection list.
Chit fund companies

How the business operates.

Every group has its own chit value, duration, number of seats and auction date, and the rules in the chit agreement differ slightly between groups. A company with ten groups may have hundreds of tickets, and a member holding three of them expects to see all three in one place.

Chit groups and tickets

Set up each group with chit value, duration, seats, subscription, auction frequency and commission rate, and give every member a numbered ticket.

Members, nominees and agents

Keep one record per member with nominee, bank details, identity papers marked verified or rejected, and the agent who introduced them.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Chit groups. Hold each group’s code, chit value, duration, seats, subscription, auction frequency, bid floor, bid ceiling and commission rate. Status runs from draft to active to completed, with draw dates for every month.
  • Members and nominees. Keep one record per person with member code, mobile number, tax number, occupation and income, plus nominee, bank details, specimen signature and the introducing agent.
  • KYC documents. Upload national ID, tax card, address proof and photograph against the member. Each paper is pending, verified or rejected with a reason, and shows the verifier’s name.
  • Subscribers and tickets. Place a member on a ticket number in a group, with guarantor, surety bond, lien notes and security details, so a defaulter’s exposure is visible before any prize is paid. One person can hold tickets in several groups, each with its own balance.

Operational bottlenecks to check

Dividend working is done on paper

One wrong formula in a spreadsheet means a subscriber pays the full instalment instead of the net, and a dispute follows. Trust takes the damage.

Agent collections reach the office late

Cash stays with the agent for days. A subscriber may hold a receipt that the office has not yet seen. The office learns on the weekend.

How work flows across this business

This module sits within a wider operating process. Use the sequence to identify the other teams and records affected by a change.

  1. 1. Opening a group

    Enter chit value, duration, number of seats, monthly subscription, foreman’s commission and auction day, then assign members to ticket numbers and print the chit agreement for each signature. The group locks when the last seat fills. That raises the first instalment.

  2. 2. Collecting instalments

    Record each payment against the ticket’s due at the counter or on the doorstep, by cash, bank transfer, cheque or mobile wallet. Every payment gets a receipt number, and a partial payment leaves the balance showing.

  3. 3. The auction

    The auction screen lists only non-prized tickets. Enter the winning ticket and bid, which is checked against the group’s bid floor and ceiling, then record the minutes of the draw and the names of the subscribers who attended. Tie bids can be settled by lot.

  4. 4. Dividend and next month’s dues

    The foreman’s commission comes out of the bid discount, and the remainder is split as dividend across the group’s tickets, with the rounding difference carried to the group’s kitty. Next month’s due for every ticket is raised with the dividend already deducted.

  5. 5. Security and payout

    The prized ticket gets a pending payout for the net prize. The office records the sureties, guarantor details and any lien, and uploads scanned bonds. Release happens only after verification.

  6. 6. Month close and records

    The group ledger shows each ticket’s net payable, receipts and arrears. After the final auction the group is marked completed. Auction minutes, the subscriber register, receipts and payout log can be listed by group and month. Which returns go to the Registrar differs by state, so check the list with your auditor.

Industry reports to connect with

  • Defaulters: every ticket in arrears, the amount, days late and the mobile number
  • Foreman’s commission ledger by group and draw month
  • Group-wise expected, collected and outstanding amounts
  • Monthly ledger and cashbook for any group and instalment

Questions before implementation.

When should chit fund companies consider collections and payment follow-up?

Use when customer credit creates balances that require organised follow-up. An invoice becomes due or a payment promise needs checking.

What should we bring to the requirements discussion?

Bring anonymised examples of Outstanding invoices; Customer contacts; Follow-up ownership and rules. Show who creates, checks and changes each record. Use only records from an activity that meets the suitability conditions above.

Does this replace our existing business software?

The starting point is your current system and the gap you need to close. Turn unpaid customer balances into assigned follow-up actions. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

Communication permissions and collection conduct remain your responsibility. The customer’s actual payment is recorded separately from follow-up activity.

How are scope, price and rollout decided?

The proposal follows a review of your records, user roles, branches and existing software. Data migration, connections, training and support are scoped separately where needed. Follow-ups use current balances. Use this check when reviewing the first working version.

Talk to us

Discuss collections and payment follow-up for your business.

Tell us which workflow needs attention and which systems your team uses. The next step is a requirements discussion and a written scope.

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