Worker register
A register of the workers you supply, each with details and documents.
Supply labour as a business: deploy the people, prove the hours, bill the client.
Manpower ERP for companies that supply people — a worker register, client contracts, deployment and replacements, attendance that proves the hours, and billing that ties those hours to what the client pays.
A manpower business sells people, and its margin is the gap between what it pays a worker and what it bills the client for their time. That gap only holds if the hours are real. Farexa builds the operation around it: a register of workers, the client contracts they're supplied under, and attendance that proves who worked — so the hours that pay the worker are the same hours that bill the client, with nothing to reconcile between the two.
Deployment is the daily work. Workers are assigned to clients and sites, replacements are recorded when someone has to be swapped, and incidents on site are logged against the assignment rather than lost in a call. Attendance — time-stamped and located — confirms who actually turned up, and timesheets record the hours. Payroll runs against those same records, and client billing is built from them, so the whole loop from deployment to invoice references one set of facts.
That's what makes it a business system rather than a rota: the owner can see margin because pay and billing come from the same hours, the account manager can run contracts because deployment and billing are connected, and a dispute about what was worked has an answer in the system.
Key features
How Farexa maps to manpower supply.
Client contracts
The agreements workers are supplied under, anchoring deployment and billing.
Deployment and replacements
Assign workers to clients and sites, recording replacements when someone's swapped.
Attendance that proves hours
Time-stamped, located punches confirm who turned up, feeding both pay and billing.
Timesheets
Record hours worked on assignment, tied to the deployment.
Payroll on the same records
Payroll runs from the same attendance, so pay reflects real hours.
Client billing tied to hours
Billing connects worked hours to the client charge, so margin is visible.
Incidents on the record
On-site incidents are logged against the assignment, not lost in a call.
How it works
From worker register to visible margin.
01
Register workers and contracts. Build the worker register and set up the client contracts they're supplied under.
02
Deploy to clients. Assign workers to sites under their contracts, recording replacements as needed.
03
Prove the hours. Located attendance and timesheets confirm who worked and for how long.
04
Pay and bill from the same hours. Payroll runs on those hours, and client billing is built from them too.
05
See the margin. Because pay and billing share the hours, the gap between them is a visible number.
Who it's for
Who supplies labour with it.
- Manpower and staffing suppliers — Workers, contracts, and billing that tie labour cost to client charge.
- Security and guarding companies — Guards deployed to sites with proven attendance.
- Cleaning and soft-services firms — Crews supplied under contract with recorded replacements.
- Owners and account managers — Owners see margin; account managers run contracts and billing.
Works with
The app cluster for manpower.
- Manpower — The labour-supply business — register, contracts, deployment, billing.
- HR — The worker records the business is built on.
- Attendance — Located punches that prove the hours for pay and billing.
- Payroll — Runs on the same hours that bill the client.
- Analytics — Deployment, utilisation, and margin reporting.
FAQ
What labour suppliers ask.
How does it keep pay and billing consistent?
Both come from the same attendance. Located, time-stamped punches prove who worked, timesheets record the hours, payroll runs on those hours, and client billing is built from them too — so the hours that pay the worker are the hours that bill the client, with nothing to reconcile.
Can I track replacements and site incidents?
Yes. When a worker has to be swapped, the replacement is a recorded action against the assignment, and on-site incidents are logged against it — so cover and problems are on the record rather than in a phone call.
Does attendance work for people who aren't at a desk?
Yes. Punches carry their time and location, so they suit crews deployed across client sites — the punch records where and when it happened, which is exactly what a manpower business needs to prove hours to a client.
Can I see the margin on supplying labour?
Yes. Because pay and client billing are built from the same hours, the gap between what you pay a worker and what you bill the client is a visible number rather than something worked out later.
Which apps does a manpower supplier start with?
Usually Manpower and Attendance to get deployment and proven hours in place, then Payroll and Analytics so pay and margin run off the same records.
Run the supply business on proven hours.
Book a walkthrough with your own contracts and workers, and see attendance prove the hours that pay and bill.