A living purchase order is a PO that keeps updating as reality changes.
The old purchase order is a static document. You create it, send it, and hope the rest of the business remembers what changed afterward.
The living purchase order is different. It starts as an order request, but it keeps absorbing the supplier conversation, price changes, substitutions, partial shipments, receiving events, invoice IDs, payment status, and inventory updates.
That is the core object in closed-loop procurement.
It is also the object that makes upstream reconciliation possible. In a static PO workflow, AP waits until the invoice arrives and tries to match the original PO, receiving record, and invoice after the order has already changed. In a living PO workflow, the supplier and PO creator reconcile changes when the supplier replies, the receiver reconciles what arrived against the supplier-confirmed state, and supplier AR reconciles the invoice against the current order before AP is asked to pay.
The goal is not to remove accounting control. The goal is to make AP the final checkpoint instead of the first person trying to discover what happened.
Quick answer
A living purchase order is a purchase order that remains the shared commercial record after it is sent. Supplier confirmations, price changes, substitutions, ETA changes, partial shipments, receiving events, invoice IDs, payment status, and accounting handoff update the same object instead of scattering across email, receiving, and AP.
That is why living POs matter: they let teams reconcile upstream before AP has to investigate.
Static PO vs living PO
| Static PO |
|---|