Skip to content
Hypamoon

For teams that run on Nmbrs

Nmbrs payroll run check: what changed and why

Nmbrs shows the run output next to earlier periods for the person who processes payroll. The owner or client who approves the run often sees totals, and changes made with retroactive effect are hard to trace, so payslips get checked by hand.

How it goes today

  1. Open the payslips one by one after each run.
  2. Compare net pay with last month in a spreadsheet.
  3. Look up retroactive changes per employee.
  4. Explain the differences to the client by email.

How it can go

See what changed in each payroll run before you approve it.

After each run in Nmbrs you get a short summary: who joined or left, whose gross or net pay moved by more than the margin you set, and which wage components caused it, compared with the previous run. The person who approves payroll gets it by email in plain words, with the employees to look at first.

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, after each payroll run in Nmbrs, compare the run output with the previous run per employee. List who joined or left, and whose gross or net pay changed by more than 5 percent, with the wage components behind it. Email a short summary in plain words to me and to the person who approves payroll, with the employees to check first at the top.

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.