ERP for Facility Management: Contracts, PPM, SLAs & Billing
By Vikas Saroj, ERP, Digital Transformation & Growth Consultant
Key takeaways
- ERP for facility management connects service contracts, planned preventive maintenance, reactive work orders, field technicians, SLA tracking and billing so every job is invoiced against the right contract.
- Model each contract first, including sites, assets, scope, PPM frequencies, SLA definitions, billing model and inclusions and exclusions, because unflagged out-of-scope work is where revenue leaks.
- An accurate, tagged asset register is the foundation of PPM; schedules generated from an incomplete register produce false compliance figures.
- SLA clocks need contract-specific rules for business hours, pauses and holidays, and escalations should trigger before a breach rather than after it.
- Chargeable jobs should flow straight into a billing queue with job sheets, photos and signatures, and labor, parts and subcontractor costs recorded per contract reveal true contract profitability.

ERP for facility management connects service contracts, planned preventive maintenance (PPM), reactive work orders, field technicians, SLA tracking and billing, so that every job is scheduled, completed, evidenced and invoiced against the right contract. The core question a facility management (FM) company needs its system to answer is: for each contract, are we meeting our obligations, and are we making money doing it?
FM businesses often run on a patchwork: a helpdesk tool for tickets, spreadsheets for PPM schedules, paper job sheets, and an accounting package for invoicing. Each piece works on its own, but nobody can see contract profitability or SLA performance without manual consolidation. This guide covers what an FM-focused ERP should handle.
Contracts as the foundation
In facility management, the contract defines everything: which sites and assets are covered, what services are included, response and resolution times, what is billable on top, and how pricing works. Model it properly in the system before anything else.
A well-structured contract record includes:
- Client, sites and buildings covered.
- Asset register per site, or reference to it.
- Scope of services: hard services (HVAC, electrical, plumbing, fire systems), soft services (cleaning, security, landscaping) or both.
- PPM frequencies per asset type.
- SLA definitions by priority level.
- Billing model: fixed monthly fee, per-visit, time and materials, or a combination.
- Inclusions and exclusions, such as parts covered up to a limit, or labor included but materials chargeable.
- Start date, renewal date and any escalation terms.
The inclusions and exclusions are where revenue leaks. If a technician replaces a part that is outside contract scope and nobody flags it as chargeable, that cost is absorbed. The system should make chargeable work visible at the point the job is closed.
Asset register
PPM depends on an accurate asset register: each chiller, AHU, pump, fire panel, lift or generator, with its location, make, model, serial number, install date and maintenance history. Building this register is often the most labor-intensive part of an FM implementation, especially when taking over a new contract from a previous provider. Plan site surveys with asset tagging (QR codes or barcodes) so technicians can scan the asset when they work on it.
Planned preventive maintenance
PPM schedules generate work orders automatically based on frequency (monthly, quarterly, annually) or, for some assets, runtime or meter readings. Each PPM task should carry a checklist that reflects the maintenance standard you work to, so technicians follow a consistent procedure and record readings.
Practical points for PPM setup:
- Group tasks by site and technician skill to reduce travel and visits.
- Allow scheduling windows rather than fixed dates, so planners can balance workload.
- Track PPM compliance: scheduled versus completed on time, by contract and site.
- Capture defects found during PPM and convert them into reactive jobs or quotations.
PPM compliance reporting is often a contractual requirement. If it is produced by hand each month, it is a strong candidate for automation.
Reactive work orders and the helpdesk
Reactive jobs come from client calls, emails, a client portal, or defects found during PPM. Each request should be logged with site, asset, priority and description, and assigned an SLA clock automatically based on the contract and priority.
| Stage | What the system should capture |
|---|---|
| Logged | Requester, site, asset, priority, description, photos |
| Assigned | Technician or team, based on skill, location and availability |
| Attended | Arrival time on site, used for response SLA |
| Resolved | Work done, parts used, time spent, before and after photos |
| Closed | Client sign-off, chargeable flag, feedback |
Escalations should trigger before an SLA is breached, not after. A notification to the supervisor when a job reaches a set share of its response window gives time to act.
Field technicians and mobile
Technicians are the main users of an FM system, and if the mobile app is clumsy, data quality collapses. A good field app lets technicians:
- See their assigned jobs, with site address, access notes and asset history.
- Record arrival and completion, ideally with location stamps.
- Complete checklists and readings.
- Take photos and capture client signatures.
- Request or record parts used from van stock or the store.
- Work offline in plant rooms and basements with no signal, syncing later.
Van stock is worth tracking as its own location. It shows what parts are with each technician and ensures materials used on jobs are recorded, which matters for both cost and billing.
SLA measurement
SLAs are usually measured on response time (how quickly someone attends) and resolution time (how quickly the issue is fixed), by priority. Decide how the clock behaves: business hours or round the clock, whether it pauses while awaiting client approval or parts, and how public holidays are handled. These rules differ by contract, so the system needs to support contract-specific SLA calendars. Agree definitions with clients up front, because disputes about SLA reports usually come down to how the clock was measured.
Billing
FM billing typically combines recurring and variable elements:
- Recurring contract fees, invoiced automatically each period.
- Chargeable reactive work: labor and materials outside contract scope, billed at contract rates.
- Quoted works: larger repairs or replacements, approved by the client and billed on completion.
- Penalties or service credits where SLAs are breached, if the contract includes them.
The link between job completion and billing is critical. Chargeable jobs should flow straight into a billing queue with supporting evidence (job sheet, photos, signature), so finance can invoice without chasing operations for details.
Contract profitability
When labor time, parts, subcontractor costs and revenue are all recorded against contracts and sites, you can finally see which contracts make money. That visibility helps with renewals, pricing new tenders and deciding where to change staffing. It requires discipline: technicians' time must be recorded against jobs, and shared costs need an agreed allocation method.
Subcontractors and specialist services
Most FM providers subcontract some services, such as lift maintenance, fire suppression, pest control or specialist HVAC work. Those jobs still count toward your SLA with the client, so subcontracted work orders should sit in the same system, with the subcontractor's attendance and completion recorded, their certificates and insurances tracked, and their invoices matched to completed jobs. Otherwise you are accountable for performance you cannot see.
Implementation tips from FM projects
- Pilot with one contract that is representative but not your most complex, then roll out contract by contract.
- Survey assets before go-live. PPM generated from an incomplete asset register creates false compliance figures.
- Involve technicians in app design. A few field trials will reveal problems that office workshops miss.
- Standardize priority definitions across contracts where possible, while allowing contract-specific SLA times.
- Agree the client reporting pack early, since it often drives what data must be captured on every job.
Platform and integration choices
Some FM companies use a dedicated CAFM or field service tool connected to their ERP; others build FM workflows on a configurable platform such as Zoho or Odoo. The right answer depends on contract complexity, technician numbers and existing systems. Key integrations include accounting, payroll, client portals and, in some cases, building management systems for automatic fault alerts. See my system integration work and the business process automation guide for related approaches.
Next steps
If your PPM compliance reports, SLA tracking or chargeable work billing depend on spreadsheets, there is usually a clear path to bring them into one system. I help FM providers map their contract-to-cash process and implement the right platform through ERP consulting. Get in touch to discuss your contracts and current tools.
Frequently Asked Questions
What is PPM in facility management?
Planned preventive maintenance is scheduled maintenance carried out at set intervals or based on usage, such as quarterly HVAC servicing or annual fire system inspections. An FM system generates PPM work orders automatically from the asset register and contract, and tracks whether each task was completed on time.
How should SLAs be measured in an FM system?
Typically on response time and resolution time by priority level. The system should use contract-specific calendars and rules, including whether the clock runs outside business hours or pauses while waiting for client approval or parts. Agree these definitions with each client before go-live.
Do FM companies need a separate CAFM tool and ERP?
Not necessarily. Some use a dedicated CAFM or field service tool integrated with their ERP, while others configure FM workflows within a single platform. The choice depends on contract complexity, number of technicians, client portal needs and how much customization the business can maintain.
How can FM companies stop losing revenue on chargeable work?
Flag chargeable work at job closure based on contract inclusions and exclusions, and route those jobs straight into a billing queue with job sheets, photos and client signatures attached. That removes the manual chase between operations and finance that lets billable work slip.