Maintenance and Repair Invoices
How maintenance and repair invoices are coded and verified in AP, the capitalisation boundary between maintenance and improvement, and the high exception rate that makes maintenance invoices an AP challenge.
Maintenance and repair invoices are among the most common invoice types in industrial businesses -- manufacturing plants, mining operations, construction equipment fleets, and commercial properties all generate significant and ongoing maintenance spend. They are also among the most challenging to process correctly, because the coding decisions are more nuanced than most expense categories and because maintenance work is often reactive and poorly documented compared to planned procurement.
A maintenance invoice from a trade contractor may arrive without a purchase order (because the work was requested verbally in an emergency), with a vague service description ("repairs to Plant 3"), for a job that was done over two shifts spread across a weekend. Verifying this invoice requires: confirming with the maintenance team that the work was done and the quoted hours are reasonable, checking whether a purchase order should have been raised and was not, coding the cost to the correct plant or equipment, and making a judgment about whether the repair extended the asset's life (capitalise) or maintained it in its existing condition (expense).
Planned vs reactive maintenance
Planned maintenance -- scheduled servicing, periodic inspections, preventive maintenance programs -- is processed with more documentation and predictability than reactive maintenance. Planned maintenance work should have a work order or maintenance plan reference, a pre-approved scope, and an expected cost range. These parameters allow the AP team to verify the invoice against the plan and flag variances. The three-way match concept applies to planned maintenance even without a traditional purchase order: the work order is the equivalent of the PO, the maintenance completion record is the equivalent of the GRN, and the invoice is the invoice.
Reactive maintenance -- emergency breakdowns, urgent repairs, unplanned replacements -- almost never has a purchase order or work order. The AP team receives an invoice for work that was urgently authorised verbally and learns about it for the first time when the invoice arrives. The best practice in this situation is a fast-track verification process: a quick confirmation from the maintenance manager that the work was done and the cost is reasonable, followed by normal coding and approval. Requiring a full PO process for emergency repairs is impractical and damages supplier relationships; having no verification at all creates an obvious fraud pathway.
Related terms
See it in action
Maintenance Invoice Automation