Designing a Purchase Order Workflow That Construction Actually Uses
Every construction company has POs in theory. The reality on most projects is that POs show up after the material does, are created by the AP team matching invoices to retroactive purchase documentation, or don't exist at all for field-level purchases. The consequence is an AP process that can't three-way match reliably, spending that isn't visible until invoices hit, and budget overruns that surface after they've happened rather than before.
A PO workflow that actually works — meaning POs exist before the purchase, field teams create them voluntarily because it's the fastest path, and the system enforces compliance at critical points — requires specific design choices. It's not about adding process; it's about removing friction so that following the process is easier than working around it.
Understanding the failure modes makes the design choices clearer. Common reasons POs fail to get created in construction:
Common PO compliance failures
- PO creation requires desktop access — the field doesn't have it when they need to buy
- PO approval workflow takes hours — the field can't wait when the concrete truck is showing up
- PO system is unfamiliar to field crews — trained for office use, not jobsite use
- Vendor has standing account — field just charges it, sees no reason to document
- PO threshold is so low that every purchase needs approval — compliance burden overwhelms
- No downstream consequence for missing PO — AP processes the invoice anyway
Each of these is a design problem, not a discipline problem. Training people harder when the system makes compliance impractical doesn't change behavior.
POs need to be created where the buying decision happens — at the jobsite, on a phone or tablet. A mobile-first workflow:
Mobile PO creation requirements
- Native mobile app or mobile-optimized web — not a desktop interface squeezed onto a phone
- Vendor selection from recent vendors plus searchable master — not scroll-through-300-vendors
- Quick line item entry — voice-to-text, barcode scanning, or photo of the quote
- Job/cost code selection from the user's active projects — not navigating the full chart
- Approval request submitted in seconds
- Approval response visible on the mobile device
- PO number available to give to the vendor immediately
When creating a PO from the jobsite takes under two minutes, field crews do it. When it requires going back to the trailer to log into a desktop, they skip it. The speed of creation determines compliance.
Approval thresholds should match the risk of the purchase. Two extremes fail:
Threshold design principles
- Threshold too low (every purchase approved) — approval delays on $50 hardware purchases; approvers ignore the flood and become rubber stamps
- Threshold too high (only major purchases approved) — meaningful spending happens without review; approval is meaningless
- Tiered threshold — small purchases by superintendent-level approval; larger by PM; largest by exec
- Budget-based threshold — if a line item has budget remaining, automatic approval; if it doesn't, escalation required
- Role-based threshold — experienced superintendents have higher limits than new ones
The specific thresholds depend on company size and project scale, but the principle is that approval should add value where it matters and get out of the way where it doesn't. A superintendent buying $200 of consumables on a $10M project doesn't need executive approval; an unusual $25K buy does.
The PO workflow should check against the project budget at creation time, not discover the over-budget condition at invoice time. Budget check features:
Budget check at PO creation
- Current budget for the cost code displayed as the PO is created
- Remaining budget visible after proposed PO — real-time calculation
- Warning when PO would exceed budget — not a silent block, a visible warning
- Escalation path for budget exceptions — can continue with higher approval
- Budget-adjusted commitments displayed — PO plus outstanding commitments plus invoiced
Budget visibility at PO creation prevents most overruns before they happen. The PM sees that this PO would put the cost code over budget and either chooses a different approach, secures the budget increase, or proceeds with eyes open — not after the invoice arrives and the overrun is already real.
POs work best when vendors are part of the workflow. Key vendor integrations:
Vendor integration approaches
- Electronic PO delivery — PO sent to vendor automatically when approved
- Vendor acknowledgment — vendor confirms ability to fulfill per PO terms
- Delivery ticket matching — delivery tickets reference the PO
- Invoice reference required — invoice must reference PO number
- Vendor portal for invoice submission — invoices submitted through portal with PO match enforced
- Top-vendor EDI integration — major suppliers integrate directly with PO system
Vendors who are part of the system help enforce it. A vendor portal that requires a PO number before accepting invoice submission effectively requires POs on those vendors. A vendor who can't submit an invoice without a PO becomes an ally in enforcing PO compliance.
The strongest PO enforcement mechanism is vendor-side — requiring vendors to submit through a portal that needs a valid PO. Field compliance problems disappear when the vendor can't get paid without the PO.
Get AP insights in your inbox
A short monthly roundup of construction AP + accounting posts. No spam, ever.
No spam. Unsubscribe anytime.
Three-way matching (PO + receipt + invoice) only works if all three exist and can be matched. Common data discipline requirements:
Data discipline for three-way match
- PO number structure that's unique and visible on all documents
- Delivery tickets or receiving confirmations entered in the system at time of delivery
- Invoice required to reference PO number
- PO line items specific enough to match — not blanket "materials"
- Unit of measure consistency between PO and invoice
- Quantity and price tolerance policies for acceptable variances
A PO that says "miscellaneous building materials, $10,000" can't meaningfully three-way match against invoice. Specific line items — quantity, unit of measure, unit price — enable real matching. Investing in PO specificity pays off in reduced matching exceptions.
The workflow needs enforcement to prevent bypass. Effective enforcement points:
PO workflow enforcement points
- Invoice won't post without matched PO (above threshold)
- Payment won't release to vendor for invoice without PO reference
- Exception reports identify invoices posted without POs for management review
- Periodic field audits of spending patterns vs PO patterns
- Vendor-side enforcement: vendor can't submit invoice through portal without PO
Without enforcement, the workflow is advisory. Field teams who know AP will process the invoice either way don't bother with POs. Teams who know payment stalls without a PO develop the habit.
Some legitimate situations require purchases without POs — true emergencies, minor purchases below threshold, recurring service charges where PO isn't practical. The workflow needs exception handling:
Legitimate PO workflow exceptions
- Emergency purchases — post-facto PO allowed within 24 hours with documentation
- Small-dollar spending — p-cards or company credit cards with monthly reconciliation
- Recurring services — blanket POs or contracts that don't require per-event POs
- Change order work — PO created from approved change order rather than from scratch
- Field purchases below threshold — documented on expense reports, coded to job
A workflow without exception handling either has excessive exceptions piling up or drives legitimate work underground. The exceptions should be explicit, tracked, and monitored for pattern abuse.
PO workflow governance requires regular review of metrics:
PO workflow governance metrics
- PO compliance rate — percent of invoices with matching POs
- PO creation lead time — time from purchase decision to approved PO
- Approval cycle time — time from PO submission to approval
- Exception rate — percent of purchases requiring exception handling
- Match rate — percent of POs that pass three-way match without intervention
- Budget adherence — percent of POs within budget vs requiring exception
Trends in these metrics show whether the workflow is improving or degrading. A rising exception rate signals that the thresholds or workflow aren't matching reality. A falling compliance rate signals enforcement erosion.
A construction PO workflow that actually gets used requires mobile-first creation, right-sized approval thresholds, budget visibility at PO time, vendor integration, three-way match data discipline, meaningful enforcement, and governance metrics. The goal is to make following the process faster than bypassing it — once compliance is easier than non-compliance, field teams comply without being pushed. Companies that invest in workflow design rather than in training their teams to tolerate a broken system consistently achieve higher PO compliance rates and get the downstream benefits: cleaner three-way matching, earlier visibility of spending, fewer budget surprises, and less time spent reconciling invoices that shouldn't have been ambiguous in the first place. The PO workflow is foundational AP infrastructure — the companies that get it right have materially better AP operations than companies that treat POs as optional documentation applied after the fact.
Written by
Sarah Blake
Head of Product
Former AP Manager at a $200M construction firm, now leads product at Covinly. Writes about what AP teams actually need from automation — beyond the marketing promises.
View all posts