Create and track the PO
Purchase Order Lifecycle focuses on purchase order creation, status updates, vendor invoice, payment, and closeout. In AWRA, procurement work is strongest when the need, supplier decision, approval, purchase order, receiving evidence, and payment context remain connected.
The practical goal is to buy with discipline. Users should know who requested the purchase, why it is needed, which supplier path is being used, and what evidence will make the decision defensible later.
In practice, a PO moves from created to acknowledged, partially received, invoiced, paid, and closed with each state visible.
PO lifecycle
Create
PO is generated from award or request.
Acknowledge
Vendor confirms the order path.
Receive
Goods or services are recorded.
Invoice and pay
Vendor invoice and payment proof are attached.
Close
Open issues are resolved.
Procurement model
- Procurement records should preserve source need and decision context.
- Approvals, RFQs, quotations, POs, and receipts each answer a different control question.
- Supplier and item data quality affect every downstream procurement report.
- Evidence makes buying decisions reviewable instead of personal.