Leave, absence and time
Everhour to Nmbrs integration: approved hours of hourly paid staff as variable hours, leave back in planning
With an integration between Everhour and Nmbrs, the clocked hours of hourly paid staff go to Nmbrs automatically as variable hours once the week is approved, on the right hour code and in the company's current period. Approved leave from Nmbrs comes into Everhour as time off, so capacity planning takes it into account.
What the integration does
Organisations that track hours and clocking in Everhour and run payroll in Nmbrs, often with a payroll bureau, make an hours summary for hourly paid staff each month that the bureau enters into Nmbrs. Leave is approved in Nmbrs and is not visible in Everhour.
- Employees clock in Everhour and submit their week.
- An admin approves the week in full or in part.
- KoppelHet finds the employee and company in Nmbrs for each Everhour user.
- The approved work time arrives in Nmbrs as variable hours on the agreed hour code.
- Approved leave from Nmbrs appears as time off in Everhour.
Back: Approved leave as time off · Leave balance per type as allocation, if you want it
What to watch for with Everhour and Nmbrs
- Nmbrs knows an employee per company, Everhour one user per person in the whole account. If hourly paid staff work for several entities, KoppelHet records per user which Nmbrs company the hours belong to, so they do not appear on the payslip of the wrong employer.
- Everhour has no approval notification, and a week can be partly approved. KoppelHet checks the status each week, takes only the days approved in the approval history, and checks again for late approvals before the period closes in Nmbrs.
- Nmbrs accepts variable hours in the company's current period, or in an earlier period with unprotected mode. KoppelHet splits a week that spans two periods by day, and hours from a period already closed go to the current period.
- An hours line in Nmbrs has a comment field. KoppelHet puts the Everhour week and the user there. If the same week comes in again after a correction, the integration books only the difference and not the whole week again.
- Nmbrs stores leave with a status and with start and end hours for part of a day. Only approved leave goes to Everhour. Half a day in Nmbrs becomes half a day of time off; if the number of hours does not fit Everhour's parts of a day, an alert follows.
- Nmbrs has four leave types, Type1 to Type4, with a balance per type. Everhour has its own time off types with allocations. KoppelHet maps each Nmbrs type to an Everhour type, so for example extra-statutory leave stays visible separately in planning.
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 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.
Frequently asked questions
Do employees on a fixed salary also have to clock?
No. The integration only sends hours of users marked as hourly paid. The rest stays in Everhour for projects and planning.
Do new employees from Nmbrs go to Everhour automatically?
No. Everhour does not allow users to be created through the API. You invite them in Everhour; the integration then finds them by email address.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Everhour through api.everhour.com with X-Api-Key. GET /timesheets?weekId= (approval.status, approval.history[].days), GET /timecards (workTime and breakTime in seconds), GET /users. Time off through POST /resource-planner/assignments/time-off (timeOffType, timeOffPeriod, status approved); balances through the allocation endpoints. Webhooks are not signed and have no approval event. Limit 100 requests per 10 seconds.
- Nmbrs through the REST API with OAuth 2.0 and a subscription key, per company. In the SOAP EmployeeService these are HourComponentVar_Insert (Period, Year, UnprotectedMode, Comment) or HourComponentVar_InsertCurrent, Leave_GetList (NL-only; Status, Hours, StartHours, EndHours, Type) and LeaveBalance_GetPerType. The SOAP API stops on 1 March 2027.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Everhour | Field in Nmbrs | Notes |
|---|---|---|
user (Everhour-id) en e-mailadres | EmployeeId in Nmbrs | Matched on the work email address |
timecard.workTime (seconden) | Hours | Totalled per approved day |
Soort uren | HourCode | Hour code of the Nmbrs company |
weekId en gebruiker | Comment | Reference to prevent double booking |
Datum van de dag | Period en Year | |
Leave_GetList met Status Approved (terug) | time-off met timeOffType en timeOffPeriod | |
LeaveBalance_GetPerType (terug) | allocation per time off type |
Related
Everhour → AFAS Profit
Everhour to AFAS integration: approved weekly timesheets as project costing in AFAS, leave back in planning
Everhour → Visma Raet YouForce
Everhour to YouForce integration: approved clocked hours of hourly paid staff to payroll
HiBob → Everhour
HiBob to Everhour integration: approved time off and balances from Bob in Everhour's resource planner
Personio → Everhour
Personio to Everhour integration: approved absences from Personio as time off in Everhour