TL;DRIn 2026, mid-market Nordic companies have access to native integrations between expense management, time tracking, and payroll systems that eliminate most manual re-entry. But setting them up correctly requires mapping four distinct data flows, choosing the right architecture for your payroll system, and designing around Denmark's compliance rules — including the 2026 mileage rate of DKK 3.94/km (first 20,000 km) and per diem meal allowance of DKK 625/day. This guide covers each decision point.
Connecting time tracking and expense management to payroll sounds straightforward. The data exists. The systems exist. The question is why the connection between them is so often a patchwork of manual exports, monthly spreadsheet rituals, and reimbursements that arrive one payroll cycle too late.
The answer is that the integration involves four different data flows, each with its own compliance requirements, each needing to reach the right system at the right time. Getting it right means making deliberate choices about architecture, routing, and compliance rules — not just turning on a connector and hoping the data arrives.
Here is how to build it properly.
Before configuring any integration, you need to answer one foundational question: which expenses go through payroll, and which go through accounts payable?
This is not a technology choice. It is a compliance and process design choice, and getting it wrong creates tax and audit problems that are difficult to unwind.
Route through payroll: mileage and per diem allowances. These are tax-regulated reimbursements that appear on the employee's payslip and are reported to SKAT via the employer's monthly e-indkomst filing. They belong in the payroll run. The payroll system knows how to handle them as tax-free compensation line items, and your external auditor will expect to see them there.
Route through AP: variable, receipt-based expenses. Hotel bills, flight tickets, restaurant meals with receipts, client entertainment — these are reimbursed faster and with cleaner tax treatment as direct bank transfers through accounts payable. They do not need to appear on the payslip. They generate GL journal entries in your ERP, not payroll postings. For most employees, this means reimbursement arrives in days rather than weeks, without waiting for the monthly payroll run.
The mistake many organisations make is routing everything through payroll because it feels simpler — one payment to the employee. In practice, this mixes taxable and tax-free items on the same payslip line, complicates VAT reclaim, and creates a reimbursement dependency on a monthly payroll cycle for expenses that could have been paid the next business day.
Four integration architectures exist in the Nordic market. The decision is straightforward once you know what your payroll system is.
Native connectors — always the first choice. If your expense tool has a pre-built, maintained connector to your payroll provider, use it. For companies running Acubiz alongside Visma DataLøn, Danløn, Lessor, or SD Worx, native API connectors are available and require no engineering resource. They handle schema differences between systems, enforce the approval gate (only approved records transfer), and update automatically when either vendor changes their API. The setup is a matter of hours, not months.
iPaaS middleware (Zapier, Make, Frends) is a viable option for companies whose systems are not yet natively connected. For European companies specifically, Frends is recommended as an EU-data-residency-compliant integration platform with strong ERP connectors. The limitation: iPaaS tools cannot natively handle the effective-dated payroll records and retroactive adjustments that Danish payroll compliance requires. You will need to build custom logic for edge cases, which erodes the no-code benefit.
Custom API integration gives you complete data fidelity when built correctly, but a single-country deployment takes 3–6 months and requires permanent engineering maintenance. Only viable if you have dedicated IT capacity and a non-standard payroll system not covered by native connectors.
Unified API middleware (Merge, Finch, Kombo) provides a clean abstraction layer that works well for analytics. For write-path integrations to Nordic payroll providers — DataLøn, Danløn, Lessor — coverage is thin, and canonical schemas lose country-specific payroll fields. Not recommended as a primary integration path for Danish payroll.
Tax-free mileage and per diem allowances are set annually by Skatterådet. For 2026, the official rates (SKM2025.725.SKTST) are:
Mileage (kørselsgodtgørelse):
Per diem (rejsegodtgørelse):
These rates apply only when the employee uses their own private vehicle (not a company car) and is on a business trip to a temporary work location for a minimum of 24 hours including an overnight stay. Tax-free standard allowances apply for up to 12 months at the same temporary work location. From month 13, all reimbursements at that location must be backed by documented receipts — the flat-rate allowance becomes taxable income if continued beyond the limit.
Your expense system must track two things the payroll system cannot: cumulative km per employee per calendar year (to apply the correct mileage tier), and rolling 12-month presence per temporary work location (to flag approaching per diem limits). These calculations belong in the expense tool before data reaches payroll — not in the payroll system after the fact.
Most integration failures trace back to configuration decisions made at setup that were never documented or tested. Work through these before you go live:
Employee ID alignment. Audit whether your expense system and payroll system use the same employee identifier. If not, build the translation table now. Choose a stable key — typically the company-wide employee number or CPR number — and verify it covers rehired employees and name changes.
Earnings code mapping. Map every expense category in your expense tool to a specific earnings or deduction code in the payroll system. Mileage at the standard rate, mileage above 20,000 km, per diem meals, per diem lodging, and taxable reimbursements must all map to distinct codes. This is the most common source of integration failure — unmapped codes either post to the wrong account or drop silently.
Approval gate configuration. Confirm that only records with status "Approved" transfer to payroll. Never configure an integration to transfer submitted but unapproved records — this bypasses your expense policy and creates payroll entries that managers have not reviewed.
GL account mapping. Every expense type needs a GL account. For multi-entity companies: entity + cost centre per line. Configure the integration to post aggregated journal entries per payroll run per entity — not per-employee-per-component, which generates thousands of GL lines and overwhelms most ERP systems.
SEPA timing. The bank file for salary payments must be submitted 1–2 business days before the payment date. Build this buffer into your payroll run schedule and automate file submission — do not rely on someone remembering to trigger it manually.
Three-way reconciliation check. Before each payroll run: verify expense system totals match payroll import totals, GL debits and credits balance, and bank payment matches net pay. Any discrepancy should block the run — not be resolved post-hoc.
These are the failure modes that appear most often in practice — and that are entirely preventable if you know to look for them:
The 20,000 km tier ignored. Paying DKK 3.94/km for all mileage regardless of cumulative total. Once an employee exceeds 20,000 km driven for work in the calendar year, only DKK 2.28/km is tax-free; excess is taxable income. Systems that do not track the annual total will overpay tax-free allowances and create a SKAT liability. High-mileage employees — typically field sales or service roles — hit this threshold more often than finance teams realise.
VAT reclaim lost through payroll routing. When variable expenses are processed as payroll items rather than AP items, the VAT categorisation is often wrong or lost. The organisation loses the input VAT reclaim entitlement on those expenses — a problem typically caught only at the annual tax review, when correction is expensive.
The terminated employee posting. An employee leaves. Their cost centre is deactivated. Their final expense report, submitted after departure and approved by the line manager, posts against the deactivated cost centre — requiring a manual GL correction during a busy close period. Fix: include terminated employee handling in your integration specification, not as an afterthought.
GL posting to the wrong fiscal period. An expense approved on the last day of a month, but where the payroll run posts to the following period. Define which date governs the GL posting — check date (payment date) is the standard — and confirm this with finance before go-live. Changes after the first live payroll run are retroactively complex.
The common thread across all of these is that they are configuration decisions, not technology limitations. The tools exist to handle them correctly. The question is whether someone has made the explicit decision about how each scenario should behave — before the first payroll run goes live.
Should expense reimbursements go through payroll or a direct bank transfer?
It depends on the type of expense. Mileage and per diem allowances are structurally tied to the payroll run — they appear on the payslip and are reported to SKAT via e-indkomst. These should route through payroll. Variable, receipt-based expenses such as hotel bills and transport should go through a direct AP payment instead. Direct AP payment is faster for employees, cleaner for tax treatment, and easier to reconcile. Mixing the two paths on the same payslip line creates compliance complexity.
What are the official mileage reimbursement rates in Denmark for 2026?
The Skatterådet-approved rates for 2026 (SKM2025.725.SKTST) are DKK 3.94 per kilometre for the first 20,000 km driven for work per calendar year, and DKK 2.28 per kilometre above 20,000 km. The bicycle and moped rate is DKK 0.64 per km. These apply only when the employee uses their own private vehicle, not a company car. Your expense system must track cumulative km per employee per calendar year to apply the correct rate tier automatically.
Which payroll systems does Acubiz integrate with natively?
Acubiz has native API connectors to Visma DataLøn, Danløn, Lessor, and SD Worx — the four most widely used payroll systems in Danish and Nordic mid-market companies. For organisations running Microsoft Dynamics 365 Business Central or Finance and Operations, SAP, or SAP ByDesign, Acubiz also provides direct ERP integrations. Native connectors are always preferable to custom builds: they are maintained by the vendor, require no internal engineering resource, and handle API schema updates automatically.
What is the 12-month rule for tax-free per diem allowances in Denmark?
Under Danish tax rules, an employee can receive tax-free standard per diem allowances for up to 12 months at the same temporary work location. From month 13 onwards, reimbursements at that location must be backed by documented receipts — flat-rate allowances become taxable income. Your expense system should track the rolling 12-month window per employee per work location and flag when the limit is approaching, so you can switch the employee to a receipt-based workflow before SKAT exposure arises.