How Compliance Tracking Works in Viewpoint Vista

If your company runs on Viewpoint Vista, you’ve probably heard that it “handles compliance.” And it does, to a point. Vista has real compliance infrastructure built in: compliance codes, compliance groups, an AP verification flag, and hooks into subcontract and purchase order workflows.

But most controllers and AP managers we talk to are still chasing certificates manually, getting surprised by expired COIs at payment time, and spending hours every week on vendor follow-up that Vista was never designed to eliminate.

This guide explains exactly how Vista’s compliance system works, what it’s genuinely good at, and the specific gaps that cause most of the pain.

---

The basics: what “compliance” means in Vista

In Vista, compliance tracking is built around three connected concepts: compliance codes, compliance groups, and the Verify flag in Accounts Payable. Together, they let you assign document requirements to subcontracts and purchase orders, then block or warn at payment time if those requirements aren’t met.

This is more sophisticated than most people give it credit for. The challenge isn’t that Vista can’t track compliance. Vista tracks compliance status, while someone still has to collect and validate the underlying documents. That gap is where manual work lives.

---

Compliance codes: the building blocks

A compliance code in Vista represents a single trackable requirement — think of it as a line item on a compliance checklist. Common examples include:

• Certificate of insurance (COI) on file
• COI meets required coverage limits
• W-9 collected and verified
• Business license current
• Certified payroll report received
• Master Service Agreement executed
• Lien waiver on file

Each code carries a few key properties:

• Description: What document or condition is being tracked
• Expiration tracking: Whether the item expires and how far in advance Vista should flag it
• Verify setting: Whether this code should trigger an AP hold when not met
• Apply to level: Whether this requirement applies to the vendor, or cascades down to their own suppliers

Codes are created once and reused across multiple groups. If every subcontractor needs a COI, you create that code once and reference it in every relevant compliance group.

---

Compliance groups: assigning requirements to subcontracts and POs

A compliance group is a named collection of compliance codes. When you create a subcontract in PM Subcontract Header, or a purchase order in PM Material Detail, you assign a compliance group to it. That group tells Vista which compliance codes apply to that vendor relationship.

Once a compliance group is attached to a subcontract or PO and interfaced to accounting, Vista can begin checking compliance status when that vendor appears in AP workflows.

This is genuinely useful architecture. The problem is that Vista’s compliance tracking is only as current as the data someone manually enters. The codes are flags — they don’t automatically know whether the COI you received yesterday meets your coverage requirements.

---

The BILLY compliance code: how the integration is set up

When you connect Billy to Viewpoint Vista through the AppXchange integration, one of the first setup steps is creating a dedicated compliance code in Vista called BILLY.

This is the mechanism that allows Billy’s compliance data to surface inside Vista’s workflows. When Billy verifies a vendor’s COI or W-9, it updates the status of the BILLY compliance code in Vista, so your AP team sees current compliance status in the system they’re already working in — without logging into a separate platform.

Once that’s in place, compliance status flows bidirectionally: Billy collects and reviews documents, updates the status, and Vista’s AP workflows reflect it.

---

The AP Verify flag: Vista’s payment hold mechanism

The Verify flag is the enforcement mechanism in Vista’s compliance system. When a compliance code is set to Verify = Y, Vista displays a warning when someone attempts to process an invoice for a vendor whose compliance status isn’t current.

Depending on how your AP workflows are configured, this operates as:

• A soft warning: a message is displayed, but the invoice can still be processed
• A hard block: the transaction cannot proceed until compliance is resolved or manually overridden

From a risk management perspective, this is exactly the right design. You don’t want to pay a subcontractor whose insurance has lapsed. The flag gives accounting a checkpoint.

The operational problem is what happens next. When the AP Verify flag fires, someone has to resolve it: identify the code, contact the vendor, receive and review the document, enter it into Vista, and clear the hold. At low volume, manageable. At 50–500 active subcontractors, it becomes a significant and unpredictable operational burden.

---

SLHD and SLIT tables: why permissions matter

Two database tables are central to Vista’s compliance tracking: SLHD (Subcontract Header) and SLIT (Subcontract Item). These tables store the subcontract records and line-item data that compliance codes are attached to.

