How do I match vendor field tickets to purchase orders in construction?

March 27, 2026

Matching vendor field tickets to POs requires a three-way match: field ticket quantities and unit rates must align with the original PO and the incoming invoice before any approval is triggered. Vergo's AP automation handles this with cost-code-level PO matching and mobile field ticket capture, flagging variances before they reach the AP desk.

Why Field Ticket and PO Matching Breaks Down in Construction

Field tickets are generated at the job site—often on paper, handwritten, or submitted via a subcontractor's own format. By the time they reach the AP team, critical context is missing: which phase of work, which cost code, which change order, and whether the quantities actually reflect what was installed or delivered.

The result is a matching problem that generic AP processes were never designed to solve. Common breakdowns include:

Quantity drift: Field tickets reflect actual hours or materials used, which frequently exceed the original PO line items due to scope creep or undocumented change orders.
Format mismatch: Vendors use their own ticket formats—different unit descriptions, non-standard cost codes, or lump-sum entries that can't be mapped directly to PO line items.
Missing supervisor sign-off: Field tickets arrive at AP without documented approval from the project superintendent or foreman who actually verified the work.
Split deliveries: A single PO covers multiple deliveries across weeks; partial field tickets accumulate without a clear running total against the committed amount.

The Recommended Workflow for Field Ticket to PO Matching

This five-step process creates a defensible audit trail from job site to final payment.

Require field ticket capture at delivery or completion. The foreman or site superintendent must sign and date the vendor's field ticket at the time of service or material delivery. Both parties retain a copy. Digital capture (photo, e-signature) is strongly preferred over paper.
Log field tickets against the open PO in real time. As signed tickets arrive, the project manager or field coordinator enters quantities, cost codes, and the associated PO number. Each entry reduces the remaining committed balance on that PO line.
Flag variances before invoice receipt. If a field ticket quantity exceeds the PO line balance, route it immediately to the project manager for a change order determination—before the vendor's invoice arrives. Resolving discrepancies upstream prevents payment holds downstream.
Perform three-way match at invoice entry. When the vendor invoice arrives, AP matches it against (a) the original PO, (b) the accumulated signed field tickets, and (c) the invoice line items. All three must reconcile on quantity, unit rate, and cost code before the invoice is approved for payment.
Escalate unmatched items with a documented exception. If the invoice exceeds field ticket totals or references work not on the PO, place the invoice in a formal dispute queue with a written exception note. Assign resolution to the project manager with a defined response window—typically 48–72 hours.
Sync approved invoices to your ERP with full job cost coding. Once matched and approved, post the invoice to the correct job, phase, and cost code in your construction ERP. This updates committed costs and keeps project financials current.

Tips for Construction AP Teams

Establish PO tolerance thresholds by trade. Define acceptable variance bands (e.g., ±5% for material deliveries, ±0% for subcontractor labor) so AP staff know when to auto-approve versus escalate without judgment calls.
Use a field ticket log as a control document. Maintain a running log per PO that shows each ticket number, date, quantity received, and running balance. This prevents duplicate ticket submission—a common vendor billing tactic.
Require cost codes on the ticket, not just the invoice. Train field staff and subcontractors to include the project cost code on signed field tickets. Retro-coding at the AP desk introduces errors and slows approval cycles.
Set invoice submission rules in your subcontract. Include a clause requiring that invoices be supported by signed field tickets before AP will process payment. This shifts the burden of documentation to the vendor.
Automate the match with a construction-specific AP platform. Platforms like Vergo are built to ingest field tickets, map them to PO line items and cost codes, and flag variances automatically—eliminating the manual spreadsheet work that creates matching errors. Vergo integrates natively with Sage 100/300, Viewpoint Vista/Spectrum, Procore, Foundation, QuickBooks, Acumatica, CMiC, COINS, Epicor, Jonas, and Deltek, so matched invoices post directly to your ERP with full job cost data.

How Vergo Automates Field Ticket to PO Matching

Vergo's AP automation workflow is purpose-built for construction matching complexity. AP managers upload or receive field tickets digitally; Vergo's extraction layer reads vendor formats, maps quantities to open PO lines, and validates cost codes against the job budget. Variances trigger a structured approval routing—project manager first, then AP—so disputes are resolved before payment runs, not after. Because Vergo maintains native integrations with all major construction ERPs including Sage, Viewpoint, Procore, Foundation, QuickBooks, Acumatica, CMiC, COINS, Epicor, Jonas, and Deltek, approved invoices sync automatically with full job cost coding, eliminating double entry and keeping committed costs accurate in real time.

How Vergo Helps

Vergo is a card-agnostic expense management platform built for construction. Connect any corporate or project credit card and get full visibility and control over field spending.

Job-cost coding at the point of capture — field teams assign job number, cost code, and cost type from their mobile device before the receipt leaves the job site.
Per-job spend controls — set card limits by project, cost code, or cardholder so spending stays within approved budgets.
Mobile receipt capture — superintendents and PMs photograph receipts on-site with automatic data extraction.
Role-based approval workflows — route expenses through project managers, job-level approvers, and controllers based on your org structure.
Vergo integrates natively with major construction ERPs, syncing coded expenses directly into job cost and general ledger without manual re-entry.

Frequently Asked Questions

What is a three-way match in construction AP?

A three-way match in construction compares the original purchase order, the signed field ticket or delivery receipt, and the vendor invoice before approving payment. All three documents must agree on quantities, unit rates, and cost codes. Discrepancies on any leg of the match trigger a hold and escalation to the project manager.

What should I do when a field ticket exceeds the PO amount?

Treat any field ticket that exceeds the open PO balance as a potential change order. Route it to the project manager immediately—before the invoice arrives—to determine whether a change order is warranted, the PO needs amendment, or the vendor overbilled. Document the decision in writing before approving or rejecting payment.

How do I handle duplicate field ticket submissions from vendors?

Maintain a running field ticket log per PO that records each ticket number, submission date, and cumulative quantity received. When a new ticket arrives, verify it against the log before posting. Duplicate ticket numbers or quantities that push the PO balance negative are automatic holds for vendor dispute resolution.

Can field tickets submitted in a vendor's own format be matched to our POs?

Yes, but it requires a mapping step. AP staff must translate the vendor's line descriptions and quantities to the project's cost code structure before matching. Construction AP platforms that use document extraction and line-item mapping—like Vergo—can automate this translation across vendor formats, reducing manual re-keying and the errors it introduces.

How do partial deliveries against a single PO get tracked for matching?

Assign each field ticket a receipt sequence number tied to the PO and log it with the partial quantity received. The PO tracking record should show original quantity, cumulative received quantity, remaining open balance, and ticket references. This running balance prevents over-invoicing on split deliveries and gives AP a clear picture at final invoice.

What's the best way to reduce field ticket disputes with subcontractors?

Require dual sign-off on field tickets at the time of work completion—the subcontractor's foreman and your site superintendent both sign. This eliminates after-the-fact quantity disagreements. Including this requirement in the subcontract agreement and making payment conditional on properly signed tickets gives your AP team a defensible position when disputes arise.