Skip to main content
GullySystem
Financial services

Mandates and Auto-Debit for Chit fund companies

Track customer payment permissions and recurring debit outcomes.

Subscriptions

Does this function belong in your operation?

Use when recurring customer charges are collected through supported payment mandates.

A customer authorises recurring collection through a supported provider.

Subscribers who agree to a standing debit have a mandate recorded against the ticket. Monthly debit files run on the due date. A bounced debit returns to the collections list with its reason.

Bring the records the workflow depends on.

  • Customer mandate details
  • Billing schedule
  • Provider response and cancellation rules

Outputs to check

  • Provider-confirmed mandate register
  • Debit attempt and result history
  • Failed-collection and settlement list

Follow the mandates and auto-debit workflow.

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

  1. 1. Obtain authorisation

    Use the supported provider's customer-permission process.

  2. 2. Confirm the mandate

    Record the accepted reference, status and permitted terms.

  3. 3. Prepare the debit

    Use an eligible bill and the agreed amount and date.

  4. 4. Submit and monitor

    Track each attempt without confusing a queued request with success.

  5. 5. Reconcile settlement

    Match received funds and manage failures or revocation under the approved rules.

Who uses the module, and who approves?

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

Accounts assistant

Reconciles collection outcomes, investigates failures and follows the approved retry or refund process.

Sales or front desk

Gets the mandate approved while the customer is signing up, which is the only moment they will do it.

Owner

Sees how much of the month’s collection arrives without a phone call.

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.

Mandate revoked

Stop future submissions and review any request already in progress.

Debit fails

Record the provider reason and use only the approved retry or customer-contact process.

Response duplicated

Match the attempt reference before creating another receipt or retry.

Can this work independently?

Mandates depend on an authorised bank or payment-provider process and cannot be created by an internal record alone. Subscription billing supplies eligible amounts; receipts and reconciliation confirm collection. A submitted debit, successful provider response and settled funds are separate states.

Systems and records it connects with

  • Subscription billing: Recurring plans, billing periods and account changes.
  • Invoice management: Issued invoice references, line amounts and outstanding balances.
  • Payment gateways and direct debit: Authorised recurring charges and provider-confirmed outcomes.
  • WhatsApp and SMS: Permitted message content and channel delivery responses.

Configure, test and introduce the workflow.

  • We review your gateway or bank and the kinds of mandate it supports. You provide your account details for set-up. You get a short note on what is possible.
  • Plans, due dates and limits per charge are set out. The owner approves them. Wording of customer notices is agreed. Test mandates and debits are run in the gateway’s test mode. Accounts checks that results post against invoices.
  • A few willing customers are invited to sign up. The team watches notices, debits and failures. Remaining customers are invited in stages. The register is reviewed with the accounts team at regular meetings.

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.

  • Debits require an active valid mandate.
  • Retries follow the agreed rule.
  • Collections reconcile with provider settlements.
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 mandates and auto-debit?

Use when recurring customer charges are collected through supported payment mandates. A customer authorises recurring collection through a supported provider.

What should we bring to the requirements discussion?

Bring anonymised examples of Customer mandate details; Billing schedule; Provider response and cancellation 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. Track customer payment permissions and recurring debit outcomes. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

Customer authorisation, provider support and current payment rules determine whether a debit can be made.

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. Debits require an active valid mandate. Use this check when reviewing the first working version.

Talk to us

Discuss mandates and auto-debit 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