NMBRS connector

Use your NMBRS data for reporting, automation and AI.

Data Panda pulls your NMBRS companies, employees, employments, payroll runs, leave and absence data into the same warehouse as your finance and operations data. From one place we turn it into dashboards, automations, AI workflows and custom apps that the payroll desk and the firm's partners use during the month, not only the week of a payroll close.

Data Panda Reporting Automation AI Apps
NMBRS logo
About NMBRS

The Dutch payroll engine that accountancy firms and SMEs run on.

NMBRS is a Dutch cloud platform for payroll (loon) and HR, founded in Amsterdam in 2007 and part of the Visma group since 2020. The product covers the full Dutch payroll cycle for SMEs and the firms that serve them: employee and employment records, contracts, salary tables, the loonheffing and CAO logic that the Dutch tax authority and collective agreements demand, leave and absence registration, sick reporting, expense declarations, the loonstrook the employee receives and the jaaropgaaf at year-end. A mobile self-service app sits on top of that record, and a public REST API exposes the same entities to integration partners.

The platform's reach is concentrated where its language and tax logic fit. NMBRS reports more than 100,000 companies running monthly payroll on it, processed through both in-house HR teams and a long tail of accountancy and salarisadministratie firms that operate dozens or hundreds of client environments inside one NMBRS account. That second segment is the platform's structural strength: a fiscalist or salarisadministrateur can manage many clients from one console, with the same loonheffing rules and CAO updates pushed everywhere. Pulled into a warehouse next to Exact Online, Yuki or Silverfin, the NMBRS record finally answers questions that one client environment alone cannot: payroll cost per legal entity over twelve months, sick-leave trend across a portfolio of clients, or which recurring payroll engagements are quietly absorbing more hours than the fee covers.

What your NMBRS data is for

What you get once NMBRS is connected.

Payroll and HR reporting

Loonkost, FTE, verzuim and recurring-fee realisation on one page across every client environment.

  • Payroll cost per legal entity, cost centre and CAO over twelve rolling months
  • Sick-leave trend per team and client, with the Bradford-style pattern named
  • Realisation per recurring payroll engagement, fee against actual hours

Process automation

Turn NMBRS payroll-run events into the downstream work the rest of the stack expects.

  • Post NMBRS journal entries to Exact Online, Yuki or Silverfin per entity
  • Sync new joiners and leavers from NMBRS into the firm's CRM and ticketing
  • Push loonstrook delivery confirmations into client portal notifications

AI workflows

Put the payroll record, leave history and CAO context behind AI that reads the full workforce picture.

  • Sick-leave anomaly detection per team, weighted by season and CAO
  • Fee-review scoring on recurring payroll engagements that have drifted
  • Natural-language Q&A across employees, contracts and pay components

Custom apps on your data

Lightweight tools on NMBRS data for partners, payroll managers and the client-facing fiscalist.

  • Partner workbench with the loon-portfolios that lost margin this quarter
  • Payroll-manager cockpit with run readiness, exceptions and CAO change impact
  • Client-facing portal with loonkost trend per entity, refreshed monthly
Use cases

Use cases we deliver with NMBRS data.

A list of concrete reports, automations and AI features we have built on NMBRS data. Pick the one that matches your situation.

Payroll cost per entityLoonkost per legal entity and cost centre, twelve-month trend.
Sick-leave by teamFrequency and duration patterns per team, manager and CAO.
Headcount versus planFTE on payroll against the approved plan, per entity and month.
Loonheffing reconciliationLoonheffing posted in NMBRS against what landed in the GL.
Recurring-fee realisationHours on recurring payroll engagements against the agreed fee.
Joiner-and-leaver flowIn and out movement per month, across the client portfolio.
CAO change impactCost impact of CAO updates per client and entity, before they hit.
Payroll-run exceptionsRecords flagged in the run, per cause and frequency.
Jaaropgaaf and year-end checksYear-end totals reconciled across NMBRS, GL and tax filings.
Multi-environment consolidationOne view across every client environment in the firm's NMBRS account.
Real business questions

Answers you will finally get.

Which payroll clients have quietly become unprofitable?

Hours at internal cost against the recurring fee per client environment, over twelve and twenty-four months. Ranks the loon-portfolios where the fee stayed flat while the run-time and exceptions drifted upward, which is where most payroll-desk margin disappears.

Where is sick-leave concentrating, and is it a team or a CAO pattern?

Frequency and duration per team, manager and CAO, with the Bradford-style ranking applied across the portfolio. Distinguishes one team that is genuinely struggling from a CAO-wide trend that no individual manager can fix on their own.

Does next month's NMBRS run match what we told the client to expect?

Pre-run cost projection per client and entity against the previous run and the budget. Surprises in loonheffing, CAO indexation or new contracts surface in the warehouse before the run posts, not on the call afterwards.

Value for everyone in the organisation

Where each function gets value.

For finance leaders

Payroll cost per entity, loonheffing reconciliation against the GL and recurring-fee realisation on the loon-portfolio. Fee-setting moves from gut feel to a client-by-client view of where margin on the payroll desk is leaking.

For sales leaders

Recurring-fee health and renewal signals on the loon-portfolio, on the same record as the client. Renewal and fee-review conversations open against drift the partner can show, not against feel.

For operations

Run readiness, exceptions and the CAO-change calendar on one board. The payroll manager sees what is going to break before the cut-off, not on the day after.

Ideas

What you can automate with NMBRS.

Pair with Exact Online

Post NMBRS journal entries to Exact Online

