Overview
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
Workflow Detail
Step 1: Set Up the Project in Vista
Projects and contracts are first created and maintained in Viewpoint Vista.
In Vista, teams typically:
Create the project and prime contract
Set up the Schedule of Values (SOV) in the JC Contract module
Configure retention, tax behavior, and payment terms
Maintain cost codes and cost types
This ensures Siteline always pulls from a clean, authoritative source.
Step 2: Import the Project into Siteline
From Siteline, users import the project directly from Vista.
Siteline pulls in:
Project and contract details
Customer / GC information
Addresses
Payment terms
Retention settings
Tax configuration
SOV line items
Approved change orders (when synced)
At this point, Siteline becomes the workspace for billing and collections.
Step 3: Manage Billing in Siteline
All billing activity happens in Siteline.
Teams use Siteline to:
Update progress on SOV line items
Add and manage Change Order Requests (CORs)
Generate AIA-style pay apps and invoices
Track invoice status and aging
Collaborate across accounting and project teams
This avoids billing directly in Vista while keeping data aligned.
Step 4: Sync AR Invoices to Vista
Once billing is finalized, invoices are synced back to Vista.
From Siteline:
Users sync detail-level AIA invoices to Vista
Invoice data is posted to Vista’s AR module
Batch numbers are applied for posting and reconciliation
In Vista:
Invoices are validated and posted using the AR Batch Process
Vista remains the source of truth for financial reporting
Step 5: Sync Change Orders to Vista (Optional)
For customers using CORs:
Approved Change Order Requests in Siteline are synced to Vista
CORs are created as Posted ACOs
Contract values and related data stay aligned across systems
This allows PMs to manage CORs operationally while finance maintains clean contract data.
Step 6: Handle Lien Waivers and Sworn Statements
Siteline augments Vista with compliance workflows.
Using Vista data, Siteline can:
Pull AP invoices to suggest vendors and amounts
Generate lien waiver requests
Populate sworn statements and affidavits
Track collection and completion status
Compliance documents live in Siteline and do not sync back to Vista.
Step 7: Payments Flow Back to Siteline
As payments are recorded in Vista:
AR payment data flows back into Siteline
Invoice status and aging update automatically
Teams get real-time visibility without manual updates
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 chose to sync to JB instead by following the section below.)
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.
JB Billing Sync
Depending on your integration configuration, Siteline invoices may sync to Vista’s JB Billing module instead of the AR module. When JB Billing is enabled, pay applications created in Siteline are written directly to the corresponding Vista contract in JB Billing.
JB Billing must be enabled before invoices can sync to Vista’s JB Billing module. To turn this on:
Click the Company dropdown in the upper right corner of Siteline.
Select Company Settings.
Scroll to the Vista section.
Click Edit.
Turn on the Write to JB Progress Billing toggle. (see screenshot below)
Click Save.
Once enabled, invoices will sync to Vista’s JB Billing module instead of the AR module. If this setting is off, invoices will sync to Vista’s AR module by default.
Siteline billing data | Result in Vista |
AIA invoice (detail) | Creates a JB Billing invoice |
Line-item billing | Updates contract billing amounts |
Retention | Reflected in SM/Tax or retention fields |
Invoice date | Applied to JB Billing invoice |
Batch number (if generated) | Generated from Vista configuration |
Need some visuals? Click here to jump to screenshots of how it works.
Setup
Our team will guide you through setup and validation. To enable the Vista integration, you will need to:
Whitelist Siteline’s static IPs
Create a SQL user for integration access
Share connection details securely with Siteline Support
Supported Vista Environments
The integration supports the following Vista environments via Agave:
On-premise Vista
Vista SaaS
Trimble Construction One (TC1)
Viewpoint One (VP1)
Viewpoint Enterprise Cloud (VEC – RDP)
Vista for Cloud (VFC) is not supported.
Important Things to Know
Retention Handling
New jobs (recommended):
Set up SOVs in Vista JC
Bill exclusively through Siteline
Retention lives entirely in AR
Existing jobs previously billed in JB:
Pre-Siteline retention remains in JB
Siteline-issued retention posts to AR
Retention releases may need to occur in both modules
Batch Processing (Best Practice)
Pull the first batch number from Vista
Reuse that batch number for all invoices in the same billing period
This keeps transactions grouped and simplifies posting
Known Limitations
Export T&M Invoices
Export retention-only invoices
Export lien waivers
Export compliance documents
Stored materials automation (manual only)
Appendix: Screenshot Mappings
This is typically what a project looks like in Viewpoint Vista before importing into Siteline:
These screenshots show what the above project looks like when imported from Vista into Siteline. (To import a project, select “New project” on the homepage. Next, in the modal box that pops up: select the project type, select the ERP you want to import the project from, and then search for your desired project in the search bar.):
This is where the SOV is imported from in Vista:
This is what the imported SOV looks like in Siteline:
This screenshot shows what an invoice looks like after updating billing in Siteline and before syncing over to Vista (To sync an invoice, you can click the “Sync invoice to Vista” button shown in the top right corner of the screenshot below):
These screenshots show what newly generated invoices look like in Vista after syncing from Siteline
This screenshot shows what a Vendor would look like after importing from Vista to Siteline:
Appendix: JB Billing Functionality
This screenshot shows the JB Billing sync modal in Siteline prior to syncing.
This screenshot shows the newly generated invoice in Vista’s JB Billing module after syncing from Siteline.
