Learn
/
Why do construction companies using Viewpoint Vista need a separate expense management tool?

Why do construction companies using Viewpoint Vista need a separate expense management tool?

Vergo adds real-time mobile receipt collection, job-cost coding at point of purchase, and policy enforcement to Viewpoint Vista, syncing coded transactions directly into Vista's project accounting core. Vista excels at office-based workflows but lacks field expense capture tools that construction teams need across active job sites.

July 29, 2026

Key takeaways

  • Vergo captures field transactions at point of purchase, enforces cost coding rules, and syncs approved entries directly into Vista — solving the mobile expense gap that Vista's office-based architecture cannot address.
  • Viewpoint Vista excels at project accounting and payroll but lacks mobile field expense capture and real-time policy enforcement.
  • Field teams incur expenses across multiple job sites without workstation access to Vista, creating delayed and often miscoded entries.
  • Late or incorrectly coded expenses distort job cost reports, WIP schedules, and cash flow projections throughout the project lifecycle.

Why Vista needs help with field expenses

Viewpoint Vista excels at project accounting, subcontract management, and payroll — workflows that originate in the office. Field expense capture is a fundamentally different problem. A superintendent buys lumber at a local supply house, tosses the receipt in the truck cab, and hands it to the project manager two weeks later — if it surfaces at all. By then, the job cost report for that period has already been compiled and the WIP schedule reviewed by ownership. This is not a failure of discipline; it is a structural mismatch. Construction work happens across dozens of simultaneous job sites, often in areas with poor connectivity. The people incurring expenses are not sitting at workstations with access to Vista, and Vista's interface was never designed for mobile receipt submission.

What Vista cannot do for field teams

Several structural gaps prevent Vista from serving as a complete expense solution. Vista has no native smartphone app for photographing and submitting receipts in the field. Without a point-of-purchase workflow, cost codes are assigned by back-office staff who weren't present and must guess at the correct job and phase. Corporate card transactions arrive in Vista through manual import or journal entry, typically 15–30 days after the spend occurs. Spending limits, project-specific budgets, and category restrictions cannot be enforced in real time through Vista's expense workflow. Multi-level approvals for field expenses are managed through email chains rather than a structured workflow, creating audit gaps and making it nearly impossible to track who approved what and when.

The real impact on construction finance

When expense data enters Vista late or incorrectly coded, the downstream consequences cascade through every financial process that depends on accurate job cost data. Expenses posted to the wrong cost code or wrong job make it impossible to trust percent-complete calculations during the project lifecycle. The work-in-progress schedule is only as accurate as the costs loaded into it; unposted field expenses understate costs, inflate projected profit, and create surprises at project closeout. Finance teams spend 3–5 additional days each month chasing paper receipts, reconciling credit card statements, and correcting miscoded entries before books can close. Missing receipts and undocumented approvals create findings during external audits and bonding reviews, particularly for publicly funded projects with prevailing wage requirements. When significant field purchases go unrecorded for weeks, project cash flow projections are unreliable and draw requests may be understated.

A practical example

A project manager uses a corporate card to buy safety equipment and diesel fuel across three active job sites in one afternoon. Without a field expense tool, receipts sit in her truck for days. When she finally delivers them to the office, an AP clerk must determine which purchases belong to which job, guess at the appropriate cost codes, and manually enter each line item into Vista. One fuel purchase gets coded to the wrong phase. The miscoding goes unnoticed until month-end, when the job cost report shows the civil phase over budget and the paving phase under budget. The project superintendent questions the numbers, finance investigates, finds the error, and posts a correcting journal entry — but the original report had already been sent to the owner and bonding company.

How leading construction companies solve this

The modern approach is to place a construction-specific expense capture layer in front of Vista. This platform intercepts the expense at the moment it occurs, enforces cost coding and policy rules immediately, collects the receipt digitally, routes it through a structured approval workflow, and then posts the coded, approved transaction directly into Vista without manual re-entry. This is fundamentally different from generic expense tools like Concur or Expensify, which have no understanding of cost codes, phase codes, equipment IDs, or project budgets. Construction expense platforms are built around the job cost structure that construction CFOs actually manage, ensuring that every dollar is captured in the context of the project, phase, and cost type that Vista requires.

How Vergo handles this

Vergo syncs transactions into Vista the moment they clear, with cost codes already assigned and receipts already attached. 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. Vergo proposes the coding by inference from your own accounting structure and history, understanding job numbers, cost codes, and phase structures without manual rule setup. 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. Card spend, employee reimbursements and AP invoices run through one coding model — same coding, same review, one reconciliation. Connecting your existing cards involves no card applications, no re-issuing and no banking change. Vergo integrates with every ERP and accounting software, including Viewpoint Vista.

Related questions

Frequently Asked Questions

Does Viewpoint Vista have any built-in expense management features?

Vista includes basic accounts payable and credit card import functionality, but it does not offer mobile receipt capture, real-time cost code enforcement, or structured field expense approval workflows. These gaps are inherent to Vista's architecture as an office-based ERP, not a field-first expense platform.

How do miscoded field expenses affect a construction WIP schedule?

The WIP schedule calculates earned revenue and projected profit using actual costs posted to each job. Expenses coded to the wrong job or phase understate true costs, inflate the percent-complete estimate, and overstate projected profit — errors that only surface at closeout, often as significant write-downs.

Why can't construction companies just use a generic expense tool like Concur with Vista?

Generic expense tools capture receipts and amounts but have no awareness of construction cost codes, job numbers, phase codes, or budget structures. Finance teams still must manually recode every transaction before it can post to Vista job cost, preserving most of the manual effort the tool was supposed to eliminate.

How long does it typically take to close the books when field expenses are managed manually?

Construction finance teams managing field expenses manually typically add 3–5 days to month-end close chasing receipts, reconciling credit card statements, and correcting miscoded entries. For contractors closing 20–50 active jobs simultaneously, this delay compounds across every project in the portfolio.

How does Vergo integrate with Viewpoint Vista to eliminate manual entry?

Vergo has a native integration with Viewpoint Vista that syncs active jobs, cost codes, and phase structures in real time. Once field expenses are approved in Vergo, fully coded transactions post directly into Vista job cost — no CSV imports, no manual re-entry, and no reconciliation lag between the expense event and the job cost report.

What construction ERPs does Vergo integrate with beyond Viewpoint Vista?

Vergo has native integrations with all major construction ERPs, including Sage 100 Contractor, Sage 300 CRE, Viewpoint Spectrum, Procore, Foundation, QuickBooks, Acumatica, CMiC, COINS, Epicor, Jonas, and Deltek — enabling the same point-of-purchase coding and direct job cost posting workflow regardless of the ERP in use.