Academy / Fortnox
Get started with Fortnox in ComplyComp
Connect your company, keep employee records up to date and add final payroll amounts. This guide follows the workflow in Import & sync.
Updated 27 October 2026
1. Connect the right company
Your company needs Fortnox Payroll (Lön) and a Fortnox integration licence. A Fortnox system administrator approves the connection. In ComplyComp, you need the owner or admin role to manage it.
- Open Import & sync Integrations Activate Fortnox.
- Select Connect Fortnox and sign in to Fortnox. Choose the company to connect and review the consent.
- Back in ComplyComp, check the company name and organisation number, then select Confirm company.
ComplyComp checks the company identity and blocks the connection if the organisation number does not match. One ComplyComp workspace connects to one Fortnox company. The Fortnox tab remains available after disconnection so you can read the history and reconnect.
Open integrations2. Choose how to sync
The API sync retrieves employees, job titles, employment details and contracted monthly pay where the source supports the selected month. Contracted pay stays separate from actual paid earnings.
After confirming the company, an owner/admin can enable nightly sync. It runs at 03:00 Stockholm time and processes the current and two preceding calendar months. It is off by default.
For a different month, use the month selector under Manual sync. Owners, admins and analysts can start a sync and import data. Viewers can read status and history.
Normal sync preserves manual corrections and imported actual earnings. Select Overwrite manual changes only when you explicitly want to replace protected fields.
3. Export final payroll from Fortnox
A successful API sync does not mean the reporting data is complete. Use a payroll export reconciled against final payslips for actual gross amounts. Fortnox menu names below are shown in Swedish.
- In Fortnox, open Lön Rapporter Lönestatistik and select the correct payroll year.
- Select all relevant employees, including people who left during the period. Check the periods and selection.
- Use Exportera for the year's payroll transactions or Exportera .csv for the selected statistics.
- Reconcile amounts against final payslips or the gross payroll report before confirming the export is complete.
Do not include both detail rows and their summary rows. An employee entirely absent from the export is not automatically treated as receiving zero pay. A confirmed zero payment needs an explicit zero row.
4. Review and import
Open Import finalized Fortnox payroll in the Fortnox tab and choose the CSV file. The preview shows how columns and pay codes will be used.
- Summa is the row total. The Fortnox column Belopp may contain a unit price. When both are present, Summa is used for the gross amount.
- The payroll period is not always the payment month. For period labels such as 2025.M.12, enter the actual payment month from the final payslips. If payment was made in January, select January even if the payroll period is December.
- Classify every pay code as actual gross basic pay, actual gross complementary pay or exclude. Review local pay codes, benefits, deductions and reimbursements with the payroll team.
- Negative actual amounts may be needed for corrections and deductions. Hours and contracted monthly pay cannot be negative.
The import is blocked if a pay code or payment month is unmapped. Review the preview by employee and payment month, and confirm that the file covers final payroll for the selected people and months. Only then are missing pay classes within those monthly rows treated as confirmed zero.
If monthly rows already exist, you must approve replacing them. Overwriting manual corrections is a separate setting. Files are limited to 20,000 rows and 4 MB; split larger datasets by month.
5. Complete the reporting data
ComplyComp does not infer gender from names or identity numbers, and does not treat contracted hours as actual hours worked.
- Add gender information through the company's usual employee and import controls.
- Provide the reporting categories the employer has established for equal work or work of equal value.
- Count only hours verified as actual hours worked, without double counting. Missing hours can be added using Add actual worked hours after importing payroll amounts.
Blank values mean information is missing. Enter an explicit 0 for confirmed zero. The Payroll data completeness card shows remaining gaps for the selected month. Also check the annual-data review before publishing.
6. Understand status and logs
Connection, latest run and reporting data completeness describe different things. A connected company can have a failed run or be missing actual payroll amounts.
The Fortnox tab's Logs show syncs, payroll imports, connections, disconnections and setting changes. History brings together events from all data sources. Filter by source, event type or status.
- Queued
- The run is waiting to start.
- Running
- The run is processing. Status updates automatically.
- Completed
- The operation finished. Its result shows what was processed; it does not confirm that the report is complete.
- Failed
- Open the details for the next action. Previously imported data is retained during temporary connection failures.
The details show timestamps and a reference you can share with support. Older events may not include a user, record count or period.
Common problems
The company needs confirmation
Review the organisation number and confirm the correct company before importing or enabling nightly sync.
Reconnection is required
Check Fortnox licences and the administrator's permissions. Select Reconnect Fortnox and approve the connection again if consent has been withdrawn.
Another import is running
Read the operation history and let the active run finish before trying again.
An employee ID is missing or duplicated
Sync employee records and check that the export's employee ID matches one unique employee. Preserve any leading zeros.
The data source cannot be reached
Try again later. If the problem persists, give support the run reference.
Disconnect Fortnox
An owner/admin selects Disconnect in the Fortnox tab. This disables automatic sync and removes ComplyComp's locally stored access credentials. Earlier imports and customer history are retained.
To revoke the service account's consent in Fortnox as well, the administrator must do so under Hantera integrationer in Fortnox. A new connection then requires new approval.
Official Fortnox sources
- Fortnox: payroll statistics report
- Fortnox: pricing models and integration licences
- Fortnox: service-account access
This guide describes ComplyComp's workflow. Menu names and available Fortnox features may depend on the company's licences. The linked Fortnox support articles are in Swedish.