Construction purchase-order invoice matching: resolve the reference before resubmitting
Match a construction invoice to its purchase order, scope and receiving evidence with a quantity example, exception workflow and free review sheet.

Direct answer
Check the contracting entities, project, PO or subcontract reference, authorized scope, units, quantities and supporting receipt records before changing an invoice. Ask which specific match failed. Preserve the submitted version and distinguish an administrative reference correction from a disputed entitlement or price.
A missing PO number can hide several different problems
A Houston construction supplier receives a returned invoice marked “PO mismatch.” The office adds the number from the last email and resends it. The invoice comes back again: the number belongs to a different location, and the receiving record covers only part of the shipment. The problem was never just an empty reference field.
Treat the return as a request to identify the mismatched record. Ask for the project, commitment number, affected line and missing or conflicting evidence. Then compare the order and invoice side by side. Start with the invoice packet checklist, but use this narrower review when the stated blocker concerns a PO, subcontract or receiving match.
Procore’s official invoicing documentation connects subcontractor invoices to project commitments and billing periods. That describes its software workflow; it does not make every Texas construction customer use Procore or a universal PO rule. Follow the agreed submission instructions and the actual contracting documents.
Match the parties and scope before matching totals
Confirm who ordered the work or goods and which entity receives the invoice. A familiar jobsite nickname does not establish the customer’s legal entity. Check the project reference, vendor record and order version. If the customer uses several commitments for the same vendor, identify the one covering the billed scope.
For material or unit-based orders, compare units as well as quantities. Ten boxes and ten individual units are different entries. For a lump-sum subcontract, do not force progress work into a delivery-quantity model. Use its agreed schedule of values and billing basis.
Keep an exception note for each mismatch. A reference correction should not quietly change a claimed amount, waive a disputed extra or imply that a pending order revision is already approved.
| Record | Check | Evidence to retain |
|---|---|---|
| PO / subcontract | Correct entity, job and approved version | Executed record or authorized order |
| Invoice | Reference, scope line, units and billing period | Submitted version and line detail |
| Receiving / field support | What arrived or was performed | Dated delivery or field evidence |
| Changes | Approval status and affected line | Approval or clearly identified pending request |
Use matching terms accurately
Oracle’s procurement documentation distinguishes two-way matching of order and invoice quantities from three-way matching that also includes receipt quantities; its four-way model adds inspection acceptance. Tolerances and matching settings belong to the particular purchasing system.
For your own review, ask whether the customer is missing an order reference, a receiving entry or an acceptance record. A supplier’s delivery ticket and the customer’s posted receipt can be different records. Send the relevant evidence and ask the authorized reviewer to resolve the missing entry; do not create a fictional acceptance date to make a match appear complete.
These are workflow concepts, not a statement that a software hold settles whether payment is legally owed. Preserve separate contract and deadline review where applicable.
Worked example: ordered quantity is not received quantity
Original illustrative example: an order authorizes 100 units at $80 each. A dated delivery record supports 75 units at the jobsite, and an invoice requests payment for all 100. There are no taxes, freight charges, prior billings, retainage or adjustments in this simplified example.
The authorized order value is $8,000. The documented 75-unit delivery corresponds to $6,000, leaving a 25-unit, $2,000 difference to investigate. An order proves the authorized quantity in this example; it does not by itself prove that all 100 units arrived.
If a second delivery record supports the remaining 25 units, attach it and request confirmation of the receiving match. If the other units have not arrived, review the actual billing terms before correcting the invoice. An agreement may treat deposits, staged deliveries or stored materials differently; the example does not determine the amount legally payable.
| Comparison | Quantity | Amount at $80 per unit |
|---|---|---|
| Authorized order | 100 | $8,000 |
| Supported delivery | 75 | $6,000 |
| Invoice submitted | 100 | $8,000 |
| Difference requiring evidence / review | 25 | $2,000 |
Separate a correction from a commercial disagreement
If the amount and scope are supported but the PO reference is wrong, prepare a controlled revision that identifies the changed reference and preserves the original. Ask how the customer wants the corrected version labeled so the same claim is not entered twice. Keep the original invoice number or revision treatment consistent with the accounting policy.
If the mismatch concerns quantity, rate or an extra outside the order, route it to the authorized commercial reviewer. Use the invoice dispute log for the claimed and challenged amounts. Do not downgrade a disagreement into an administrative typo simply to get a packet accepted.
For a returned packet, use the resubmission workflow. Save the correction reason, new version, submission receipt and reviewer response. Received, accepted for review and approved are separate states.
Download a line-by-line matching review sheet
Download the PO and invoice matching review sheet. Add one row per affected line and record the exception rather than marking the entire invoice “wrong.” The blank CSV supports an internal review in your approved spreadsheet or accounting workflow.
The sheet does not connect to a purchasing system, establish approval authority or calculate Texas legal deadlines. Keep the work-month record and any separate notice review active while the customer resolves its matching hold.
When the discrepancy concerns the supplier account total rather than a single order, use the supplier statement reconciliation guide to trace bills, credits and payment allocations at a common cutoff.
- Verify the correct job and contracting parties.
- Compare the order version, scope line and units.
- Identify the specific receiving or acceptance gap.
- Assign an owner for each exception.
- Save the original, revised submission and dated response.
PO matching questions
Does a missing PO number automatically mean the work is unpaid legally? This guide does not decide entitlement. Identify the actual contract and submission requirements and obtain project-specific advice for a dispute.
Can I use the same PO for every project with one customer? Confirm the customer’s records. A shared customer name does not establish a shared commitment or project reference.
What if I delivered everything but their receipt shows less? Supply dated delivery support and ask the authorized reviewer to reconcile the receiving entry. Preserve the difference until it is resolved.
Should I issue a second invoice after a rejection? Follow the documented revision process and check for duplicate entry. Keep the original submission and its relationship to the correction visible.
Related reading
Turn project facts into a review queue.
Keep unpaid work months, parties, invoices, documents and estimated review dates in one private workspace.
Create your free accountOfficial sources
- Procore: subcontractor invoice prerequisites and commitments
- Oracle: two-, three- and four-way match approval levels
Source note: Reviewed October 14, 2026. Verify the current statute and obtain qualified advice for a specific project or claim.