Cost centres and ledgers

Keeping cost centres from the ERP in line with payroll

You keep cost centres in line by making the ERP, such as Exact Online, Microsoft Dynamics 365, Oracle NetSuite or Unit4, the single source and comparing the values with YouForce, Nmbrs or HR2day before every payroll run. Whatever payroll lets an integration create, KoppelHet adds itself; whatever it does not, goes on a list for payroll before the run.

What it is

Finance creates cost centres in the ERP, payroll picks them per employee in the payroll system. Those two lists drift apart: a new code is not yet in payroll, a closed cost centre is still in use.

You only see the result in the journal. Payroll costs land on a catch-all cost centre, or a posting is rejected because the cost centre no longer exists in the ERP.

How the integration handles it

  • The ERP is the source. A new cost centre always starts with finance, and payroll follows.
  • Nmbrs lets an integration add and update cost centres. KoppelHet puts new codes from the ERP there itself.
  • YouForce only lets an integration read cost centres. KoppelHet compares both lists and gives payroll a list of what is missing before the run.
  • When finance closes a cost centre, KoppelHet reports which employees in payroll still use it.
  • The second dimension goes along: cost unit in Exact and Nmbrs, class in NetSuite, or HR2day's second dimension for projects. When posting it returns to the same place.
  • With a group ERP KoppelHet only takes the Dutch entity's cost centres, so payroll does not show departments from other countries.

Edge cases we handle

  • A cost centre code in YouForce is at most seven characters. Longer codes from Dynamics, NetSuite or Unit4 get a fixed translation, which KoppelHet reverses when posting.
  • Exact Online only changes a code through its recode function. Payroll then keeps the old code; KoppelHet shows old and new side by side.
  • Business Central can block combinations of dimensions, such as a grant project allowed for one department only. KoppelHet checks every combination from the HR2day cost allocation before posting.
  • A cost allocation in HR2day can be set up in advance to run to a date. If it runs longer than the cost centre exists in Exact, KoppelHet warns.

What KoppelHet does

KoppelHet builds the cost centre stream alongside the journal, so both use the same codes. At the start we agree which dimension is the cost centre and which the cost unit, and which translation is needed. After that the comparison runs before every payroll run and the differences are shown on the platform.

Common integrations

Frequently asked questions

Who creates a new cost centre?

Finance, in the ERP. The integration adds it to payroll if that allows it, and otherwise puts it on the list for payroll.

Does a cost centre disappear from payroll when finance closes it?

Not automatically. Nmbrs does not let an integration delete cost centres. KoppelHet reports which employees still use it, so payroll can move them.

How is this different from HR to ERP?

Here cost centres go from the ERP to payroll. With HR to ERP employees with their department and cost centre go the other way.

More on Payroll to finance

Payroll to finance: the overview

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.