Skip to main content
GullySystem
Professional services

Commission and Incentives for Recruitment agencies

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.

Recruiters earn on placements that have joined, with different rates for the lead recruiter and the sourcer. Targets are set per recruiter. A fee refunded to a client reduces the next payout.

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.
Recruitment agencies

How the business operates.

The fee is earned on joining day. It is kept only if the candidate is still at the desk when the replacement window closes. Most agencies watch the first half of that closely and the second half not at all.

Mandate and job description register

Hold each client requirement with its fee terms, replacement clause, number of positions and the recruiter it belongs to, so nobody works a mandate that closed last week.

Candidate pipeline

Move candidates through sourced, screened, submitted, interviewed, offered and joined, with a duplicate check running at submission.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Client records and fee terms. Keep each client company, its hiring contacts, the fee basis agreed, payment days and the replacement window on one record.
  • Mandates and job orders. Record every requirement with the job description, seat count, location, salary band, priority and closing date against the client who raised it.
  • Candidate database. Hold candidate profiles with their CVs, current role, notice period, expectation, skills and every mandate the person was considered for. Recruiters look a candidate up by skill, role, location or notice period.
  • CV sourcing and intake. Add CVs from mail, portal downloads, referrals and walk-ins, catch duplicates on phone or mail, and tag each one to a mandate.

Operational bottlenecks to check

The same résumé goes twice

Two recruiters submit one candidate to the same client, and the client notices before either of them does. Your credibility takes the hit.

Client feedback never comes back

Candidates sit after the first or second round with nobody chasing the panel. A good profile goes cold. The mandate stays open.

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. Mandate taken

    A client sends a requirement. The role, seat count, location, salary band, fee basis and closing date are recorded against that client company.

  2. 2. Sourcing

    Recruiters pull CVs from the database, portals, referrals and walk-ins. Every CV attaches to a candidate record. Tagging then links it to the mandate it answers.

  3. 3. Screening

    The recruiter calls the candidate and notes current role, notice period and expectation. A rating against the mandate decides who enters the shortlist.

  4. 4. Submission and interview

    Shortlisted profiles go to the client with a submission date. Rounds are booked with the panel, and each verdict is written on the candidate’s row.

  5. 5. Offer and joining

    The offer, the joining date and the documents collected are recorded. Notice period and the day the candidate reports are followed until joining is confirmed.

  6. 6. Invoice and replacement window

    The fee is invoiced on the trigger agreed with that client. The replacement clock starts at joining, and collection follow-up sits with accounts.

Industry reports to connect with

  • Open mandates by client, recruiter and age
  • Pipeline count at sourced, screened, submitted, interviewed and offered
  • Closures made, offers declined and backouts before joining
  • Candidate sources that end in a placement

Questions before implementation.

When should recruitment agencies 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