InnerWeb
Skip to main content

Billing the agency for attendance: best practices for the production manager

The agency's invoice shows hours, and the gate shows entries and exits. Until someone has settled how these two relate, every month ends with a sheet of discrepancies. The practices below help the production manager keep records in a way that makes the gate statement a useful proof, agreed with the agency.

3
maximum number of merges after which the result moves to the active account
Source: feature card
20 days
attendance days in a month in the sample calculation
Source: sample calculation

First the definition: presence is not working time

The production manager is responsible for people being where they should be, not for interpreting the agency contract. Even so, his data goes into the billing, so it is worth knowing one principle: presence on the plant site according to gate records is not the same as working time. The difference covers breaks, the walk to the workstation, changing clothes and briefings.

A consistent definition of billing must be set in the contract with the agency. In the sample calculation we take an attendance day as a day with an entry and an exit, and any correction of working time is agreed with the agency separately. The lack of this definition is the main source of monthly disputes.

Practice 1: every entry and exit has a record

Recording an entry or exit from the panel creates a gate record, so the person appears on the On site list and on the evacuation list. The same record is the basis of the statement for the agency, which is why a missing exit record damages two things at once: the evacuation list and the invoice.

Practice for the shift: at the end of the day, the supervisor or security reviews the On site list, and for people who left without a record, adds the exit with an appropriate note. The task takes a few minutes and saves dozens of explanations at the end of the month.

Sample calculation: days with a complete entry and exit record (20 days, 40 people)

Sample calculation: days with a complete entry and exit record (20 days, 40 people)Bar chart: 88 percent of complete days without a review and 98 percent with a daily review of the list.020406080100%Without a daily review: 88 %88 %Without a daily reviewWith a daily review of the list: 98 %98 %With a daily review of the list
Source: Sample calculation: our own assumptions about missing exits

Practice 2: KD system events only where they exist

If the plant has an access control system, card swipes can be passed to InnerWeb as events, and InnerWeb links them with qualifications, permits and attendance. InnerWeb does not sell readers or cards: it uses the infrastructure the plant already has. For agency workers without their own cards, the QR code takes their place.

Good practice: do not mix two sources in one statement without marking them. If some people swipe a card and others scan a QR code, the statement should show a column with the type of event, so the agency knows where each entry comes from.

Practice 3: duplicate and merged accounts

Records fall apart when the same person has two accounts, because the hours split across two people. A training result recorded on a duplicate account that is later merged is transferred to the active account, for up to three merges, rather than being lost with the deleted account. For the production manager the conclusion is simple: report duplicates to the administrator straight away, and review the statement for the month in question after the merge.

It is also worth remembering people without a password: they stay on the invitation list with the No password label, so their entries do not disappear from the records, even if registration was never completed.

Practice 4: an agreed statement by the 5th day of the month

Agree a rhythm with the agency: the statement of entries and exits for the previous month goes to it by the 5th day, the agency raises comments by the 8th, and the invoice comes after agreement. These dates are examples and depend on the contract. The statement has a fixed structure: person, day, entry, exit, type of event.

It is also advisable to agree a rule for a day with an entry but no exit. The simplest rule: the day is recognised once the supervisor explains it within two working days, otherwise the statement marks it as unconfirmed.

  • fixed structure of the statement for each agency
  • marking the type of event: KD card or QR code
  • list of unconfirmed days to be explained
  • one person responsible for agreement on the plant side

Checklist

Video

Frequently asked questions

Can working hours be counted from gate records?

No, because presence on site is not working time. The statement shows the days and hours on site, and the billing definition is set by the contract.

What about workers who do not have a card?

For them the record comes from a scan of the QR code or from an entry recorded from the panel.

Who corrects a missing exit?

The supervisor or security adds the exit with a note. The plant's procedure sets the rules.

A gate statement that can be agreed

We will show what the On site list and the entry statement look like for one agency and match the structure to your billing.

Let's talk