Skip to main content

Siteline + Viewpoint Vista - Overview (Siteline)

Siteline handles the billing. Viewpoint Vista handles the books. Together, they eliminate double entry and keep your financials aligned.

Written by Bradley LaFave

Siteline and Viewpoint Vista have a two-way, real-time integration. This lets you manage billing, change orders, lien waivers, and sworn statements in Siteline while keeping Vista as the system of record for accounting.

How the integration works

  1. Project information, SOVs, and change orders flow from Vista into Siteline.

  2. You generate and submit payment applications in Siteline.

  3. Billing amounts (pay apps) flow from Siteline back into Vista as A/R invoices.

  4. A/P invoice amounts and A/R payment records from Vista populate vendor and lower-tier lien waivers within Siteline.

Data flow overview

Vista (source)

Direction

Siteline (destination)

Job information

Vista → Siteline

Project information

Contract

Vista → Siteline

SOV

Change orders

Vista ↔ Siteline

Change orders

A/R and JB Billing invoices

Siteline → Vista

Pay apps

A/P invoices and A/P payments

Vista → Siteline

Vendor lien waivers

A/R payments

Vista → Siteline

Primary lien waivers

What Siteline reads from Vista

Siteline reads the following data directly from your Vista SQL Server database to populate projects, contracts, change orders, and lien-waiver workflows.

Job information → project information

Siteline reads job records from Vista's Job Cost module to create and sync project information in Siteline. This includes job number, job name, company, division, and contract details.

Vista data

How it appears in Siteline

Project name

Imported as the Siteline project name

Internal project ID

Stored as the internal project reference

Customer / GC

Set as the General Contractor

Project & mailing addresses

Used for project and GC address fields

Contract number

Imported as the Siteline contract ID

Contract date

Stored on the Siteline contract

Payment terms

Applied to billing terms in Siteline

Contract retention %

Imported and used for billing calculations

Tax behavior

Applied based on Vista tax configuration

Contract → schedule of values (SOV)

Contract line items from Vista's JC Contracts screen populate the Schedule of Values (SOV) in Siteline. This includes line item descriptions, amounts, cost codes, and unit of measure.

Vista data

How it appears in Siteline

Contract line items

Imported as Siteline SOV line items

Scheduled values

Preserved on import

Retention settings

Applied at the SOV and billing level

Tax groups

Applied based on Vista configuration

Best practice: SOVs should be maintained in Vista's JC Contracts module. Siteline reads from this source to ensure clean imports and accurate change order handling.

Change orders

Approved change orders from Vista's JC Change Orders sync into Siteline, keeping the SOV up to date. This includes change order number, description, and amount adjustments per line item.

Vendors

Siteline reads the vendor list from Vista's AP Vendors screen so vendors can immediately be used for lien-waiver requests and sworn statements.

Vista data

How it appears in Siteline

Vendor name

Created as a Siteline vendor

Addresses

Imported into vendor profile

Payment terms

Stored on the vendor record

Vendor type

Used for billing and waiver workflows

A/P invoices → vendor lien waivers

With a click of a button, A/P invoice amounts from Vista's Accounts Payable module populate onto vendor and lower-tier lien waivers within Siteline. This lets you accurately fill in amounts paid to subcontractors and suppliers.

A/R payments → primary lien waivers

Payment records from Vista's Accounts Receivable module sync into Siteline to populate amounts received on primary lien waivers.

Vista data

How it appears in Siteline

AR payments

Reflected in Siteline invoice and A/R status

AP invoices

Used to preload lien waiver and sworn statement data

What Siteline writes to Vista

When you submit a pay app in Siteline, billing amounts are written back into Vista as A/R invoices. Siteline supports two write paths depending on how your Vista instance is configured.

Pay apps → A/R invoices (AR Billing)

For customers using Vista's standard AR Billing module, Siteline writes pay apps into Vista's AR Batch Process as an invoice batch. Siteline allocates a batch ID through Vista's HQ Batch Control, uses your AR Company Setup auto-numbering when enabled, and creates one batch header row per invoice plus one batch line per SOV line item (amounts, retainage, tax, JC contract item reference).

Siteline billing data

Result in Vista

AIA invoice (detail)

Creates an AR invoice in Vista

Line-item billing

Posted at the contract item level

Retention

Posted with retainage values

Invoice date

Applied to the Vista AR invoice

Batch number

Used in Vista's AR Batch Process

After Siteline writes the batch, your team posts it from Vista's AR Batch Process (Validate → Post), which moves the rows from the staging batch into Vista's posted AR transactions.

Pay apps → JB Billing invoices (Job Billing)

For customers using Vista's Job Billing (JB) module, Siteline writes billing data into JB Billing instead of the standard AR module. This path is used when your Vista instance is configured to use JB for contract billing rather than the standard AR module. The data written includes billing period amounts, retainage, and line item references per JC contract item. After Siteline writes the JB invoice, your team runs JB Interface in Vista to push the data into AR.

Change orders (CORs)

For Vista customers, Siteline supports syncing Change Order Requests directly into Vista's PM Change Orders. Multiple related CORs can be linked, added to the SOV, and synced together.

Siteline COR data

Result in Vista

Approved COR

Synced as a Posted ACO

Cost codes & types

Validated against Vista

Contract value updates

Reflected in Vista contracts

Schedule-related fields (optional)

Passed through when provided

After Siteline writes the change order on the PM side, your team runs PM Interface in Vista to push it into Job Cost.

Multiple Vista projects on one contract

Some Vista customers structure work so that several Vista projects (jobs) all link to a single Vista contract — for example, when internal divisions run separate jobs against the same customer contract. Siteline supports this setup by importing the contract, not each individual job, as a single Siteline project.

When this mode is enabled:

  • The Siteline project is created from the Vista contract and takes the contract's name and number.

  • The SOV is pulled from the Vista contract.

  • AP invoices, vendors, and payments are pulled from all Vista jobs linked to the contract, so lien waivers and sworn statements see a consolidated view.

  • AR invoices and approved CORs sync back to the single Vista contract.

This is a Vista-specific import configuration. It is set up by Siteline Support during onboarding — see Setup — and cannot be toggled on a per-project basis after import.

Connection & configuration notes

  • Connection type. Siteline connects directly to your Vista SQL Server database.

  • Hosting. Your Vista database must be accessible to Siteline's servers. Siteline will connect to your instance using one of 2 IP addresses — see Setup (Siteline) for details.

  • Write path configuration. Siteline supports two write paths for billing — AR Invoice (standard AR module) and JB Billing Invoice (Job Billing module). Your Siteline implementation team will help you configure the preferred path as a default, and you can adjust per project.

  • Posting in Vista. Siteline writes billing data as a batch in Vista's AR Batch Process. Your team must log into Vista and post the batch to finalize the A/R invoice entries.

  • Change order sync. Only approved change orders in Vista will sync into Siteline. Pending or unapproved change orders are not pulled.

  • Real-time sync. The integration is real-time — reads from Vista are performed on demand when you access a project or trigger a sync in Siteline.

Did this answer your question?