Skip to main content
GullySystem
Financial services

Client Portal for Chit fund companies

Give customers controlled access to account documents and requests.

Finance & Accounting

Does this function belong in your operation?

Use when customers repeatedly request copies, statements or account updates.

Customers need their own financial records or updates.

Subscribers log in to see their ticket, instalments paid, dividend credited and next auction date. A prize bidder sees the prize amount once the foreman confirms it. Statements download for the chosen group.

Bring the records the workflow depends on.

  • Customer contacts
  • Available documents
  • Access rules

Outputs to check

  • Customer account view
  • Document-access record
  • Customer request and response history

Follow the client portal workflow.

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

  1. 1. Authorise the contact

    Verify the person and the account they may access.

  2. 2. Prepare account data

    Choose approved documents and reconcile balances with the source.

  3. 3. Publish the view

    Expose only the permitted records and their data date.

  4. 4. Handle requests

    Route customer questions to the responsible account owner.

  5. 5. Maintain access

    Review departed contacts, document changes and resolved queries.

Who uses the module, and who approves?

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

The client’s accounts assistant

Downloads the bill and the statement when it suits them, even after your office has shut.

Your accounts desk

Stops attaching PDFs all morning, and sees which clients have opened their bills.

Account manager

Reads the requests raised, and answers before the client escalates to the owner.

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.

Contact leaves the customer

Remove that person's access while retaining the business account.

Disputed invoice

Record the query without changing the issued invoice or outstanding balance automatically.

Outdated statement

Display the data date and reconcile the source before presenting it as current.

Can this work independently?

The portal needs approved customer-account data and login access. Financial documents come from invoicing or accounting, either through imports or agreed connections. Online payment and support-ticket creation are separate handoffs; customer access does not grant editing rights over the ledger.

Systems and records it connects with

  • Invoice management: Issued invoice references, line amounts and outstanding balances.
  • Receipts management: Recorded customer payments and invoice allocations.
  • Ticket management: Numbered requests, ownership and resolution history.
  • Payment gateways and bank transfers: Payment references and reconciled settlement or bank evidence.

Configure, test and introduce the workflow.

  • We list the documents and actions you want to expose. You decide what stays internal. A written view of the portal pages comes back.
  • Customer records are matched to login holders. You supply contact names, and we return a trial import to check. Logo, colours and domain are applied. You get a private link to try the portal as a client would.
  • A small group goes in early. Their notes on wording and missing documents come back to you as a short list. Invitations go out in groups. Your accounts desk learns the reply screens, and phone requests for copies fall away as clients get used to the page.

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.

  • Customers cannot view other accounts.
  • Balances reconcile with the ledger.
  • Requests retain submission dates.
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 client portal?

Use when customers repeatedly request copies, statements or account updates. Customers need their own financial records or updates.

What should we bring to the requirements discussion?

Bring anonymised examples of Customer contacts; Available documents; 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. Give customers controlled access to account documents and requests. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

Payments, signing and identity connections need separate scope confirmation.

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. Customers cannot view other accounts. Use this check when reviewing the first working version.

Talk to us

Discuss client portal 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