Payroll to finance
Unit4 and HR2day integration: cost centres and projects to HR2day, payroll journal back to Unit4
With an integration between Unit4 ERP and HR2day, the cost centres and projects from Unit4 reach HR2day automatically, and the payroll journal goes to Unit4 as a batch after every payroll run. HR only picks codes finance knows in Unit4 for an appointment or cost allocation, and the allocation from HR2day reaches the ledger per cost centre and project.
What the integration does
Organisations that keep their finances in Unit4 ERP and run payroll in HR2day maintain cost centres and projects separately in both systems. After the payroll run finance imports the journal by hand, and a line on a closed cost centre holds up the whole batch.
- Finance opens or closes a cost centre or project in Unit4.
- KoppelHet reads the change per Unit4 company and makes new codes available at the HR2day employer that belongs to that company.
- HR picks a cost centre and, where needed, a project for the appointment or in a cost allocation.
- After the payroll run KoppelHet places the journal from HR2day as a batch in Unit4, with the cost centre and project on every line.
- Unit4 checks the batch; KoppelHet reads the result and reports rejected lines.
Back: Payroll journal per run · Journal lines per cost centre and project
What to watch for with Unit4 ERP and HR2day
- HR2day keeps the cost allocation separate from the appointment and includes the costs in the journal pro rata to that allocation. One employee thus produces lines on several cost centres and projects. KoppelHet puts each combination as a separate line with both dimensions in the Unit4 batch.
- When finance closes a cost centre or project in Unit4, it is marked as terminated there. A cost allocation in HR2day may still point to it. KoppelHet reports straight away which employees in HR2day are still on that code, so payroll moves them before the next run.
- Unit4 refuses a batch with a batch number and interface that already exist. KoppelHet uses the run number from HR2day as the batch number, so a journal that is sent again does not land in the ledger twice.
- After import Unit4 returns the check result per batch, transaction and line. KoppelHet links a rejected line back to the employer, cost centre and project from HR2day, so payroll knows which allocation is wrong.
- Unit4 accepts at most ten thousand lines per call. A journal per employee with a detailed cost allocation can be larger; KoppelHet therefore totals the lines per GL account, cost centre and project, and only splits when still needed.
- In Unit4 cost centres belong to a company. If the organisation has several employers in HR2day, KoppelHet records per employer which Unit4 company it belongs to, so codes and journal do not end up at the wrong company.
- Unit4 posts to a period in the form year and month. A correction run in HR2day over an earlier month is posted by KoppelHet in the period finance still has open, with the original run number in the description.
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
What happens to a cost centre finance closes in Unit4?
KoppelHet reports the code with the employees still on it in HR2day. Payroll adjusts the appointment or cost allocation before the next run.
Does Unit4 post the journal per employee?
Usually not. Finance gets the journal per GL account, cost centre and project; the detail per employee stays in HR2day.
What if a batch is rejected in Unit4?
The batch stays in Unit4 and KoppelHet reports per line what is wrong. After correction the same run goes again, without a double posting.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Unit4 ERPx through the Attribute Values API (attributeValue, description, companyId, status C = terminated) for cost centres and projects, and the Financial Transaction Batch API (POST /v1/financial-transaction-batch with batchInformation.batchId and interface; account, accountingDimension1 and 2, currencyAmount, period YYYYMM). At most 10,000 lines per call and 200,000 per batch; 422 on an existing batchId and interface combination. Validation results of the GL07 import process per batch, transaction and line.
- HR2day runs on Salesforce and publishes no API documentation. Writing cost centres and reading the journal goes through the APIs HR2day makes available for the customer; we confirm that at the start.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Unit4 ERP | Field in HR2day | Notes |
|---|---|---|
attributeValue (kostenplaats) | Kostenplaats | Code identical in both systems |
attributeValue (project) | Kostenplaats dim2 | |
description | Omschrijving | |
companyId | Werkgever | Lookup table Unit4 company to HR2day employer |
status C (beëindigd) | Melding | Not closed in HR2day without agreement |
Grootboekrekening op de journaalregel | accountingInformation.account | |
Kostenplaats en dim2 op de journaalregel | accountingDimension1 en accountingDimension2 | |
Bedrag | amounts.currencyAmount | Credit as a negative amount |
Salarisperiode en run | period (JJJJMM) en batchId |
Related
ADP Workforce Now → Unit4 ERP
ADP Workforce Now to Unit4 integration: workers from ADP as employees in Unit4 ERP, with cost centre and manager
AFAS Profit → Unit4 ERP
AFAS to Unit4 integration: payroll journal posted in Unit4 ERP
BambooHR → Unit4 ERP
BambooHR to Unit4 integration: employees from BambooHR in Unit4 ERP, with department, job and end date
BuddeeHR → Unit4 ERP
BuddeeHR to Unit4 integration: Buddee position periods as dated relations in Unit4