Workforce management: From employee to payroll data
Workforce management is the process a business uses to connect employee information, staffing, communication, absence and working time. For a shift-based business, that process starts before the first shift is assigned. It ends when hours, additions and absence have been reviewed and can be handed over as an approved basis for payroll processing.
At Café Nord, the work starts when Sara joins as a barista. We follow her from the employee record and first shift to the approved hours passed to payroll.
Step 1: Create the employee and organisation
Café Nord creates Sara with contact details, employee number and start date. She is connected to the relevant department and location, given the role of barista and assigned an access level.
Keep role and access level separate. A role describes the work an employee performs. An access level defines what the person can see or change. The same source data later supports scheduling, targeted communication, time grouping and payroll exports.
From practice
Incomplete setup is often discovered only when a manager tries to schedule the new employee. Finish the employee record before planning begins.
Use the employee onboarding checklist, or explore employee management in Monoplan.
Step 2: Collect terms, contracts and documents
The employee profile should include the information used each day, such as employment start, how the employee is paid and contracted hours. Contracted hours are a reference for expected working time; they are not the same as scheduled or recorded hours.
Contracts and amendments can be sent for digital signature. Company policies can be shared with the relevant employees, while read receipts make it visible that a document has been opened. A receipt does not by itself guarantee that every legal requirement has been met.
Templates and digital workflows support administration but do not replace legal advice. The business remains responsible for matching each document to the employment relationship, collective agreement and applicable rules.
Read the practical guide to employee documents, contracts and read receipts.
Step 3: Gather the planning inputs
A good schedule starts with operational demand, not employee names. Café Nord first describes how many people and which roles are required across the day. The manager then matches demand with availability, approved leave, absence, contracted hours and role requirements.
The schedule needs demand, opening hours, role requirements, employee availability, approved absence, the intended distribution of hours and relevant working-time rules. Conflict checks can surface possible issues, but the business must still review contracts, collective agreements and legislation.
Planning is more reliable when decisions follow a fixed order. First cover the required number of people and roles. Then check known absence and availability. Next distribute hours with contracted hours and employment terms as reference points. Finally, review overlaps, rest periods and other conflicts before saving. Reversing that order can produce a schedule that looks balanced by hours but still lacks the required role at the busiest time.
From practice
A schedule can be free of overlaps and still be weak if it does not match actual staffing demand. Describe the need before assigning people.
Continue with leave and absence in the schedule, contracted hours, overtime and time off in lieu, or the hub for working-time rules in Denmark.
Step 4: Create and save the schedule
Templates can provide a starting point for a typical week, while open shifts expose demand that has not yet been assigned. The manager reviews overlaps, availability, role fit and total hours before applying a proposal. In Monoplan, saved changes are visible to the team immediately; there is no separate publishing step.
An automatically generated proposal is still a proposal. A manager should review the operational context before employees receive a shared version. The schedule records what is expected; it does not prove what was worked.
Follow the complete employee scheduling guide, explore employee scheduling software, and review the specialist guide to schedule notice in Denmark.
Step 5: Keep daily operations in sync
Once the schedule is saved, an employee may call in sick, accept an open shift or request a swap. If the final decision exists only in private messages, the business no longer has one reliable schedule.
Sara sees her current schedule in the employee app. Team chat delivers information through relevant channels. Shift swaps and open shifts follow an approval flow, so the shared schedule changes only after the responsible manager has decided.
From practice
Changes are usually not lost because nobody discussed them. They are lost because the final decision was never written back to the shared plan.
Read about shift swaps, open shifts and approvals.
Read our advice on team communication between shifts to help work messages and new routines reach the right colleagues.
Step 6: Record what actually happened
Employees record start and finish times during the working day. Breaks, absence, missing records and shifts that ended differently from the plan also need attention.
Keep scheduled and recorded time as separate values.
| Time record | What does it show? | Typical next action |
|---|---|---|
| Scheduled time | When the employee is expected to work | The employee sees the shift and the manager follows coverage |
| Recorded time | When the employee clocked in and out | Missing or unusual records are investigated |
| Effective time | Calculated working time after items such as breaks | The calculation is checked against rules and configuration |
| Approved time | Time accepted by the manager after review | The time can become part of the payroll basis |
These values should remain comparable without losing history. If a manager corrects a missing clock-out, it should still be clear what the employee originally recorded, what changed and which value was ultimately approved. That supports a better conversation with the employee and a more understandable audit trail before payroll.
Explore the employee time clock, learn how a digital time clock works, and review Danish working-time recording requirements.
Step 7: Resolve variances and approve hours
Before the period closes, Café Nord compares scheduled, recorded, effective and approved time. The manager checks missing clock events, unexpected extensions, breaks, absence, comments, additions and pay codes.
A practical review order is to find incomplete records, compare them with the current schedule, resolve material differences with the employee, check absence and additions, and finally approve the hours.
It helps to distinguish approval of an individual shift from closure of the full period. A shift can be approved once its variances are resolved. The period should close only when all employees have been reviewed, open questions have an owner, and the required additions and pay codes are present. A status such as “12 shifts awaiting approval” is more actionable than discovering the same gaps while creating the payroll export.
Café Nord can let department managers review shifts continuously while the payroll owner checks the overall period status. Both roles use the same data but make different decisions. The payroll owner no longer has to reconstruct daily operations from comments and message threads at month end.
Contracted hours provide a reference, but they do not by themselves determine overtime or time off in lieu. Those outcomes depend on employment terms and any collective agreement. If Café Nord maintains a time-off-in-lieu balance, the business therefore needs a clear rule for which approved hours affect it and who may change it.
The detailed workflow is in From schedule to approved payroll data.
Step 8: Produce approved payroll data
Once variances are resolved, the basis for payroll may include approved hours, relevant pay codes and additions, absence, employee numbers and department information.
A payroll report is a reviewable overview. A payroll file is a structured export for a particular payroll system or a generic format. Payroll calculation and payment then take place in the payroll system. Monoplan does not calculate or pay wages.
A useful payroll basis is therefore more than a downloadable file. The business should be able to understand where each value came from and why it is included. Before export, check that employee numbers match the payroll system, departments and pay codes are mapped as intended, absence has the correct status, and no unresolved time variances remain. On the first export, or after a configuration change, sample employees across hourly pay, fixed salary, absence and additions as a practical final control.
The handover should also be repeatable. If the same question returns every month, an owner, status or rule is probably missing earlier in the journey. Improve the process at the source instead of adding another manual spreadsheet beside it. The purpose is not to remove professional review, but to move it to the point where a variance is easiest to understand.
Depending on the configuration, data can be handed over to Danløn, DataLøn, Zenegy or as generic PDF/CSV output. Explore payroll reports and approved payroll data and the available integrations and export paths.
Once the period has been reviewed, the payroll data is ready for the payroll system. It began as an employee record, employment terms and a schedule. It has now been recorded, explained and approved.
Assign ownership at every handover
A connected system cannot compensate for unclear responsibility. Before Café Nord digitises the workflow, it decides who owns each handover: who completes an employee profile, who approves leave, who follows up on a missing clock event, and who may close the period before export.
Each stage needs three clear answers:
- Which information is authoritative? The saved schedule is the shared expectation, while approved time is the outcome after review.
- Who must act? A request without an assigned approver is simply another inbox. Tie the department, location or process to a responsible manager role.
- When is the stage complete? Created, sent, recorded and approved are different statuses. The next stage should begin only when the relevant status has been reached.
This distinction also makes exceptions easier to handle. Sara may exist as an employee while her contract workflow is still incomplete. She may have clocked out while the recorded time is still awaiting approval. The system should expose those differences instead of hiding them behind one generic completed state.
