Purchase Orders: Product Overview and Details Page
Last updated: August 18, 2026
Overview
The Purchase Orders module inside Procure-to-Pay gives your finance and procurement teams a unified view of every purchase order generated through Spendflo — including their current lifecycle status, line item details, linked bills, and ERP record.
In the P2P context, Purchase Orders play a critical upstream role: they represent the pre-approved spend commitment. When a supplier invoice arrives and a bill is created, Spendflo automatically checks whether the bill is backed by an open PO — and uses the PO's data to pre-populate GL codes, departments, and the spend owner on the bill.
Who Is This For?
Audience | What they do here |
|---|---|
Finance Executives / Admins | View all POs, check remaining balances, verify bills have been matched to the correct PO |
Approvers | Review PO match details on a bill before approving payment |
Spend Owners | Confirm or update the PO matched to a bill they own |
End Users (Requesters) | View POs generated from their own procurement requests |
Key Concepts
Term | Definition |
|---|---|
PO Number | A unique identifier for the purchase order, generated by your ERP (e.g. NetSuite) |
Remaining Balance | The unconsumed value of a PO — total PO value minus the sum of all bills already matched to it |
Open PO | A PO with a remaining balance greater than $0 and no bills matched yet |
Partially Matched PO | A PO with one or more bills already matched against it, with some remaining balance |
Fully Consumed PO | A PO with a remaining balance of $0 — no longer available for matching |
PO Match | The confirmed link between a bill and its corresponding PO, validated by AI and confirmed by an Approver or Spend Owner |
How POs Connect to the P2P Workflow
Purchase Orders are created upstream through Spendflo's procurement workflows (see the Purchase Orders documentation for how POs are generated from requests).
Inside the P2P module, POs are used in two ways:
GL enrichment on bill creation: When a bill is created and matched to a PO, the GL account, department, class, and location from the PO's line items are copied to the bill's line items automatically — reducing manual coding.
PO matching validation at approval: When an Approver reviews a bill, Spendflo shows which open POs from the same supplier could match this bill, ranked by AI match score. The Approver confirms the correct PO before approving the bill.
Purchase Orders Listing
Navigate to Procure to Pay → Purchase Orders in the left navigation to see all POs.
Once a PO is fully consumed, it is no longer available for matching and will not appear as a match option on future bills. If a bill arrives without a matching PO, or if the remaining PO balance does not cover the invoice amount, Spendflo flags the shortfall during the approval step. The approver is notified to resolve the gap before the bill can be approved and synced to NetSuite.