Skip to main content
GullySystem
Financial services

Roles and Permissions for Chit fund companies

Control which records and actions each user can access.

Platform

Does this function belong in your operation?

Use when different staff should see or change different business information.

A user joins, changes responsibility or leaves.

The foreman, the cashier, the auctioneer and the field agent see different parts of a group. Only authorised staff can confirm a prize payout. Agents see their own subscribers and nobody else’s.

Bring the records the workflow depends on.

  • User list
  • Role responsibilities
  • Record-level access rules

Outputs to check

  • Approved role-access matrix
  • User assignment history
  • Access-review exception list

Follow the roles and permissions workflow.

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

  1. 1. Map responsibilities

    Identify the records and actions each role needs.

  2. 2. Review sensitive rights

    Separate high-impact actions and define approval authority.

  3. 3. Assign named users

    Grant the approved roles without sharing credentials.

  4. 4. Test access

    Check permitted actions, denied actions and combined-role effects.

  5. 5. Review changes

    Remove obsolete access after transfers, temporary cover or departures.

Who uses the module, and who approves?

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

Owner

Decides who may see money. It is the one setting most owners want to make themselves.

Branch manager

Works inside their own branch and requests anything beyond it.

Office admin

Adds a new joiner to a role on the first morning, and closes it on the last.

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.

Temporary cover required

Grant time-limited authority with an owner and review date.

Conflicting roles assigned

Review combined permissions rather than checking each role in isolation.

User leaves

Revoke access in each connected system and track any unconfirmed closure separately.

Can this work independently?

Permissions operate on the applications and records that enforce them. A documented role matrix alone cannot restrict an unrelated system. Employee or identity-provider links can support joiner and leaver actions, while audit records show assignments and privileged changes.

Systems and records it connects with

  • Audit trail: Actor, timestamp and change evidence for controlled actions.
  • Multi-branch consolidation: Branch identifiers and reconciled combined reporting inputs.
  • Workflow and approvals: Authorised decisions and pending request status.
  • Payroll: Approved pay inputs, deduction calculations and payment instructions.

Configure, test and introduce the workflow.

  • You describe who does what in the business. You get a proposed set of roles to confirm.
  • Cost, margin, wastage and salary visibility are settled. A note records who may see each. Staff are entered with their own sign-in. Shared passwords are retired as people move across.
  • A few staff try their screens on the trial. They tell us what is missing or too open. Gaps are found early. Exceptions granted to individuals are reviewed with the owner. The leaving routine is written down.

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.

  • Restricted records are inaccessible to unauthorised users.
  • Role changes affect the intended permissions.
  • Departed users lose access as configured.
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 roles and permissions?

Use when different staff should see or change different business information. A user joins, changes responsibility or leaves.

What should we bring to the requirements discussion?

Bring anonymised examples of User list; Role responsibilities; Record-level access 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. Control which records and actions each user can access. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

Permissions require ongoing ownership and do not replace broader security controls.

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. Restricted records are inaccessible to unauthorised users. Use this check when reviewing the first working version.

Talk to us

Discuss roles and permissions 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