• About us
Log inDemo

Referrals · Human Resources

Hire the people your people already know. Pay the bonus where the payslip is.

From the shared job to the payslip line, in five steps.

The open job is in your people's hands

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.

From the shared job to the payslip line, in five steps.

  1. 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.

  2. Léa applies through Karim's link and is a candidate in Recruitment like any other, in the same stages, screened by the same recruiter. One thing differs: the card says who referred her, and the referral is open from that minute.

  3. The card moves to Hired, the contract is signed, and the employee file is created from the candidate. The referral reads the hire date and the trial period from that contract and writes down the day the reward falls due.

  4. On 4 August the rule asks one question of the employee file: is Léa still here. On yes, the referral is earned. On no, it is closed with the reason, and nobody had to remember the date.

  5. The bonus is a payroll input on Karim's August pay, labelled with the hire it rewards. Not a note to the accountant, not a payment made somewhere else.

The referral, the link, the rule, the board, and what the referrer sees.

Who may refer, what a referral earns and when it is paid are yours to set.

Book a demo

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.

A link per employee, per job

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.

The reward rule, in one line you can read

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.

The board, without the shop

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.

What the referrer sees

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.

Book a demo

The same referral, for a cleaning contractor and for a web agency.

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.

See it on your own data

A cleaning contractor hiring through its own staff

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.

A web agency hiring developers

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.

Where the hires come from.

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.

See it on your own data

The rule that pays it, running.

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⟩.

See it on your own data

What the referral feeds and reads.

Who may refer, what a referral earns and when it is paid are yours to set.

See it on your own data

The pipeline. The referred candidate is a card in the Recruitment pipeline, moved by the recruiter like any other card. The referral reads the stage; it never asks for it.

See Recruitment.

The pipeline. The referred candidate is a card in the Recruitment pipeline, moved by the recruiter like any other card. The referral reads the stage; it never asks for it.

The employee file. The referrer is an employee, the hire becomes one, and the trial period the rule waits for is on the contract, not typed into the referral.

See Employees.

The employee file. The referrer is an employee, the hire becomes one, and the trial period the rule waits for is on the contract, not typed into the referral.

The message that shares it. The open job goes to the whole team as an email from your template, each recipient with their own link in it, held for a person to approve before it goes.

See Enobase Email Marketing.

The message that shares it. The open job goes to the whole team as an email from your template, each recipient with their own link in it, held for a person to approve before it goes.

The payslip. The earned reward is a payroll input on the referrer's next run, labelled with the hire it rewards, and the payroll lead sees it before the run closes.

See Payroll.

The payslip. The earned reward is a payroll input on the referrer's next run, labelled with the hire it rewards, and the payroll lead sees it before the run closes.

This is the room.

This 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.

See it with your own open jobs

The referral tool you would otherwise buy syncs the job in, syncs the candidate out and hands the bonus to payroll as a note.

  • A share link per employee, on the open job

    A spreadsheet
    No
    A referral tool
    Yes, on a job synced from your hiring system
    A suite module
    Yes
    Enobase
    Yes, on the job the recruiter works
  • The referred candidate in the same pipeline as the others

    A spreadsheet
    No
    A referral tool
    Exported to your hiring system
    A suite module
    Yes
    Enobase
    Yes, with the referrer on the card
  • The trial period read from the contract

    A spreadsheet
    Typed in
    A referral tool
    Someone tells it
    A suite module
    Sometimes
    Enobase
    Yes, from the employee file
  • The reward created on the payslip

    A spreadsheet
    A note to the accountant
    A referral tool
    A note, or a payment made elsewhere
    A suite module
    In its own payroll
    Enobase
    Yes, a payroll input on the referrer's run
  • Source of hire, beside the other sources

    A spreadsheet
    By hand
    A referral tool
    Referrals only
    A suite module
    Yes
    Enobase
    Yes, on the pipeline's own dashboard
  • Time to live

    A spreadsheet
    A day
    A referral tool
    Weeks
    A suite module
    Months
    Enobase
    One week
