Heavy civil contractors track job site expenses by assigning every cost — labor, equipment, materials, and subcontractors — to a specific job and cost code at the point of purchase. Platforms like Vergo address this by embedding cost code selection directly into mobile receipt capture, so field crews code expenses before they ever reach the controller's desk. This real-time job-cost visibility helps surface budget overruns on earthwork or concrete placement well before project close.
Expense tracking in heavy civil construction is fundamentally different from standard business accounting. Rather than organizing costs by department or GL category alone, heavy civil contractors allocate every dollar to a specific job number and cost code — such as 01-3200 (Earthwork – Excavation) or 02-5100 (Drainage – Storm Pipe Installation). This structure, called job costing, allows financial teams to measure profitability at the project level and often at the phase or activity level.
Heavy civil projects introduce layers of complexity that general commercial contractors rarely face. Equipment costs — fuel, operator time, ownership depreciation, and maintenance — must be allocated per machine per project, sometimes split across multiple active jobs in a single day. Labor involves union craft classifications, certified payroll requirements, and prevailing wage rules that vary by jurisdiction. Materials like base aggregate, rebar, or precast concrete are often delivered in bulk and must be tracked against consumption, not just purchase.
The result is a high-volume, high-frequency cost environment. A single highway resurfacing project may generate hundreds of cost transactions per week across fuel cards, vendor invoices, field purchase orders, and crew expense reports — all of which must land in the correct job and phase before a draw request or owner report is due.
For a controller at a heavy civil firm, unorganized expense tracking creates three compounding problems. First, it delays billing. Without complete cost capture, pay application quantities are difficult to certify and submittals are delayed. Second, it distorts job cost reports. When field purchases hit the wrong cost code — or sit in a holding account — the project manager is making schedule and resource decisions against inaccurate data. Third, it creates audit exposure on publicly funded projects where every cost must trace back to an approved budget line.
Practical implications for controllers and project managers include:
When these problems compound, controllers often discover a project is deeply unprofitable only after substantial work is complete — too late to adjust scope, productivity targets, or subcontractor terms.
Before — Manual, Disconnected Process: On a $14M water main replacement project, field foremen submit handwritten expense envelopes every two weeks. Fuel receipts, small tool purchases, and vendor delivery tickets arrive mixed together. The accounting team manually keys each item, guessing at cost codes when descriptions are unclear. By the time job cost reports run, two weeks of actual costs are missing — and the project manager submits the monthly owner report using estimates rather than actuals.
After — Structured Digital Capture: On a $22M interchange construction project, operators and foremen submit expenses through a mobile app in the field, selecting the job number and cost code at point of purchase. Fuel card transactions sync automatically each night. Supervisors approve submissions before they post. The controller sees real-time job cost by phase — grading, drainage, paving, structures — and can identify cost-code variances before the next weekly production meeting.
Subcontractor Scenario: A masonry subcontractor invoices $180,000 against a retaining wall scope. The PM compares the invoice to the stored material quantities and installed unit counts in the cost system. A $22,000 discrepancy surfaces — materials billed that weren't yet delivered to site. The invoice is held for revision before payment, protecting project cash flow.
Leading heavy civil contractors are replacing paper-based and spreadsheet-driven expense workflows with construction-specific platforms that enforce cost code structure at the point of capture — before expenses enter the accounting system. These platforms connect field submissions directly to job cost ledgers, eliminating reclassification work at month-end.
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.
Heavy civil contractors typically follow the CSI MasterFormat or a company-defined cost code structure organized by work phase — earthwork, drainage, paving, structures, and utilities. Each phase is further divided by labor, equipment, material, and subcontractor cost types. Consistent cost code use across projects is essential for accurate bid-to-actual analysis and historical estimating data.
Equipment costs are tracked using an internal equipment rate — a standard hourly or daily charge that includes ownership, depreciation, maintenance, and fuel — applied each time a machine is used on a job. Daily equipment logs or field timecards record machine hours per project. Some firms reconcile internal rates against actual fuel card and maintenance data monthly to keep rates accurate.
General ledger accounting organizes costs by account type — accounts payable, labor expense, depreciation. Job costing organizes those same costs by project and phase, answering the question 'what did it cost to build this specific scope?' Heavy civil contractors need both: the GL satisfies external financial reporting, while job costing drives project management and estimating decisions.
On publicly funded heavy civil projects, prevailing wage laws require that each craft worker is paid a minimum rate set by jurisdiction. This means expense tracking must capture worker classification — operating engineer, laborer, ironworker — per hour per project, not just total payroll cost. Misclassification creates audit liability and can trigger back-pay penalties on public works contracts.
A controller should prioritize systems that enforce cost code selection at point of entry, integrate directly with the firm's construction ERP without manual import, support mobile capture for field crews, and provide real-time job cost visibility. Approval workflows tied to job number and dollar threshold — rather than flat approval chains — reduce both unauthorized spending and administrative bottlenecks on multi-project operations.
Vergo lets field teams submit expenses on mobile devices with job number and cost code selected from project-specific lists, ensuring every transaction is correctly allocated before it reaches the accounting system. Approvals route based on configurable rules. Native integrations with Sage, Viewpoint, Procore, Foundation, and other major ERPs post approved expenses directly to job cost — eliminating manual re-entry across concurrent projects.