Payroll to finance
Unit4 and YouForce integration: shared cost centres, payroll journal posted automatically
With an integration between Unit4 ERP and Visma Raet YouForce, the payroll journal lands in Unit4 automatically after every payroll run, split over ledger, cost centres and projects. Payroll sees new or closed cost centres in Unit4 straight away, so finance posts to the same cost centres HR assigns to employees.
What the integration does
Organisations that run finance and projects in Unit4 ERP and payroll in Visma Raet YouForce open new cost centres in Unit4 without payroll hearing about it. After every run the journal goes to finance as a file and has to be adjusted before it fits into Unit4.
- A controller opens a new cost centre or closes one in Unit4.
- Payroll gets a notice of new, changed and closed codes, and updates YouForce before the next run.
- After a processed payroll run KoppelHet fetches the payroll journal from YouForce.
- The amounts are summed per account, cost centre and cost unit and translated to the Unit4 accounts.
- The journal goes to the familiar batch processing (GL07) in Unit4, where it is checked and posted.
Back: Payroll journal per payroll run · Split over cost centre and cost unit
What to watch for with Unit4 ERP and Visma Raet YouForce
- YouForce only lets an integration read cost centres. KoppelHet therefore cannot put a new Unit4 cost centre into YouForce itself; the integration reports the difference and payroll records the code.
- A cost centre code in YouForce is at most seven characters long. If Unit4 uses longer codes, we work with a lookup table between the two.
- YouForce provides the journal per employee. Finance wants it at account and cost centre level, so KoppelHet sums the lines first; per-employee detail stays in YouForce.
- Unit4 closes a cost centre with a status instead of deleting it. KoppelHet can therefore see which cost centres are closed and warns when employees in YouForce are still assigned to them.
- The journal goes through Unit4's batch processing, so finance keeps the same checks as with a manual import.
- A correction run in YouForce produces extra lines for a period already posted. KoppelHet posts these as a separate batch with its own description, so finance recognises the correction.
- Unit4 works with periods, YouForce with dates. KoppelHet converts cost centre validity and the pay period to the Unit4 period.
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
Can KoppelHet create cost centres in YouForce automatically?
Not through an integration, as YouForce only allows reading cost centres. KoppelHet does track which codes are missing or closed and reports it, so payroll updates them before the next run.
Do you post per employee in Unit4?
Usually not. We post per GL account and cost centre. The per-employee detail stays in YouForce and can be looked up there.
Does this also work with Unit4 ERP on-premise?
What is described here applies to Unit4 ERPx in the cloud. For an older or on-premise version we check per customer which import option exists, and a small KoppelHet program runs inside the own network.
What if a journal line uses an unknown account?
Then the batch stops before anything is posted. The alert in the platform names the account, and once the lookup table is updated the journal goes through.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Unit4 ERPx is read through the Attribute Values API (attributeValue, description, status C = terminated, periodFrom and periodTo) and written through the Financial Transaction Batch API for the GL07 import process (account, accountingDimension, currencyAmount, period). OAuth 2.0 with client credentials.
- YouForce is read through the Youforce Data API (journal lines per employee with Amount, ContraAccount, CostCenterCode, CostTypeCode, CostUnitCode, Year and ProductionPeriod) and the WFM API (cost centres, CostCenterBK at most seven characters, read-only). OAuth 2.0 with client credentials.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Unit4 ERP | Field in Visma Raet YouForce | Notes |
|---|---|---|
attributeValue (kostenplaats) | CostCenterBK | YouForce accepts at most seven characters |
description | Naam kostenplaats | Cost centre description |
status | CostCenterStatus | Status C in Unit4 means terminated |
periodFrom / periodTo | Geldigheid kostenplaats | Unit4 works with periods, YouForce with dates |
ContraAccount | account | YouForce contra account mapped to the Unit4 ledger through a lookup table |
CostCenterCode | accountingDimension (kostenplaats) | Which dimension holds the cost centre differs per Unit4 setup |
CostUnitCode | accountingDimension (kostendrager of project) | |
Amount | currencyAmount | Summed over all employees per account and dimension |
Year + ProductionPeriod | period | Converted to the Unit4 period format (year and month) |
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