Skip to content
TimeTracking

Payroll exports that match your payroll

Approved hours are only useful once they reach payroll. TimeTracking exports them in the layout your payroll provider expects, so nobody has to retype a timesheet into another system.

Start freeSee pricing
Animated demo: approved hours go through an export mapping and pre-export checks into an SD Worx-format file, and the period is locked. Approved period, Mapping, Checks, Export and lock.

How payroll exports work

  1. Approve the period

    Hours, overtime, allowances, mileage and expenses are approved internally and, where needed, by the client.

  2. Pick a mapping

    Choose a saved export mapping: which hour types go to which payroll codes, which columns appear, and how people are identified.

  3. Export and lock

    Download the file or send it through the API. The period is marked exported and locked, so the numbers payroll received cannot drift.

What is available today

TimeTracking is upfront about integration status. Today you can export approved hours as configurable CSV and XLSX files, as an SD Worx-format export, and through the open API. Native connectors for Loket, Nmbrs, AFAS and DATEV are on the roadmap and marked as coming soon on their integration pages.

Because the CSV and XLSX mappings are configurable, many payroll systems that accept a file import can already be served while a dedicated connector is being built.

  • Live: configurable CSV and XLSX exports
  • Live: SD Worx-format export
  • Live: REST API for your own integration
  • Coming soon: Loket, Nmbrs, AFAS, DATEV connectors

Mappings, not manual work

An export mapping translates TimeTracking's hour types into your payroll codes: regular hours, overtime at different percentages, irregular-hours allowances, public holidays, mileage and fixed allowances. Set it up once per payroll provider or per client, and every export follows the same rules.

Exports can be split per legal entity, per client or per period type, which matters for agencies that run weekly and monthly payrolls side by side.

Exported means locked

Once a period is exported it is locked. If something turns out to be wrong later, the fix is a correction line in the next period. That keeps payroll, the client invoice and TimeTracking in agreement, and gives auditors a clean trail.

Your data stays yours: a full account export in open formats is available at any time.

Before you export

The export screen lists anything that could make the file wrong: timesheets that are not yet approved, conflicts that are still open, and people without an employee number for the payroll system. Fixing those first means payroll receives a complete period instead of a file that needs manual corrections.

Each export run is stored with the mapping that was used, the person who started it and the exact file that was produced. If payroll asks a question months later, you can see what was sent and when.

  • Open approvals and conflicts shown before export
  • Missing employee numbers flagged
  • Every export run stored with its file and mapping

Frequently asked questions

Which payroll exports are live today?

Configurable CSV and XLSX exports, an SD Worx-format export and the REST API. Loket, Nmbrs, AFAS and DATEV connectors are coming soon.

Can I customise the export layout?

Yes. Mappings define columns, hour-type codes and identifiers, and can differ per payroll provider or per client.

Which plan includes payroll exports?

Basic CSV, XLSX and JSON exports are in every plan, including Free. Payroll export mappings are included in Core and Pro.

What happens if hours change after export?

Exported periods are locked. Changes are booked as a correction in the next period so every system stays consistent.

Related pages

Try TimeTracking free

Free for up to 5 users. Core from €1 per user per month, everything included.

Start freeSee pricing