Employee leave and B2B contractor unavailability in one team
Many Polish companies have employees on an employment contract (UoP) and B2B contractors in the same team. To a manager, both are simply away sometimes. To the company they are two different things — and the system should tell them apart too.
Checked against the product:
Why it is not the same absence
An employee on an employment contract is entitled to paid annual leave. How much follows from the law and their length of service, and the employer keeps a record of what has been used.
A B2B contractor is not an employee. They have no annual leave under the Labour Code — when and for how long they are unavailable follows from their contract and what they agree with the team. Calling it “B2B leave” is convenient, but it mixes two regimes: it suggests an entitlement the contract may not grant, and it puts contractors on the same record as employees.
That is why Tivero calls it planned unavailability for B2B contractors. It is the same calendar and the same request for the manager, but a separate policy, separate limits and a separate export.
What managers and HR need to see
A manager plans the team’s work, so they need one view of availability: who is away next week, whatever their contract. HR needs something else — a reliable leave balance for employees and a month-end summary that leaves contractors out.
- one team calendar with everyone’s absences, according to permissions;
- leave balances only where they make sense — for employees, or for contractors whose contract sets a limit;
- an export split into UoP and B2B, so only employee data goes to payroll.
How to set up policies for both groups
The simplest set-up is one policy per type of contract. For employees, a policy with an annual leave allowance, a balance and manager approval. For B2B contractors, a planned-unavailability policy: no limit if the contract sets none, or a limit if the parties agreed one.
The second question is approval. Employee leave usually needs the manager’s consent. For a contractor, letting the team know is sometimes enough — then the type can skip approval and the unavailability appears in the calendar straight away.
How Tivero does it
When you create a policy you start from the “UoP — 20 days”, “UoP — 26 days” or “B2B — planned unavailability” template and adapt it to your company. The allowance can be the same for everyone, set per person, or none at all for unavailability without a pool.
Everyone appears in one calendar. Private types, such as sick leave, show to the team as “Absence”, without details. CSV/XLSX exports can cover everyone, only UoP or only B2B.
What Tivero does not do
- The policy templates follow Polish practice but are not legal advice — check the allowance that applies in your company.
- Tivero does not work out the leave allowance from length of service and does not accrue leave over the year; balances are annual, with manual adjustments.
- Tivero does not handle pay or “paid days” for contractors — it records unavailability and limits, not money.
- Tivero does not assess whether a B2B contract is set up correctly.
Step-by-step instructions
Detailed instructions are in the Tivero Help Center: