How do I set up expense approval routing for a construction company?
Set approval routing in construction by defining thresholds, assigning approvers by job ownership, requiring cost codes before submission, and building escalation rules for delays. Vergo routes approvals by GL account, amount, or project and syncs approved expenses to your ERP with job cost mapping intact.
Key takeaways
- Vergo routes approvals by GL account, by amount, or by project—fitting how construction companies already control spend—and syncs approved expenses to your ERP with job cost mapping intact.
- Route expenses to the project manager responsible for the job number, not to a central inbox, to keep cost accountability with budget owners.
- Set dollar thresholds that match your project size—common tiers are under $250 to supervisor, $250–$2,500 to project manager, and above $2,500 to controller or CFO.
- Require valid job numbers and cost codes before the approval workflow initiates to prevent unapproved expenses from reaching accounting without proper allocation.
- Build escalation rules with named backup approvers for project managers who are frequently on-site, triggering after 48–72 hours of inactivity.
- Audit routing quarterly as job rosters change and project managers turn over to avoid rules pointing to former employees.
Why Expense Approval Routing Breaks Down in Construction
Construction companies operate across multiple job sites, cost centers, and crews simultaneously. Without a defined approval chain, expenses get submitted to the wrong person, sit unapproved for weeks, or get coded to the wrong job number—causing budget overruns that only surface at month-end. The core problem is that most construction firms treat expense approval as a one-size-fits-all process. A $40 hardware store receipt and a $4,000 equipment rental don't belong in the same workflow. Common breakdown points include no role clarity at the field level, where foremen submit expenses directly to the CFO and bypass project managers who own the job budget; missing cost code assignment, creating manual rework for accounting; threshold blind spots where approvers approve everything regardless of amount; and no escalation path when a primary approver is unavailable in the field.
The Recommended Expense Approval Workflow
This process applies to any construction company with field crews, project managers, and a central accounting function. First, define expense categories—materials, fuel, tools, meals, lodging, subcontractor reimbursements—and require a job number and cost code at submission for every category. Second, set dollar thresholds for each approval tier: a common model routes under $250 to the direct supervisor or foreman, $250–$2,500 to the project manager, and above $2,500 to the controller or CFO. Third, assign the first-level approver by job or crew, routing field expenses to the project manager responsible for that job number. Fourth, require cost code validation before approval is triggered so the workflow only initiates after the submitter has assigned a valid job number and cost code. Fifth, build in an escalation rule for delayed approvals—if an expense sits unapproved for 48–72 hours, automatically escalate to the next level and name a specific backup approver for each primary. Vergo routes approvals by GL account, by amount, or by project, and approval workflows are optional—you can skip them entirely and let policy flags catch only what breaks a rule.
A Practical Example
A general contractor runs six active projects ranging from $500K to $3M. Each project manager owns the budget for their job. When a foreman on the $3M commercial build purchases $180 in materials from a local supplier, the expense routes directly to that project's manager because it falls under the $250 threshold and carries the correct job number. When the same foreman rents a skid steer for $1,800, the expense routes to the project manager but also requires a photo receipt because it exceeds the $75 documentation threshold. If the project manager doesn't approve within 72 hours—common when they're on-site all day—the system escalates to the operations director who serves as the designated backup. Once approved, the expense syncs to the ERP with the job number and cost code intact, posting directly to the WIP schedule without manual re-entry by the accounting team.
Tips for Construction Controllers Setting Up Approval Routing
Tie approval authority to job ownership, not org chart position alone. A project manager overseeing a $2M job should have appropriate approval authority for expenses tied to that job, even if their title is junior. Separate approval routing for union versus non-union labor reimbursements, as these often have different documentation requirements and audit trails under collective bargaining agreements. Document your threshold policy in writing—controllers frequently enforce undocumented approval rules, and when auditors or bonding companies review expense processes, written policy protects you. Audit the routing quarterly, as job rosters change, project managers turn over, and new cost codes get added. A routing rule pointing to a former employee creates silent failures that stall approvals and frustrate field teams.
How Vergo Handles This
Vergo routes approvals by GL account, by amount, or by project, fitting how construction companies already control spend. Approval workflows are optional—you can skip them entirely and let policy flags catch only what breaks a rule. Transactions are ready to code the moment they happen, with no waiting for clearing, and once they clear they sync into your accounting or ERP software with job cost mapping intact. Vergo integrates with every ERP and accounting software, so approved expenses land in the right job cost buckets automatically. Employees handle everything by text message—no app to download, no portal login—and Vergo chases missing receipts itself instead of waiting for a report. Card spend, employee reimbursements, and AP invoices run through one coding model with the same coding, same review, and one reconciliation. Connecting your existing cards involves no card applications, no re-issuing, and no banking change. See how it works at getvergo.com/products/expense-management.
Related Questions
- What is construction expense management and why is it different from regular expense tracking?
- How do general contractors track expenses across dozens of active jobs?
- What are the hidden costs of manual expense management in construction?
- Expense management software comparison for construction ERP users
Frequently Asked Questions
How many approval tiers should a construction company have?
Most construction companies use two to three tiers: a field-level supervisor for small incidentals, a project manager for job-related expenses up to a mid-range threshold, and a controller or CFO for anything above that. Companies with multiple divisions or over $50M in revenue often add a division manager tier between the PM and CFO.
What should happen when a project manager is unavailable to approve an expense?
Define a named backup approver for every primary approver before the routing system goes live. The most reliable construction practice is to assign the superintendent or assistant PM as the automatic escalation contact after a 48-hour delay. Avoid routing to a generic 'accounting inbox' as a fallback—it breaks cost accountability and slows month-end close.
Should subcontractor reimbursements go through the same approval routing as employee expenses?
No. Subcontractor reimbursements typically require lien waiver documentation, insurance verification, and contract reference before payment—making them better handled through the AP workflow rather than an expense approval chain. Routing them through employee expense approval creates compliance gaps and muddies your job cost reporting. Keep the two workflows separate with distinct documentation requirements.
How do you handle expenses submitted without a job number or cost code?
The submission should be rejected or returned to the submitter automatically before it enters the approval queue. Allowing uncoded expenses to flow through approval creates manual rework for accounting and risks misallocation on WIP schedules. Build cost code validation as a required field at submission—not an optional one resolved after the fact.
How does Vergo handle approval routing for construction companies with multiple job sites?
Vergo allows controllers to configure routing rules by job number, cost code, dollar threshold, and expense type—so field expenses automatically route to the project manager assigned to that job. Escalation rules, backup approvers, and receipt requirements are set once and enforced consistently. Approved expenses sync directly to the connected ERP with job cost mapping intact.
What documentation should be required as part of the approval workflow?
At minimum, require a photo receipt or vendor invoice for any expense above your reimbursable threshold—commonly $25–$75 in construction. For fuel and equipment-related expenses, also require the job number and equipment ID. For lodging and per diem, cross-reference against your company's travel policy. Documentation requirements should be enforced at submission, not collected retroactively during audit.



