After applying the calculation rules in Strobbo, you might see conflicts in the "Payroll" overview.
🚫 These conflicts must be resolved first before you can export your payroll.
👉 So, always check the payroll overview first to see if any red warnings or issues appear.
✅ Once all conflicts are cleared, you can safely export your payroll.
If there is a conflict in Strobbo, it is usually caused by data that has already been entered. Before you start the payroll process, you need to perform standard checks, which you can find here.
There are different conflicts:
Conflicts at the beginning of the month
📆 If you see a conflict on the first or last working day of the month, we recommend adjusting the date filter to get the full picture.
ℹ️ Why?
Strobbo calculates working hours from Monday to Sunday.
👉 So if a Monday falls in the previous month, the hours worked that day are still included in the calculation.
🔍 Simply adjust the date range to include those days — that way you get a complete and accurate view of the worked hours.
Let's follow the example below:
We notice here that an employee has a conflict on Wednesday 02/02
1️⃣ First, change the start date to Monday 31/01.
Leave the end date as it is.
🖱️ Click on "Apply filters".
2️⃣ You will now see the working week from Monday to Sunday.
📊 In this example, only 19h12 of worked hours or absences have been recorded, while 24h are required by contract.
🔄 The system will now:
Either fill in extra hours as an absence,
Or allow more than 11 hours per day,
… in order to meet the contractual requirement.
The following step can provide the solution:
- An existing time entry/absence should be adjusted (increase/decrease)
After you have resolved the issue by adjusting one of the above, you need to reset the data and apply the rules.
A conflict on a shortage of performance/absence
One frequent mistake when applying calculation rules in Strobbo is that there are too few or too many hours registered as worked time or absences. This causes a conflict in the payroll overview.
📌 Example:
The employee has a contract of 38h00 per week, but only 30h24 is recorded as absence.
➡️ The 7h36 shortfall creates a conflict that must be resolved before exporting the payroll.
💡 Tip: Always check that the total of worked hours and absences matches the contract hours.
The following step can provide the solution:
- An existing time entry/absence should be adjusted (increase/decrease)
After you have resolved the issue by adjusting one of the above, you need to reset the data and apply the rules.
A conflict on a surplus of performance/absence
Sometimes, an employee accidentally requests 7 consecutive days of absence.
➡️ This may result in incorrect overtime calculations.
🕒 Another frequent issue is an error in the time clock overview, such as missing or double punches.
📌 Example:
The employee has a 32-hour contract, but 32h30 of sick leave was recorded.
➡️ This exceeds the contract hours and creates a conflict in the payroll.
💡 Tip: Always verify:
that the total absence hours match the contract
that the time clock data is correct
This helps avoid payroll discrepancies.
In the example below, we can see that there are still many errors in the time entry overview, which we must first correct in order to successfully process the payrolling.
The following steps may be the solution:
- Did an employee forget to clock out? Then follow this manual.
After you have resolved the issue by adjusting one of the above, you need to reset the data and apply the rules.
A conflict on an incorrectly completed profile
If you notice a conflict with an employee’s recorded hours,
➡️ Make sure to check if the profile is filled in correctly.
📌 Example:
An employee with a part-time schedule is still listed as a full-time worker.
In this case, you need to adjust both the employment status and the contractual hours.
✅ Fix this to avoid payroll errors!
The following step may be the solution:
After you have resolved the issue by adjusting one of the above, you need to reset the data and apply the rules.