Who these recommendations are for and why HR should know them
These recommendations are aimed at HR and personnel departments that are responsible for working time records but do not choose the access control system. Usually security or IT selects the access control vendor, and HR learns about the limitations only at the first settlement. By then corrections are expensive.
The employer keeps working time records, which are the basis for calculating pay and other benefits (Kodeks pracy, art. 149 § 1). If card punches are to be the source of these records, each punch must carry information that can be defended during an inspection.
InnerWeb does not produce or replace access control readers. It integrates with the client's existing access control (KD) system and receives card punch events, so it can link them with qualifications, permits, attendance and working time records. This means the requirements below go to your access control vendor, not to us.
Seven requirements for the access control vendor
Each requirement has a rationale that is worth keeping in the specification, because vendors usually reject points whose purpose is not clear.
1. Event time from the access control clock, not the sending time
The event must carry the time of the punch, not the time the message arrived. During a line failure the event queue may arrive hours late, while the records count minutes.
2. Place of the punch
The event identifies the gate or reader. Without this we cannot distinguish entry to the site from passage between zones inside the plant.
3. Person and company data
The card must be unambiguously linked to a person and to the company that employs them. This is the condition for separating own employees from external contractors, who are subject to different stay limits.
4. Number of the active card
The event passes the number of the card that was active at the moment of the punch. A lost and blocked card should not generate records, and a card reissued must point to the same person.
5. Direction: entry or exit
This requirement is critical: every event states whether it is an entry or an exit. The access control system sends the direction resulting from the reader configuration, and InnerWeb receives it together with the event time, place, person data, company and active card number. The rules for pairing entries and exits are set in the specification with the access control vendor.
6. Unique event identifier
The identifier allows a duplicate to be rejected when an event is sent again. The duplicate rejection rules are set in the specification with the access control vendor, because the credibility of the records depends on them.
7. Authentication and availability
The access control system sends events in real time through an authenticated webhook. The token has a limited validity period and is renewed automatically by the integration, and the vendor reports sending errors. HR should ask for a written indication of who in the vendor's team is responsible for integration failures.
Fields of a punch event in the integration specification
What not to require
Do not require the access control vendor to calculate working time, norms or rest periods. That is the task of the time records module. Access control must deliver reliable punches, while rules such as exit tolerance, reminder call time or the 11 and 35 hour rest checks are set in the working time module.
Do not require replacing readers just to run the integration. If the existing readers distinguish direction and pass events on, replacement is unnecessary.
How to verify the requirements before signing the contract
Ask for a sample of several dozen punch events from different gates, including direction and identifier. HR checks three things: whether every event has a complete set of fields, whether the time is consistent with the plant clock, and whether a duplicate carries the same identifier.
Then ask for a failure scenario: what happens to the punches when the link is down for one hour. The answer must show that events are queued and sent with their original time.
InnerWeb's role in this chain
InnerWeb is an independent system that complements the client's existing systems: access control, time and attendance, HR and ERP. For HR this means one place to review exceptions and permissions: each employee sees their own record, HR sees the employees of their company, a supervisor sees their team, and the administrator sees everything.
Only hours and days are passed to ERP, without rates or amounts. The module does not settle pay; it provides a structured record that the personnel department uses in its own process.
Video
Frequently asked questions
Does InnerWeb supply card readers?
No. Readers and the access control system stay with the client, and InnerWeb receives punch events according to the specification for the access control vendor.
Which fields must a punch event carry to feed the time records?
Reader event time, place, person data, company, active card number, direction (entry or exit) and event identifier. The rules for pairing entries and exits and rejecting duplicates are set in the specification with the access control vendor.
How will the records know that a person comes from an external company?
The event carries person and company data. On this basis the matching stay limit is applied, by default 12 hours for an external company.
Sources
Pass the specification to your access control vendor
We will prepare for your vendor a list of event fields and a description of the integration. Book a meeting with the InnerWeb team.
Let's talk