Receives from payroll run
Payroll
Payroll line per employee, location and contract type
Payroll lines per employee, location and contract type — with surcharges, deductions and absence impact.
System architecture
Four operational modules. One data model. No conversion steps.
ONA is composed of four operational modules that share the same data model: scheduling, time tracking, payroll and integrations. Every shift, clock-in and contract rule lands in the payroll run without conversion.
Scheduling
Shift · checks · availability
← Shift · availability
Integrations
POS revenue · sync interval
← POS revenue · sync interval
Time tracking
Punch · breaks · planned/actual
← Punch · planned/actual
Payroll
Trial run · surcharges · deductions
→ Payroll line · surcharge · deduction
Data modelEmployee · shift · contract · surcharge · payroll line
Data model
Employee · shift · contract · surcharge · payroll line
- Scheduling← Input
Shift · checks · availability
Shift · availability
- Integrations← Input
POS revenue · sync interval
POS revenue · sync interval
- Time tracking← Input
Punch · breaks · planned/actual
Punch · planned/actual
- Payroll→ Output
Trial run · surcharges · deductions
Payroll line · surcharge · deduction
From the clock-in to the payroll line.
Six processing steps in the same system. Each step reads from and writes to the same data model.
Phase 1 · Capture
- 01
Input
Shifts, clock-ins, contracts and absences are captured in operations.
- 02
Validation
Labour-law limits, contract-type rules and break logic are checked at write time.
- 03
Surcharges & rules
Surcharge type, allowances and absence impact are applied to each shift.
Artifact · 01
Lena R. · Late shift · 16–22 · Service
Artifact · 02
Labor-law checked · break detected
Artifact · 03
+ night surcharge · + Sunday surcharge
Phase 2 · Payroll run
- 04
Trial run
Gross, surcharges and deductions are calculated and shown per employee.
- 05
Finalization
After review the payroll run is locked in. Payroll lines are traceable down to the individual shift.
- 06
Output
Reports, payout and optional export interfaces for external payroll providers.
Artifact · 04
Gross €286 · surcharges €143
Artifact · 05
Payroll run finalized
Artifact · 06
PDF · payout · optional export
Four modules. One data model.
Every module reads from and writes to the same data model. No conversion, no re-entry between stages.
Scheduling
Availability, contracted hours and labour-law limits are checked while the plan is created.
- Shift templates
- Preferred days
- Shift swap
- Mobile publish
Integrations
SumUp, Lightspeed G-Series, Lightspeed K-Series. POS revenue is synchronized hourly and daily.
- SumUp
- Lightspeed G-Series
- Lightspeed K-Series
- Manual entry
ONA data model · shared schema
Time tracking
Clock-ins run by code on the on-site tablet or through the mobile app. Both write to the same data model as scheduling and payroll.
- On-site tablet
- Mobile app
- Break logic
- Target/actual
Payroll
Surcharges, allowances and absence impact are derived from the clocked-in shift. 32 German contract types pre-configured.
- 32 contract types
- Automatic surcharges
- Absence impact
- Tax classes
Three outputs from the same run.
What ONA produces from the locked-in payroll run — directly from the data model, without a second system.
Source
Payroll run · Week 16 · Berlin Mitte
47 employees · finalized
Total gross: €14,220
Receives from payroll run
Reporting
Staff cost ratio, hour mix and compliance status
Staff cost ratio, total hours, contract mix and compliance status per location and period.
Receives from payroll run
Payout
Payout amount per employee
Payout and statutory reporting are part of the payroll process. Bank transfers can be connected via finAPI depending on setup.
Book a demo
One payroll run. Your setup. 30 minutes.
No generic demo. We configure ONA around your locations, contracts and POS connection — and run trial payroll in the system.
- Locations and contract types as input
- Trial payroll live in the system
- Response within one business day
- No contract commitment