Client Portal for Mutual fund distributors
Give customers controlled access to account documents and requests.
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.
Investors log in to see their folios, SIP dates, capital gain statements and the documents shared with them. They upload a cancelled cheque directly. A nominee form needs no chat thread.
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.
Who uses the module, and who approves?
Keep responsibilities distinct even when one person holds more than one role.
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.
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.
How the business operates.
Your book is hundreds of SIPs across families, fund houses and folios. It earns trail only while those SIPs keep running, and keeping them running is follow-up work done on the 5th, 10th and 15th of every month.
The records that hold the operation together.
- Family and folio register. Group every folio of a household together, with fund house, plan type, holder names and the goal each holding was opened for.
- SIP calendar and failure alerts. List each plan against its debit date and flag rejections or lapsed registrations in the morning, with the client’s number beside the line.
- Debit mandate register. Track each mandate from form to approval, with bank, limit, validity and the plans that depend on it, and chase any stuck for too long.
- KYC and nominee board. Show every investor’s KYC status and nominee declaration in one list, with the missing item named and the person who will chase it.
Operational bottlenecks to check
Failed SIP debits are spotted too late
After two rejected instalments the registration lapses, and the client has quietly stopped investing. You hear about it at the next review.
KYC on hold blocks the next purchase
A KYC record shows on hold, or the nominee declaration was never given, and you learn when a fresh purchase is rejected. The client asks what went wrong.
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. Enquiry
Each referral or walk-in is recorded with where it came from, what the family wants and the next step promised. The reminder fires on the date the owner set.
2. Onboarding
The investor’s KYC status, nominee choice, bank account and debit mandate are recorded, with the missing item named. Scanned forms are kept on the client’s file.
3. Plans and folios
Each regular plan is entered with its folio, fund house, amount and date, and grouped under the family. The goal each plan was started for is noted beside it.
4. Report reading
Reports from the registrars and platforms are loaded each morning. Rejected debits, ceased plans and status changes become tasks on a named staff member’s list.
5. Reviews and statements
Before a review, the family page shows plans, dates and notes from the last meeting. At year end, holding and gains statements are gathered family by family.
6. Brokerage check
Expected trail is worked out per folio and compared with what each fund house paid. Folios with a gap go onto a query list for that fund house.
Industry reports to connect with
- Failed and lapsed plans by client, fund house and week
- Mandates and KYC items outstanding, oldest first
- Enquiries by source, goal and stage
- Follow-up tasks open and closed by staff member
Questions before implementation.
When should mutual fund distributors 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.
Related functions for mutual fund distributors.
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
- We review your brief and the systems you already use.
- We clarify the workflow, missing information and the work to consider first.
- The proposed scope sets out the deliverables, responsibilities and dependencies.
- 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