What you must record and why it matters
The fastest way to stay compliant with annual leave and absence in Poland is to standardise a workflow that captures every step: request, approval, calculation, payroll impact, and archiving. The Labour Code requires employers to maintain working-time and leave documentation and to present it during inspections. Your records should tie each absence to the employee’s schedule, employment basis, and current entitlement, so balances remain defensible if the Polish Labour Inspectorate asks for evidence.
Record types should include: annual leave; sick leave supported by medical certificates; parental, maternity, paternity, and childcare leave; unpaid leave; occasional/special leave; and training leave where applicable. For each event, store dates and hours, balance before/after, approver, legal basis, any certificate reference (for sick leave), ZUS communications, and subsequent corrections. Keep a clear link to the employee’s contract and working-time schedule for context.
A practical workflow: from request to payroll
Build a single flow you can repeat across teams. One: the employee submits a request (self‑service portal or paper) with proposed dates and type. Two: HR checks eligibility and remaining quota. Three: the system calculates hours against the person’s schedule and planned handovers. Four: the supervisor approves or proposes alternatives. Five: HR updates the roster and hands off to payroll. Six: the employee receives written confirmation. Seven: payroll applies pay rules. Eight: HR archives source documents and audit logs.
Handle exceptions upfront. For urgent or retroactive absences (e.g., sickness), accept initial notice by phone or email, then match the e‑certificate when it arrives. Set SLAs for approvals and corrections to avoid payroll cutoff issues. Reconcile monthly: balances, carryovers, and any manual adjustments. Quarterly, sample approvals and check documentation completeness. For leavers, finalise balances in writing and settle or schedule leave per the Code and internal policy.
Examples: full‑time, part‑time and mid‑year changes
Illustrative example only: a full‑time employee with a statutory entitlement tier (commonly 20 or 26 days, depending on aggregate service; always verify current rules) requests five days in July. Convert to hours based on the person’s daily schedule so irregular shifts are handled correctly. If Tuesday is a 10‑hour day and Friday 6 hours, deduct accordingly. Keep a pre‑ and post‑leave balance snapshot and log the approver and any handover notes.
Another example: a 0.5 FTE employee hired mid‑year. Pro‑rate the annual entitlement to hours according to FTE and, where applicable, monthly accrual rules for first‑time employment. If the contract changes to 0.75 FTE in September, recalculate the remaining quota from the change date. If leave is carried over, plan to grant it by the commonly referenced 30 September deadline in the following year, documenting both the reason and the grant date.
Document formats, retention and privacy
Paper or electronic files are acceptable when they are complete, legible and consistently organised. If you digitise, use controlled repositories with role‑based access, time‑stamped approvals, and immutable audit trails. Scan paper requests, keep the original numbering, and store supervisor approvals together with the request and the recalculated balance. Define standard absence codes, naming conventions and version control so payroll, HR and audit teams speak the same language.
Retention rules depend on the broader employee‑documentation regime and employment dates. Many employers align leave and working‑time records with the 10‑year post‑termination retention that applies to newer personnel files, while retaining older files longer if required; confirm your exact obligations. Apply GDPR principles: data minimisation, lawful basis (usually legal obligation), strict access, and timely disposal. Consider a DPIA if deploying new absence technology or large‑scale monitoring.
Coordinating sick leave and ZUS e‑certificates
In practice, sick leave hinges on e‑ZLA medical certificates submitted electronically by doctors to ZUS. Employers retrieve data via PUE ZUS and must reflect it in records and payroll. Typically, part of the sick‑pay period is borne by the employer, after which ZUS pays a benefit; thresholds and percentages can depend on age, situation and collective agreements, so map these carefully and verify current parameters before each payroll run.
Key failure modes include back‑dated certificates that miss the payroll cutoff, overlapping sick leave with approved vacation, and mismatched absence codes that distort balances. Set daily checks for new e‑ZLA entries, lock overlapping leave until resolved, and keep evidence of the employee’s immediate notice when required. Do not record medical diagnoses—only what is necessary for pay and absence processing. For long absences, schedule return‑to‑work steps and fitness‑for‑duty confirmations where appropriate.
Internal controls: a checklist and common pitfalls
A usable checklist: a single request channel; automated entitlement check; schedule‑aware hour calculation; supervisor approval with timestamp; employee confirmation; payroll mapping for each absence code; monthly balance reconciliation; quarterly sample audit of files; leaver balance settlement; carryover monitoring with alerts; access control review; retention and disposal log; exception register for retroactive changes; disaster‑recovery backup for electronic records.
Common mistakes include tracking annual leave in calendar days without reflecting variable daily hours; failing to grant carried‑over leave by the expected deadline; inconsistent coding between HR and payroll leading to pay errors; allowing managers to approve outside the system; ignoring contract or FTE changes when recalculating quotas; and keeping medical details beyond what is legally required. Another frequent gap is not training supervisors, resulting in informal approvals and missing audit trails.
Next steps: verify, automate, and get help when needed
Start with a gap analysis: list your absence categories, where requests come from, who approves, how hours are calculated, and how records flow to payroll and to archives. Verify current statutory expectations on reputable sources such as the Polish Labour Inspectorate, the Polish government’s family and labour services, and ZUS. Pilot the workflow in one unit for a quarter, then roll out with targeted supervisor training and a standing monthly reconciliation routine.
If your documentation is fragmented or you are onboarding new tools, consider light external support to validate legal bases, codes and retention schedules. Auranik’s Workforce Compliance Support (/poland/workforce-management) can help you translate legal requirements into practical controls without over‑engineering. Because specific obligations vary by contract type, tenure and individual circumstances, seek professional advice before finalising policies or making payroll‑relevant decisions.
Community content reflects individual experiences and should not be treated as legal, immigration, financial or government advice.
Know someone who may find this guide useful?