Vista Integration

COI Tracking for Vista by Viewpoint

Vista tracks compliance codes at the vendor and subcontract level. The gap is keeping those codes current when certificates of insurance expire, subcontracts change, and vendors go non-compliant.

 

PINS connects to Vista through Trimble AppXchange. Vendors submit COIs, W-9s, contractor licenses, and other required documents through a no-login upload link. PINS reviews submissions against your requirements and writes compliance status back to Vista: at the AP Vendor level, the SL Subcontract level, or both.

 

See how COI tracking software works behind the integration.

Book a Demo Request Pricing
PINS vendor compliance record for Apex Mechanical showing Approved status across two active projects, with a Written back to Vista panel confirming AP Vendor compliance codes and SL Subcontract compliance hold released for payment via Trimble AppXchange, synced 4 minutes ago.

How It Works

Vista stays current. Automatically.

When a subcontract is flagged in Vista, PINS takes over. Documents are collected, reviewed, and approved. Compliance status writes back without manual entry.

Vendors and subcontracts sync to PINS

Vista pushes AP Vendors and SL Subcontracts to PINS automatically. No manual imports. No duplicate data entry.

Compliance codes write back to Vista

PINS pushes compliance status to the AP Vendor record, the SL Subcontract record, or both. You configure the level. Vista reflects current status without anyone touching it manually.
Step 1

Vendor uploads documents

Vendors and brokers submit through a simple upload link. No login required.

Your team decides
Step 2

AI reviews. Your team approves.

PINS AI reviews each submission and identifies issues. Your team decides what happens next.
Step 3

PINS requests renewals

Automated reminders and follow-up requests keep compliance current. The cycle repeats at every renewal.

Key Features

Built for Vista compliance workflows

Configurable write-back to Vista

Push yes/no status, expiration dates, or both to Vista at the AP Vendor level, SL Subcontract level, or both. Write-back maps to your existing Vista compliance setup.

AP can enforce the stop payment flag

Compliance status writes back to Vista automatically. Your AP team can use Vista's payment controls as intended without manually checking compliance before every payment run.

All compliance documents, one code

COIs, endorsements, W-9s, contractor licenses, and other documents tracked in PINS can roll up to a single compliance code in Vista or you can send a unique comp code for each requirement. Configuration choice is yours.

AI-assisted review with team approval

PINS reviews each document against your requirements and identifies issues. Your team makes the final call. The comp code that writes back to Vista reflects a real review, not a rubber stamp.

Vendors and subcontracts sync automatically

The integration pushes AP Vendor and SL Subcontract records to PINS without any manual import. New subcontracts are tracked from the moment they are created.

Automated renewal tracking

PINS tracks expiration dates and sends renewal reminders before certificates lapse. Vista's compliance status stays current because the underlying documents stay current.

For AP and Compliance teams

Your AP team stays in Vista. Your compliance team works in PINS.

Two tools. One source of truth. PINS manages the compliance detail and writes status back to Vista so your payment workflow reflects current compliance without anyone crossing systems.

What AP sees in Vista

  • Compliance status written back to AP Vendor and SL Subcontract records automatically
  • Supports both Flag-type and date-type compliance codes, based on your Vista setup
  • Stop payment flag relies on automated comp code updates
  • Covers AP Vendor Compliance, Subcontract Compliance, and PO Compliance fields

What Compliance manages in PINS

  • COIs, endorsements, W-9s, contractor licenses, and other required documents
  • Requirements mapped to each AP Vendor or SL Subcontract record
  • AI-assisted document review with your team retaining every approval decision
  • Renewal tracking and automated follow-up before certificates expire

For teams also running Procore, PINS integrates natively with both. See how the Procore integration works.

Vista Integration FAQ

Common questions

Does Vista track certificates of insurance?

Vista includes compliance code fields that can flag a vendor or subcontract record as compliant or non-compliant. However, Vista does not collect, review, or store COI documents, endorsements, or other insurance certificates. Teams that rely on Vista alone for compliance tracking typically handle document collection and review outside the system, then update compliance codes manually. PINS connects to Vista to automate that full workflow: collecting documents from vendors, reviewing them against your requirements, and writing compliance status back to Vista automatically so your AP team never has to cross systems.

How does the PINS and Vista integration work?
PINS connects to Vista through Viewpoint's API. When a vendor or subcontractor is added in Vista, PINS pulls the record and maps it to the compliance requirements you have configured. As PINS reviews and approves documents, it writes compliance status back to the corresponding AP Vendor or SL Subcontract record in Vista automatically. Your AP team sees current compliance status without leaving Vista.

Which Vista records does PINS update?

PINS writes compliance status back to AP Vendor Compliance, Subcontract Compliance, and PO Compliance fields in Vista. The integration supports both AP Vendor and SL Subcontract record types. Which record types are in scope depends on how your team uses Vista and how the integration is configured during onboarding.

Does the stop payment flag in Vista update automatically?

Yes, when PINS is configured to support it. The stop payment flag in Vista relies on compliance code updates, and PINS writes those updates automatically as document status changes. If a certificate expires or a gap is identified in PINS, the compliance code update flows to Vista and the flag reflects the current status. Your AP team does not need to manually update Vista when compliance changes.

Does PINS support both Flag-type and date-type compliance codes in Vista?

PINS supports both. Flag-type compliance codes are updated when a vendor or subcontractor moves in or out of compliance. Date-type codes are updated with the relevant expiration or effective date from the document. Which code type PINS uses depends on how your Vista environment is configured. Your implementation contact will confirm the right setup during onboarding.

How long does it take to set up the Vista integration?

Most teams go live within 60 to 90 days depending on scope and the number of vendors being onboarded. The implementation includes configuring compliance requirements, connecting the Vista integration, and migrating any existing vendor records. A dedicated PINS implementation contact manages the setup and remains your primary contact after go-live.

Stop Reviewing.

Start Approving.

Schedule Demo
Insured Profile Page showing insurance policies in compliant status-1