Referrals · Human Resources
Every open job carries a share link per employee. Karim sends his by WhatsApp, by email or posts it, and whoever applies through it is his referral. No form asks the candidate who told them.
Every open job carries a share link per employee. Karim sends his by WhatsApp, by email or posts it, and whoever applies through it is his referral. No form asks the candidate who told them.
Who may refer, what a referral earns and when it is paid are yours to set.
A referral is not a row in a list kept beside the pipeline. It is the candidate's card, the employee's file and the reward rule held together, so the stage the recruiter moves is the stage the referrer sees and the stage the reward waits for.
Copy it, send it, post it. Whoever applies through it is that employee's referral, without a "who told you about us" field to get wrong.
When a referred hire passes the trial period, create a payroll input for the referrer. Split it in two, cap it per year, vary it by job.
Who referred whom this year, and how far each one got. Points if you want them, a cap if you need one, and no catalogue of prizes to run.
Their referrals, the stage each one is at, and the day the reward falls due. Not the interview notes, not the other candidates.
One card: the candidate, the referrer and the stage
A referral is not a row in a list kept beside the pipeline. It is the candidate's card, the employee's file and the reward rule held together, so the stage the recruiter moves is the stage the referrer sees and the stage the reward waits for.
What adapts: what an open job asks of a candidate (a phone number, a CV, a portfolio), how the link travels, what a referral earns and when (at the hire, after the trial period, in two parts), who may refer, who confirms it, and where the reward lands. Two businesses can run Referrals and disagree on every one of those.
The job is an evening shift on a client site. The link travels by WhatsApp from the team leader's phone, the application is a name and a phone number, and the reward is €150.00 in two parts: €50.00 on the first payslip after the hire, €100.00 once the three-month trial period has passed. The site supervisor confirms the hire from the site.
The job is a senior developer with work to show. The link goes on LinkedIn, the application carries a CV and a repository, there are three interviews, and the reward is €1,000.00 after a six-month trial period, one reward per hire, to whoever shared the link first. The managing partner approves the reward before it reaches payroll.
Every candidate carries a source: the job board, the website, an agency, an employee's link. So "is the referral programme working" is a question the pipeline answers itself, per job and per month: how many hires came through a link, how long each source took from application to hire, and what each one cost against the reward you pay. The referral tool that only holds the referrals cannot compare them with anything, because the other sources live in another system. Source of hire, time to hire and referral share are saved views on these records, per job and per month, on a dashboard nobody had to build.
Léa is hired on 4 May with a three-month trial period. The rule reads both from her contract and writes down 4 August. On 4 August it asks the employee file one question, is she still here, and on yes it creates a payroll input of €500.00 for Karim on the August run. On no, it closes the referral as not earned and says why. Nobody keeps the date in a diary and nobody tells payroll. The rule is one you can read and change: the trigger, the check, the amount, the run it lands on; two parts, a cap or a different amount per job are edits, not requests. The amounts here are examples; what the payslip withholds from a referral bonus follows the rules your payroll applies ⟨to confirm⟩.
Who may refer, what a referral earns and when it is paid are yours to set.
See Recruitment.
The pipelineSee Employees.
The employee fileSee Enobase Email Marketing.
The message that shares itSee Payroll.
The payslipThis year's referrals: who referred whom, for which job, the stage each is at, the day each reward falls due, and what has reached payroll.
A share link per employee, on the open job
The referred candidate in the same pipeline as the others
The trial period read from the contract
The reward created on the payslip
Source of hire, beside the other sources
Time to live
| What you need | A spreadsheet | A referral tool | A suite module | Enobase |
|---|---|---|---|---|
| A share link per employee, on the open job | No | Yes, on a job synced from your hiring system | Yes | Yes, on the job the recruiter works |
| The referred candidate in the same pipeline as the others | No | Exported to your hiring system | Yes | Yes, with the referrer on the card |
| The trial period read from the contract | Typed in | Someone tells it | Sometimes | Yes, from the employee file |
| The reward created on the payslip | A note to the accountant | A note, or a payment made elsewhere | In its own payroll | Yes, a payroll input on the referrer's run |
| Source of hire, beside the other sources | By hand | Referrals only | Yes | Yes, on the pipeline's own dashboard |
| Time to live | A day | Weeks | Months | One week |
Yes. On its own it is an open job with a link per employee, the referrals that came through each link, and the reward each one earns. Turn Recruitment on and the referred candidate moves through the same pipeline as everyone else; turn Payroll on and the earned reward lands on the payslip instead of in a list you hand to your accountant.
30 minutes, your real events on screen. We'll show you exactly where Enobase saves your team time, no slides.
© 2026 Enobase, Inc. All rights reserved.