It’s the end of the month. You’re working through the payment queue. A vendor invoice gets flagged. Compliance not met. Hold. Now you’re not processing invoices — you’re figuring out which document is missing, calling the vendor, waiting for a certificate. Meanwhile, the subcontractor is calling the project manager asking why their check is late.
Vista’s AP compliance hold is the right concept in the wrong workflow. The hold itself isn’t the problem. The problem is that it fires at exactly the wrong moment: when you’re trying to pay someone, rather than 30 days earlier when there was still time to collect a renewal without stopping anything.
This guide explains how Vista’s Verify flag works, why holds happen, and what the process change looks like to prevent them from becoming a routine part of your AP cycle.
How Vista’s AP Verify flag works
Vista’s compliance hold system is built around a setting on individual compliance codes called the Verify flag. When this flag is set to Y on a compliance code, Vista checks the current status of that requirement before allowing an invoice to move through AP.
The check happens when a vendor invoice comes up for processing. If the vendor’s compliance status for any Verify = Y code is not current — whether because a document expired, was never collected, or was never entered into Vista — Vista surfaces a warning or blocks the transaction entirely.
- A soft warning: a message is displayed, but the invoice can still be processed
- A hard stop: the transaction cannot proceed until compliance is resolved or manually overridden
Most organizations configure high-stakes requirements like COIs as hard stops. Either way, when the flag fires, someone’s attention is getting pulled away from the payment queue to resolve a compliance issue.
The four most common reasons Vista AP holds fire
In our experience with Vista contractors, the same root causes come up repeatedly:
The document expired and nobody caught it in advance
The expiration date sits quietly in Vista until someone tries to process an invoice. Then Vista flags it. At that point, you’re starting the renewal collection process while the payment is on hold. With 200 active subcontractors, you likely have 15–25 certificate expirations in any given 30-day window.
The document was received but never entered into Vista
Especially common during busy seasons or after team turnover. A COI renewal came in by email, got filed, and simply wasn’t entered into Vista. The vendor is actually compliant — Vista doesn’t know it. Someone spends 20 minutes tracking down a document that already exists.
The vendor wasn’t fully onboarded before work started
Subcontractors sometimes start work before all compliance documents are collected. The AP hold is often the first time accounting realizes there’s a gap, even though the vendor has already been on-site for weeks.
The document exists but doesn’t meet requirements
A COI is on file. But the certificate shows $500k general liability, and your subcontract requires $1M. This kind of gap is often missed at collection time because nobody reviewed the coverage limits against the contract requirements.
The real cost of reactive compliance management
Most organizations think about AP holds as an inconvenience. They’re actually a symptom of a more expensive process problem.
- Direct labor cost: At 10 holds a month, that’s 5–10 hours of AP staff time every month on unplanned work that arrived without warning.
- Delayed payments: Subcontractors who experience regular payment delays will price that uncertainty into their bids.
- Coverage gaps you don’t know about: Every hold resolved by a quick override represents a period where the GC is carrying liability that should be on the subcontractor’s policy.
- Audit exposure: The question isn’t “did you eventually get the document?” It’s “was the document current when the vendor was working?”
Why Vista’s compliance system wasn’t designed to prevent holds
It’s worth being clear about what Vista’s compliance framework does and doesn’t do — not as a criticism, but because misunderstanding it leads to process designs that create unnecessary holds.
Vista’s compliance system is a status tracking and enforcement tool. It was never designed to be a collection system.
What Vista’s compliance system doesn’t do:
- Send collection requests to vendors when a compliance item is missing or expiring
- Review incoming documents against your contract requirements
- Automatically update compliance status when a policy renews
- Proactively alert your team to upcoming expirations before they hit the AP queue
- Provide vendors with a structured portal to submit documents without email back-and-forth
These capabilities require a dedicated compliance collection tool — one that’s integrated with Vista so the status it maintains feeds back into the Verify flag workflows, rather than living as a separate system your team has to reconcile manually.
The process change that prevents holds
The core shift is moving from reactive to proactive compliance management. Instead of finding out about expiring certificates when an invoice is flagged, your team knows about upcoming expirations 30–60 days in advance and has already initiated renewal collection before it becomes an AP problem.
BILLY compliance code, current compliance status feeds directly into Vista. When AP processes an invoice, the Verify flag check reflects what Billy’s review confirmed — not what was manually entered by someone on your team last week.What this looks like for your AP team
The day-to-day experience for an AP manager running Vista + Billy looks different than managing compliance in Vista alone:
| Scenario | Vista only | Vista + Billy |
|---|---|---|
| COI expires in 30 days | AP discovers it when invoice is processed | Billy sends renewal request to vendor and broker automatically |
| New subcontractor added | Email chase for COI and W-9 before setup in Vista | Billy sends structured onboarding request; documents collected before first invoice |
| COI received in email | Manual data entry into Vista to update status | Billy extracts data, updates status, feeds into Vista automatically |
| Invoice for non-compliant vendor | AP hold fires; team researches and chases vendor | AP hold fires only for genuine issues; evidence is on-demand for faster resolution |
| Audit request for vendor COI history | Search email threads and shared file servers | Single auditable compliance trail per vendor in Billy, accessible on-demand |
One thing that doesn’t change
The AP Verify flag in Vista is still the right enforcement mechanism. The goal isn’t to disable it — it’s to make the compliance inputs it’s checking always accurate and current.
The AP Verify flag fires when there’s a genuine compliance issue, not when your team fell behind on paperwork. That’s the difference between a compliance system that creates friction and one that protects the business.
Reduce AP holds from routine to rare
Walk through how Billy integrates with Vista and what your vendor compliance process would look like at your current subcontractor volume.
Summary
Vista AP holds happen because the Verify flag catches compliance gaps at payment time — which is exactly the wrong moment to be starting the collection process. The four root causes (expired documents, documents not entered, incomplete onboarding, and coverage gaps) all have a common fix: a proactive compliance collection process that handles renewals, reviews, and vendor onboarding upstream of the AP queue.
Through the Billy + Vista integration, compliance status in Vista reflects real-time document collection and review rather than manual data entry, so the Verify flag fires when there’s a genuine problem, not when your team fell behind on paperwork.
Want to understand how Vista’s compliance system is structured from the ground up? Read: How compliance tracking works in Viewpoint Vista →
