SERVICETRADE X VIEWPOINT VISTA
Sync operations and finance with Viewpoint Vista
Customers, jobs, invoices, and approved timecards flow from ServiceTrade into Viewpoint Vista with the right contract, customer, and cost-center context already attached — and new Vista customers and service sites flow back to the field, so accounting and operations work from the same record.
Customer and Company Records
Companies
AR Customers
Companies
SM Customers (paired)
Companies
AR Customers
Customer Address and Phone
Customer Address and Phone
Locations
SM Service Sites
Base Vista Configuration
Account Configuration
JC, AR, and SM Company Codes
Customer Code Generation
AR Customer Code Range and Prefix Rules
Payment Terms
AR Terms
Tax Configuration
AR Tax Codes (with optional state-based derivation)
Department Setup
JC Departments
Cost Center Setup
JC Cost Centers
Job Numbering
Configurable
Job Prefix and Format Rules
Job Phase Template
JC Template Job (optional)
PR Group
PR Groups
Pay Period Validation
PR Pay Periods
Employee Records
PR Employees
Department Source
Configurable
Job Type, Assigned Office, or Default
Job Cost and Contracts
Jobs
JC Jobs
Jobs
JC Contracts
Job Phases (optional, from template)
JC Phases
Location Address
JC Mailing Address
Assigned Office
JC UDF (when enabled)
Accounts Receivable
Approved Invoices
AR Batch Entries (Contract Invoice)
Voided Invoices
AR Credit Memos
Invoice Tax Rate
Invoice Tax Code
Mixed-Sign Invoice Lines
Split into Positive and Negative AR Submissions
Invoice Posted / Failed Status
Vista AR Result
Reporting and Cost Coding
Service Lines
PR Departments (on labor entries)
Office / Branch
JC Department (configurable source)
Job Type
JC Department (alternate configurable source)
Jobs
JC Jobs and JC Contracts
Technicians
PR Employees
Job Phases (template-based)
JC Phases
Location State
PR Work State Code
Location State
Tax State
Cost Centers (multi-cost-center accounts)
JC Cost Center
Payroll Time Capture
Approved Labor Daylogs
PR Time Batch Entries
Clock-In / Clock-Out Events
PR Time Batch Entries (with Start and End Time)
PTO, Holiday, Other Generic
PR Time Batch Entries (Type J)
Technician (User)
Vista Employee
Job Service Line
PR Department
Location State
Tax State
Testimonial
“Running my business with ServiceTrade and Sage Intacct has reduced my days of sales outstanding by 80%!”
Key Benefits
Key Benefits of the ServiceTrade and Vista Integration
One Customer, Both Directions
Service Sites Flow to the Field
Jobs Land With Contracts Attached
Invoices Post to AR Batches Automatically
Approved Time Reaches Vista Payroll
Your Vista Setup Stays in Charge
FAQs
common questions
What data flows between ServiceTrade and Vista?
ServiceTrade syncs companies, jobs, approved invoices, and approved timecards into Vista. Companies create paired AR and SM customer records; jobs create JC Jobs with matching contracts; invoices post to AR batches; timecards land in PR time batches. In the other direction, Vista AR Customers and SM Service Sites flow back to ServiceTrade as companies and locations — so both systems stay in step without manual entry.
Do customer records sync both ways?
Yes. A customer added in ServiceTrade creates AR and SM Customer records in Vista. A customer added in Vista AR creates a company in ServiceTrade. Customer name, address, and phone updates carry across when changed. Both systems link the records by external ID, so the same customer is recognized everywhere.
How are jobs created in Vista?
When a new job is created in ServiceTrade, the integration creates a JC Contract and a JC Job in Vista together — with customer code, service site, cost center, and department already assigned. If your team uses a template job, phases can be copied from the template onto the new job automatically. Job number and description follow the format your implementation team configures.
What happens to a voided invoice?
When an invoice is voided in ServiceTrade, the integration creates an offsetting credit memo in Vista AR automatically — so your AR ledger stays balanced without a manual reversal. If the original invoice was already voided or never posted, the integration recognizes it and skips re-processing.
Which timecards sync to Vista payroll?
Only timecards in the approved status flow to Vista. The integration handles three entry types: labor (with job, department, and tax state), clock-in / clock-out events (with start and end times), and generic entries like PTO and Holiday. Each entry is validated against the active Vista pay period and the Vista employee record before posting, and duplicate detection prevents re-processing the same entry on retries.
How does the integration handle errors and missing data?
Failed invoices update the ServiceTrade invoice status to failed and add a comment explaining what went wrong, so AR can fix the source record. Missing prerequisites — like a customer without a Vista external ID, a missing pay period, or an employee record that doesn’t exist in Vista PR — stop the affected record and trigger an email alert to the support contacts you configure during setup.
Can the integration match my Vista setup?
Yes. Your Vista financial structure drives the integration — not the other way around. Company codes, AR Customer code ranges, job number formats, AR Terms, tax codes, cost centers, departments, PR Groups, and pay periods are all read from Vista and applied automatically. Your implementation team tailors the configurable pieces (department source, customer prefix, template job, multi-cost-center logic) to match your Vista setup during onboarding.
How does field activity show up in Vista cost reporting?
Service lines flow to PR departments on labor entries, jobs flow to JC Jobs with paired contracts, technicians map to PR employees, and location state flows to PR work state and tax state. Multi-cost-center accounts can configure jobs to be created per cost center, and template-based job phases can be copied onto new jobs automatically — so Vista cost reporting reflects how your field teams actually operate, not a generic structure forced by the integration.
How is this different from a custom file import?
The integration is event-driven and built on the AppXchange (Trimble Connected Community) platform — the same trusted middleware Vista customers already rely on. When data changes in either system, the change flows in seconds to minutes, not overnight. There are no manual files to upload, no scheduled imports to babysit, and no batch failures buried in a folder somewhere — failures surface where your team can act on them.