Timply and your payroll system

A standard, not a connection per vendor

PAXml 2.0 is the Swedish standard for a payroll record. Timply writes the file and your payroll system reads it, and in between there is nothing built specifically for your vendor.

That is why the list is long. Fortnox Lön, Visma Lön, Hogia Lön, Kontek, Crona, Agda PS, Flex HRM and Björn Lundén all read the same format. Change payroll system and the records follow with nothing to rebuild, and there is no connection to stop working when a vendor changes its interface.

Moving the file is not the hard part

Exporting a record and importing it takes a couple of minutes a month. It is the route the payroll systems themselves document for taking in a payroll record, and that route is short.

What actually takes time is deciding which hours are Saturday unsocial hours, which are paid overtime, and which are additional hours against a part-timer's contracted measure. Made afterwards in a spreadsheet, that is where the errors come from and where the hours go.

Timply sets the payroll code as the time is recorded. By the end of the period the record is already worked out, and the file is only how it gets across.

What the file carries

A PAXml 2.0 file from Timply carries worked time as ARB, unsocial hours split across OB1 to OB5, paid overtime as ÖT1, time off in lieu as ÖK1, additional hours as MER, and absence on its own codes as SJK, SEM, VAB and FPE. The period is marked as approved, so the payroll system can see the record has been signed off.

More on the split on the page about the payroll file and PAXml.

Before the first run

Three things have to line up on your side, and they are the same whichever payroll system you use:

1. Employee numbers. Every employee in Timply needs the same payroll employee number as in the payroll system.
2. Pay types. The codes Timply sends have to exist in the payroll system. With no OB2 set up, Saturday unsocial hours are rejected.
3. One reconciliation. Run the first period in parallel and read the totals in both systems before you pay out. That is when a wrong code setup shows.

If you want more than a file

If you want the record fetched automatically, or employees kept in sync between the systems, we build that as a piece of work. Tell us which payroll system you run and we will look at what it would take and what it would cost.

Pages per payroll system

We publish the steps for a payroll system once somebody here has taken a real Timply export into that vendor's import and checked the result. An instruction nobody has followed all the way through is worse than no instruction.