What you needA spreadsheetA referral toolA suite moduleEnobase
A share link per employee, on the open jobNoYes, on a job synced from your hiring systemYesYes, on the job the recruiter works
The referred candidate in the same pipeline as the othersNoExported to your hiring systemYesYes, with the referrer on the card
The trial period read from the contractTyped inSomeone tells itSometimesYes, from the employee file
The reward created on the payslipA note to the accountantA note, or a payment made elsewhereIn its own payrollYes, a payroll input on the referrer's run
Source of hire, beside the other sourcesBy handReferrals onlyYesYes, on the pipeline's own dashboard
Time to liveA dayWeeksMonthsOne week

Questions about Referrals

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.

RecruitmentThe pipeline the referred candidate moves through, like every other candidate.ExploreEmployeesThe employee who referred, the employee who was hired, and the contract the trial period is read from.ExploreEnobase Email MarketingThe open job sent to the whole team, each with their own link in it.Explore

See Enobase on your own open jobs.

Book a demoGet access
Solutions
  • Finance
  • Quotes
  • E-Invoicing
  • HR & Payroll
Industries
  • Catering
  • Construction Company
  • Private Equity
  • All industries
Platform
  • Data Model
  • Knowledge & Collaboration
  • AI & Workflows
  • Analytics
  • Integrations
Company
  • About us
  • Hiring policy
  • Press & Brand
  • Download
  • Privacy
  • Terms
  • Subprocessors

© 2025 Enobase, Inc. All rights reserved.

  • LinkedIn
  • X
  • GitHub
