Birthday & Loyalty Bonuses: Reward Employees with Extra PTO
A birthday day off or an anniversary bonus costs almost nothing but signals that you value people. Here's how to automate these perks.
There's a category of employee benefits that costs almost nothing but punches above its weight in morale: a paid day off on your birthday, and a bonus day if you actually used all your vacation last year. Small gestures that people remember.
BreezeLeave supports both. The birthday is a separate leave type the employee requests when their date approaches. The loyalty bonus is auto-credited on January 1 to people who used their full annual allocation last year. The two mechanisms are deliberately different, and the rest of this article explains why.
Birthday leave as a leave type
In BreezeLeave the birthday day off is a separate leave type, not a bonus credited to the annual balance. The employee submits a Birthday leave request on or near their birthday (the eligibility window is configurable). The request lands in the approval chain like any other leave type. Approved birthday leave does not deduct from the standard annual balance, and it bypasses the usual advance-notice rule, the same way sick leave does.
That keeps the math simple. The employee has their normal annual balance and a separate right to a birthday day. The balance breakdown never shows a phantom plus-one; the birthday day shows up as a request when the employee asks for it, not as a credit they might forget to use.
Common variations
Some companies let the employee take the birthday itself off. Others give them a window of a few days around the date. The eligibility window lives in the leave type configuration. HR can also auto-approve birthday requests through the rules engine so the employee does not wait for a manager to click.
Loyalty (full-usage) bonuses
Loyalty bonuses reward employees for using their full vacation allocation. The logic: employees who take all their vacation days are healthier, less likely to burn out, and more productive when they're working. So why not incentivize it?
BreezeLeave supports a "full usage bonus." If an employee uses all their allocated vacation days in a year, they earn bonus days the following year. The exact number is configurable.
This creates a positive cycle:
- Employee uses all 25 days this year
- They earn 1 to 2 bonus days next year
- More incentive to actually take vacation
- Healthier, more engaged employees
It's particularly effective in cultures where taking vacation is stigmatized or where employees tend to hoard days. The bonus reframes vacation as something to be used, not saved.
How the two mechanisms differ
The birthday day and the loyalty bonus are different mechanisms even though both reward the employee. Read the table once before turning either one on so the policy document matches the configuration.
| Mechanism | Trigger | How it appears | Configurable |
|---|---|---|---|
| Birthday leave | Employee submits a Birthday leave request near their date of birth | Approved leave, does not deduct from the annual balance | Eligibility window, auto-approval rule |
| Full-usage (loyalty) bonus | Employee used their full allocation last year (balance at or below zero on Dec 31) | Bonus days credited to next year's starting balance | On/off, bonus day count |
The full-usage bonus is auto-credited by a January 1 cron in BreezeLeave. The cron reads each employee's previous-year usage, marks the qualifying users, and adds the configured bonus day count to their starting balance for the new year. Birthday leave has no cron. It is a request the employee submits when their date of birth approaches.
How the loyalty bonus stacks with seniority accruals
Loyalty bonus days stack on top of seniority-based accruals. Here is what the starting balance of a 7-year employee who used their full allocation last year might look like:
- Base allocation (seniority rule): 25 days
- Carry-over from last year: 3 days
- Full-usage bonus (used all days last year): 1 day
- Total: 29 days
Each component is tracked separately and visible in the employee's balance breakdown. The birthday day does not appear in this list because it is not credited to the balance. The employee requests it separately when their birthday approaches, and it leaves the annual balance untouched.
For more on how carry-over interacts with the loyalty bonus, see our carry-over guide.
The ROI of bonus days
Let's do the math. A bonus vacation day costs you roughly one day's salary per employee. For a 50-person company with an average salary of €50,000, that's about €192 per person for a birthday day off. That's €9,600 per year for the whole company.
What does that buy you?
- Higher retention (employees cite PTO as a top-3 benefit in satisfaction surveys)
- Better employer branding ("we give you your birthday off" is a memorable perk)
- Reduced burnout from employees who actually use their vacation
- Zero ongoing administrative cost once it's automated
Compare that to the cost of replacing one employee (typically 6 to 9 months of salary). The math is not close.
Setting both up
Birthday leave and the loyalty bonus are configured in different places. Set them both once and the rest runs:
- Enable the Birthday leave type in Settings. Configure the eligibility window around the date of birth.
- Optionally add an auto-approval rule for Birthday in the rules engine so the request does not wait on a manager.
- Open the Vacation Rules section and add a Full-Usage Bonus rule. Set the day count.
- Confirm employee profiles have a date of birth on file. The Birthday leave type uses it to validate the request window.
- Save.
After setup, the loyalty bonus runs once a year on January 1 and credits qualifying employees' starting balance for the new year. Birthday leave runs whenever an employee submits the request near their date of birth.
The two rewards are different mechanisms. The loyalty bonus shows up in the balance on January 1; the birthday day shows up when the employee requests it. Both cost the company almost nothing once configured.
