Viewpoint Vista COI Tracking: Stop AP Compliance Holds

The short version

The workflow every Vista contractor describes

We hear a near identical version of this from project administration teams running Viewpoint Vista. It goes like this:

1. A subcontract is executed. The subcontractor is required to send a job specific certificate of insurance.
2. The project admin team collects it and verifies it manually against the insurance requirements.
3. Once it’s compliant, it’s tracked in Vista at the job or subcontract level, usually in the PM Subcontract module.
4. A copy also goes in the job folder in SharePoint.
5. Nobody is watching this stepThe COI expires.
6. Vista places a compliance hold on payments tied to that subcontract.
7. Nobody knows until accounting calls to ask why a payment is blocked.
8. Project admin manually re collects and re verifies the certificate. Payment eventually releases.

Every step in that list is competent work. The process isn’t broken because people are careless. It’s broken because the only alarm in the system fires downstream of the problem.

Why the compliance hold is a symptom, not a control

Vista’s compliance tracking does exactly what it’s designed to do: it checks vendor compliance in AP workflows and blocks payment when documentation has lapsed. That’s a genuinely valuable last line of defense.

But a hold tells you something has already gone wrong:

• The certificate expired at some earlier date.
• Work may have continued on site uninsured, or with coverage nobody has verified.
• A subcontractor is now waiting on money, which means a phone call, an escalation, and a rush job for project admin.
• The renewal chase starts from a standing start, with a payment clock running.

A control catches the problem before the consequence. Right now, the consequence is the notification.

The gap isn’t in Vista. It’s in the space between “the certificate arrived” and “the certificate is about to expire,” the 300 plus days where nobody is actively watching, because watching means checking expiration dates across every subcontract by hand.

The two systems of record problem

Most Vista teams store certificates in at least two places: Vista (at the job or subcontract level) and SharePoint (in the job folder). Some also keep a spreadsheet.

Notice the phrasing project admins actually use: “We should be saving all COIs in Vista.”

That word is doing a lot of work. When a document lives in two systems and neither is authoritative, you get:

• Certificates in SharePoint that were never posted to Vista
• Certificates in Vista with no endorsements attached
• Endorsement PDFs that were reviewed once and never linked to the certificate they modify
• An audit where somebody has to reconcile the two by hand

If you’re still running part of this in Excel, the failure modes are well documented. See COI Tracking in Excel: When the Spreadsheet Works and When It Breaks, and grab the free COI tracking template if you’re not ready to move off spreadsheets yet.

“How many COIs do you track?” is a question you shouldn’t have to calculate

When we ask contractors how many certificates they track annually, the honest answer is usually: “That’s really hard to calculate.”

The math tends to look like this:

Several hundred expiration dates, each attached to a different subcontract, each requiring outreach to a different broker. That is not a task a human should be doing by memory.

If your team can’t answer “how many COIs do you track?” in under thirty seconds, that’s the finding. There’s no single dashboard where compliance lives.

Blanket and project specific: you need both, tracked differently

Most Vista contractors collect both blanket certificates at the company level and project specific certificates at the job level. They behave differently and should be modeled differently:

• Company level or blanket: general liability, umbrella, workers’ comp, W9, business license. Renews annually, applies across jobs. In Billy this is handled through Company Level Compliance Tracking.
• Project specific: additional insured status, limits stepped up for a particular owner, project descriptions in the box. In Billy these are set with Requirement Groups, which let you vary requirements by project, vendor type, or trade.

The mistake we see most often is applying one global requirement set to every vendor, which produces either false non compliance on small vendors or under verification on high risk trades.

Verification is where the real risk sits

Collecting a certificate is the easy half. Verifying it is where compliance programs quietly fail, because the certificate face rarely tells you what you need to know. The endorsements do.

The four things most commonly accepted without confirmation:

• CG 20 10 additional insured, ongoing operations
• CG 20 37 completed operations, the one that matters after the sub leaves the site
• Primary and non contributory language
• Waiver of subrogation

A manual reviewer working through several hundred certificates a year will miss some of these. So will an AI working alone. We wrote about exactly where each one succeeds and fails in AI COI Review vs. Human Review. Billy’s AI Review Assistant reads endorsements, and the Managed Plan puts a human compliance team behind it. Here’s exactly what that review covers.

What changes when compliance moves upstream

Connecting Billy to Vista through Trimble App Xchange restructures the sequence:

1. Requirements are defined once, by project type, trade, or vendor type.
2. Billy requests the certificate from the vendor or their broker directly. No logins, no account creation for the sub. Templates for that first ask are in How to Request a COI from a Subcontractor.
3. Endorsements are reviewed, not just the certificate face.
4. Compliance status syncs to Vista so AP can make a payable or not payable call without an email thread.
5. Renewal outreach starts before expiration, not after. Automated 30 day, 15 day, and day of expiration emails go to the vendor and their broker. See the full list of automated emails Billy sends.
6. Reporting is standing, not ad hoc. 13 built in compliance reports cover global compliance, non compliant vendors, newly compliant, and audit exports.

The compliance hold doesn’t disappear. It just stops being the thing that tells you.

The prequalification gap Vista contractors keep hitting

A pattern worth naming: estimating teams go shopping for subcontractor prequalification software on their own, find a tool they like, and discover it doesn’t talk to Vista. Meanwhile project administration is running insurance compliance in a separate system. Two vendor lists, two onboarding flows, one very confused subcontractor.

Prequalification and COI compliance are the same conversation with the same vendor. Billy’s prequalification tool shares the vendor record with compliance tracking, so a prequalified sub is already set up for certificate collection, and prequalified vendors sync out to Vista, Procore, and Sage Intacct.

Useful next reads: Best Vendor Prequalification Software for Construction (2026) · Prequalification Activity Report · Automatic requalification on your schedule.

And then there’s lien waivers

Almost every Vista contractor who solves COI tracking asks about lien waivers next: same vendors, same subcontracts, same payment gate, same manual chase.

Billy handles document collection and signature through its DocuSign integration, which covers lien waivers, hold harmless agreements, and other signed documents alongside insurance. See DocuSign Templates and Tracking and Does Billy Track Hold Harmless Agreements? If you need a starting form, there’s a free subcontractor lien waiver form.

Self service or managed?

Two ways to run this, and the right answer depends on your headcount:

Most evaluations involve a controller, a CIO or IT lead, and the project administration team. Worth bringing all three to the same demo. The questions are different and they interlock.

Frequently asked questions

Also worth reading: COI tracking software for general contractors · Best COI Tracking Software for Construction · CMiC COI Compliance · Free 2026 Audit Ready Checklist