marketing/widget-experience-detail
widget: marketing/widget-experience-detail family: widget kind: record frame: stack subject: one referral with its candidate, its referrer, its stage and what it will earn, and the activity that got it there move: the stage chip moving from Screening to Interview, the activity row appearing beneath neighbour: widget-experience-detail · same one-record layout with an owner, a schedule and a status; a referral instead of a workshop content: REF-2026-0044 · Candidate: Léa Dumont, CND-2026-0318 · Job: JOB-2026-0027 Field technician · Referred by: Karim Haddad, Tue 24 Mar, by link · Stage: Interview, Thu 2 Apr · Reward: €500.00, after a 3-month trial period · Recruiter: Thomas Peeters · activity: Applied 26 Mar · Screening call 30 Mar · Interview booked 2 Apr props: the candidate, the referrer, the stage, the reward not: the recruiter's pipeline static: no tags: modules=referrals,recruitment · categories=human-resources · capabilities=data-model · industries= · sections=bento,zoom,split,two-up · reusable=yes
Open asset editor
marketing/widget-actions
with Copy my link, Send by email, Share on LinkedIn
Open asset editor
marketing/asset-workflow-node
with trigger "Trial period ended" · if "A referral is on the hire" → "Payroll input €500.00 for the referrer, next run" · else "Close the referral"
Open asset editor
marketing/asset-invoice-itemized
kind: record, sticker; scope "2026 to date"; rows Karim Haddad 3 referred, 2 hired · Sofie Claes 2 referred, 1 hired · Mathilde Renard 1 referred, 1 hired · Thomas Peeters 1 referred, 0 hired
Open asset editor
marketing/widget-experience-detail
kind: record, sticker; "My referrals", Karim Haddad; Léa Dumont, Field technician, Hired 4 May, trial period passed 4 Aug · 3 referred, 2 hired, 1 in progress · "€500.00 on your August payslip"
Open asset editor
marketing/widget-experience-detail
widget: marketing/widget-experience-detail family: widget kind: record frame: sticker subject: one business's version of the unit of work, its own fields visible move: the fields that differ from the other case landing last, marked neighbour: widget-case-card · reused; the content is this case content: Cleaning contractor · Job: Cleaning agent, evenings, Brussels North · Link: WhatsApp · Application: name, phone · Reward: €150.00 in two parts (€50.00 at hire, €100.00 after 3 months) · Trial period: 3 months · Who may refer: any employee · Confirmed by: site supervisor · Lands on: the payslip · marked fields: Application, Reward, Confirmed by props: the business label, the object, the marked fields not: a filled operational record; this is the shape one business gave it static: yes
Open asset editor
marketing/widget-experience-detail
widget: marketing/widget-experience-detail family: widget kind: record frame: sticker subject: one business's version of the unit of work, its own fields visible move: the fields that differ from the other case landing last, marked neighbour: widget-case-card · reused; the content is this case content: Web agency · Job: Senior developer, remote · Link: LinkedIn · Application: CV, repository link · Stages: Screening, Technical, Partner interview · Reward: €1,000.00 after 6 months · Trial period: 6 months · One reward per hire: first link wins · Approved by: managing partner · Lands on: the payslip · marked fields: Stages, Trial period, Approved by props: the business label, the object, the marked fields not: a filled operational record; this is the shape one business gave it static: yes
Open asset editor
marketing/asset-bar-chart-orders
widget: marketing/asset-bar-chart-orders family: widget kind: chart frame: stack subject: this year's hires by source, per job, with the time each source took move: the bars filling per job in four tones, then the time-to-hire figures landing beside them neighbour: asset-client-exposure · same split-bar vocabulary; hires by source instead of money by state, one job per row instead of one client content: 2026 to date, 9 hires; rows Field technician 4 (2 referral, 1 job board, 1 website) · Dispatcher 2 (1 referral, 1 agency) · Support agent 3 (1 referral, 2 job board); beside: median days from application to hire, referral 31, agency 39, job board 47, website 52; footer "Referral share: 4 of 9" props: the period, the jobs, the sources not: a leaderboard of employees static: yes tags: modules=referrals,recruitment · categories=human-resources · capabilities=analytics · industries= · sections=split,bento,grid,zoom · reusable=yes
Open asset editor
marketing/widget-workflow-run
widget: marketing/widget-workflow-run family: widget kind: run frame: sticker subject: one referral reward rule executing from the hire to the payroll input, step by step move: each step checking itself off, the payroll step spinning, the last one stating the referral earned neighbour: widget-workflow-run · reused; the steps are this rule's content: rule "Referral reward" on REF-2026-0044; steps: Hired: Léa Dumont, Mon 4 May 2026, JOB-2026-0027 (done) · Trial period from the contract: 3 months, ends Tue 4 Aug (done) · 4 Aug: employed today? yes (done) · Payroll input: Referral bonus €500.00, Karim Haddad, August run (running) · Referral closed as Earned (pending) props: the referral, the trial period, the amount not: the rule's definition (that is the workflow node in the feature cells) static: no
Open asset editor
marketing/widget-experience-detail
with CND-2026-0318 Léa Dumont at Offer, Tue 14 Apr, "Referred by Karim Haddad"
Open asset editor
marketing/asset-status-roll
with Léa Dumont: Candidate, 26 Mar · Hired, 4 May · Trial period passed, 4 Aug
Open asset editor
marketing/widget-mail-approval
with "New open job: Field technician" to all employees, "{your link}" in the text, approver Thomas Peeters
Open asset editor
marketing/widget-experience-detail
with the August line, "1 input from rules" in the run's header
Open asset editor
marketing/screen-events-table
screen: marketing/screen-events-table family: screen view: list nav: Inbox, AI Assistant, Dashboards, Employees, Open jobs, Candidates, Referrals (active), Time Off, Payroll, Documents subject: the referral programme as rows by referral with the candidate, the referrer, the job, the stage, the due date and the reward's state content: filter "2026, all jobs"; columns Referral, Candidate, Referred by, Job, Stage, Reward due, Reward; rows REF-2026-0044 Léa Dumont, Karim Haddad, Field technician, Hired, 4 Aug, €500.00 On payslip · REF-2026-0041, Sofie Claes, Support agent, Hired, 12 Oct, €500.00 Waiting · REF-2026-0039, Mathilde Renard, Dispatcher, Hired, 1 Sep, €500.00 Earned · REF-2026-0037, Karim Haddad, Field technician, Interview, to be set, €500.00 Open · REF-2026-0033, Thomas Peeters, Support agent, Not retained, none, none; footer: 7 referrals, 4 hired, €1,500.00 earned this year, €500.00 waiting; candidate names hidden on rows other than the first, per the referrer's access rule neighbour: screen-hiring-board · that one is the recruiter's pipeline by stage; this is the programme read across jobs, with the reward's state as a column tags: modules=referrals · categories=human-resources · capabilities=analytics,access · industries= · sections=full-screen,swipe,spotlight · reusable=yes
Open asset editor

© 2026 Enobase, Inc. All rights reserved.

Log in
All systems normal