Skip to main content
GullySystem
Financial services

Commission and Incentives for Mutual fund distributors

Calculate incentive amounts from approved sales or collection rules.

Sales and Distribution

Does this function belong in your operation?

Use when compensation depends on recorded sales, collections or other agreed outcomes.

A commission period is ready for review.

Trail brokerage received from fund houses is matched with what is due on each scheme. A short payment is highlighted. Staff incentives follow assets brought in, as the firm has set them.

Bring the records the workflow depends on.

  • Eligible transactions
  • Commission rules and dates
  • Participant assignments

Outputs to check

  • Transaction-level incentive calculation
  • Adjustment and approval statement
  • Payout handoff record

Follow the commission and incentives workflow.

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

  1. 1. Approve the scheme

    Record eligibility, calculation basis and effective dates.

  2. 2. Collect eligible activity

    Use the agreed sale or collection evidence.

  3. 3. Calculate earnings

    Apply attribution, slabs and exclusions without manual overwriting.

  4. 4. Review adjustments

    Resolve returns, reversals and approved exceptions.

  5. 5. Approve payout

    Send the authorised statement to payroll or accounts and retain settlement references.

Who uses the module, and who approves?

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

Owner

Sets the rules and approves the month’s payout.

Accounts assistant

Runs the working, checks the holds, and pays from the same statement.

Sales executive or agent

Sees what has been earned so far this month, and which customer’s payment is keeping the rest back.

Branch manager

Reads the team’s earnings against targets, without opening anybody’s salary.

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.

Sale later returned

Apply the approved reversal rule and show the affected prior earning.

Participant changes territory

Use the agreed attribution date rather than today's owner automatically.

Manual adjustment requested

Require a reason and approval separate from the formula result.

Can this work independently?

Calculation needs eligible sales or collection records and effective-dated rules. It can run from imports without payroll, but payroll or accounts performs the payment. Returns, credits and reversals must feed the calculation so a booked sale is not rewarded twice or retained after reversal.

Systems and records it connects with

  • Invoice management: Issued invoice references, line amounts and outstanding balances.
  • Receipts management: Recorded customer payments and invoice allocations.
  • Collections and follow-up: Due balances, payment promises and follow-up outcomes.
  • Payroll: Approved pay inputs, deduction calculations and payment instructions.

Configure, test and introduce the workflow.

  • You describe how each role is paid, on paper or aloud. You get a written note of each rule in plain language to confirm. Plain words are enough.
  • Old and new rates are entered with the dates they apply from. You get a screen to check a past month against what was paid. Past months are good tests. Statements are produced for a few people from last month’s bills. They read them, and you hear what does not match. People check their own.
  • You decide what pulls a commission back and when. The rules are tested with returned orders and bounced cheques. Edge cases come out here. The accounts team prepares payouts from the statements and marks them. Staff are shown how to read their own statement. Questions drop quickly.

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.

  • Calculations trace to qualifying transactions.
  • Returns follow the agreed reversal rule.
  • Rule changes use the correct effective date.
Mutual fund distributors

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.

SIP failure and cessation alerts

Flag mailback entries every morning with the client’s number beside them, so the call happens before the next debit date.

KYC, mandate and nominee board

List every investor’s KYC, debit mandate and nominee status in one place, with the missing item named.

See the full industry workflow, reports and implementation plan →

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. 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. 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. 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. 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. 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. 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 commission and incentives?

Use when compensation depends on recorded sales, collections or other agreed outcomes. A commission period is ready for review.

What should we bring to the requirements discussion?

Bring anonymised examples of Eligible transactions; Commission rules and dates; Participant assignments. 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. Calculate incentive amounts from approved sales or collection rules. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

Employment terms, tax treatment and payout approval remain with your authorised team.

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. Calculations trace to qualifying transactions. Use this check when reviewing the first working version.

Talk to us

Discuss commission and incentives 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