How do I handle change order invoices in construction AP?

Key takeaways

• Change order invoices must be approved in the field, logged in the ERP with updated PO details, then matched by AP before payment.
• Successful workflows require visibility between field teams, project managers, and the AP department to prevent discrepancies and payment delays.
• Clear approval thresholds, consistent cost-code policies, and ERP-to-accounting integration reduce manual rework and ensure accurate job costing.
• Three-way matching—purchase order, change order documentation, and revised invoice—provides the audit trail needed for change order payments.
• Vergo processes AP invoices, card spend, and employee reimbursements through one coding model, so change orders follow the same job-cost workflow with inference-based coding and optional approval routing by project or amount.

Why change order invoices create AP bottlenecks

Change order invoices frequently mismatch the original purchase order, causing AP teams to pause payment until discrepancies resolve. The field team may have approved a scope change on site, but if that approval and revised amount never reach the ERP as an updated PO, the invoice arrives at AP with no corresponding record. This breakdown happens at handoff points: field teams lack visibility into what AP needs, project managers log changes inconsistently, and AP staff must chase down approvals after the fact. The result is delayed payments, strained vendor relationships, and incomplete job cost records when invoices are coded to approximate categories instead of the actual change order details.

The recommended workflow for change order invoices

Field teams submit change order details and supporting documentation to the project manager as soon as scope changes on site. The project manager reviews the change order, validates it against contract terms and budget, then logs it in the ERP system as an amendment to the original purchase order. When the revised invoice arrives, the AP department matches it to the updated PO in the ERP, verifying that amounts, line items, and change order references align. AP then approves the invoice for payment, applying the correct cost codes, job number, and cost type so the expense posts to the right project budget. Vergo automates this matching and coding step, proposing cost codes by inference from your own accounting structure so invoices sync directly into your ERP with the correct project and GL account. The ERP syncs the change order, invoice, and payment records, creating a complete audit trail from field approval through final disbursement and ensuring job cost reports reflect actual spending.

A practical example

A superintendent discovers underground utilities that require rerouting electrical conduit, adding $8,400 in labor and materials. She documents the change on site and texts the project manager, who verifies the work falls within contingency allowances and logs a change order in the ERP, updating PO #3392 from $42,000 to $50,400. Two weeks later, the electrical subcontractor submits an invoice for $50,400 referencing change order CO-107. The AP clerk opens the invoice, sees it exceeds the original PO, and checks the ERP: PO #3392 now shows $50,400 with CO-107 attached. She matches all three documents—original PO, change order, and invoice—applies cost code 16050 (electrical rough-in) and job number J-2847, and approves payment. The transaction posts to the project ledger with full backup, and the monthly job cost report reflects the additional $8,400 under the correct line item.

Best practices for construction teams

Establish clear approval thresholds so field teams know when a change order requires project manager sign-off versus senior leadership review, and document these thresholds in writing. Integrate your ERP with accounting software so updated POs flow automatically into the system AP uses for invoice matching, eliminating duplicate data entry. Train AP staff to recognize change order documentation and understand construction-specific invoice formats, including how cost codes and job numbers should appear on subcontractor invoices. Provide project managers with real-time dashboards showing which change orders have been logged, which invoices are pending, and which payments have cleared, so they can answer field questions without waiting for month-end reports. Require that every change order include the original PO number, job number, and cost code before it enters the ERP, ensuring downstream teams have the data they need for accurate matching and coding.

How Vergo handles this

Vergo processes AP invoices, card spend, and employee reimbursements through one coding model, so change orders and all other construction expenses follow the same job-cost workflow. The platform codes invoices by inference from your own accounting structure and job cost history—no rule library to build, no keyword lists to maintain—and new vendors are coded on first sight. Every coding shows why it was chosen, so a reviewer confirms in seconds instead of re-coding by hand. Approval workflows are optional and fit how you already control spend: route by GL account, by amount, or by project, or skip approval flows entirely and let policy flags catch only what breaks a rule. Transactions are ready to code the moment they happen, and once they clear, they sync into your construction ERP or accounting software. Card spend, employee reimbursements, and AP invoices run through one coding model—same coding, same review, one reconciliation—and payment stays on the rails you already use.

Related questions

• What is construction AP automation and how is it different from generic AP software?
• How do general contractors manage hundreds of vendor invoices per month?
• What is the cost of processing a single invoice manually in construction?
• What are the top AP automation tools for construction companies in 2025?