Siteline integrates directly with Viewpoint Vista via an API-based connection, allowing contractors to 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

The Siteline–Vista integration is a two-way, API-based sync. The Siteline–Vista integration follows a clear, repeatable workflow that keeps Vista as the system of record while allowing teams to bill and manage A/R in Siteline.

Workflow summary

Vista → Siteline: Project setup, SOVs, vendors, AP invoices, payments

Siteline: Billing, CORs, lien waivers, sworn statements, reporting

Siteline → Vista: AR invoices and approved change orders

What data imports from Vista into Siteline

Project & contract information

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

Schedule of Values (SOV)

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 Contract module. Siteline reads from this source to ensure clean imports and accurate change order handling.

Vendors

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

Imported vendors can immediately be used for lien waiver requests and sworn statements.

Costs & payments

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 syncs from Siteline to Vista

AR invoices

Siteline syncs detail-level AIA invoices into Vista's AR module. (You can also choose to sync to JB instead — see Usage.)

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 syncing, invoices are finalized in Vista using the AR Batch Process (Validate → Post).

Change orders (CORs)

For Vista customers, Siteline supports syncing Change Order Requests directly into Vista.

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

Multiple related CORs can be linked, added to the SOV, and synced together.

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.