Inside the platform
In retail, HR is spread across points of sale, each with its own manager and opening hours, and head office sees a branch only through the paper that reaches it, so the full picture lags by days and an absence reaches sales before the record. So TAC HR is built around the employee and the branch together: one file for the employee, a branch assigned to them that can be several, a punch accepted by the boundary of the branch where it was made, and a shift that suits that branch's opening hours. The run reads the attendance, overtime and approved requests that were recorded. This page explains how that runs in a business managing many branches, and what stays outside the system.
01
Every branch has its boundary and its shift
Every branch in the system has a name, a city and a boundary drawn on the map as a polygon or a circle, and it has payroll settings that override the company's and are overridden by the employee's own file. At the punch the system checks the phone's coordinates against the boundary: inside it the punch is accepted and attributed to the branch, and outside it the punch is rejected with a message naming the nearest allowed site and the employee's distance from it, and admins see the attempt on the web. Before every punch the app inspects the device, rejecting spoofed locations, emulators and modified devices. Shifts are defined with start and end times, a lateness grace and days off, so the evening shift goes to the mall's staff and the morning one to the residential branch's, and lateness is worked out on the employee's own shift.
02
Whoever covers another branch
Covering leave and offers seasons means an employee works a week at one branch and a week at another. Each employee has a punch place setting that overrides the company's: only their assigned branch, or several branches you choose, or all of the company's branches, or anywhere. So whoever covers can punch at any allowed branch with no transfer request each time, and the branch they punched at is recorded and shown in the attendance sheet. Someone who moves to a new branch for good raises a location change request with the new branch chosen, or an admin who holds the on-behalf permission within their scope raises it for them, and it goes through the approval route while earlier punches stay in the sheet as recorded.
03
The branch manager, requests and alerts
An admin account can be given a scope of one or more branches or departments, so a branch manager works only on their branch's staff, while a holder of the full permission is not restricted. Each request type has an approval route that the company sets and edits: steps by role, by user or by the direct manager, sequential or parallel. So pre-season leave goes to the branch manager and then management, and so do permissions, early leave, forgotten punches and late removal. Whoever has not punched by the configured grace after their shift starts, 120 minutes by default, is flagged to their direct manager once a day, and whoever sees company-wide reports at head office gets a 07:00 summary with yesterday's absences, pending requests and expired documents.
04
The offers season and overtime
Before the offers season, branch hours grow beyond the shift's end. The overtime source is an explicit setting. Approved assignments only is the default, so only time approved through an overtime request is paid and its minutes are written to the attendance day when it is approved, while the attendance log option pays everything beyond the shift's end. Under the Saudi labour law model on basic pay, an overtime hour is paid at 1.5 times the normal hourly rate: a cashier on a SAR 3,600 basic has a normal rate of SAR 15.00 an hour, so ten approved hours appear on the payslip as a separate line with its formula, worth SAR 225.00. Lateness is deducted by the minute from the basic by default: an employee on a SAR 3,000 basic who arrives 18 minutes after their shift starts loses SAR 3.75.
05
The run and the documents
The run draft is created automatically on a day the company sets each month. It reads each employee's attendance, lateness, overtime, loans and approved requests and writes every line with its formula. The employee's branch is kept on their run line at the moment of calculation, so the payroll cost report groups the month by branch, and an employee moved mid-month is recorded at one branch in that month's run. Before export the wage file page checks IBANs, IDs and the company number, and alongside it come a journal entry with your account codes and a payslip on every employee's phone.