Time tracking for payroll
Plan, clock in, calculate, approve and export hours to the payroll or ERP system you already use. Every line can be traced to a rule, and a past period can be recalculated.
Most payroll teams know the week before payday: chasing missing clock-outs, checking supplements by hand and retyping hours from one system into another. Payroll-ready time tracking moves that work upstream. In VRS, the hours that are approved are the hours that get paid, and the period can be replayed later to show exactly why each line was paid the way it was. Book a demo to see it on your own week.
What "payroll-ready" means, and what it doesn't
Payroll-ready time tracking means hours arrive in payroll already classified, calculated and approved, so nobody has to fix or retype them. Each clocked hour is calculated under your versioned pay rules (hour types, supplements, time windows), approved in a multi-level workflow, and handed to the payroll or ERP system you already use.
VRS prepares the payroll-ready result. Your payroll system still runs payroll and applies the money. VRS does not replace it.
Where payroll corrections come from
Most corrections start long before payroll sees the data. The usual sources are practical, not dramatic:
Missing or wrong clock-outs that nobody notices until the period closes.
The gap between plan and actual: a shift ran long, someone swapped, a site changed.
Supplements applied by hand: evenings, nights, weekends and public holidays worked out in a spreadsheet.
Rule changes mid-period: a new agreement or local variation that only some lines picked up.
Retyping between systems: every copy-paste between the clock and payroll is another chance for an error.
A payroll-ready flow deals with each of these before approval, not after payday. For a step-by-step version, read how to reduce payroll corrections.
From clock-in to payroll: the five steps
1. Plan
Plan the week by person or by work category. Rotations and rest are visible on the board, and plan rules you configure can warn or block. Timebank caps can warn while the week is still being planned, early enough to fix it. See plan rules and rotations and timebank and leave balances.
2. Clock in
Employees clock in with one tap on their own phone, or on a shared tablet that runs as a browser kiosk. Geofencing can start or add context to a punch; it does not block it. See clock in on phone or kiosk.
3. Calculate
Every hour is classified under versioned rules: hour types, supplements, rate agreements and time windows. Each calculated line traces back to the rule, and the rule version, that produced it. The calculation is a rules engine, not AI.
4. Approve
Managers review results and approve in a multi-level path, and an external approver can be invited by link. When a decision is recorded, the policy version that governed it is frozen with the decision. See multi-level approvals.
5. Export
The approved, released period goes to payroll as quantities per wage-type code for a legal entity and a period. Nothing is retyped. Where you invoice, billing lines can come from the same result.
Rules you can read, lines you can trace
Your agreement is expressed as versioned, verifiable calculation rules. Readable work-rule profiles and a rules studio hold the hour types, supplements, rate agreements and time windows that apply to each group. When someone asks "why was this paid this way?", the answer is on the line: the rule, and the version of it, that produced the quantity. VRS does not ship a fixed national agreement; the rules are configured for you, including local variations. See versioned pay rules.
One shift, followed end to end
An illustrative example. Nordhavn Drift AS and Nora Berg are fictitious, not a customer. Quantities are hours, no money is shown, and the wage-type codes are labels the company chose.
Assumptions: the rules effective on the work date say a day up to 7 h 30 min is ordinary time and minutes past that are overtime; hours from 21:00 to 06:00 also carry an evening supplement. The payroll system accepts correction postings. Breaks are left out so the arithmetic stays visible.
Clock-in and calculation
Nora clocks in at 18:00 on Thursday 14 May 2026 and out at 02:00 on Friday. The work date is Thursday, the clock-in day, and the record is not split at midnight. The rules effective on Thursday classify the 8 hours:
Wage-type code | What it is | Quantity |
|---|---|---|
ORDINARY | First 7 h 30 min | 7 h 30 min |
OVERTIME | The rest of the span | 30 min |
EVENING | 21:00 to 02:00 | 5 h 00 min |
Each line traces to the rule and rule version that produced it. The evening line is a supplement quantity, not a second copy of the shift.
Approval and first export
The approval policy version in force for Nora on that date is frozen onto the approval. Once approved, the lines go out in the May run for Nordhavn Drift AS. The first export is a full send of the approved quantities, and each line is marked as exported. Retrying the same run does not send the hours twice.
A correction after export
The end time was wrong: the real end was 00:30. Saving the edit does not overwrite the exported lines. The day goes back for a new approval, and recalculation uses the Thursday rule versions, not a newer version published later. The filed May run is not edited. The next export sends only the difference:
Code | Already sent | Now | This export |
|---|---|---|---|
ORDINARY | 7 h 30 min | 6 h 30 min | −1 h 00 min |
OVERTIME | 30 min | 0 | −30 min |
EVENING | 5 h 00 min | 3 h 30 min | −1 h 30 min |
If the company's rules had changed in June, a replay of 14 May would still use the 14 May versions.
When something is found after approval
Correction exports send the difference
The first export sends the approved quantities. If a line is corrected after that export, the next export sends the difference for that line, not the whole period again, when the payroll system accepts a correction. If it does not, the change stays in VRS and nothing is sent. A retry of the same export does not send the lines a second time.
Replay a past period
Approvals freeze the policy snapshot they were taken under, and calculation reads the rule version effective on the work date. A past pay period can be replayed under exactly the rules that applied, even after the rules have changed. That is what makes a payslip provable.
An audit trail you don't have to assemble
Every governed change is written to an append-only audit trail: who changed what, when, and the before and after. See security and audit.
Keep your payroll system
You don't have to switch payroll system. VRS prepares clean, classified hours and hands them to the payroll or ERP you already run.
Microsoft Dynamics 365 Business Central and Dynamics 365 Finance & Operations: native integrations. VRS sends and removes approved hours and fetches customers, projects, tasks and hour types, with a result for every line, so operations and finance are not reconciled by hand. See Business Central and Finance & Operations.
Visma: payroll-ready hours with pay rules, leave types and overtime supplements applied before handoff, set up for your Visma configuration. See Visma.
Unimicro and SpareBank 1 Regnskap: the SpareBank 1 Regnskap connection rides the Unimicro integration. See Unimicro.
A payroll-ready file: a ready run can be downloaded as a file of quantities per payroll code, with no live connection required.
Open REST API: OAuth 2.0 and scoped clients under the caller's identity.
VRS has worked with the Microsoft ERP stack for more than ten years, from Dynamics NAV to Business Central and Finance & Operations. See all integrations.
Payroll and billing from the same hour
An approved hour can produce a payroll line and a billing line from the same result. Billing can also differ from pay, cover something that is not pay, or be left off for time that is paid but not billed. Contractor settlement is kept separate from statutory payroll.
Where AI fits, and where it doesn't
The calculation engine is not AI. The VRS assistant, on web and as Ask VRS on mobile, reads only what the signed-in person can already see. It explains hours, flags and rules, and it can propose a change, such as a correction, that a person must confirm. It cannot change sealed pay. See VRS AI.
What customers say
"Before VRS, payroll corrections were a monthly nightmare. Now the data is cleaner, and we spend far less time fixing errors before payday." Agnete Bjelland, HR Manager, Odda Technology
"Implementation was surprisingly fast. Our team picked it up quickly, and within two weeks everyone was using the app without any prompting from management." Jonny Selsvik, Project Manager, Høyer
Read the Odda Technology story and the Høyer story.
See it on your own week
In a focused 30-minute walkthrough we go through your operating model, your agreements and the payroll or ERP system you run today. Book a demo.
Frequently asked questions
- What does payroll-ready time tracking mean?
Payroll-ready time tracking means hours arrive in payroll already classified, calculated and approved, so nobody has to fix or retype them. In VRS, each clocked hour is calculated under the customer's versioned pay rules (hour types, supplements, time windows), approved in a multi-level workflow, and exported to the payroll or ERP system the company already uses, such as Visma, Unimicro or Microsoft Dynamics 365 Business Central. VRS prepares the payroll-ready result; the payroll system still runs payroll.

- How do you stop payroll corrections before payday?
Most payroll corrections start upstream: a missing clock-out, a supplement applied by hand, a rule changed mid-period, or hours retyped between systems. VRS catches these before payday by calculating every line under readable, versioned rules, flagging exceptions for approval, and exporting approved lines without manual re-entry. If a line is corrected after it was exported, the next export sends the difference for that line, where the payroll system accepts corrections, instead of the whole period again.

- Can you re-run a past pay period and get the same result?
Yes, in VRS. When hours are approved, VRS records which rule and policy versions governed that decision, so a past period can be replayed under exactly the rules that applied at the time, even after the rules have changed. Every calculated line traces back to a rule, and an append-only audit trail records who changed what, when and why. The calculation is rules-based, not AI.

- Do we have to change payroll system?
No. VRS hands payroll-ready hours to the system you already run: native integrations with Microsoft Dynamics 365 Business Central and Dynamics 365 Finance & Operations, Visma, and Unimicro (including SpareBank 1 Regnskap), or a payroll-ready file of quantities per payroll code.

- Is AI calculating our pay?
No. Pay is calculated by versioned rules. The assistant explains hours and flags and can propose a correction, but a person confirms every change, and sealed pay cannot be altered by the model.