When setting up any external integration with Vista (including Billy through AppXchange), the Vista service account needs read/write access to these tables. Without it, the integration can’t match vendors to subcontracts or update compliance status correctly.

---

What Vista compliance tracking does well

Before getting into the gaps, it’s worth being clear about what Vista’s built-in system handles effectively:

• Compliance code infrastructure: the framework for defining what documents you need from each vendor category is solid and flexible
• AP integration: the Verify flag creates a real enforcement point at the payment workflow, which is exactly the right place to catch gaps
• Compliance group flexibility: different requirement sets for different subcontract types is genuinely useful for large GCs with varied vendor relationships
• Cascade tracking: Vista can track compliance at the sub-tier level, requiring your subcontractors’ suppliers to also meet certain requirements
• Reporting: once data is entered correctly, Vista’s reporting capabilities let you see compliance status across projects and vendors

---

Where Vista compliance tracking consistently falls short

Vista’s compliance system was built to track status. The collection, review, and renewal of the underlying documents — that’s outside its scope. Here’s where that creates real problems:

1. Vista doesn’t collect documents

Vista has no mechanism to send a vendor a request for their COI, follow up when they don’t respond, or receive and store the document. That workflow lives in email, and in most organizations it means one person spending a significant portion of their week chasing certificates.

2. Vista doesn’t review documents

When a COI arrives, Vista doesn’t know whether the coverage limits are sufficient, whether the general contractor is listed as additional insured, or whether the policy effective date actually covers the project period. A missed endorsement or insufficient coverage limit doesn’t trigger a Vista compliance flag. It just means you’re carrying a risk you don’t know about.

3. Vista doesn’t track expiration proactively

Vista can flag a compliance item as expired after someone updates the expiration date. But it doesn’t automatically know when a policy is about to expire and send a renewal request to the vendor. That means you find out about expired certificates when someone tries to process a payment — not 30 days before expiration when there was still time to act.

4. Manual entry creates lag and errors

Every document that needs to be reflected in Vista has to be manually entered by someone on your team. In a busy AP environment, there’s often a gap between when a document is received and when it’s entered, which means Vista shows a hold for a vendor who is actually compliant.

5. Vendor onboarding is unstructured

Vista’s compliance system works well once a subcontract exists. But getting the right documents from a new vendor before the subcontract is executed happens entirely outside Vista, usually via email with no standardized process.

---

How Billy fills the gaps for Vista contractors

Billy is built to handle exactly the parts of compliance that Vista’s infrastructure doesn’t cover. The integration is designed so that Billy does the document collection, review, and renewal work — and Vista’s compliance status reflects the output.

Automated collection and renewal requests

When a vendor is set up in Billy, the platform automatically sends a collection request for their COI, W-9, and any other required documents. As expiration dates approach (typically 30 and 60 days out), Billy sends renewal reminders to the vendor and their broker automatically. No calendar reminders. No manual follow-up emails.

Document review by licensed insurance professionals

On managed plans, Billy’s team reviews every incoming COI against your specific contract requirements: coverage limits, endorsement language, additional insured status, and effective dates. The AI Review Assistant handles the initial pass; licensed insurance professionals handle escalations. Your AP team gets a clear compliant/non-compliant status, not a stack of PDFs to interpret.

Real-time status in Vista

Through the AppXchange integration and the BILLY compliance code, current compliance status flows into Vista. When AP is processing invoices, they see whether the vendor is compliant — and the evidence (the actual COI) is accessible from Billy without leaving the workflow.

Structured vendor onboarding

Before a subcontract is ever executed, Billy can send a structured onboarding request to the vendor. They submit their documents once, through a portal that doesn’t require creating an account. Billy extracts the key fields, pre-fills the vendor record, and keeps everything in a single auditable trail.

---

Vista + Billy: complement, not replacement

Vista’s compliance infrastructure — the codes, groups, and Verify flag — is genuinely useful and worth keeping. Billy doesn’t replace it. The two systems do different jobs:

• Vista owns the AP enforcement layer: the flag that catches non-compliant vendors at payment time
• Billy owns the document layer: the collection, review, renewal, and evidence storage that keeps compliance current before it ever reaches the AP queue

When both are working together, AP holds become rare rather than routine — because the compliance inputs are being managed proactively, not reactively.