The payroll journal

Correction runs, four-weekly periods and closed months in the payroll journal

You handle correction runs and diverging periods by putting every run from AFAS, Nmbrs or YouForce into the ERP as its own entry with a recognisable description, and by agreeing beforehand which accounting period in Exact Online, Visma.net or NetSuite each pay period falls into. If a correction lands in a month finance has already closed, the integration holds the journal and asks finance which period to use.

What it is

A payroll run is not always one run per month. There is a correction run after approval, an extra run for a bonus, or a run for December that only happens in January. With four-weekly payroll there are thirteen periods, while finance usually posts in twelve months.

Without fixed agreements someone posts a correction in the wrong month, posts a run twice, or loses an extra run. A posted journal entry in Exact Online cannot be changed afterwards either.

How the integration handles it

  • Every run becomes its own entry with run and period in the description, so finance sees which amount belongs to the correction.
  • A fixed table puts every four-weekly period into the right accounting period of the ERP.
  • KoppelHet compares the payroll's run list with what is already in the ERP. An extra run thus becomes its own journal and is not lost.
  • Before posting KoppelHet checks whether the period exists and is open in the ERP. If it is closed, the journal is held and KoppelHet asks finance for a period.
  • An error in a posted period in Exact Online is fixed with a reversal followed by the correct journal, so the history stays visible.
  • When the same period comes out of payroll again after a correction, KoppelHet recognises it by the document number and prepares the correction separately.

Edge cases we handle

  • Nmbrs ties the journal to the company's active year. A December run made in January is posted, by agreement, in the old financial year, as long as finance has that period open.
  • AFAS can show a correction period together with the main period. The integration only posts the lines of the approved processing, so a main period never reaches the ERP twice.
  • For a negative total, such as a correction, KoppelHet swaps debit and credit for Visma.net instead of posting a negative amount.
  • An AFAS period that does not match a calendar month is posted in Unit4, by agreement, in the period of its end date.

What KoppelHet does

At the start KoppelHet agrees the period table and the rules for corrections with finance and payroll, and tests a correction run and the year end before go-live. After an outage the integration can safely retry, because it keeps track of which runs have been posted.

Common integrations

Frequently asked questions

What happens with a correction run?

It becomes its own entry with its own description, so finance recognises the correction. The original entry is not touched.

We run four-weekly payroll. Is the accounting period still right?

Yes. At the start we agree which accounting period each four-weekly period falls into, so payroll costs are in the right month.

What if the month is already closed?

Then KoppelHet holds the journal and asks finance for a period, instead of posting it somewhere else.

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.