Connect Miter and Viewpoint Spectrum

Sync frequency depends on the data type. API-based syncs for projects, cost codes, and GL accounts can run automatically on a scheduled basis. CSV-based syncs, including employee records, timesheets, and payroll exports, are initiated manually by your team. Your Miter implementation contact can help you set up a sync cadence that matches your payroll cycle and reporting needs. If you need data updated more frequently for a specific workflow, flag that during setup and the team can work through the options with you.

Yes. The integration maps Viewpoint Spectrum phase or cost codes into Miter as activities, which means field teams can select the correct phase-level cost code directly on their Miter timesheet. This keeps labor costs tied to the right project phase from the moment hours are captured, rather than requiring finance to reclassify entries after the fact. If your Spectrum cost code structure uses multiple levels or custom naming conventions, work through the mapping configuration with your Miter implementation contact to confirm the structure translates correctly into Miter activities.

Nothing — and that’s by design. The Miter-Spectrum integration is an accounting integration, not an employee sync. After payroll is processed, Miter exports GL Journal Entries to Spectrum via CSV. Employee records are managed entirely in Miter and do not need to exist in Spectrum for the integration to work. Miter is the system of record for all employee and pay data. Spectrum only receives the job-costed GL entries needed for your general ledger.

Once a payroll run is completed in Miter, the payroll data is exported as a CSV file containing GL journal entries. Your finance team imports that file into Viewpoint Spectrum, where labor costs are posted to the correct GL accounts, jobs, and cost codes. The export is structured to match Spectrum’s import format so the file can be uploaded without manual reformatting. If your Spectrum configuration uses custom GL account structures or project hierarchies, those should be mapped and tested during the integration setup to confirm the export file lands correctly on the first live payroll run.

Multi-entity support depends on how your Viewpoint Spectrum environment is structured. If your company runs multiple entities within a single Spectrum instance, discuss that configuration with your Miter implementation contact during setup so the GL account and job mapping is handled correctly across entities. Miter supports multi-entity payroll natively, including separate pay runs, cost code structures, and GL posting by entity. The goal during implementation is to confirm that GL journal entries export from Miter and post to the correct entity and GL account in Spectrum without manual intervention after each payroll run.

Setup requires access to your Viewpoint Spectrum instance for the API connection covering GL accounts, projects, and cost codes. For the payroll export, your team will download the GL journal entries CSV from Miter and import it into Spectrum after each payroll run. Your Miter implementation contact will walk through the full setup checklist, including field mapping, sync scheduling, and a test payroll export before go-live. Plan to involve both your finance team and your Spectrum administrator in the setup process, since the integration touches GL configuration, project structure, and employee records across both platforms.