Payroll

Komma owns gross.Your engineowns net.

We build and validate the gross pay lines, then hand them over. Errors surface before the run rather than in the reconciliation afterwards — and you do not change payroll provider to use Komma.

What is stopping the pay run?
One blocking issue. Validation also shows 3 warnings, 3 changes are awaiting a decision, and 5 registrations are still pending. Gross to transfer is 1,087,618.80 kr across 3 pay periods.
Draft · open the blocking issue
Nothing is sent until the run is approvedApprove
Book a demoSee a pay run

Pay run

Validation before the run, not reconciliation after it.

A pay run opens against a period, pulls the registrations already valorized by Workforce, and validates every line before anything is approved. Blocking errors stop the run; warnings point at the employee and field they came from.

  1. 1Gross to transfer for all 3 pay periods, split into unchanged, changed and variable pay.
  2. 3Employee pension is part of gross. The engine withholds it.
Pay run for Komma ApS across 3 pay periods: gross to transfer, a warning about 5 pending registrations, an eight-step checklist and the payroll group summary123
  1. 2Five registrations still pending: approve them on the manager’s behalf, or send without them.
  2. KarmaOne blocking issue, found in the eight checks, stops the run before your payroll engine sees it.

The pay run

From the first change to the payroll system.

Scroll through a run the way a payroll officer works it: changes decided, hours approved, the approval flow signed, and the approved gross handed over.

Step 1

Every change since the last run, decided line by line.

Changes
Changes since June in the pay run: before and now for each salary change, new hire and reimbursement, with Approve and Reject per line and the effect on the run total123
  1. 1Before and now, side by side, for every change since June.
  2. 2Approve and it joins this run. Reject and it stays out.
  3. 3A raise from 1 August waits for the August run.

Step 2

Hours and supplements, approved before they are paid.

Hours and supplements
Pending approval in the pay run: hours, supplements, absence and holiday that no manager has approved yet, each with what it adds if approved and Approve, Decline or Delete, above the approved time lines by pay code123
  1. 1Hours and absence no manager has approved yet: approve, decline or delete them here.
  2. 2Anything undecided stays out of every total. The run can still be sent; it rolls to the next one.
  3. 3Approved hours by pay code, with a check that each rate matches the policy.

Step 3

The right people approve, in the right order.

Approval flow
Approval flow in three levels: level 1 where all must approve and 2 of 3 have signed, level 2 with a stand-in for an approver on holiday, and level 3 where any one approver is enough123
  1. 1Level 1: all must approve. Two have signed; the third is on holiday with no stand-in, so the level waits.
  2. 2When an approver is away, the stand-in signs instead.
  3. 3Level 3 opens after level 2, and any one approver is enough.

Step 4

Approved gross, handed to your payroll system.

Transfer
Send to payroll: 1,093,423.30 kr gross to transfer with hours, holiday and absence days and mileage, the gross per employee for each payroll group, and a button that sends 2 groups to Zenegy while 2 are blocked123
  1. 1The gross to transfer: salaries, hours and supplements, mileage and travel.
  2. 2Gross per employee and payroll group. Zenegy handles tax, net pay and payslips.
  3. 3One click sends the 2 groups that are ready. The 2 blocked groups are held back, not sent.

Payroll

From forecast to handoff.

Every legal entity, every payroll group, and the trail each run leaves behind. Once approved, the lines are locked and cannot drift.

Payroll

Every legal entity and the next paydays on one page.

Overview
Payroll overview: a card per legal entity and a forecast of upcoming paydays per payroll group123
  1. 1One card per legal entity: runs, people and what needs attention.
  2. 2A new pay run opens against a period.
  3. 3The next paydays forecast, with the reason for every change.

Payroll

Every person’s line: fixed pay, hours, supplements, mileage and absence.

Payroll report
Payroll report for Komma ApS across 3 pay periods, with amounts hidden per employee and a note that 4,549.50 kr in one-offs awaits approval123
  1. 1Amounts stay hidden until you choose to reveal them.
  2. 2One-offs awaiting approval are kept out of every total.
  3. 3Pending amounts sit on the person’s line, outside every total.

Payroll

Who ran it and who approved it, for every payroll group, every month.

Activity
Payroll activity: the latest run and the run history per payroll group, with who ran and approved it123
  1. 1Each payroll group names its engine. Here: Zenegy.
  2. 2July is in review, and you can see who ran it.
  3. 3Month by month: who approved it, and when it was confirmed.

Structure

Pay groups, codes and bands that outlive a single run.

Pay components and codes are configured once and reused. Groups decide who is paid on which cycle and under which agreement, and pay transparency reads the bands directly from the job structure in Organisation.

  • Pay groups with their own cycle, agreement and approvers
  • Pay components and codes with history, so old runs stay explainable
  • Pay-band placement per level, reported without a separate exercise
  • EU Pay Transparency reporting from the live structure
Pay transparency under EU directive 2023/970 for Komma ApS: reporting entity and size tier, unadjusted and adjusted pay gap, median salary for men and women, gender distribution and salary development123
  1. 1Reported per legal entity. Under 100 employees, reporting is still voluntary.
  2. 2Unadjusted and adjusted pay gap, across comparable roles and bands.
  3. 3The gap per department, one click from its people.

What is in it

Payroll, in full.

Pay runsOpen, validate, approve and hand over — with every step on the activity log.
Pre-run validationBlocking and warning states that point at the record that caused them.
Pay codesComponents and codes with history, so a run from last year still explains itself.
Pay groupsCycle, agreement and approvers per group.
Pay transparencyEU directive reporting straight off the job structure.
Six enginesZenegy, Danløn, Dataløn, Visma, Lessor and Intect. Keep the one you have — it still calculates net pay, tax and payslips.

See it on your own data.

A 30-minute walkthrough with someone who knows the module — and your org structure, not a demo tenant.

Book a demoSee pricing