Skip to content
Book a demo

What is in the Fortnox (PAXML) export

Payroll & Reporting 3 min readUpdated 5 days ago

The PAXML 2.0 file CLVR builds for Fortnox payroll, and the fields each transaction carries.

When you open a month on the Payroll reports page, select Download, and choose Fortnox, CLVR builds a PAXML 2.0 file: the standard Swedish payroll XML, made to be imported into Fortnox rather than opened and read by hand. This article explains what is inside that file so you know exactly what Fortnox receives.

The shape of the file

The Fortnox download is a single XML file with three parts:

  • A header that identifies your company and the export.
  • A payroll transactions section (lönetransaktioner), one line per expense.
  • An employees section (personal), one entry per employee in the file.

You normally never read the XML yourself. If you want a human-readable view of the same numbers first, download the Excel format instead, then import the Fortnox file when you are ready.

What the header carries

The header tells Fortnox which company and which export this is. It includes:

  • Your company name.
  • Your organisation number (digits only, no dash).
  • The export date and time.
  • The producing program, recorded as CLVR Benefits.

What each transaction carries

Every approved expense that belongs in the month becomes one transaction line. Each line holds:

  • The employee number, used as the employee reference.
  • The employee's personnummer, written as 12 digits with no dash.
  • A pay code (lönkod): one of UTLÄGG for an expense report, FÖRSKOTT for a benefit purchase, or AVDRAG for an overused-allowance deduction.
  • A pay code (löneart) for your payroll setup, when one is configured.
  • A short description, for example the benefit category or benefit name.
  • The expense date.
  • The amount (belopp), written with two decimals.
Note.

The löneart (the company-specific payroll code) only appears when one is configured for that benefit. If it is blank, the line still exports without it. See why a payroll report shows the wrong löneart if a code looks unexpected.

Which expenses are included

The Fortnox file holds the same approved expenses as the other formats for that month, with a few inclusion rules:

  • Approved expense reports and benefit purchases that draw on the benefit allowance are included.
  • A benefit purchase paid entirely from salary is left out, because there is nothing to reimburse through this file.
  • Lines that come to zero or a negative amount are dropped, with one deliberate exception below.
  • An overused-allowance deduction is included as a negative amount (an AVDRAG), so the over-spend is recovered through payroll.

For why a specific expense you expected is not in the file, see why an expense is missing from the payroll export.

The employees section

Transactions are grouped per employee, and every employee who appears in the file gets one entry in the employees section with their first name, last name, and personnummer. This lets Fortnox match each transaction to the right person on import. If a personnummer or employee number is blank, see why personnummer or employee number is blank in an export.

Troubleshooting

  • Fortnox rejected the file. Confirm you imported the Fortnox download, not the Excel or Flex HRM file. Only the Fortnox option produces the PAXML that Fortnox reads.
  • An employee is missing a personnummer in Fortnox. The personnummer comes from the employee's profile. Set it, then download the month again.
  • An expense I expected is not there. Only approved expenses for that month are included, and salary-paid purchases and zero-amount lines are excluded by design. See why an expense is missing from the payroll export.
  • I want to read the numbers first. Download the Excel format for a readable layout, then download Fortnox for the import.
14-day onboarding · live by next payroll

Not ready to apply?
Let's just chat.

30 minutes, no deck, no discovery call. We'll walk you through the real product with real numbers from your industry. If it fits, great. If it doesn't, we'll tell you who does.

  • See the real product
    Live app, your data shape, not a Loom recording.
  • Your numbers, not a template
    We'll model the BIK savings off your headcount and salary bands.
  • No sales theatre
    If we're not a fit, we'll point you at someone who is.
Talk to a founder

See what CLVR Benefits can do for your team.

Share a few details and we'll come prepared with numbers from your industry. Usually back within one business day.

By submitting this form, you agree to our Privacy Policy and Terms of Service.