Learn
/
Why doesn't Concur work well for construction expense management?

Why doesn't Concur work well for construction expense management?

Vergo addresses construction's job-cost allocation needs with inference-based coding at point of capture and direct construction ERP integrations. SAP Concur Expense was designed for corporate travel and reimbursement workflows, not the multi-level cost codes, field-friendly capture, and native integrations with Sage 100 Contractor, Viewpoint Vista, and Foundation that construction requires.

July 29, 2026

Key takeaways

  • Vergo proposes the coding by inference from your own accounting structure and job cost history, enforcing job, phase, cost code, and cost type at the moment of capture with no rule library to build.
  • SAP Concur Expense was built around corporate travel reimbursement, not the job-cost allocation and multi-level cost-code structure that construction companies require.
  • Construction expense management demands job number, phase, cost code, and cost type on every transaction before it posts to the WIP schedule and general ledger.
  • Per its own positioning, SAP Concur targets larger organizations with scalable policy-heavy travel and expense management, but lacks native integrations with Sage 100 Contractor, Viewpoint Vista, Foundation, and other construction ERPs.

Why construction workflows don't map to Concur's design

SAP Concur Expense automates expense reporting, receipt capture, approvals, and reimbursements in a workflow built around corporate travel: employee submits receipts, manager approves, finance reimburses. That model fits law firms and consulting agencies reasonably well. It maps poorly to a general contractor 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.

What construction companies need that Concur doesn't provide natively

Concur's categorization and coding system, which assigns accounting codes based on merchant and transaction data, wasn't designed with CSI divisions, phase codes, or cost type breakdowns 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 include: no native cost code hierarchy that maps to the multi-level job/phase/cost-code/cost-type structure required for accurate job costing; field crew usability challenges when superintendents and foremen face complex mobile submission flows; ERP disconnect, as Concur has no native integrations with Sage 100 Contractor, Viewpoint Vista, Foundation, or other construction ERPs; equipment and fleet expenses that split across jobs have no standard handling; and no concept of billable-to-owner expense classification for T&M or cost-plus contracts.

The downstream impact on construction finance

When expense data doesn't flow cleanly into job cost, the downstream effects compound quickly across every financial process the controller owns. Distorted job cost reports emerge when expenses are coded to overhead or wrong jobs, overstating profitability on some projects and understating it on others — often not caught until month-end or project close. WIP schedule errors occur when costs sit in an expense queue rather than posted to jobs, skewing percent-complete calculations and materially misstating revenue recognized under ASC 606. Slow month-end close results as controllers spend three to five additional days manually reclassifying field expenses, chasing missing receipts, and reconciling exports against ERP job cost ledgers. Audit exposure increases with inconsistent cost code application and missing receipt documentation, creating findings in internal audits and owner audits on public projects. Cash flow surprises happen when reimbursable expenses that aren't flagged at submission can't be invoiced promptly on T&M work, delaying billing cycles by weeks.

A practical example

Consider a superintendent who purchases $1,200 in plumbing fixtures for Building B Phase 2 at a local supply house. In a general-purpose expense system, that superintendent photographs the receipt, submits it through a mobile app, and selects a broad category like "Materials" or "Supplies." The expense sits in an approval queue, then posts to a general expense account. Three days later, an AP clerk manually reclassifies it to the correct job and cost code — sometimes wrong, sometimes never. The result: the project manager's job cost report doesn't reflect the spend until well after the purchase, WIP calculations lag reality, and month-end close requires manual reconciliation. The modern approach enforces job, phase, cost code, and cost type at the moment of capture, so the expense posts directly to job cost without rework.

How Vergo handles this

Vergo proposes the coding 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. 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 — same coding, same review, one reconciliation — and payment stays on the rails you already use. Connecting your existing cards involves no card applications, no re-issuing, and no banking change. Vergo integrates with every ERP and accounting software, including Sage 100 Contractor, Sage 300 CRE, Viewpoint Vista, Viewpoint Spectrum, Procore, Foundation, QuickBooks, Acumatica, CMiC, COINS, Epicor, Jonas, and Deltek.

Sources

https://www.concur.com/products/concur-expense (retrieved 2026-07-28) · https://www.concur.com/en-us/card-integration (retrieved 2026-07-28)

Related questions

Frequently Asked Questions

Can you customize Concur for construction cost codes?

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.

How does poor expense coding affect the WIP schedule?

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.

What expense data does construction job costing actually require?

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.

How does Vergo handle expense coding for field employees with limited accounting knowledge?

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.

Does switching expense platforms disrupt an active construction accounting workflow?

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.

What happens to reimbursable expenses on T&M contracts when expense coding is inconsistent?

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.