Why Attendance Is the Hardest Problem in Manpower Supply
A manpower supply or contract staffing company sells one thing: a verified person, at a client's location, for an agreed number of hours or days. Every rupee of revenue and every rupee of wage cost traces back to an attendance record. Yet the record is created somewhere the agency does not control, by a worker the agency sees a few times a month, under the eye of a client supervisor whose incentive is to dispute rather than confirm.
This is why agencies with 300 people across 25 client sites often spend the first ten days of every month reconciling. The client's gate register says 24 days; the agency's supervisor says 26; the worker says 27 including a Sunday. The invoice cannot go out until it is settled, wages get delayed, workers drift to another contractor, and the fill rate at that site drops. Fixing attendance capture fixes cash flow, retention and client trust at once.
The framework below works for housekeeping, security, industrial helpers, loaders, drivers, pantry staff and general contract labour. Security agencies have extra PSARA obligations, covered separately in our guide on billing clients for guard man-hours, but the attendance-to-invoice pipeline is the same.
- Revenue, wages and statutory liability all derive from one attendance record you did not create yourself
- Disputes are usually about days, not rates: the fix is a shared, timestamped record both sides trust
- Late reconciliation delays wages, which drives attrition, which drives no-shows, which drives more disputes
Deployment Records: Who Is Posted Where, at What Rate
Before any attendance is captured, each worker must be mapped to a client, a site, a role category and a shift. This deployment record is what turns a raw punch into a billable and payable event. Without it, a check-in at 08:00 is just a timestamp; with it, it is 'Ramesh, skilled category, Client A, Plant 2, general shift, bill rate per day X, wage rate per day Y'.
Keep the deployment record separate from the employee master. Workers move between sites, sometimes mid-month, and you need to bill Site A for 14 days and Site B for 12 without editing history. A good record has a start date, an end date (open if ongoing), the client purchase order or work order reference, the agreed monthly headcount and shift pattern, and the rate card for that client. Under the Contract Labour Act and the OSH Code, you also need a register of workers deployed per principal employer, so the deployment record doubles as compliance evidence.
Agencies running on WhatsApp and Excel typically keep this in the head of one operations manager. When that person is on leave, billing stops. Putting deployment into a system with site-wise views, such as the guard and staff deployment module in Attend Mitra's staffing agency solution, means anyone in the back office can see who is posted where today and what has been agreed with the client.
- One deployment record per worker per site posting, with start and end dates
- Link each record to the client work order and the applicable rate card
- Record the agreed headcount and shift pattern so shortfalls are visible daily, not at month end
- Keep the register of contract workers per principal employer that the Contract Labour Act and OSH Code expect
Capturing Attendance at Client Premises
The client controls the gate, so your attendance method has to work without client cooperation and still be acceptable to the client's own security. Three methods fit: a geofenced check-in on the worker's phone with a selfie, a QR code posted at the site that the worker scans, or a shared kiosk tablet at the client's time office. Fingerprint devices are rarely practical because you cannot install hardware on someone else's premises for a contract that may end in six months.
Whichever method you use, the record must carry three things: identity (selfie or face match), location (inside the site geofence), and time. A selfie with GPS inside a 150-metre geofence around the plant gate, timestamped at 07:56, is evidence a client supervisor finds hard to argue with. Set the shift's grace period to match the client's own late rule so your late marks and theirs agree.
Do not abandon the client's gate register; reconcile against it. Many principal employers keep their own muster of contract workers, and under the OSH Code they remain liable for unpaid wages, so they have every reason to check your numbers. A weekly comparison of your app attendance against their gate log, done by your site supervisor every Monday, catches problems while they are four days old instead of thirty. Attend Mitra captures selfie plus GPS attendance per site, supports offline check-in that syncs when the network returns (common inside factory compounds), and gives site supervisors a live view of who is present at each client location.
- Selfie plus geofence plus timestamp is the minimum evidence standard for a billable day
- Use QR or kiosk mode where workers share phones or have no smartphone
- Match grace and half-day rules to each client's terms, per site, not globally
- Reconcile your app records against the client gate register weekly, not monthly
Client Approval Before Billing
The single biggest cause of billing leakage is invoicing days the client will not accept. The cure is a sign-off step: before the invoice is drafted, the client's authorised person sees a site-wise attendance summary and approves it. The summary should show each worker, days present, days absent, overtime hours, national or festival holidays worked, and any replacements, in the same format every month.
Send the summary within two working days of the cutoff, give the client a fixed window (say three working days) to raise objections, and treat silence as acceptance if your contract allows. Where the client disputes a day, resolve it with the evidence: the selfie, the geofence result and the timestamp. In practice most disputes disappear when the client can see the selfie taken at their own gate.
Some clients want to see the data themselves rather than a PDF. A shareable report or an exported site-wise man-hour sheet works. Attend Mitra produces site-wise man-hour exports designed for client billing, so the same numbers that drive payroll are the numbers the client signs off, which removes the classic mismatch between what you paid and what you billed.
- Fix an attendance cutoff (for example the 25th or the last calendar day) in the client contract
- Send a standard site-wise summary within two working days of cutoff
- Set a three-working-day objection window; document silence as acceptance
- Resolve disputes with selfie, geofence and timestamp evidence, not with arguments
Wage Rate vs Bill Rate: Statutory Pass-Through
The bill rate a client pays is the worker's wage plus the statutory costs the agency bears plus the agency's service charge. Getting this structure explicit in the contract protects you when minimum wages revise, which in many states happens twice a year through variable dearness allowance. If your contract quotes a lump sum per head, every wage revision eats your margin; if it quotes wage plus statutory plus service charge, the revision passes through.
The statutory components you must build in are the employer's EPF contribution (12% of basic plus DA, with the wage ceiling now ₹25,000 per month from 17 September 2026), EDLI and EPF administrative charges, the employer's ESIC contribution (3.25% of gross for workers earning up to ₹21,000 per month in implemented areas), statutory bonus (minimum 8.33% of eligible wages for workers with basic plus DA up to ₹21,000 per month, calculated on a ceiling of ₹7,000 or the scheduled minimum wage, whichever is higher), labour welfare fund where the state levies it, and provisions for gratuity and leave encashment. Our guide on statutory bonus calculation walks through the arithmetic.
GST on manpower supply services is charged at 18%. Most manpower supply is billed on a forward-charge basis, but security services supplied by a non-body-corporate to a registered business fall under reverse charge, and there are other situations where the recipient pays; confirm your position with a chartered accountant and reflect it correctly on the invoice, because the client's finance team will reject an invoice with the wrong GST treatment and that delays payment further.
- Quote bill rate as wage + statutory + service charge so minimum wage revisions pass through
- Build EPF (with the ₹25,000 ceiling), ESIC, bonus, LWF, gratuity and leave provisions into the statutory line
- Confirm the GST charge mechanism for your service category with your CA before invoicing
- Re-issue rate cards to clients whenever the state revises VDA
The Month-End Sequence: Cutoff, Sign-off, Payroll, Invoice
A predictable month-end sequence is what separates agencies that pay on the 7th from those that pay on the 15th. It runs: attendance cutoff on the agreed date; supervisor review and regularisation of missed punches within 24 hours; client summary sent by day two; client sign-off by day five; payroll run and payslips by day seven; invoice raised the same day; EPF ECR and ESIC contributions paid by the 15th of the following month.
The order matters. Running payroll before client sign-off means paying for days you may not bill. Invoicing before payroll means the invoice and the wage register can disagree, and the principal employer's auditors will notice. When both are derived from the same approved attendance, they cannot disagree. Attend Mitra's attendance-linked payroll derives LOP and overtime from the same records the client approved, produces payslip PDFs and a bank NEFT file, and exports site-wise man-hours for the invoice, so the sequence runs from one dataset.
Note that the Contract Labour framework expects the contractor to pay wages in the presence of the principal employer's authorised representative or to provide proof of payment. Bank transfers with a wage register and payslips satisfy this in practice and are what most principal employers now demand. The agency remains responsible for filing EPF and ESIC returns; attendance and payroll software prepares the data but does not file the returns for you.
- Cutoff, regularisation, client summary, sign-off, payroll, invoice, statutory payment: in that order
- Derive wages and invoice from the same approved attendance dataset
- Pay by bank transfer and keep the wage register and payslips as proof for the principal employer
- Diarise the 15th for EPF and ESIC payment; the software prepares data but you file
Compliance Expectations, Disputes and the KPIs That Matter
Principal employers are increasingly careful because the principal employer remains liable for wages, EPF and ESIC if the contractor defaults. Expect clients to ask for your labour licence (required at 50 contract workers under the OSH Code, 20 under the older Act where its rules still apply), your EPF and ESIC registration, monthly challans, the muster roll and wage register for their site, and wage slips. An agency that can produce these from its system in an hour wins renewals; one that scrambles loses them. Our guide on contract labour compliance for principal employers explains what the client side is checking and why.
When disputes reach a labour officer or a client audit, the evidence that settles them is the attendance record with identity and location proof, the deployment record showing the worker was posted to that site, and the wage register showing what was paid. Digital records with an audit trail carry more weight than a register with corrections in different ink.
Finally, run the business on three numbers. Fill rate: the percentage of contracted positions actually staffed each day, per site. No-show rate: the percentage of rostered workers who did not check in. Billing leakage: the difference between man-days paid and man-days invoiced. A site with a fill rate below the contracted headcount is a client at risk; a leakage above a couple of percent is margin you are giving away. Use the absenteeism rate calculator to benchmark sites against each other.
- Keep licence, registrations, challans, muster roll, wage register and wage slips ready per client site
- Digital attendance with identity and location evidence settles disputes faster than paper
- Track fill rate and no-show rate per site daily; track billing leakage monthly
- Treat a falling fill rate as an early warning of client churn, not just an operations issue

