Procurement in a CAFM system starts when a technician realises a part is needed and ends when a vendor gets paid. Eight steps, four roles, multiple approval gates. Design it cleanly and it becomes background noise. Design it poorly and you spend your week expediting POs.
The eight-step workflow
- Purchase Request (PR): Supervisor raises need based on work order or stock replenishment.
- PR Approval: FM Engineer reviews and approves technical scope.
- RFQ & Quotations: Procurement issues RFQ, receives vendor responses, evaluates commercially.
- PO Creation: Procurement creates PO based on selected vendor.
- PO Approval: Finance and/or senior management approves based on value thresholds.
- PO Issued to Vendor: Approved PO sent to supplier.
- Delivery & GRN: Materials received, inspected, Goods Receipt Note created.
- Payment Processing: Invoice matched to PO + GRN, payment processed through finance system.
Who does what
Supervisor
Creates PR from maintenance need
FM Engineer
Approves PR, validates technical scope of quotations
Procurement
RFQ, vendor management, PO creation, commercial evaluation
Finance
PO approval, budget compliance, payment processing
PO approval matrix
Value-based approval thresholds prevent everyone having to approve everything:
| PO Value | Approvers |
|---|---|
| Up to AED 2,000 | FM Engineer + Finance |
| AED 2,000 – 50,000 | FM Engineer + Finance + General Manager |
| Above AED 50,000 | FM Engineer + Finance + GM + Board |
Adjust thresholds to your organisation. The principle is the same: higher value = more approvers = slower but safer.
PO types
- Standard PO, one-time purchase for specific items or services.
- Blanket PO, framework agreement for recurring purchases over a defined period.
- Service PO, outsourced services with defined scope and deliverables.
Linking procurement to work orders
The key design decision
Every PR raised for a maintenance need should reference the originating work order. This lets you track total cost per work order (labour + parts + external services) and calculate true maintenance cost per asset. Without that link, procurement spend and maintenance cost live in separate reports and never reconcile.
GRN and three-way matching
When materials arrive:
- Store Keeper receives delivery, verifies against PO (quantity, quality, spec).
- GRN created in CAFM linking to PO reference.
- Partial delivery creates partial GRN; PO remains open until fully received.
- Rejected items flagged, vendor notified.
- GRN data syncs to finance system for three-way matching against invoice.
See Three-Way Matching: PO + GRN + Invoice for the matching logic.
Common workflow issues
- Verbal PRs. Supervisor calls procurement to "rush this one through", breaks audit trail.
- Skipped RFQs. "We always use this vendor", fine once, dangerous as policy.
- POs without work order linkage. Cost attribution becomes guesswork.
- Ghost GRNs. Invoice arrives, someone creates a GRN retrospectively to unlock payment. Control failure.
- Value thresholds never updated. Inflation happens. AED 2,000 in 2010 is not AED 2,000 in 2026.
Conclusion
A clean procurement workflow is the glue between maintenance operations and finance. When PR, PO, and GRN are linked to work orders and synchronised with finance, maintenance cost becomes measurable, auditable, and honest. Get this workflow working end-to-end and half of your reporting problems disappear automatically.
Written by Muhammad Abbas
Enterprise integration specialist. Designed procurement workflows for multi-site FM operations.
