Lease and mobility
Nmbrs to Athlon integration: drivers to Athlon, lease contract in the right period in Nmbrs
With an integration between Nmbrs and Athlon, new drivers and leavers from Nmbrs go to Athlon automatically, with address, company and end date. Athlon's lease contract comes back into Nmbrs on the company car, with registration, list price and the actual delivery date, so Nmbrs calculates the taxable benefit from the right period.
What the integration does
Employers with lease cars from Athlon and payroll in Nmbrs look up registration, list price and taxable benefit in the Athlon paperwork after every delivery and enter them by hand. A car delivered at the end of the month thus sometimes reaches the payslip a month late, and correcting the start date takes extra work.
- HR enters a new employee with a lease entitlement in Nmbrs, at the right company.
- Athlon receives the driver with address and work email for the order and the MyAthlon account.
- After delivery KoppelHet puts the contract in Nmbrs on the company car, in the period of the delivery date.
- On a car swap the new contract gets the delivery date of the new car as its start date.
- If the employee leaves, Athlon receives the end date; on return the last driven date comes back as the end of the contract in Nmbrs.
Back: Registration, list price, taxable benefit percentage and contract start date · Last driven date on return
What to watch for with Nmbrs and Athlon
- In Nmbrs a lease car can only be entered on the employee in the period in which the contract start date falls, not as a future change. Athlon often plans delivery weeks ahead. KoppelHet holds the contract and puts it into Nmbrs as soon as that period is open.
- Nmbrs looks up make and model itself from the registration, but asks for the list price including accessories and the taxable benefit percentage. Those are in the Athlon contract. KoppelHet takes them from there, so the taxable benefit is not based on a list price without options.
- On a car swap Nmbrs sets the contract start date to the date of the change by default. A wrong start date can only be fixed by deleting the contract through the history. KoppelHet therefore uses the delivery date of the new Athlon car, not the day the swap is processed.
- Nmbrs asks for the last driven date as the end of the lease contract, not the end of employment. A leaver sometimes returns the car later, or takes it over. KoppelHet ends the contract on the date Athlon records on return.
- A second contract in Nmbrs is only meant for two company cars at the same time in the same tax period. A replacement car from Athlon during a swap therefore does not become a second contract in Nmbrs, but a change to the existing contract.
- Nmbrs only records means of transport and fuel for the work-related mobility report on expense claims. The kilometres driven in lease cars are therefore not in Nmbrs. For that part of the report the odometer readings in MyAthlon remain the source.
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
Does the integration calculate the taxable benefit?
No. Nmbrs calculates the taxable benefit itself, also on a swap halfway through the period. The integration makes sure registration, list price, percentage and dates are right.
And the employee contribution for a more expensive car?
That follows from your lease policy. HR sets a fixed contribution in Nmbrs once; a one-off contribution only counts in Nmbrs in the period in which it is entered.
Does this work when we have several entities in Nmbrs?
Yes. The integration carries the company as part of the key and puts the contract on the employee of the right company.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Nmbrs is read through the Nmbrs REST API with OAuth 2.0 and read scopes for employees, addresses and employments, per company; webhooks on changes.
- When the company car dashlet is used, Nmbrs creates the output codes L5300 to L5332 on the payslip itself; no manual value is possible on them. The integration therefore writes the contract, not the taxable benefit as an amount.
- Athlon publishes no API documentation for employer integrations; the connection on the Athlon side is agreed per customer with Athlon.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Nmbrs | Field in Athlon | Notes |
|---|---|---|
Bedrijf en personeelsnummer | Berijder bij Athlon | Together the key, because numbers are per company |
Roepnaam, tussenvoegsel en achternaam | Naam berijder | |
Woonadres | Adres berijder | |
Zakelijk e-mailadres | E-mailadres berijder | |
Einde dienstverband | Einddatum berijder | |
Kenteken (terug) | Kenteken in het dashlet auto van de zaak | Nmbrs fills in make and model itself |
Cataloguswaarde inclusief accessoires (terug) | Cataloguswaarde | |
Bijtellingspercentage (terug) | Bijtellingspercentage | |
Afleverdatum (terug) | Startdatum contract | |
Laatst gereden datum (terug) | Einddatum contract |
Related
ADP Workforce Now → Nmbrs
ADP Workforce Now to Nmbrs integration: the Dutch payroll group from ADP in the right Nmbrs company
AlexisHR → Nmbrs
AlexisHR (Simployer One) to Nmbrs integration: Dutch employees into payroll
BambooHR → Nmbrs
BambooHR to Nmbrs integration: Dutch payroll next to a global HR system
Bullhorn → Nmbrs
Bullhorn to Nmbrs integration: placements with hourly pay and end date in payroll