A security officer covers an absence at a different client site. Their hours and premium are paid correctly, but the shift stays coded to their home cost centre. Payroll is right. But both contract P&Ls are wrong.
One contract carries labour it never used. The other receives cover that shows up nowhere. Closing the pay run closes neither problem.
And this isn’t a one-off. Research has found that 84% of Facilities Management and real estate leaders cited budget constraints and rising costs as a top concern, while 81% named cost efficiency as a leading priority. For FM providers, delivering that efficiency depends on knowing where labour cost sits, so a payroll run that pays everyone correctly can still get that wrong.
In fact, Deloitte and the National Payroll Institute’s 2026 research found that pay errors most often start before payroll ever sees the data, in areas like time and attendance, exactly where this kind of misallocation begins.
Which is exactly why facilities management workforce management, done well, keeps four records aligned: employee pay, contract cost, client billing and evidence of delivery. When those records pull apart, a clean payroll can hide a material contract error.
Key takeaways:
|
The payslip can be right while the contract P&L is wrong
Payroll only answers one question, whether the employee got paid the right amount. A Facilities Management contract needs two more answers on top of that. Did the cost land on the contract, site and service line that used the labour? And can the provider prove to the client that the work happened, so it’s allowed to bill for it?
Here’s where it breaks. A site manager agrees a genuine variation over the phone, an extra two hours to cover a client’s urgent request. The engineer works it, and payroll pays it correctly. Nobody logs the variation against the contract. The hour ends up worked, paid, and completely unrecoverable. No operational mistake was made anywhere in the chain. There is no record connecting it to client authorisation, because payroll was never built to ask for one.
Multiply that across a contract portfolio and it corrupts the number contract directors watch most closely, cost-to-serve. A contract can show rising cost-to-serve for months while the real driver is unbilled variations sitting outside the system, with no overspend behind it at all. That distorted figure still gets used to defend margin in a client review, price next year’s renewal, or justify pulling resources from a site that was never the problem.
Where facilities management payroll errors become contract errors
People cross sites, services often share a single location, and cover gets arranged after the rota is published. On top of that, mobilisations introduce employees protected by TUPE rules, sometimes with terms that differ from colleagues doing similar work.
Here’s what that looks like day to day. Five situations where the hours are recorded correctly and the contract still loses money:
| What happened on the contract | What payroll may see | What the contract loses |
| A cover manager pre-approves overtime for a seasonal push at one site | Overtime paid at the standard premium rate | No link to the seasonal rate clause agreed with the client |
| A relief officer covers another site | Correct hours and premium | Labour defaults to the officer’s home contract |
| An engineer attends an out-of-hours call-out | Worked time plus an allowance | Standby, travel and job time follow different allocation rules |
| A TUPE employee works beside a colleague on different terms | Two similar shifts | The correct rule may depend on the employee as well as the site |
| A porter moves between bundled service lines | One continuous attendance record | Cost and delivery evidence cannot be separated by service |
The last two rows point to something bigger. Mobilisation concentrates several of these risks at once, employee terms, site codes, approval routes and client rate cards often arrive from different owners on different timetables. So a wrong default at go-live can repeat every pay cycle, eroding margin for months before anyone traces it back to the transfer.
More broadly, the system can know who worked and for how long, and still lose which rules applied and who should bear the cost. That’s when a payroll discrepancy becomes a contract problem.
A payroll correction only fixes one version of the shift
Fixing one of these discrepancies only fixes what the person making the correction can see. If a manager supplies revised hours after cut-off, the additional payment may be processed correctly. But does the change also update job costing, the contract accrual, the supporting schedule and the client invoice? If not, the organisation now holds two versions of the same event.
Once the period has closed, more steps get added. The fix may need to trigger a cost transfer, revised evidence or a client credit and rebill. Payroll can close its ticket before that commercial clean-up has begun.
A year later, the contract comes up for renewal. The client’s procurement team pulls the historical cost data to negotiate the new rate, and the commercial team pulls the same data to defend it. Both sides are working from job costing. Neither side knows payroll corrected the underlying hours months earlier, because that correction never reached the report either side is now negotiating from.
This kind of split is showing up more often. KPMG’s 2025 analysis of financial close processes found material weaknesses rose again in 2024, with restatements hitting a nine-year high, evidence that mismatches like this are increasingly coming to light rather than staying buried.
One approved amendment should update pay, cost, billing and the audit trail together. Anything less means the correction only lives in one system, and everyone working from the others is still standing on the old number.
How payroll errors distort Facilities Management commercial decisions
Bad allocation changes how a contract’s whole performance reads, well beyond the one shift where it started. On fixed-price work, it can mask whether the delivery model is genuinely over plan. On open-book work, an unexplained labour line invites client challenge. On cost-reimbursable work, a legitimate cost becomes unrecoverable because its approval or evidence is missing.
Clients are already looking at this through a cost lens. CBRE’s 2025 UK facilities management survey found 77% of industry experts rank cost and value for money as the top driver of FM purchasing decisions. That puts the accuracy and transparency of labour costs inside every contract-review and renewal conversation, whether the provider raises it or not.
The distortion carries forward into decisions that have nothing to do with the original shift.
- Recovery plans target the wrong cause, fixing a process that was never actually broken.
- Forecasts repeat an unreliable labour baseline, so next year’s budget inherits this year’s error.
This is different from the direct labour leakage covered in our guide to contract margins. Here, leadership cannot tell where the leakage occurred, or even which contract owns it.
Why a delayed payroll correction costs more the longer it waits
Exceptions are inevitable. What determines the risk is how far each one travels before it’s caught.
- During the shift, the employee and site manager can still establish what happened.
- At approval, the difference needs a reason before sign-off.
- After payroll cut-off, the correction now has to reach job costing, the accrual and the invoice separately, or two versions of the same event start circulating.
- After month-end, it can surface in a compliance audit or client accreditation review, months after anyone still working there could explain what happened.
Every hand-off adds another owner, and another place for the correction to stall. That’s why the same mistake costs almost nothing on day one and a great deal by month-end.
Four questions to ask about your own contracts
Everything above compounds unless someone in the organisation can already answer these four questions.
- Can every paid hour in your operation be traced to the contract and service line that used it?
- When payroll corrects a shift, which other systems update automatically?
- How much labour sits in default or suspense cost centres after cut-off?
- Can contract teams tell the difference between a contract that’s genuinely losing money and one that’s just carrying someone else’s cost?
If answering takes several teams and several exports, the contract record is being rebuilt after the fact, every time someone asks. Every example above has been building to that same test.
How WFM answers all four
Here’s what happens when one system holds the answer instead.
Trace every hour to a contract
Intelligent scheduling records the employee, site, skills, hours and labour requirement. Cover stays attached to that requirement, instead of becoming an unexplained clocking or message trail.
Stop a correction from living in one system
Managers can use MiTime to view team status and process anomalies, while employees can see their own shifts and clockings. The site manager can resolve a disputed hour while the people involved can still explain what happened. From there, WFM applies the relevant rules before approved information moves into payroll, with integrations including Sage, IRIS, SAP and SD Worx removing the need to rekey it. Through job costing, that same corrected record stays connected to jobs, cost centres or budget codes and can feed finance and invoicing systems, so a fix made once reaches payroll, costing and the invoice together, not one at a time.
Keep labour out of suspense
Because scheduling, attendance and job costing share one record, hours only get coded to a contract or service line once, at the point they’re worked. Nothing waits in a default cost centre for someone to allocate it later, because there’s no separate allocation step to skip.
Separate real overspend from someone else’s cost
Payroll receives what should be paid. Commercial teams keep the data that shows where the cost belongs, so a contract carrying cost that started somewhere else can be identified correctly instead of logged as overspend.
Time and attendance captures all of this in real FM conditions, fixed terminals, mobile tools and shared devices covering secure sites, mobile teams and employees without company phones. Because WFM supplies the clocking hardware and the platform together, there’s one route for configuration, implementation and support.
WFM already runs this for a global facilities provider with thousands of frontline employees across hundreds of UK sites. One system for clocking, scheduling and absence feeds payroll directly, reducing manual corrections and month-end chasing.
If you are considering Facilities Management software options, this guide is worth a read: How to choose the best workforce management software.
A few things worth bearing in mind about the alternatives. App-first scheduling tools tend to struggle with secure sites, shared devices and complex UK pay rules. Payroll suites only get involved once the operational decisions have already been made. And hardware-only systems can tell you who’s on site, but nothing about the contract sitting behind them.
WFM brings all of that together instead. Configurable software, fixed and mobile clocking, payroll and job-costing integration, implementation and UK-based support, all under one roof.
Protect the contract before payroll closes
For an FM provider, the payroll result is only complete when the employee’s pay, the contract cost and the evidence of delivery agree.
WFM is built to run that whole operating chain across different sites and attendance methods, inherited rules, mobile teams and manager exceptions. Payroll integration and job-level allocation keep the approved record moving without rebuilding it downstream. Operations, payroll and commercial teams work from one governed account of what happened.
Bring us a difficult example from your own operation, such as cross-site cover, a TUPE rule or a retrospective correction. In a tailored WFM demonstration, we will show how it moves from rota to attendance, approval, payroll and job costing.