BuildOps + Vista (Viewpoint) integration
BuildOps + Vista, heavy commercial GC operations on a project-first ERP
Vista is Spectrum's project-first sibling, the ERP heavy commercial GCs and heavy-civil contractors pick when AIA, retainage, prevailing wage, and bonding requirements are the central workflow. BuildOps runs the service side. The integration is custom every time.
The problem
BuildOps + Vista is structurally identical to BuildOps + Spectrum at the integration layer, no native connector, one-way payment sync because Vista is the GL of record, custom pricebook-to-cost-code mapping per tenant. The Vista-specific overlay: Vista is more project-first than Spectrum (less hybrid service+project, more pure GC orientation). That means three things matter more on this stack, (1) AIA G702/G703 source-of-truth routing for jobs that have service tickets AND progress billing, (2) multi-state prevailing-wage payroll with rate-table currency, and (3) bonding-capacity-aware reporting where retainage held, completed-contract revenue, and work-on-hand all need to roll up cleanly for surety review. Service ticket volume is lower than on a hybrid Spectrum buyer; AIA + retainage + prevailing wage are heavier.
Why this integration matters
$50M+ commercial GCs, heavy-civil contractors, and self-performing primes are the typical Vista buyers. BuildOps is increasingly the operational system for the service-and-maintenance side of the business at this scale, the recurring revenue arm of an otherwise project-driven shop.
Bonding capacity is the operational ceiling for these contractors. Surety analysis depends on accurate retainage held, work-on-hand, completed-contract margin, and rolling DSO. Vista handles all of these natively, IF the underlying transactions are correctly tagged and routed. Most native BuildOps-to-Vista integrations don't enforce that tagging, so bonding-agent reviews see noisier numbers than the business actually has.
Multi-state prevailing-wage compliance is the highest-cost-of-error workflow on this stack. Federal Davis-Bacon, state-specific prevailing-wage statutes, and municipal contract requirements each have different rate tables that update on different cadences. Vista maintains the rate tables; BuildOps timesheets feed payroll operationally. Rate-table drift between the two systems causes back-pay clawbacks at audit, typical exposure $50K-$500K depending on project size.
AIA routing on hybrid jobs (a major project that also generates service tickets during the construction period) is where revenue leakage and double-billing happen. Without explicit source-of-truth routing per job, service tickets that should have been wrapped into AIA progress billing get billed separately, or AIA progress invoices get duplicated by service tickets that were supposed to be wrapped. Annual audits surface 2-8% revenue restatements when this is loose.
Outside accounting firms and surety reviewers can review Vista records in isolation. The finance gap is reconciling the BuildOps service operation with Vista's project accounting at month-end and organizing the resulting work-on-hand, retainage, payroll, and subcontractor records for review.
Product capability and finance-control checklist
These rows combine documented product capabilities with Level's finance-side validation questions. Confirm behavior in the installed edition and configuration using the official sources below. A partial or custom status describes the finance workflow, not a judgment about the vendor's product quality.
| Capability | Status | Detail |
|---|---|---|
| Native BuildOps connector in VistaProduct behavior to verify | Separate finance control | No native connector exists. Vista's ecosystem is strongest with Procore, Viewpoint Field View, and Trimble's own job-site tools. |
| Vista REST API + ODBC / SQLProduct behavior to verify | Documented / available | Modern REST API + legacy SQL Server access. Coverage on AR, AP, GL, jobs, customers, vendors, payroll. |
| 2-way payment sync (BuildOps ↔ Vista)Product behavior to verify | Separate finance control | Structurally impossible. Vista is the GL of record; one-way for payment status. |
| Pricebook → Vista cost code × cost type × phase mappingProduct behavior to verify | Separate finance control | Custom per tenant. Vista's grid is similar to Spectrum's; mapping table is 1,000+ rows for typical commercial mechanical/electrical/plumbing trade. |
| AIA G702/G703 native in VistaProduct behavior to verify | Documented / available | Vista handles AIA natively, pay applications, schedule of values, retainage held, change orders. Native is excellent for projects routed correctly to Vista. |
| AIA source-of-truth routing per jobProduct behavior to verify | Separate finance control | BuildOps can also produce progress billing. Without explicit routing rules per job, double-billing or dropped revenue happens on hybrid jobs. |
| Multi-state prevailing-wage payrollProduct behavior to verify | Documented / available | Vista handles multi-state prevailing wage, fringe benefits, certified payroll (WH-347) natively. |
| Prevailing-wage rate table currencyProduct behavior to verify | Separate finance control | Vista maintains rate tables; rate-table updates from state/federal sources have to be applied. BuildOps doesn't read Vista's rate tables when calculating operational labor cost. |
| Subcontractor compliance gatingProduct behavior to verify | Separate finance control | Vista holds the compliance master. BuildOps doesn't natively read from it before sub assignment. |
| Work-on-hand / bonding-capacity reportingProduct behavior to verify | Documented / available | Vista produces work-on-hand and completed-contract reports natively for surety review, when the underlying job data is correctly tagged and routed. |
| Multi-entity / multi-company routingProduct behavior to verify | Separate finance control | Vista supports multi-company; BuildOps sync defaults to one. Multi-entity routing is custom for contractors with bonding-segregated entities. |
Where the connection needs finance-side validation
Use these as finance-side validation questions. Dollar and count examples are illustrative scenarios unless a named source or benchmark is stated. Recurring failure patterns are Level operating observations, not market prevalence estimates. The answer depends on product configuration, report scope, accounting policy, and workflow ownership.
Illustrative scenario
AIA double-billing or revenue leakage on hybrid jobs
Project starts as a $4M new-construction install (AIA progress billing in Vista). Mid-project, the customer adds service requests, change orders, and small maintenance tickets that BuildOps handles operationally. Without explicit routing, service tickets in BuildOps generate invoices that ALSO show up in Vista's AIA progress, or never show up at all. Either double-billed or dropped revenue.
Why it matters: Annual audit findings; revenue restatement of 2-8% on hybrid jobs; customer disputes when they receive duplicate invoices; trust in monthly numbers erodes.
Illustrative scenario
Prevailing-wage rate table drift causing certified-payroll audit failures
Federal Davis-Bacon rate update published for Mechanical class in County X effective March 1. Vista's rate table is updated by the payroll administrator on March 4. BuildOps payroll calculation runs on March 5 using the OLD rate from operational pricebook (not Vista's rate table). Timesheets reflect old wage rate. Certified payroll WH-347 submission for that project shows incorrect rate.
Why it matters: Project clawback exposure $50K-$500K depending on project size; certified-payroll resubmission; insurer review; GC partner can hold final payment until audit closed.
Illustrative scenario
Bonding-capacity reporting noise from BuildOps service AR mixed with Vista project AR
Surety reviews work-on-hand, completed-contract margin, and DSO quarterly. If BuildOps service AR is co-mingled with Vista project AIA AR without invoice-type tagging, the rolling DSO calculation includes service AR aging dynamics (30-45 days) that pull down the apparent project AR aging (60-120 days normal). Surety reviewer can't tell what's a project receivable in good standing vs. what's a service receivable that's actually late.
Why it matters: Bonding capacity reduced because the surety doesn't trust the rolling metrics. Owner is operationally over-capacity but can't access the bonding to chase new work.
Level finance validation pattern
Cost code mapping drift on a project-first grid
Vista's project cost code structure is deeper than QBO/Intacct and similar to Spectrum. BuildOps Pricebook updates that aren't propagated to Vista's cost code grid cause revenue to post to wrong code combinations. Project profitability reports become directional.
Why it matters: Self-performing GC scrutiny, 'are our piping subcontract costs within the bid range at this project phase?', gets unreliable answers.
Illustrative scenario
Sub compliance lapse window between assignment and AP release
Vista holds sub compliance master (COI, lien waiver, W-9, license, bonding). Operations assigns sub via BuildOps without checking Vista's master. Sub goes on site uninsured for 3 days. Vista AP then pays sub's bill because the compliance check at AP wasn't gated against the operational assignment record.
Why it matters: Lien exposure on bonded project; insurer coverage gap; GC partner withholds project payment until cleared.
Illustrative scenario
Service ticket flooding lower than Spectrum, but allocation issues higher
Vista users do less recurring service ticket work than Spectrum users (heavier GC orientation). The volume problem is smaller. But allocation issues are larger, overhead bills (equipment rental, fuel, insurance, indirect labor) need to be allocated across active projects using rules that account for cost code × phase × project type.
Why it matters: Manual monthly allocation eats 4-6 days of bookkeeper time at close. Allocation accuracy directly affects project profitability conclusions, which directly affect bidding strategy on future work.
Level finance validation pattern
Multi-entity routing for bonding-segregated entities
Heavy commercial GCs and heavy-civil contractors often run multiple Vista companies, separate legal entities for different bonding programs, joint ventures, or risk-segregation. Transactions need to route correctly per job's entity assignment. Manual routing every month.
Why it matters: Multi-entity consolidated reporting unreliable; surety reviews require manual reassembly each quarter.
Illustrative scenario
Outside accounting firm + bonding-agent CPA can't close the consolidated view
Same family of problem as BuildOps + Spectrum, with bonding-agent-CPA implications. Close stretches to 25+ days for a view that ties to operational reality.
Why it matters: Surety review cadence (typically quarterly) gets stale data. New bond capacity requests delayed.
When the connection works but the numbers do not
Compare same-period detailed records before assuming a software defect. Check record IDs, counterparty, amount, payment or write-off treatment, status, dates, dimensions, and report filters. A mismatch can come from a connection, mapping, timing, workflow, migration, or accounting treatment.
Level's approach
Stitch BuildOps + Vista + prevailing wage + subcontractor controls + surety reporting
Level's data layer holds BuildOps (operational SoT) and Vista (financial SoT + project-accounting + certified payroll + sub compliance + bonding-capacity reporting) and reconciles them against a unified canonical model, same approach as BuildOps + Spectrum, with Vista-specific GC-oriented and prevailing-wage handling.
AIA source-of-truth routing is set per job at job creation. Pure project jobs route through Vista AIA exclusively; hybrid jobs use deterministic rules to decide what wraps into AIA vs. what bills as service. Double-billing prevented; revenue leakage closed.
Prevailing-wage rate tables maintained as versioned, source-of-truth data in Level's layer; rate updates from Davis-Bacon / state / municipal sources flagged and verified against Vista's rate-table currency BEFORE BuildOps payroll calculation runs. The certified-payroll submission is right the first time.
Subcontractor compliance gating two-gate enforced (BuildOps operational assignment AND Vista AP release). Lien-exposure window closed.
Bonding-ready reporting: work-on-hand, completed-contract margin, rolling DSO, retainage held, all produced cleanly by tagging invoice types (project AIA vs. service AR) and routing entity allocations correctly. Surety reviewer sees consistent, defensible numbers.
Cost code × phase × cost type mapping versioned + drift-alerted. Overhead allocation rules applied deterministically each month, equipment, fuel, insurance, indirect labor, using cost-driver data (mileage, labor hours, equipment usage).
Multi-entity routing per job → entity → Vista company deterministic. Inter-entity activity reconciled monthly with audit trail.
Target state: certified-payroll records and work-on-hand reports organized for the responsible finance, CPA, or surety reviewer.
Step 1
Ingest both + compliance
BuildOps API + Vista REST/SQL + certified payroll + compliance master + rate tables
Step 2
Route + tag + gate
AIA per-job routing; invoice-type tagging; sub-compliance two-gate; entity routing
Step 3
Verify prevailing wage nightly
Rate-table currency + BuildOps timesheet calculation reconciled before payroll runs
Step 4
Close with surety review support
One reconciled view with work-on-hand, retainage, and receivables reports organized for review
AI-assisted workflows a reconciled data layer can support
When BuildOps and Vista (Viewpoint) records reconcile, AI can help classify, compare, and route exceptions. Humans retain policy, approval, posting authority, and responsibility for the financial result.
AIA hybrid-job routing exception detection
Agent monitors jobs that have both AIA progress billing AND BuildOps service tickets; flags any double-billing risk or wrapping ambiguity for routing decision before invoice generation.
Prevailing-wage rate table monitoring + reconciliation
Agent monitors federal Davis-Bacon, state, and municipal prevailing-wage rate publications by trade classification; verifies Vista rate-table currency; flags any drift between Vista rate table and BuildOps payroll calculation BEFORE payroll runs.
Sub compliance two-gate enforcement
Agent verifies COI / lien waiver / W-9 / license / bonding currency at BuildOps assignment AND at Vista AP release. Blocks both gates with notification on lapse.
Overhead allocation rule application
Agent applies configured allocation rules to multi-project overhead bills (equipment rental, fuel, insurance, indirect labor) using cost-driver data; posts allocation JEs with audit trail.
Bonding-capacity reporting QA
Agent runs work-on-hand, completed-contract margin, retainage held, and rolling DSO reports monthly; flags any tagging or routing issues that would cause noisy surety review; surfaces clean reports for quarterly bonding agent meetings.
Multi-entity inter-entity activity reconciliation
Agent reconciles inter-entity transactions monthly; flags any imbalanced postings before close.
Close-control sequence: current workflow and target state
This is an illustrative Level planning sequence, not a measured customer cohort or guaranteed timeline. Keep the useful steps and replace the timing assumptions with the company's actual access, data condition, configuration, controls, exception volume, and implementation scope.
| Close step | Current workflow | Controlled target state |
|---|---|---|
| BuildOps service AR ↔ Vista AR reconciliation + invoice-type tagging | Day 10-14. | Day 2. Auto-tagged + reconciled. |
| AIA hybrid-job routing audit | Day 14. Manual when conflicts surface. | Day 1. Routing rules upfront; exceptions caught at job creation. |
| Prevailing-wage rate-table reconciliation | Discovered at certified-payroll audit (annual). | Day 1. Nightly. Errors caught before submission. |
| Certified payroll cumulative review | Day 14. Manual. | Day 1. Auto. |
| Subcontractor compliance check before AP release | Spot checks. | Every in-scope payment passes the configured evidence gates or remains an exception. |
| Retainage reconciliation | Day 14. | Day 3. |
| Overhead allocation across active projects | Day 16. Manual every month. | Day 3. Auto-allocated with audit trail. |
| Work-on-hand + rolling DSO + completed-contract margin for surety | Quarterly manual reassembly. | Day 4. Standing reports refreshed monthly. |
| Multi-entity allocation + inter-entity reconciliation | Day 18. | Day 4. |
| Owner + bonding-agent review | Day 28+. | Day 6. |
| Total time to close | 24-30 days | ~6 days |
CFO-level insights the unified data layer surfaces
Finance questions the combined record set can support when the required identifiers, mappings, and source populations are complete. A Level benchmark is used only where the metric and eligible cohort match the question.
AIA project profitability by phase × cost type × cost code, fully-burdened
Vista's grid filled correctly from BuildOps operational data; multi-dimensional drill-down.
Prevailing-wage cost variance vs. bid rates by project + state
Surfaces rate-change impact in real time; informs future bidding on similar work.
Bonding-capacity headroom, work-on-hand vs. available bonding
Clean monthly reporting; surety reviews see consistent numbers; capacity requests get faster approvals.
Sub-by-sub performance on bonded projects with audit trail
Sub assignment + cost code + compliance currency + project outcome analyzed together.
Hybrid-job revenue capture without double-billing or leakage
Routing rules audited; revenue recognition complete + non-duplicated; trust in monthly numbers rebuilt.
Multi-entity consolidated profitability + bonding-segregated entity views
Auto-routed; surety reviews per-entity work-on-hand reliably.
Certified-payroll audit readiness every month, not annual scramble
WH-347 cumulative + rate currency verified nightly.
How to start
We first scope your specific BuildOps and Vista (Viewpoint) setup, the records that matter, the responsible owners, and the finance decisions the workflow must support. Any implementation work, timing, and commercial scope are confirmed for that engagement. See the pricing page for Level's service tiers.
Frequently Asked Questions
Vista vs. Spectrum?
Both Trimble products. Vista is project-first, GC-oriented, heavy-civil, larger commercial new-construction. Spectrum is hybrid service+project, heavier service ticket volume, mid-market commercial mechanical/electrical/plumbing common. Heavy commercial GCs and heavy-civil contractors usually go Vista. Self-performing trades at $20M+ often go Spectrum. Level supports both.
Do you handle bonding-agent reporting directly?
We produce the underlying reports (work-on-hand, completed-contract margin, retainage held, rolling DSO, certified-payroll audit trail). Your bonding agent reviews them. Level's role is making sure those reports are clean and defensible every month, not on a quarterly scramble.
Multi-state prevailing-wage rate updates, do you maintain the rate tables?
We maintain a versioned canonical rate-table source in Level's data layer and reconcile against Vista's rate table. If Vista's rate table drifts from current Davis-Bacon / state / municipal publications, we flag it. We don't replace Vista's payroll calculation, we make sure the inputs are current.
How long does setup take?
Timing depends on access, active-job complexity, cost code, phase, cost type, project mapping, and AIA routing decisions. The assessment defines those dependencies before a timeline is promised.
Is integration work charged separately?
Custom integration work is included in most Level engagements. Bonding-ready reporting and certified-payroll-aware reconciliation are included in Platform. See /pricing for tier details.
Official product sources
These primary vendor references support statements about documented product behavior. Level's setup, reconciliation, and control recommendations are finance-side interpretations from our operating work, not instructions from either software provider.
Related integrations + pages
Simple pricing
Three tiers, one ladder.
$99-$500/mo
Bookkeeping
The clean data layer: monthly books, reconciliations, and organized financials AI can work with.
$1,500-$5,000/mo
Scale
The full AI operating layer: custom agents, weekly actions, and benchmarks to grow margin per hour.
Custom
Platform / Multi-Office
Multi-branch benchmarking and scorecards for PE-backed and multi-location groups.
Get BuildOps and Vista (Viewpoint) on the same page
Get a finance-side assessment of your BuildOps + Vista (Viewpoint) setup, including the mappings, controls, and ownership behind the numbers.
No commitment. Finance-side guidance, not vendor support.