Connect Miter and Viewpoint Vista

The following data syncs from Vista into Miter via API: projects (as jobs), cost codes and phases (as activities), GL accounts (as ledger accounts), and cost types. Project status maps to job status in Miter, cost codes sync at the job level, and account classifications are preserved when GL accounts sync across. This gives field teams an accurate, up-to-date project structure to clock in against from day one without anyone manually recreating it in a second system.

Miter pushes two types of records back to Vista: journal entries (generated from payroll runs, expenses, and other GL activity) and job cost transactions (when a clearing account is configured). Both push via API, so labor and expense costs land on the correct project, phase, and cost code in Vista without finance teams manually re-entering data after each payroll cycle or expense posting.

Yes. Credit card transactions recorded in Miter push back to Viewpoint Vista as journal entries and job cost transactions via API. Field expenses captured in Miter with a job and cost code assigned post directly to the correct project and GL account in Vista without finance teams exporting a file or manually matching expenses after the fact. During setup, your team will configure how expense categories in Miter map to the GL account and cost code structure in Vista so posting lands correctly from the first transaction.

Miter automatically updates the corresponding journal entry in Vista. The existing Vista entry is deleted and recreated with the updated information to ensure accuracy. You can check the sync status of any GL entry in Accounting > Entries, where synced entries display a “Synced” badge. Full sync history is also available under Company > Integrations > Vista > History.

Yes. Miter connects to Vista through Agave, which supports both cloud and on-premises deployments. For on-premises Vista instances, you will need to configure Agave’s connector before completing the integration setup in Miter. Your Miter implementation contact can walk you through the on-premises connection steps and confirm that your environment meets the prerequisites before go-live.

Yes. Miter supports multi-entity mapping, allowing you to connect multiple Vista companies and map each one to a Miter entity. If your company operates multiple entities within Vista, discuss that configuration with your Miter implementation contact during setup so GL accounts, jobs, and cost code mapping are handled correctly across all entities. Miter supports multi-entity payroll natively, including separate pay runs and GL posting by entity, so each payroll and expense transaction posts to the correct Vista company without manual intervention after each run.