From time report to payroll data without manual gaps
Payroll documentation in personal assistance and LSS (Swedish law for support to people with disabilities) rarely fails in one big step. Problems arise in the small gaps: late time reports, schedule changes without comments, unmapped OB rules. Here is a practical walkthrough of the flow from hours worked to wages – with a checklist and traceability every step of the way.
From time report to payroll data without manual gaps
Payroll documentation in personal assistance and LSS (Swedish law for support to people with disabilities) rarely fails in one big step. Problems occur more often in small gaps: a late time report, a schedule change without a comment, an OB (unsocial hours) rule that is not mapped, or an approval that occurs before all deviations are finalized. Therefore, the flow from hours worked to wages needs to be both practical and traceable.
The goal is simple: the right person should receive the right compensation for the right period, and the documentation must simultaneously serve the organization's follow-up, payroll administration, and external accounting.
Where the payroll data begins: schedule, time report, and deviation
A sustainable payroll flow does not start in the payroll program. It starts in the schedule. The schedule shows planned staffing, while the time report shows what was actually performed. The difference between the two is the deviation, and it is often there that the payroll documentation either becomes clear or starts requiring manual inquiries.
In personal assistance, there is also a specific link between hours worked and assistance allowance. Försäkringskassan states that the assistant must report performed assistance every month, certify the information, and submit it to the employer; the employer then submits the time report to Försäkringskassan so that compensation can be paid out according to Försäkringskassan's information for personal assistants.
For payroll, it is therefore not enough to simply total the hours. The documentation also needs to show what type of time it covers: regular time, OB, on-call (jour), standby (beredskap), additional time (mertid), overtime, absence, sick pay, or other compensation. Each type of compensation needs to have a clear path from the time report to the payroll code.
Common gaps between assistance work and payroll processing
The most common gaps arise when the operations, the approval role, and the payroll function work with different versions of the truth. A shift may be approved in the schedule but not time-reported. A time report may be submitted but lack approval. A payment may be correct according to the agreement but lack a payroll code in the export.
Late time reports after the approval deadline are a particularly sensitive situation. In such cases, the organization needs to know who owns the cutoff, when the period may be reopened, and if a new approval is required. If this is handled informally, the payroll administrator often ends up making practical judgments that actually belong in the organization's control flow.
Another recurring gap concerns multiple recipients of documentation. Payroll needs documentation per employee and payroll period. Försäkringskassan and the municipality may require different fields, different period boundaries, or different summaries. In our customer flows, we see that quality increases when these documents are reconciled before handover, not after the payroll run has already started.
Checklist: Control points before time becomes payroll data
Last checked: June 18, 2026. The checklist below is intended as a practical order of work before payroll processing. It does not replace agreements, law, or local routines, but makes it clear when the documentation is ready and when it should be stopped.
Control point | Verification method | Stop condition | Recommendation |
|---|---|---|---|
1. Time report is complete | Compare planned shifts, performed shifts, and submitted time reports per period. | Stop if a shift lacks a time report, person, or certification. | Ready? Yes/No. Missing value: investigate before export. |
2. Schedule deviation is explained | Check changed times, swapped shifts, cancelled shifts, and extra shifts against comments or cases. | Stop if the deviation affects pay but lacks a reason. | Assign ownership to the responsible manager or coordinator. |
3. Approval is done after complete data | Check approval log, approval role, and timestamp. | Stop if approval was done before a late change or if a period was opened without new approval. | Use a clear cutoff and reopening routine. |
4. Compensation types are mapped | Test OB, jour, beredskap, mertid, and overtime against payroll codes in export. | Stop if payroll code, date, or period is missing. | For unknown export templates: Contact sales/system administrator. |
5. Jour, overtime, and mertid are traceable | Total per employee and compare with working hours records. | Stop if totals are missing or cannot be audited. | Save traceable calculations, not just a grand total. |
6. Absence is reconciled | Compare absence against schedule, time report, and impact on pay. | Stop if absence affects pay without a documented reason. | Ensure absence code and period are correct. |
7. Data for external reporting is separated | Check which fields are required for payroll, Försäkringskassan, and the municipality. | Stop if the same export is used despite different period boundaries or field requirements. | Reconcile before handover. |
8. The export is tested | Import a test file or validate export against the payroll program before the live run. | Stop if rounding, personal identity numbers, payroll codes, or dates change during import. | Test new rules before the first live period. |
9. The period is locked and traceable | Check locking, change log, and responsible handover. | Stop if anyone can change time after export without new verification. | Lock only when payroll, approvals, and data are reconciled. |
Special requirements in personal assistance and LSS
LSS sets requirements for good quality, self-determination, and that the quality of operations is systematically and continuously developed and secured according to the Act concerning Support and Service for Persons with Certain Functional Impairments. For payroll documentation, this means the routine must not only be administratively efficient. It must also withstand scrutiny and support a way of working where the intervention can be followed up without unnecessary manual interpretations.
Försäkringskassan's regulations state that employers or clients must provide information about the assistant's working hours on the form Tidsredovisning assistansersättning or via an approved e-service, and the regulations also distinguish between assistance time, waiting time, and standby when calculating assistance allowance in FKFS 2016:4 on assistance allowance. This is an important reminder: the same shift may need to be described in different ways depending on whether the recipient is payroll, Försäkringskassan, or the municipality.
On the employer side, registered employers must report paid compensation, deducted tax, and employer contributions in the employer declaration for each reporting period according to Skatteverket. Therefore, payroll data should be completed, reconciled, and locked before information is passed on to payroll and further reporting.
When system support and integration make the biggest difference
System support provides the most benefit when it reduces the number of handovers. If the schedule, time report, approval, and payroll export are linked, it becomes easier to see what is ready, what has changed, and what needs to be fixed before the payroll run. It's not just about automation, but about the division of responsibility.
A cohesive way of working should show who registers, who approves, who corrects, and who exports. It should also specify which rules are hard stops and which are warnings. For organizations that want to gather scheduling, time, documentation, and integrations in the same flow, an overview of modules and system support for assistance and LSS can be a natural next step in internal mapping.
Patterns from practical payroll flows
In our work with assistance and LSS flows, a clear pattern emerges: payroll documentation becomes more stable when control is close to the event. The person who knows the operations should own the deviation. The person who approves should own the authorization. Payroll should own the payroll run, reasonableness checks, and reporting, but should not have to interpret unclear schedule changes after the fact.
Employers must also be able to track on-call time, overtime, and mertid; ATL (Swedish Working Hours Act, Arbetstidslagen) states that the employer must keep records of these times and that employees and relevant union organizations have the right to access the records according to ATL. Therefore, these values should not only exist as payroll codes at the end of the process but should be inspectable even before export.
The practical goal is for payroll administration to receive finished documentation, not a troubleshooting task. When the period, time report, deviation, approval, and compensation type are checked in the correct order, the risk of incorrect pay, late corrections, and double manual tracking decreases.