Hedda and Fortnox. Nothing entered twice.

If you use Fortnox payroll, connect it to Hedda. Employees come in exactly as they stand in payroll, and what happens in Hedda goes back to Fortnox without anyone typing it in again.

Book a demo All features

Employees and organisation in sync

The connection works both ways. When you connect Fortnox, employees come in. After that Hedda leads, and changes go back to Fortnox.

Employees

Employees, salaries, end dates and bank details come in and then stay up to date in Fortnox.

Departments as cost centres

Departments in Hedda map to your cost centres in Fortnox.

One source of truth

After the first import you make changes in Hedda, and Fortnox keeps pace.

Salary rows and holiday to Fortnox payroll

What Hedda works out does not have to be copied by hand. Variable pay and absence go across to Fortnox with the pay codes you already use.

Salary rows

Commission, bonus and extra salary rows go across as the right pay code.

Your pay codes

Map each kind of variable pay to the pay code you already have in Fortnox.

Holiday

Approved holiday goes across to Fortnox as absence.

Common questions

Common questions about the Fortnox integration

What is synced with Fortnox?

Employees, salaries, departments as cost centres, end dates and bank details, plus salary rows and approved holiday from Hedda to Fortnox.

Which system wins if the data differs?

On the first import, Fortnox wins. After that Hedda leads, and changes go across to Fortnox.

Can we keep our existing pay codes?

Yes. You map each kind of variable pay and extra salary row to the pay code you already use in Fortnox.

The same person, across the rest of the company.

Everything you need to know about your people already exists. It just lives in too many places.

Leave your details and we'll get back to you as soon as we can to book a time. The demo runs live in Hedda, so you see how it actually works.