Python notebooks • DK / H3 ready output • Runs locally or in the cloud
Tailored to you
Not you to the system
Bridge between systems
DK / H3 unchanged
No risk
Pay only on success
No need to replace DK, H3, or your existing databases
Multiple data entry
Same data in 3-4 systems
Transcription errors
Especially with many employees
Manual validations
Hand-checked every month
With most solutions, the company must adapt to the software. Here it's the opposite.
I add the validation you're missing as a separate microservice alongside your system — lighter and cheaper than a vendor change request, because one change in a large system must stay backward-compatible for every other client, while a standalone service just needs a small edit.
The system is not locked into a fixed set of codes. If your existing scheduling system already uses its own codes, we only need to know what they mean.
Hospital
Restaurant
Factory
Codes can be in any language. New codes can be added without disrupting existing ones.
DK and H3 stay unchanged. Python notebooks, tailored to you, handle the calculations in between.
Shift files
Your own codes
Python Notebooks
Calculations tailored to you
DK / H3 import
Ready Excel
Fill / export
Excel with shifts, your codes
Upload + click
"Process" in system
Python notebooks
Calculate per your rules
Download result
Excel ready for DK/H3 import
The accountant only prepares the input and reviews — every validation runs automatically.
Each of these steps is designed around your rules — not a generic standard
For each employee, system automatically checks if sick leave limit was exceeded
Tailored: Sick day limits and handling of excess days are configured based on your specific union agreements
System divides each shift into: day, evening, night, holiday hours — results in columns DK/H3 already understands
Tailored: Evening/night thresholds, holiday lists, and pay multipliers configured to your agreements
Shift: 14:00–23:00
Settings: evening from 17:00
• 14:00–17:00 = 3h day
• 17:00–23:00 = 6h evening
System calculates required hours and compares with actual — result directly into DK/H3 import columns
Tailored: Overtime rate tiers and special rules for different employee groups are built in
Employee: 0.75 position | January 2024
Required = 21 × 0.75 × 8.25 ≈ 130h
Worked: 145h → Overtime: 15h @ your rate
Tailored: Eligibility and calculation follow your specific agreement
In same Excel — output ready for DK/H3:
| Employee ID | Start DateTime | End DateTime | Shift Type | Notes |
|---|---|---|---|---|
| EMP001 | 2024-01-15 08:00 | 2024-01-15 16:00 | REG | - |
| EMP001 | 2024-01-16 08:00 | 2024-01-16 16:00 | SICK | Sick leave |
| EMP002 | 2024-01-15 14:00 | 2024-01-15 23:00 | NIGHT | Night shift |
Shift codes: These are example codes. Your company defines its own codes — unlimited number, in any language. If your existing scheduling system already uses its own codes, we only need to know what they mean.
Excel, export, SQL — your own codes
Algorithms tailored specifically to your rules
Azure, SQL, Excel — whatever you already have
Excel in your payroll system's format
The same code — tailored to your rules — runs in all environments.
If scheduling system exports to Excel → use directly as input, with your own codes
Output format adapted to DK, H3, or any other payroll system's requirements
Can use only parts — e.g. only sick leave validation
Understanding current data flow, union agreements, shift codes, and formats your DK/H3 accepts
Algorithms adapted to your union agreements, shift codes, and specific needs — not the other way around
Testing on real data, verifying DK/H3 import, accounting team training
If we successfully automate your payroll processing, you pay. If not — you pay nothing.
Pay on success
No charge if it doesn't work
Zero implementation risk
Code doesn't touch DK or H3
You decide usage
Accounting chooses each period
Try the demo or get in touch — we can walk through how the algorithms are tailored to your union agreements, shift codes, and DK/H3
Phone: +354 782 3011 | Darius Domagala