Scope agreed at the offer stage
The most common mistake when linking the time record with ERP is assuming the record should also calculate money. The scope agreed at the offer stage is different: schedules, leave balances, period settlement and the register sit on the InnerWeb side, and the client's ERP receives only quantities of hours and days per employee and pay component, without rates and amounts.
This division has practical consequences. The payroll department does not need to share rates with the time record system, and sensitive pay data stays in the payroll system. InnerWeb is an independent system that complements the client's existing systems: KD, RCP, HR and ERP, so it does not take over their functions.
What exactly goes to ERP
The export is a set of quantities: for each employee and each time component, a number of hours and a number of days. A component can be regular work, night work, overtime or absence. Mapping components to ERP codes is agreed by HR with the ERP administrator, not by the time record system itself.
When receiving the export, compare the totals: the total number of hours in the file should match the sum from the timesheets for the same group and period. A discrepancy usually means an unclosed exception, a missing exit or a component without an assigned ERP code.
Night work as a separate column
The module counts minutes worked during night hours 22:00-06:00 and passes them to an export column for HR. As a result ERP receives a ready number of night minutes and does not have to calculate them from entry and exit times. A shift crossing midnight needs no manual split.
What stays outside the export
Rates, cash supplements, deductions and everything that requires knowledge of pay stay outside the export. The module does not calculate pay. This gives a simple control rule: if an export file contains a column with an amount, it is a configuration error.
Illustrative distribution of one employee's hours in a month
How to prepare the export step by step
Start the preparation with the data, not the tool. Only when the time record is complete does the export make sense.
- Close the settlement period with the HR or administrator role, because we export closed data.
- Agree the list of components and their codes with the ERP administrator.
- Set units: hours to the minute or to the quarter hour, days as whole numbers.
- Run a test export for one group and compare it with the timesheets in PDF.
- Save the file version and date so that you know what ERP received if a correction is needed.
Honest limits: what is ready and what is in development
The schedule screens, the HR tab and the ERP export are at the preview stage with demo data. We describe them as a development option, not a ready standard. The time module was piloted on one installation and is not widely deployed. Before purchase, agree in writing which element of the export is delivered, in what form and by when.
The audit evidence remains the record: the employer keeps the employee's working time record, which is the basis for pay and other benefits (Labour Code (Kodeks pracy), art. 149 § 1). The export is only an extract of it, so keep the PDF timesheet from the export day next to the file.
Checklist
Video
Frequently asked questions
Does InnerWeb calculate pay?
No. Quantities of hours and days go to ERP, while rates and amounts stay in the client's payroll system.
Is the ERP export a ready standard?
At present it is a development option: the export tab is at the preview stage with demo data.
How will ERP know about night work?
The module counts minutes worked from 22:00 to 06:00 and passes them in a separate export column for HR.
Sources
Let's agree the export scope for your ERP
We will go through components, units and codes together, so the export does not contain a single amount. Book a conversation with the InnerWeb team.
Let's talk