Follow the transaction, not the paperwork
Construction purchasing crosses organizational boundaries. A foreman needs material. A project manager controls the budget. Purchasing deals with the supplier. A receiver sees what arrives. Accounts payable receives the invoice. Accounting posts the cost.
If each role creates a new version of the transaction, the company can have a purchase order and still lack control.
The workflow should preserve four questions from beginning to end:
- What was requested?
- What was authorized?
- What was received?
- What should be paid and charged to the job?
The eight-stage construction purchasing workflow
The eight stages below run left to right on a wide screen and stack on a phone. Each stage is described in full underneath the diagram.
- Stage 1Field or project request
- Stage 2Scope and budget validation
- Stage 3Authorization
- Stage 4Purchase order or subcontract commitment
- Stage 5Delivery and receipt
- Stage 6Vendor invoice intake
- Stage 7Matching and exception approval
- Stage 8Posting, payment and job-cost update
1. Field or project request
The requester identifies the project, required item or service, quantity, required date, delivery location and business reason. Use a controlled selection where possible, but allow enough description or evidence for the approver to understand the need.
The request is not yet a financial commitment.
2. Scope and budget validation
The project owner confirms that the request belongs to the job, uses the correct phase or cost code and fits the approved scope or an identified change.
If the budget is unavailable or the work is potentially extra, route it for an explicit decision. Do not hide it under a general code to keep the workflow moving.
3. Authorization
Apply the company's approval rules based on amount, project, cost type, requester or exception. Approval should identify who authorized the commitment and when.
4. Purchase order or subcontract commitment
Create the commercial record with supplier, scope, quantities, prices, terms, delivery information, project and coding. This is the moment committed cost should become visible to the project.
5. Delivery and receipt
Record what actually reached the site or warehouse. Capture quantity, date, location, delivery evidence and relevant lot, serial or equipment information when needed.
The receiver should not be required to solve price or accounting questions. The receiver confirms the physical event.
6. Vendor invoice intake
Capture the vendor, invoice number, date, line details, tax and supporting document. Detect duplicates before payment. Link the invoice to the purchase order and receipt rather than searching for the job after the fact.
7. Matching and exception approval
Compare the invoice with what was ordered and received. A match can proceed. A mismatch should show the reason and owner.
8. Posting, payment and job-cost update
Post the approved cost to the authoritative financial record and correct project dimensions. Payment status and project cost are related but distinct. A cost can be recorded before cash leaves the bank.
The difference between a request, commitment, receipt and invoice
| Record | What it proves | What it does not prove |
|---|---|---|
| Purchase request | Someone needs a good or service for a stated purpose | That the company approved the obligation |
| Purchase order or subcontract | The company authorized a defined commitment | That the supplier delivered it |
| Receipt or field confirmation | A quantity or service event occurred | That the price and invoice are correct |
| Vendor invoice | The supplier is requesting payment | That the request matches authorization and receipt |
| Posted vendor bill or payable | The company recognized an approved obligation | That it has already been paid |
| Payment | Cash was disbursed against an approved payable | That the original project coding was operationally correct |
A construction invoice should not be the first place where the company decides which project bought the material.
NGYN exception matrix
| Exception | Evidence to display | Primary owner | Typical resolution |
|---|---|---|---|
| No purchase order | Request, invoice, delivery evidence and project context | Project approver or designated exception owner | Approve as exception, create controlled commitment where appropriate, or reject |
| Invoice price differs from PO | PO price, invoice price, agreement and correspondence | Purchasing or commercial owner | Correct invoice, approve authorized variance or update commitment with audit trail |
| Invoice quantity exceeds receipt | Ordered, received and invoiced quantities | Receiver and AP | Confirm missing receipt, correct invoice or hold disputed quantity |
| Wrong project or cost code | Request, PO, delivery location and project structure | Project manager | Correct before posting and record reason |
| Duplicate invoice | Vendor, invoice number, date, amount and prior document | AP | Block duplicate or verify legitimate separate charge |
| Delivery without invoice | Receipt and open commitment | AP monitoring owner | Accrue or monitor according to accounting policy |
| Invoice without confirmed delivery | Invoice, PO and receiver contact | Site receiver or project owner | Confirm service or material, partially approve or hold |
| Unapproved change scope | Field evidence, request and potential-change record | Project commercial owner | Link to change workflow and decide exposure |
Where duplicate work appears
Each step below is a point where the same purchase is typed, read or guessed again.
- Touch 1Request typed into a message or spreadsheet
- Touch 2Project manager retypes it into a purchasing request
- Touch 3Buyer retypes the scope into a PO
- Touch 4Receiver sends a photo without a transaction reference
- Touch 5AP reads the invoice and guesses the job
- Touch 6Project manager approves by email
- Touch 7Accounting rekeys or corrects the cost
The controlled alternative keeps one identity from start to finish.
- Step 1One request ID
- Step 2One authorized commitment
- Step 3One receipt relationship
- Step 4One invoice match
- Step 5One posted project cost
The goal is not necessarily one application for every role. It is one identity and one authoritative owner for each record.
System-of-record decisions
| Business object | Recommended authoritative owner | Other systems may do |
|---|---|---|
| Vendor master | ERP or accounting platform | Request a new vendor and view approved reference data |
| Project and cost structure | ERP, accounting or project-control system by architecture | Display approved values and collect field selections |
| Purchase request | Best operational interface | Send approved request to the commitment system |
| Purchase order or subcontract | Commercial transaction system | Display status and selected details |
| Receipt | Best receiving interface with authoritative transaction link | Send confirmed quantity and evidence to ERP |
| Vendor invoice and payable | ERP or accounting platform | Capture document and route approval context |
| Actual job cost | Authoritative financial or ERP record | Display synchronized summary elsewhere |
What can be automated safely
- Create a draft request from a controlled mobile form.
- Carry project and coding from approved request to PO.
- Notify the receiver before delivery.
- Extract invoice header and line information for review.
- Suggest the related PO using supplier, number, amount and line context.
- Compare ordered, received and invoiced quantities.
- Route mismatches according to reason and amount.
- Prevent duplicate invoice posting.
- Update committed and actual cost after the approved event.
- Report open commitments, unmatched receipts and blocked invoices.
AI can assist with document extraction and matching suggestions. It should not silently approve an uncertain project, price variance or unsupported invoice.
What this looked like in an anonymized contractor implementation
NGYN implemented a connected purchasing and job-cost workflow for an anonymized multi-company general contractor with more than 120 employees. The operating design connected purchase requests and approvals with purchase orders, receipts, vendor bills and project-cost visibility while preserving separate company records and role-based responsibilities.
The exact configuration is documented at a higher level in the construction ERP case study.
Implementation sequence
Discovery and gap analysis
Select several real purchases, including a clean transaction and difficult exceptions. Follow each one from request to payment and mark every handoff, re-entry and delay.
Master-data cleanup
Clean vendors, projects, cost codes, items, units and approval roles. Establish how a new value is requested and approved.
Workflow and control design
Define request, authorization, commitment, receipt, matching, exception and posting states. Decide which system owns each record.
Pilot
Pilot one project group, supplier category or purchase type. Include real exceptions. A pilot containing only perfect matches does not test the process.
Reconciliation
Compare approved purchase orders, open commitments, receipts, vendor invoices, posted payables and project cost. Resolve differences before expansion.
Rollout and support
Train by role. A foreman should learn request and receipt actions, not the complete AP process. Monitor exceptions and adoption during stabilization.
Metrics that reveal control
- Percentage of invoices linked to an approved PO or controlled exception.
- Percentage of received quantities matched before invoice approval.
- Time from request to authorization.
- Time from receipt to project-cost visibility.
- Number and value of unmatched receipts.
- Number and value of blocked invoices by reason.
- Duplicate invoice attempts detected.
- Project or cost-code corrections after posting.
The practical conclusion
Construction purchasing is controlled when physical, commercial and financial events remain connected. The purchase order is important, but it is only one stage. Reliable job cost depends on the request, authorization, receipt, invoice and posting describing the same obligation.
Frequently asked questions
What information should a construction purchase request include?
At minimum, include the project, requested good or service, quantity, required date, delivery location, requester and business reason. Add cost code, specification or supporting evidence when the process requires them.
When should committed cost appear on the project?
Committed cost should become visible when the company authorizes the purchase order, subcontract or equivalent obligation, before the vendor invoice is posted.
Is three-way matching practical in construction?
It can be, but the workflow must handle partial deliveries, services, field purchases, price changes and approved exceptions. Matching should support the business rather than pretend every transaction is identical.
What happens when material arrives without a PO?
Record the physical receipt and route the transaction through a named exception process. Do not discard the evidence or silently invent a purchase order after the fact.
Can AI code and approve construction invoices?
AI can extract fields and suggest a purchase order or cost code. Approval should remain governed by authorization, match evidence, confidence and company policy.
Does the workflow require every field worker to use the ERP?
No. A mobile form, field platform or other controlled interface can capture the request or receipt and pass the approved transaction to the ERP. System ownership and reconciliation matter more than forcing every role into one interface.