Intended audience: technical user. This page covers the one-time Vista-side configuration required to connect Vista to Siteline. Day-to-day billing workflows are covered on the Usage page.
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.
Optional: enable 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.
Optional: consolidate multiple Vista jobs into one Siteline project
If your team runs multiple Vista jobs against a single Vista contract and prefers to bill the contract as a whole, Siteline can import the contract as a single project rather than importing each job separately. Line items, AP invoices, vendors, and payments from every associated Vista job are consolidated onto that Siteline project.
This is configured per company by Siteline Support during onboarding. Reach out if you'd like to enable it — we'll confirm that your Vista data is structured in a way the integration can map cleanly. See Overview for how the import behaves once this mode is on.