Each NMBRS payroll run produces a journal that lands in Exact Online with cost centre, CAO and entity dimensions intact. Loonheffing, social charges and net-to-pay rows reconcile in the GL the same day, instead of being keyed in the week after.

Pair with Yuki

Sync NMBRS payroll into Yuki administrations

The Dutch SME using NMBRS for loon and Yuki for boekhouding sees the run posted to the right Yuki administration with VAT and ledger coding aligned. The fiscalist reviews one consistent picture rather than chasing month-end exports between two tools.

Pair with Silverfin

Connect NMBRS runs to Silverfin working papers

Payroll output from NMBRS lands in the corresponding Silverfin working-paper set per entity, with loonheffing and social-charge reconciliations pre-mapped. The firm's review stops being a copy-paste exercise between the payroll desk and the file manager.

Pair with HubSpot

Notify HubSpot owners on payroll-portfolio churn signals

Drift on a recurring NMBRS engagement, repeated run exceptions or a contract end date in the next quarter all become signals the HubSpot owner of that client sees on the deal record. Renewal conversations open before the partner meeting raises the same client a quarter later.

Pair with Slack

Push NMBRS run-readiness alerts to Slack

Run-blocking exceptions, missing CAO updates and contracts ending in the cut-off week post into the payroll-desk Slack channel each morning. The team works the queue from one place rather than re-opening environments client by client to find the surprise.

Pair with HiBob

Connect NMBRS payroll to HiBob people records

Dutch entities running HiBob for the people record and NMBRS for loon keep the two sides aligned: a joiner in Bob lands as an employment in NMBRS, comp changes flow back, and headcount-versus-plan stops disagreeing depending on which screen finance opened.

Data model

Tables we make available.

These are the 33 tables we currently pull from NMBRS into your warehouse. Query them directly in SQL, join them to the rest of your stack, or build reports on top.

  • Companies
  • Company Addresses
  • Company Costcenters
  • Company Costunits
  • Company Hourcodes
  • Company Payroll Runs
  • Company Wagemodels
  • Contracts
  • Debtors
  • Departments
  • Employee Absences
  • Employee Addresses
  • Employee Costcenters
  • Employee Costperhour
  • Employee Departments
  • Employee Details
  • Employee Extrafields
  • Employee Fixedhours
  • Employee Fixedwagecomponents
  • Employee Functions
  • Employee Parentalleave
  • Employee Personal Info
  • Employee Salaries
  • Employee Variablehours
  • Employee Variablewagecomponents
  • Employees
  • Employments
  • Leave Balances
  • Leave Groups
  • Leave Requests
  • Managers
  • Payroll Run Employees
  • Schedules

Missing a table you need? We can extend the sync. Tell us what is missing and we will build it for you.

Your existing tools

Your data lands in a warehouse. Your BI tools read from it.

You keep the reporting tool you already have. We connect it to the warehouse where your NMBRS data lives.

Power BI logo
Power BI Microsoft
Microsoft Fabric logo
Fabric Microsoft
Snowflake logo
Snowflake Data warehouse
Google BigQuery logo
BigQuery Google
Tableau logo
Tableau Visualisation
Microsoft Excel logo
Excel Sheets & pivots
Three steps

From NMBRS to answers in three steps.

01

Connect securely

OAuth authentication. Read-only by default. We sign a DPA and your admin keeps the keys.

02

Land in your warehouse

Data flows into your warehouse on your schedule. Near real time or nightly, your call. You own the data.

03

Reporting, automation, AI

We build the first dashboard, workflow or AI feature with you, then hand over the keys. Or we stay on for ongoing delivery.

Two ways to work with us

Pick the track that fits how you work.

Track 01

Self-serve

We set up the foundation. Your team builds on top.

  • NMBRS connector configured and running
  • Warehouse set up in your cloud account
  • Clean access for your Power BI, Fabric or Tableau team
  • Documentation on what's in the data model
  • Sync monitoring so you're warned before reports break

Best fit Teams that already have a BI analyst or data engineer and want to own the build.

Track 02

Done for you

We build the whole thing, end to end.

  • Everything in Self-serve
  • Dashboards built to the questions your team actually asks
  • Automations between your systems
  • AI workflows scoped to real tasks your team runs
  • Custom apps where a dashboard does not cut it
  • Ongoing delivery at a pace that fits your team

Best fit Teams without in-house BI or dev capacity. You tell us what you need and we deliver it.

Before you book

Frequently asked questions.

Who owns the data?

You do. It lands in your warehouse, on your cloud account. We don't resell or aggregate it. If you stop working with us, the warehouse stays yours and keeps running.

How fresh is the data?

Near real time for most operational systems. For heavier sources we schedule hourly or nightly. You pick based on what the reports need.

Do I need a warehouse already?

No. If you don't have one, we help you pick one and set it up as part of the first delivery. Common starting points are Snowflake, Microsoft Fabric, or a small Postgres start.

Does the sync cover firms with many client environments in one NMBRS account?

Yes. Every client environment lands with its own dimension and the firm's hierarchy is preserved. Multi-client accountancy and salarisadministratie firms get per-client and per-entity reporting plus a portfolio-level view, without exporting per environment by hand.

Are loonheffing, CAO and pay-component detail kept granular?

Yes. Wage components, loonheffing rows, social charges and CAO context come across at line level, not as one aggregated salary number. Reconciliation against the GL and the Belastingdienst aangifte stays defensible because the same line that NMBRS produced is the line the warehouse stores.

GDPR-compliant
Data stays in the EU
You own the warehouse

A first deliverable live in four to six weeks.

We review your NMBRS setup and the systems around it. Together we pick the first thing worth building.