Purchase Order
A Purchase Order (PO) in maintenance is a legally binding document sent to a vendor, specifying item quantities, pricing, delivery timeframe, and payment terms for procuring spare parts, tools, or external services. In CMMS systems like ServiceGrid, POs are generated from work orders, linked to assets and cost centers, and tracked through status workflows to ensure inventory updates and financial traceability.
In shop floor maintenance, POs are essential for procuring spare parts, tools, and external services needed to keep equipment operational. They are often generated directly from work orders or requisitions, linked to the asset, cost center, and required-by date. POs are tracked through status workflows (draft → approved → sent → received) to ensure inventory updates and financial traceability. This integration streamlines procurement, reduces downtime, and provides end-to-end visibility from maintenance request to vendor payment.
- PO–Invoice mismatch: Vendor invoices do not match PO line items (quantity/price), causing payment delays or rejected invoices without proper amendment or three-way match reconciliation.
- Unlinked POs to work orders: POs created without association to a work order or asset lead to cost misallocation, lost traceability, and budget overruns on specific maintenance tasks.
- Delayed receipt recording: PO fulfillment is not updated in the CMMS when parts arrive, so stock levels remain inaccurate, causing planned downtime due to missing spare parts.
How does a PO differ from a work order in CMMS?
A work order directs internal maintenance execution (what to fix, who, when); a PO authorizes external procurement (what to buy, from which vendor, at what cost).
What is the “three-way match” in PO management?
It is the accounting control that reconciles the PO, the vendor invoice, and the receipt/proof of delivery to ensure payment accuracy before vendor payment.
Can a PO be used for contractor labor?
Yes; POs can authorize external services, but variable deliverables may require additional service contracts or agreements alongside the PO.
What fields auto-populate when a PO is generated from a work order?
Typically asset ID, work order number, cost center, required-by date, part number, quantity, and vendor address are auto-populated to eliminate re-keying.
Where does a PO “live” in the enterprise system architecture?
POs primarily reside in the ERP procurement module, but modern CMMS (like ServiceGrid) can create, track, and link them to maintenance workflows for end-to-end visibility.