If your company runs Polish payroll and HR through Workday or SAP, you’re likely managing global data well. Headcount, compensation, org structure, performance – all consolidated in one system. What you may not know is what happens at the point of Polish employment execution: the moment a contract must be signed, a document package assembled, and a compliant record created that can withstand a Polish Labor Inspectorate audit.
That’s where global HRIS systems stop. And where Polish compliance risk begins.
What Workday and SAP do – and what they don’t
Global HRIS platforms like Workday and SAP SuccessFactors are built for scale across jurisdictions. They handle core HR functions exceptionally well: employee records, compensation management, benefits, org hierarchy, and reporting. They integrate with payroll processors and provide data visibility across regions.
What they are not built for is local employment execution in jurisdictions with specific statutory requirements. Poland is one of those jurisdictions.
| Function | Workday / SAP | What Polish law requires |
|---|---|---|
| Employee contract generation | Data storage only | Locally compliant document with version-controlled template, specific clauses per Polish Labour Code |
| Electronic signature | Varies by integration | Qualified Electronic Signature (QES) per eIDAS + art. 781 KC — equivalent to handwritten signature |
| Document package (day-1) | Not automated | 12–15 documents: contract, GDPR consent, PIT-2, BHP referral, work regulations acknowledgement, bank details |
| Audit trail per document | Global, not PIP-ready | Full decision trail: who approved, which version, when — retrievable within 5 minutes for PIP inspection |
| Foreign worker compliance | Not supported | Passport upload, work permit validation, mixed signature path (no PESEL / no Profil Zaufany) |
| Template updates after law change | Manual / IT project | Automatic update required — Polish employment law changes multiple times per year |
Sources: Pergamin implementation data; Polish Labour Code (Kodeks Pracy); eIDAS Regulation EU 910/2014; PIP audit requirements.
The core issue:
Workday and SAP manage HR data. They do not manage Polish employment execution. The gap between the two is where compliance risk lives.
What Polish employment execution actually requires
Polish labour law is one of the most document-intensive employment frameworks in the EU. A single hire triggers a mandatory sequence of actions that must be completed before or on day one – with specific form requirements, signature standards, and archiving obligations.
The mandatory document package for one hire
- Employment contract – written form required (QES or wet ink signature per art. 29 § 2 KP)
- Information on employment conditions – mandatory since 2023 amendment (art. 29¹ KP)
- GDPR consent and information clause
- PIT-2 tax declaration
- BHP (health and safety) referral for pre-employment medical examination
- Acknowledgement of work regulations and remuneration policy
- Bank account declaration
- Additional documents for foreign nationals: passport copy, work permit, residence permit
This package must be assembled, signed with the correct signature type, and archived with a full audit trail – before the employee’s first day of work. For companies hiring at scale (50 – 500+ people per year), the manual version of this process generates tens of thousands of individual operations annually.
Key legal changes in 2025–2026 that expand the gap
- 27 January 2026: 12 HR actions now permitted in electronic form (e-mail). Employment contracts and terminations – still require written form (QES).
- 1 December 2025: Foreign worker hiring – fee increased from PLN 100 to PLN 400 per declaration; passport with translation required before first working day.
- 5 March 2026: New requirement to notify the Labour Office within 7 days of hiring any foreign national – including holders of the Karta Polaka.
- 2026: PIP (State Labour Inspectorate) expanded powers – digital audits, cross-system data matching with ZUS and KAS.
The Polish state is digitalising its inspection capabilities faster than most companies are digitalising their HR processes. Every law change widens the compliance gap for organisations relying on manual or HRIS-native workflows. |
Where global companies get caught – three common failure points
Failure point 1: Signature type mismatch
Many global HRIS implementations use simple e-signature tools (DocuSign, Adobe Sign) for employment contracts in Poland. These provide electronic signatures in “document form” – legally valid for freelance agreements and B2B contracts, but not for employment contracts under Polish Labour Code. Only a Qualified Electronic Signature (QES) is equivalent to a handwritten signature for employment purposes. Using the wrong signature type means the contract is not in written form – a violation of art. 29 § 2 KP.
Risk: contracts signed with non-QES tools may be challenged as not meeting the written form requirement. PIP inspectors have flagged this in audits. |
Failure point 2: Incomplete document package
Global HRIS systems track that a contract exists. They do not verify that the full statutory package has been assembled, signed, and archived. HR teams working within Workday or SAP often complete parts of the package outside the system – in Word files, shared drives, or email – with no central visibility or completeness check. At the point of a PIP inspection, missing a single mandatory document can result in a fine of up to PLN 30,000 per violation.
Failure point 3: No audit trail for PIP
Polish labour inspectors have the right to request, on-site and immediately, the full decision trail for any employee’s documentation: who prepared it, who approved it, which version was signed, and when. A global audit log from Workday or SAP does not satisfy this requirement – it tracks system events, not employment document decisions. Companies without a localised audit trail cannot reconstruct this information quickly enough to avoid complications during inspection.
How to close the gap – the local compliance layer model
The most effective architecture for global companies with Polish operations is not replacing Workday or SAP – it is adding a local compliance layer that handles Polish employment execution and feeds data back to the global HRIS.
| Layer | System | Function |
|---|---|---|
| Global HRIS | Workday / SAP SuccessFactors | Employee records, org structure, compensation, global reporting |
| Local payroll | Enova365 / Comarch / Teta HR | Polish payroll calculation, ZUS declarations, PIT returns |
| Local compliance | Pergamin | Polish document generation, QES, audit trail, PIP-ready archiving |
| Integration layer | API / SFTP / native connectors | Bidirectional data sync: Pergamin ↔ HRIS ↔ payroll |
Pergamin acts as the Polish employment execution layer: it generates locally compliant document packages, manages QES (including for employees without a Profil Zaufany or PESEL – the typical profile for foreign workers), maintains a full audit trail, and integrates with Enova365, Comarch, and Teta HR for payroll data sync.
What this looks like in practice
- A hire is initiated in Workday – employee data flows to Pergamin via API
- Pergamin generates the full statutory document package (12–15 documents) using version-controlled, legally current templates
- Employee receives signing link – QES via mObywatel (Polish nationals) or one-time QES without PESEL (foreign workers)
- Signed documents are archived with full audit trail in Pergamin and synced back to Workday / e-teczka
- At any point, HR or compliance can retrieve the complete decision trail for any document within minutes
Result: global HRIS retains its role as the system of record. Polish compliance is handled locally, to Polish legal standards, with full auditability. |
Four questions to assess your current compliance gap
1: Are employment contracts in Poland signed with a Qualified Electronic Signature (QES per eIDAS), or with a simpler e-signature tool?
If the latter – your contracts may not meet the written form requirement under Polish Labour Code.
2: Can your team retrieve the complete document package and approval trail for any Polish employee within 5 minutes?
If not – you are not audit-ready for a PIP inspection.
3: How are document templates updated after Polish law changes?
If the answer involves an IT project or manual Word file edits – there is likely a version control gap.
4: How does your process handle foreign workers without a PESEL or Profil Zaufany?
If there is no defined path – this is a compliance gap for every non-Polish hire.
If any of these answers is “I’m not sure” – the gap exists. The question is whether it will be found by your compliance team or by a PIP inspector. |
Summary
- Workday and SAP do not close Polish employment compliance. They manage HR data – not Polish execution.
- The gap covers four areas: document generation, QES signatures, complete document packages, and PIP-ready audit trails.
- The solution is not replacing global HRIS – it is adding a local compliance layer that handles Polish execution and integrates bidirectionally with global systems.
Next step: Answer the four questions in section 5. If any answer is uncertain, a compliance gap assessment will identify specific exposure points before a PIP inspection does. |
Want to assess your Polish HR compliance gap?
Pergamin offers a free compliance gap assessment for global companies with Polish operations: document process review, signature type audit, and integration mapping with your current HRIS. Based on data from 140+ implementations in Poland, including companies running Workday and SAP as their global HRIS.
