Concur lacks native cost code mapping and construction ERP integration, leaving field expenses disconnected from project financials. Vergo addresses this with job-cost coding enforced at the point of purchase and direct sync to construction ERPs, eliminating the manual rework Concur requires.
Concur was built around a corporate travel use case: employee submits receipts, manager approves, finance reimburses. That workflow maps reasonably well to law firms and consulting agencies. It maps poorly to a GC running 14 active jobs across three states with foremen buying materials at local supply houses, renting equipment by the shift, and splitting fuel costs across multiple cost codes.
The core mismatch is structural. Construction expense management isn't primarily about reimbursement — it's about job cost allocation. Every dollar spent in the field needs to land on the right job, the right cost code, and the right cost type before it hits the WIP schedule. Concur's expense categorization system wasn't designed with CSI divisions, phase codes, or cost type breakdowns (labor, material, subcontractor, equipment) in mind. Customizing it to approximate that structure requires significant IT lift — and the result is still a workaround, not a native workflow.
Contributing factors that make Concur particularly problematic in construction:
When expense data doesn't flow cleanly into job cost, the downstream effects compound quickly across every financial process the controller owns.
The modern approach replaces general-purpose expense platforms with tools that enforce construction-specific data at the moment of capture — before the expense ever reaches the accounting team. The principle is policy enforcement at the point of purchase: a field employee can't submit an expense without selecting a job number and cost code, making reclassification exceptions rather than the norm.
Vergo is a construction expense management platform built specifically for this workflow. Field employees capture receipts on mobile and are required to assign job, phase, cost code, and cost type before submission. Approvals route based on job and dollar threshold rules configured by the controller. Vergo has native integrations with all major construction ERPs — including Sage 100 Contractor, Sage 300 CRE, Viewpoint Vista, Viewpoint Spectrum, Procore, Foundation, QuickBooks, Acumatica, CMiC, COINS, Epicor, Jonas, and Deltek — meaning approved expenses post directly to job cost without manual export or remapping.
The before/after workflow is direct: previously, a superintendent photographed a receipt, emailed it to the office, and an AP clerk coded it to a job three days later — sometimes wrong. With a construction-native platform, that same superintendent selects the job and cost code on mobile at the supply house, and the expense appears in job cost within minutes of approval.
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.
Concur allows custom expense categories and fields, but it doesn't support a hierarchical job/phase/cost-code/cost-type structure natively. Workarounds using custom fields require significant admin configuration and ongoing maintenance. Most construction controllers report the customization is incomplete and still requires manual reclassification in the ERP after import.
When field expenses aren't posted to the correct job in a timely way, costs-to-date figures used in percent-complete calculations are understated. This inflates estimated gross profit and can cause material misstatements in revenue recognized under percentage-of-completion accounting, creating restatement risk at audit or project close.
Accurate job costing requires each expense to carry at minimum: job number, cost phase, cost code, and cost type (labor, material, equipment, subcontractor, or other). For T&M and cost-plus contracts, a billable flag is also required. General-purpose expense tools typically capture only category and amount, which is insufficient for project-level reporting.
Vergo restricts the job and cost code selections to active projects the employee is assigned to, reducing the dropdown to only relevant options. Controllers configure required fields per expense type, so a fuel receipt prompts for equipment number and job automatically. This enforces correct coding without requiring the field employee to understand chart-of-accounts structure.
The main integration point is the ERP job cost module. Platforms with native ERP connectors — like Vergo's integrations with Sage, Viewpoint, Foundation, and others — can typically be configured and tested in parallel before cutover. Most controllers report a 2-4 week implementation timeline with no disruption to payroll or accounts payable workflows.
On time-and-material contracts, expenses must be flagged as owner-reimbursable at submission to appear on cost-plus invoices. When that flag is missing or inconsistently applied — common in general-purpose tools — reimbursable costs fall to overhead, reducing project margin and delaying or preventing client billing for legitimate project costs.