Skip to content
Hypamoon

For teams that run on Nmbrs

Nmbrs import hours: from your rota to payroll

Nmbrs imports hours through its own sheet: one tab, plain text, a few hundred rows at a time, and an import cannot be undone. When the hours come from a rota, a care system or a paper time sheet, someone rebuilds that sheet before each run.

How it goes today

  1. Export the hours from the rota or time system.
  2. Rebuild them in the Nmbrs import sheet with the right hour codes.
  3. Split large files into a few hundred rows.
  4. Test the import in the sandbox before the live one.

How it can go

Hours from your rota or time sheets in Nmbrs each period, without retyping.

You send the export from your rota or time system as it comes, or a photo of a time sheet. Each line is matched to the employee and to the hour code you agreed once, you see a list of what will be added and what could not be matched, and after your approval the hours are added in Nmbrs for the right period.

Say this in ChatGPT, Claude or Copilot

Your chat gets connected to Hypamoon first, with this request filled in. Nmbrs works with a sign-in instead of a key: you sign in to Nmbrs once to give access, never in the chat.

Your request

With Hypamoon, each period, take the hours export from our rota system that I upload and match each row to the employee in Nmbrs and to the hour code we agreed, for example evening hours to one code and travel days to another. Show me what will be added and which rows could not be matched. After I approve, add the hours in Nmbrs for the current period.

For Nmbrs in the Netherlands, you register your own app in the Nmbrs Payroll developer portal on the Starter subscription, which needs no approval, and sign in to Nmbrs once to give it access. It stays yours.