Automate Referral Bonus Tracking and Payout
Referral programs run on trust — an employee refers someone, that person gets hired, and a bonus is supposed to follow at 90 days or whatever milestone the policy sets. In practice, attribution gets lost between the ATS and payroll, milestone dates aren't tracked anywhere central, and bonuses get forgotten until the referring employee asks HR why they never got paid. Once that happens even once, employees stop bothering to refer people, since the program's credibility rests entirely on bonuses actually landing on time without the employee having to chase it.
STARTING PRICE
From €299
Standard tier · Multi-step workflow with AI extraction/decisioning and 2-3 integrations.
Get a quote →Saves roughly 2-3 hrs/week for HR/recruiting ops, plus measurably higher referral submission rates once trust in payout reliability improves.
How the automation works
We capture referral attribution at the moment of application and keep it attached to the candidate record through hire, so there's no gap where the link between referrer and referred candidate can get lost in a handoff between the ATS and payroll. Once a referred candidate is hired, the relevant milestone date — 90 days, 6 months, whatever the policy specifies — is tracked automatically, and the payout request generates and routes to payroll on that date without anyone needing to remember it. If a referred employee leaves before the milestone, the system flags the payout as void per policy rather than letting it process anyway, and referring employees get a visible status update at each stage instead of silence until the money shows up.
Process flow
- 01
Referral attributed at application trigger
When a candidate applies through a referral, the referring employee is attached to the candidate record immediately, not reconstructed later from memory or an email search.
- 02
Track through hire and milestone ai
The referral attribution persists through the hiring process, and once the referred candidate is hired, the relevant payout milestone date — commonly 90 days or 6 months — starts tracking automatically.
- 03
Check for policy-void conditions ai
If the referred employee leaves before the milestone, or the referral falls outside policy eligibility, the payout is flagged void per policy rather than processing automatically regardless.
- 04
Generate payout request on milestone output
When the milestone date arrives for a still-eligible referral, a payout request generates and routes to payroll without anyone needing to remember or manually track the date.
- 05
Sync payout to payroll system integration
The approved payout request syncs into the payroll run, so the bonus lands in the referring employee's paycheck without a separate manual entry step.
- 06
Update referrer on status output
The referring employee gets a visible status update when their referral is hired and again when the payout processes, instead of silence until the money unexpectedly appears.
Inputs
- Referral attribution at time of application
- Hire date and referral program eligibility rules
- Payout milestone schedule (e.g., 90-day, 6-month)
- Referring and referred employee employment status
Outputs
- Referral-to-hire attribution record
- Milestone-triggered payout requests to payroll
- Void/eligibility exception log
- Referring-employee status notifications
Works with
Prefer a fully custom build instead of an off-the-shelf integration? We scope both options during your free consultation — most jobs like this one work fine on standard connectors, but higher-volume or non-standard systems sometimes need bespoke API work, reflected in the complex tier.
Where this goes wrong if you get it wrong
- Referral attribution captured only at application and never carried through the hiring process gets lost in the handoff to payroll, especially when the referring employee has since left the company or the candidate was referred months before actually being hired — reconstructing it after the fact from email threads is unreliable and slow.
- A referral bonus milestone tracked nowhere central relies entirely on someone remembering to check back in 90 days, and across a program with dozens of referrals in flight at once, that tracking reliably fails for at least some of them, which is exactly what erodes trust in the program.
- Processing a payout without checking whether the referred employee is still employed at the milestone date pays out bonuses the policy explicitly voids, creating both a budget leak and, if caught later, an awkward clawback conversation nobody wants to have.
- Referring employees who hear nothing between making a referral and unexpectedly seeing a bonus land — or, worse, never seeing one land at all — lose confidence in the program regardless of whether the underlying process is actually working correctly; visible status updates matter as much as the payout itself.
Frequently asked questions
What happens if a referred employee leaves before the payout milestone?
The payout is automatically flagged void per policy rather than processing regardless, and the referring employee gets a status update reflecting that rather than silence.
Does the referring employee know where their referral stands?
Yes — they get a status update when their referral is hired and again when the payout actually processes, instead of finding out only when money unexpectedly appears in their paycheck.
How does the bonus actually get paid?
A payout request generates automatically on the milestone date and syncs into the payroll run, so it lands in the employee's normal paycheck without a separate manual payment step.
Can different roles have different referral bonus amounts or milestones?
Yes, bonus amount and milestone timing are configured per role tier or program rule, matching whatever the referral policy specifies rather than one flat amount for every hire.