You know your margin.
Do you know which contracts earn it?
In most manpower businesses the cost side is computed in payroll and the revenue side is raised in accounting, and the two are joined once a year by someone with a spreadsheet. Which means the blended number is knowable and the per-contract number is not.
Here both come from the same approved roster day. Wages actually paid, employer statutory cost as computed, deductions as taken, against the invoice raised at that contract's rate card.
Three reasons your contract margin is an estimate
Why traditional manpower financial reporting hides structural client losses.
1 · The cost side is assumed
Employer statutory cost is applied as a flat percentage, because pulling the real figure per worker per contract is too much work by hand. The assumption is close on average and wrong on every individual contract.
2 · The revenue side is disconnected
Invoices are raised in an accounting package from a figure assembled separately, so revenue cannot be joined back to the workers who generated it.
3 · The leaks are invisible
Overtime, unfilled posts, client deductions and statutory pass-through gaps each move a contract's margin, and none of them appears as a line anyone reviews monthly.
A blended margin tells you the business is profitable. It does not tell you which client to renegotiate, which site is losing money, or which renewal to walk away from. Those are the three decisions that actually change the number.
The cost side is computed, not estimated
Because payroll and billing read the same record, the cost attributed to a contract is what that contract's workers were actually paid — not a rate applied to a headcount.
| Cost Component | Attributed Source |
|---|---|
| Wages | As paid, per worker, per day, at the client site worked. |
| Overtime and allowances | From the approved muster, computed at the applicable statutory multiplier. |
| Employer statutory cost | PF, ESI, LWF, and bonus as the payroll run computed them — not a flat percentage assumption. |
| Gratuity provisioning | As provisioned, with continuous service held against the worker rather than the deployment. |
| Deductions and credit notes | Attributed directly to the contract that took them. |
A hard-coded employer PF rate overstated one real tenant by roughly seventeen times. That is why cost rates in this platform are derived from actual payroll rather than typed in as an assumption. A margin computed on an assumed statutory rate is a margin computed on a guess.
Margin, broken down the way you actually manage
Granular dimensions computable directly from the underlying approved muster and billing records.
The account-level commercial conversation across all facilities.
Where annual renewals and rate card revisions actually happen.
One client, several plants — identifying the one losing money.
Guarding vs housekeeping margins under integrated contracts.
Historical margin trends and the exact month a wage change hit.
Per-worker traceability: Every summary figure drills down to the underlying named workers, shifts, and invoice lines. All views support 1-click CSV and Excel export.
All four are computable. None of them is currently visible to you monthly.
Recovering profitability by exposing margin leakage before year-end accounts close.
Overtime concentration
Overtime is billed and paid, but its impact depends on your rate card multiplier versus statutory double overtime. Computed directly from site muster hours.
Unfilled posts
A contracted headcount you did not fill is revenue not earned, plus potential SLA penalties. Shortfalls are measured against contractual commitments.
Client deductions
Absenteeism and SLA deductions recorded against invoice lines with reasons. A contract with routine deductions is completely different from its rate card.
Pass-through gaps
Where contracts pass through statutory costs, recovered amounts are reconciled against actual liabilities. Unbilled revisions are immediately flagged.
A minimum wage notification is a repricing event, not a payroll event
How state statutory gazettes impact contract economics immediately.
A state revises its notified minimum wage. Your cost base moves immediately for every worker at every site in that state. Your client rate cards do not move at all.
Because the wage engine resolves the applicable floor per state, zone and skill category, and because each contract's costs are attributed per site, the affected contracts are identified with the cost delta computed per worker — rather than discovered when the quarter closes.
Whether you absorb it or take it to the client is a commercial decision. The point is making it in the month it happened, with a real number.
Three conversations this changes
Direct operational utility for leadership.
The renewal
Entering a rate renegotiation knowing the contract's actual historical margin, including overtime and deductions, rather than your original quote assumption.
The unprofitable site
One client, twelve facilities, and two of them structurally lose money because of shift patterns or a local wage zone. That is a site-level conversation, not an account loss.
The bid you should not win
Knowing what rate you can quote profitably at one location versus another because the minimum wage zone and skill mix differ. Knowing which is which before you bid.
What this is not
We state our operational boundaries plainly so you can evaluate the platform with confidence.
- This is not a business intelligence platform. No custom report builder, no drag-and-drop dashboards, and no cross-domain data modelling. It reports on your workforce, contracts, and invoices — nothing else.
- This is not a bid or quote pricing engine. It does not auto-generate tender bids. It provides the empirical cost history of comparable contracts as your decision input.
- We do not do scenario modelling or what-if analysis. We compute what actually happened off approved records, not simulated futures.
- We do not forecast margin. The figures represent completed operational runs, not future projections.
- We do not benchmark you against the industry. We hold no cross-tenant dataset that would make such comparisons honest, and we will not manufacture synthetic benchmarks.
- We do not include your overheads. Contract margin here is contribution against direct workforce cost. Office, management, transport, and financing overheads are not allocated because we do not hold them. Your accountant does that work.
- This is not an accounting system.No general ledger, no P&L, no statutory reporting. We integrate with Zoho Books and Tally Prime to post invoice data.
- There is no AI layer here. This module computes; it does not interpret or speculate. We state that plainly rather than imply artificial intelligence that is not load-bearing.
- India only. Specifically built for Indian labour laws, minimum wage notifications, and statutory compliance.
Cost attribution, overheads and reporting answers
Reconcile one month and see the real number
Send one month: your deployed roster with client sites, that month's payroll register, one client invoice, and your PF and ESI challans. We reconcile billed days against paid days per client site, test wages against the notified floor for each site's state and skill, and show you the contribution position for that contract with the cost side computed rather than assumed.