UKG Dimensions logoNmbrs logo

Leave, absence and time

UKG Dimensions to Nmbrs integration: signed-off hours per pay code as variable hours in the right Nmbrs period

With an integration between UKG Dimensions and Nmbrs, the hours and premiums of timecards signed off in UKG go to Nmbrs automatically as variable hours, per pay code on the right hour code, cost centre and company. Only days up to the date the manager signed off are included, so payroll in Nmbrs does not calculate with hours that may still change.

What the integration does

Organisations that record shifts, overtime and premiums in UKG Dimensions and run Dutch payroll in Nmbrs export an hours list every period that someone retypes per hour code in Nmbrs. Hours of days that have not been signed off sometimes go along, and a late correction to a signed-off day gets lost.

  1. Employees clock in UKG. UKG calculates overtime and premiums and puts them on pay codes.
  2. The manager signs off the timecards up to and including a date.
  3. KoppelHet reads the sign-off state per employee and fetches the totals per pay code up to that date.
  4. Each pay code becomes a line of variable hours on the matching hour code, with the cost centre of the shift, in the site's Nmbrs company.
  5. An hour line that changes in UKG after sign-off goes as a difference into the current Nmbrs period, with a notice for payroll.
UKG Dimensions → KoppelHet → NmbrsSOURCEUKG DimensionsTARGETNmbrsKoppelHetmapping · logging · monitoringUKG Dimensions → KoppelHet → NmbrsSOURCEUKG DimensionsTARGETNmbrsKoppelHetmapping · logging · monitoring
Out: Hours per pay code per employee per day · Sign-off state per employee · Cost centre per hour line · Company and period in Nmbrs · Corrections after sign-off

What to watch for with UKG Dimensions and Nmbrs

  • UKG records per employee up to which date the manager has signed off. That date need not coincide with the end of a Nmbrs period. KoppelHet only takes days up to the sign-off date and leaves the rest for the next round, so a half signed-off week is not half paid.
  • A Nmbrs company runs payroll monthly or every four weeks. For each day from UKG, KoppelHet determines which period of that company it falls in. A night shift that crosses the boundary of a four-week period thus lands in the period of the day UKG assigns it to.
  • UKG counts overtime and premiums as hours on a pay code. Nmbrs multiplies hours on an hour code by the hourly wage and possibly a percentage. Per pay code we record the hour code, so an hour of 50 percent premium in UKG is also paid at the right percentage in Nmbrs.
  • If an employee works a shift in another department or at another site, UKG records it on that shift's line. Nmbrs accepts a separate cost centre per line of variable hours. KoppelHet books the hours on the cost centre of the shift, not on that of the regular employment.
  • In UKG an employee has one person number for the whole organisation. In Nmbrs an employee is recorded per company, with its own internal key. In every round KoppelHet looks up the key in the site's company, so someone who moves from one entity to the other gets their hours at the right employer.
  • Nmbrs only accepts a period the company has already passed in unprotected mode. If a manager changes a signed-off day after the payroll run, KoppelHet books the difference in the current period and states the original date in the notice, so the payroll bureau can decide whether a correction in an old period is needed.

How we build and run it

  • The integration runs on the KoppelHet platform, hosted in a data centre in the EU.
  • Every sync and every error is visible in the functional log; on an error your administrator is notified.
  • A change that cannot go through is not half-applied but queued for another attempt.
  • KoppelHet is ISO 27001 certified. Data travels encrypted and stays on the platform no longer than needed.
  • After go-live we manage the integration and adjust it when your process changes.
  • The integration fits next to your existing integration layer. Only the fields in the design are transferred; the platform keeps no register of its own.

Implementation, architecture and compliance

Implementation and price

This is not an app you switch on. We build the integration for your organisation on our platform, with building blocks we reuse on every project. So it is custom work that does not start from scratch.

A consultant prepares the intake and analyses both systems. We then record the mapping and exceptions field by field, test in the test or acceptance environment and go live at a moment you choose. Costs are a one-off amount for the setup and a monthly amount for platform, monitoring and support.

Price indication · Basic

Leave your work email and you see the price indication right away.

We only use your address to follow up on your question about this integration.

Frequently asked questions

Do new employees from Nmbrs also go to UKG?

Not in the first version. In this setup headquarters manages employees in UKG. New employees from Nmbrs to UKG can come later as an extension.

What if a pay code has no hour code in Nmbrs?

Then that line is not booked and payroll gets a notice. They link an hour code or confirm the pay code is not paid out.

Does this work if a payroll bureau manages Nmbrs for us?

Yes. The integration needs API access to your Nmbrs environment, which we arrange together with the bureau. The bureau simply sees the booked hours in Nmbrs.

Technical details for IT

For those who want to know how it works under the hood: APIs, fields and sources used.

  • UKG Pro Workforce Management API. The sign-off state per employee through GET /api/v1/timekeeping/timecard_signoffs (managerSignOffThroughDate, signOffPending); hours from the timecard totals per pay code with amount and the line's labor category. Persons through /v1/commons/persons with personNumber and primaryLaborAccounts.
  • Nmbrs through the EmployeeService. HourComponentVar_Insert or its batch variant (EmployeeId, HourCode, Hours, CostCenterId, Period, Year); an earlier period requires UnprotectedMode. Nmbrs retires the SOAP API on 1 March 2027; new integrations use the REST API for variable hours, the operations above show which data is needed.

Which fields are transferred

The key fields. The full mapping is agreed per customer.

Field in UKG DimensionsField in NmbrsNotes
personNumber (UKG)Personeelsnummer in NmbrsKoppelHet uses it to look up the internal EmployeeId per company
Paycode (UKG)HourCode (Nmbrs)Through a table maintained by payroll
amount per paycodeHours
Labor category of kostenplaats van de dienstCostCenterIdThrough a table per site
Plek in de UKG-organisatiestructuurNmbrs-bedrijf (CompanyId)Fixed mapping per site
Datum van de tijdkaartregelPeriod en YearAccording to the period length of the Nmbrs company

Related

Which systems do you want to connect?

Tell us which systems you use and what should happen automatically. Together we define the smallest working solution, with a clear design and a quote before building.