Product
Purchase Orders & Vendor Invoices: Procurement in Field PM
The gap between committed cost and actual cost is where a lot of construction budgets quietly go wrong. A $40,000 PO for switchgear commits that cost the day it's issued, but if your job cost report only shows cost once the vendor invoice lands eight weeks later, you spent two months thinking you had budget you had already spent.
Published November 11, 2026 · 7 min read
Key takeaway
A purchase order and its eventual vendor invoice should live in one ledger, not two disconnected systems. Field PM treats POs as committed cost the moment they're issued and reconciles them against vendor invoices as bills arrive, so budget-vs-actual always reflects what's actually spoken for — not just what's been paid.
Committed cost vs. actual cost — and why the gap matters
Committed cost is money you have obligated but not yet paid — a signed PO, a subcontract, a material order. Actual cost is money that has actually hit a vendor invoice or payroll run. A budget that only tracks actual cost looks healthier than it really is right up until all the committed cost lands at once, usually near the end of the job when there's no room left to adjust.
The fix is not complicated in concept — track both numbers — but it does require the PO and the eventual invoice to be the same record, or at least tightly linked, so committed cost converts to actual cost cleanly instead of getting double-counted or lost in the handoff.
How Field PM structures the PO → invoice flow
- •PO issued — a purchase order is created against a job and cost code, committing that dollar amount to the budget immediately as committed cost, before any bill arrives
- •Vendor invoice received — when the actual bill comes in, it's matched to the open PO (quantity and amount checked against what was ordered)
- •Reconciliation — a matched invoice converts that line from committed to actual cost; a discrepancy (short-shipped, price change, partial delivery) is flagged rather than silently accepted
- •Unified ledger — vendor invoices, whether tied to a PO or standalone (a bill with no PO, common for smaller purchases), and field-captured expenses all live in the same AP ledger, so nothing is tracked twice
- •One source of truth — this is the same unification that resolved Field PM's own double-count issue between the old PO module and invoicing: vendor_invoices as the canonical cost record, POs as the commitment layer feeding it
What this looks like on the budget-vs-actual report
On the PM dashboard, a cost code shows three numbers side by side: budget, committed (open POs not yet invoiced), and actual (invoiced and paid). A cost code with $50,000 budgeted, $38,000 committed via open POs, and $22,000 actual tells a project manager something a budget-vs-actual-only view cannot: there's $12,000 of headroom left uncommitted, but also $16,000 of committed cost still in the pipeline that hasn't hit actuals yet. Ignore committed cost and that code looks like it has $28,000 of room; it actually has $12,000.
This matters most on long-lead material — switchgear, structural steel, custom fabrication — where the PO might be issued months before the invoice arrives. Without committed-cost tracking, a job can look comfortably under budget for months while actually being fully spoken for.
Why POs and vendor invoices shouldn't be separate systems
A lot of procurement problems come from POs living in one tool (or a spreadsheet) and vendor invoices/AP living in another, usually the accounting system. The two get reconciled manually, occasionally, which is exactly how a PO gets invoiced twice, or an invoice with no matching PO gets miscoded to the wrong cost code, or committed cost quietly goes stale because nobody closes out POs that were never fully used.
Field PM keeps the PO and its invoice as the same thread from issue to payment, coded to the same job and cost code throughout, feeding the same budget-vs-actual view as labor, expenses, and everything else. For contractors syncing to QuickBooks, Sage Intacct, Xero, or NetSuite, that unified record is also what pushes cleanly to the accounting side without a second manual entry.
Frequently asked questions
What is the difference between committed cost and actual cost?+
Committed cost is money obligated but not yet paid — an issued PO or signed subcontract. Actual cost is money that has hit a paid vendor invoice or payroll run. Tracking only actual cost understates how much of the budget is really spoken for, since committed dollars haven't landed yet but are already promised.
How does a PO get matched to a vendor invoice in Field PM?+
When a vendor invoice arrives, it's matched against the open PO for that job and cost code, checking quantity and amount against what was ordered. A clean match converts that line from committed to actual cost; a mismatch (short shipment, price change) is flagged instead of silently accepted.
Can a vendor invoice exist without a PO?+
Yes. Smaller purchases often don't get a formal PO, so Field PM supports standalone vendor invoices coded directly to a job and cost code, living in the same AP ledger as PO-matched invoices and field-captured expenses — nothing has to be tracked twice.
Run the numbers in the field, not the spreadsheet
Field PM turns daily reports into live job costing, productivity, and billing — built for self-perform contractors. 30-day free trial · no credit card · unlimited foremen, QA/QC, safety & subs always free.
Start free trial →Keep reading