InnerWeb
Skip to main content

Agency hours dispute: evidence from gate swipes

The temp agency invoice shows more hours than the shift leader's notes. Without shared evidence the dispute ends in a compromise that costs money or trust. This scenario shows how gate swipes, exceptions and the closing of the settlement period give HR and the warehouse manager one verifiable version of events.

780 h
example monthly hour difference with 60 people
Source: example calculation
31,200 PLN
example monthly amount in dispute at 40 PLN per hour
Source: example calculation

The situation: two versions of the same hours

The scenario concerns a logistics centre where several dozen agency workers work across three shifts. The agency issues its invoice based on its own attendance lists kept by a coordinator. The warehouse manager has notes from the shifts and the impression that some people left early. The gap on the invoice is, for example, 3 hours per week per person.

With 60 people and a difference of 3 hours a week, this gives 180 hours a week, or about 780 hours a month. At an example rate of 40 PLN per hour, the dispute concerns roughly 31,200 PLN a month. This is an example calculation based on assumptions, not data from any site.

Where the evidence comes from: gate scans as the time record

Gate scans, which are also used for the evacuation list, form the working time record in InnerWeb with daily, monthly and yearly views. The supervisor works in a console that collects exceptions into queues, and the settlement period can be closed so that the data stops changing.

Events arrive from the client's existing access control system via a card swipe webhook. The notification contains the data of the person and the company, and the swipe location makes it possible to tell gates apart. The access control system sends events in real time, with the event time read from the reader, the direction (entry or exit) and an event identifier, and InnerWeb receives them through an authenticated webhook. The rules for pairing entries with exits and for rejecting duplicates are set in the specification agreed with the access control vendor. In an audit of a dispute, the time from the reader counts, not the time the event was queued for sending.

Hours in dispute per month, example

Hours in dispute per month, exampleBefore and after chart: without shared evidence 780 hours a month are in dispute, with the gate time record about 80.0200040006000800010,000hoursWithout shared evidence (Hours agreed): 9000 hours9000 hoursWith gate time record (Hours agreed): 9700 hours9700 hoursHours agreedWithout shared evidence (Hours in dispute): 780 hours780 hoursWith gate time record (Hours in dispute): 80 hours80 hoursHours in dispute
  • Without shared evidence
  • With gate time record
Source: Example calculation: 60 people, 3 hours of difference per week, illustrative assumption of 90% of the dispute settled on swipes.

The procedure for settling the dispute step by step

The HR department opens the monthly view for the agency's company and compares the hour totals with the invoice. The differences are narrowed down to days and people: the warehouse manager reviews the exception queue and checks whether any entry needs a correction, for example because an exit swipe is missing.

  • Export the monthly hour totals per person and compare them with the attachment to the agency invoice.
  • Identify the days with the largest difference and open them in the daily view.
  • Check in the exception queue whether missing exit swipes have been explained and approved.
  • For people with reservations, compare the entries with the On site view for that day.
  • Close the settlement period once it is agreed, so that the data becomes the basis for the contract clause and for a corrective invoice.

What changes for the agency

The agency receives the same data the site works with, instead of the shift leader's notes. The conversation then stops being about trust in the relationship and starts being about specific days and swipes. A good practice is to share the monthly summary with the agency before the invoice is issued, which shortens the correspondence.

It is important that the data of agency workers is consistent: the company name and the spelling of the surname should be uniform across the access control notifications. A swipe by a person unknown to the system creates an account and a company from the notification data, so different spellings of the agency name lead to duplicate companies, and those make hour totals harder to add up.

Conclusions for HR and the warehouse manager

First, a dispute over hours is settled on data from the gate, not on memory. Second, the exception queue must be emptied on an ongoing basis, because unresolved exceptions become material for the dispute. Third, closing the period is the moment after which the figures stop changing and can be cited in a conversation with the agency.

InnerWeb does not replace the payroll system or settle the dispute for the parties: it provides evidence for audit and settlement that both sides can check.

Video

Frequently asked questions

Are gate swipes enough to settle the agency's hours?

They are the basis of the time record, but exceptions such as a missing exit swipe must be explained in the exception queue before the period is closed.

Does the swipe time come from the reader?

Yes. Under the integration specification the access control system passes the event time read from the reader, not the time the request was sent.

What does closing the settlement period achieve?

The period data stops changing, so the manager and HR can refer to fixed figures in the conversation with the agency.

Does InnerWeb replace the payroll system?

No. It provides the time record and audit evidence, and the payroll system stays on the site's side.

Settle the agency on gate data

Book a call about the working time record for agency staff. We will show how to build a settlement from swipes and exceptions that both sides can check.

Let's talk