Inside the platform
In a small business the owner knows everything, but when management spreads across branch managers and department heads three needs appear: that approvals reach the people who own the decision, that each manager has their own limit, and that the run is visible to whoever reviews it before it is approved. This page explains how TAC HR meets each of them, what the company sets, what the system works out and what goes beyond this size, so before you start you know how it will look with your branches.
01
Who approves what
Each request type in your company has a route edited from the approval sequence screen. You pick approvers from three places: an admin group, a named user, or the employee's direct manager, who is resolved from their file at the time of the decision. Then you set whether they approve in sequence or in parallel, and add observers who see the request without deciding. A request pins its route when it is created, so editing the sequence does not move a request already under approval. An approver can delegate their decision to a colleague who holds approval. Alongside the ready-made types the company adds its own, every request has a chat with attachments, and when it ends it moves to the requests archive.
02
A limit for each manager
An admin account is given a scope of one or more branches or departments, and branch and department combine with an or: whoever is assigned to the Jeddah branch and the Finance department sees the staff of either. An empty scope means the whole company, which belongs to the holder of the full permission. The company creates admin groups with their permissions and copies and edits them, and every change goes through one audit entry point with who did it and what it was before and after. Run visibility is a separate choice: all admins with the permission, or only the approval chain's members, its creator and the system admin, and the payment permission does not bypass it.
03
Automatic approval with limits the company writes
The request types screen has an automatic approval within limits table: each type has its unit, so days for leave, minutes for early leave and overtime, an amount for loans, allowances and bonuses, and a count for the rest. A rule has a per-request limit and a monthly limit per employee, and it is off for every type until you switch it on. Suppose a limit of two days a request and four days a month: a two-day request is approved at once, then one day is approved, then another two-day request goes to the approver as usual with a notice stating the limit, what was used and what remains. A request is never rejected, only referred. And seven sensitive types never enter a rule however one is written for them.
04
A run that whoever you name reviews
The run draft is created automatically on a day the company sets, reading attendance, lateness, overtime, loans and approved requests and writing every line with its formula. You choose its approval chain, so HR and finance review it together before it is approved. GOSI shares are worked out by each employee's system and the period's date, so someone on the previous system has 9.75% withheld and someone on the new one 10.75% in October 2026. The run line keeps the employee's branch at the moment of calculation, so the cost report groups the month by branch. After payment the run locks, and the wage file comes out as a detailed table after the IBAN check, with a journal entry carrying your account codes.
05
Branches with their boundaries and shifts
Each branch has a name, a city and a boundary drawn on the map as a circle or polygon, and it has payroll settings that override the company's and are overridden by the employee's own file. Shifts are defined centrally with start and end times, a lateness grace and days off and assigned to staff, so lateness is counted on each employee's own shift. Each employee has a punch place that overrides the company's: their own branch only, several branches you choose, or all branches, so whoever covers another branch punches there with no transfer request and the branch name is recorded in their attendance. Someone who moves for good raises a location change request that goes through the route, and earlier punches stay as recorded.