QuickBooks Online Vendor Insurance Evidence Index

August 23, 2026

Bottom line: every active vendor that requires insurance should be linked to a certificate on file that is legible, covers the required coverage types, and shows current dates, with any lapse held as a visible exception before a new bill is approved.

Sidebar: Insurance proof protects the hiring business. The index keeps the proof timely.

Why vendor insurance tracking matters for AP

Vendor insurance looks administrative until a claim appears. A contractor injures a worker on a client site, a property incident occurs, or a compliance review asks why an uninsured vendor was paid for high risk work. When the certificate is missing, expired, or unclear about coverage scope, the business that hired the vendor faces a coverage conversation it cannot win with goodwill alone. Many companies require general liability, workers compensation, auto, or umbrella coverage depending on the vendor's work, and they make continued engagement contingent on current proof.

For QBOAssistant clients, the virtual assistant often maintains document organization in support of accounts payable controls: collecting certificates presented by vendors, filing them in a controlled index, noting coverage types and dates, tying vendors in the review back to vendors in QuickBooks, checking that the certificate's insured name matches the vendor, and organizing renewal outreach. The assistant does not decide coverage adequacy, negotiate policy limits, or approve a lapse for convenience. An index preserves that boundary by keeping evidence, verification, and the reviewer question together until an authorized decision.

Without a structured index, the check is reactive. A bill arrives from a vendor whose general liability certificate expired two months ago, yet the bill is approved because the approval view does not surface the lapse. The index makes the lapse part of the AP decision.

Set the scope before indexing

Start with a report set that defines which vendors require insurance. In QuickBooks Online this usually includes the Vendor List and the Vendor Contact List, filtered by vendor type, service category, or any insurance flag the business maintains, paired with open and recently paid bills that indicate activity. Pair that view with the actual certificate file store the business uses, whether that is the AP document folder, a vendor master folder, or a compliance tool. Save the population before chasing renewals. Record the pull date, the filter used to flag insurance required vendors, preparer, and reviewer.

Group the index by vendor and then by coverage type. The useful structure shows one vendor and each required coverage the business expects from that vendor, such as general liability, workers compensation, auto, or umbrella, each with its own certificate row when separate documents exist. If a single certificate package covers multiple types, keep it as one file with a column that names the covered types so an invoice for a specific scope does not appear covered when only a subset is.

State exclusions. For example, vendors who supply only goods, one time parts suppliers, or small dollar service vendors below a threshold may not require vendor insurance under policy, and utility or lender vendors would not be expected to provide it. A clear scope note prevents an incomplete index from appearing as missing when those vendors were intentionally outside the required set.

Record the evidence for each vendor and certificate

For each vendor in scope, capture internal and external support side by side in one row per coverage type. Internal support begins with QuickBooks: vendor display name and ID, vendor type or service category, active or inactive status, last bill date and amount indicating recent activity, and any insurance note or custom field that records the business's expectation.

External support is the certificate file itself: file name, stored location, legibility check such as clear versus partial, completeness check such as insured name present, insurer, policy number, coverage type and limits as shown, additional insured handling as required, effective and expiration dates, and whether the certificate holder is recorded as required. Add the verification note that records whether the coverage type matches the scope the business requires for that vendor.

Add a coverage period check for the review period. For each month in which the vendor billed for covered work, indicate whether a certificate covered that month. That month by month row makes it easy to see whether an expired certificate left any billed period exposed.

Check three elements for every vendor and coverage type. First, the stored certificate should match the vendor's legal name, not a staffing firm or related entity that would not cover the vendor that actually performed the work. Second, the certificate should be legible and complete, with dates, coverage types, and insurer visible rather than cut off. Third, coverage dates should actually cover the invoiced periods where the review expects protection. Each check gets its own result so the reviewer sees a specific gap rather than a vague flagged.

Sort the exception patterns helpfully

Expired with recent bill is the most common exception. A certificate valid through May 31 supported February through May, but bills dated June 15 and July 10 from the same vendor were processed while the file was stale. Flag June and July as lapse exposure. Keep the last valid period, the expired date, and the flagged bill references together. Draft a renewal request that asks for the specific coverage types rather than a generic ask.

Incomplete is a second pattern. The certificate on file is a phone photo that is legible for limits but cuts off the effective date line. Flag the file as incomplete. Record what is present and what is missing, and request a complete copy referencing the specific lines.

Name mismatch appears when the certificate says JD Roofing LLC while the QuickBooks vendor is JDR Construction Group. Close is not exact. Flag the account as name variance. Record both names and whether the address and contact align. The reviewer decides whether the certificate actually covers the vendor entity being paid or whether the vendor should supply a corrected certificate or an explanation.

Coverage type gap is a third exception. A vendor that performs on site electrical work has a general liability certificate but no workers compensation evidence where the policy requires it. Flag the vendor as missing required coverage type. List the expected types for that vendor category, the types on file, and the gap. The VA prepares the request. The reviewer decides whether an exemption or documented alternative applies.

No certificate at all is a setup exception. A vendor flagged as insurance required has no file in the index even though it billed for covered work recently. Flag the vendor as certificate absent. Do not set a due date for the bill that masks the priority.

Renewal outreach stalled is an operational exception. A renewal request was sent three weeks ago, no updated certificate has arrived, yet bills continued. Flag the vendor as renewal pending with outreach dates. The reviewer decides whether to hold further bills for that scope, approve conditional processing with a documented risk note, or pause the vendor until evidence arrives.

Build the index the AP owner can use

A practical index fits on one file with links and ownership. Start with a cover sheet that names the business, period, vendor categories in scope, preparer, reviewer, number of vendors requiring coverage, number of certificates reviewed, and the count of expired, incomplete, mismatched, type gap, absent, and stalled vendors. That header tells the reviewer where exposure sits before the row detail does.

Follow with the certificate table, one row per vendor and coverage type, or per vendor where no certificate exists. Useful columns include vendor, QuickBooks ID, service category, coverage type required, insured name on the certificate, insurer, policy number if present, limits shown, effective date, expiration, stored file location, coverage months checked, verification results for name, legibility, and type, exception status, and owner.

Add the exception queue that isolates rows needing judgment: expired lapse, incomplete, name variance, coverage gap, absent, or renewal stalled. Each row carries vendor, certificate reference when present, affected bill dates, exception type, exposure months, evidence link, impact note, and owner. An impact note can be short and factual: July bills of 18,600 processed after general liability lapsed, or crew work billed without workers compensation evidence on file.

Include a renewal calendar that shows certificates expiring in the next 60 or 90 days and the proposed outreach date. That calendar allows the VA to request renewals before coverage ends rather than discovering the lapse when an incident occurs.

Include a holdings note that lists vendors intentionally outside the next renewal round because they are inactive, have no recent covered work, or have an approved coverage alternative with documented reason and expiration.

Use simple statuses such as covered and legible, expired pending renewal, incomplete pending resubmission, name variance pending confirmation, coverage type gap, certificate absent, renewal requested awaiting file, or awaiting reviewer decision. Close an exception only when a complete certificate covering the relevant period is filed, the vendor link is corrected, or the reviewer approves a documented alternative with a stated expiration.

Cadence and responsibility

For active trade and contractor vendors, refresh the index monthly before AP is presented for payment approvals. The VA checks expirations, verifies legibility and name match for any new file received, and drafts specific renewal requests. The AP owner approves which vendors remain eligible for dispatch and which invoices should be held. For smaller contractor populations, a quarterly pass before insurance renewal plus an immediate hold whenever an expired lapse is found is enough.

Archive the index with certificate file references, bill exports for the period, renewal outreach copies, and the exception queue so a later reviewer can verify which periods were exposed and how the business responded.

A reviewer should be able to answer five questions after reading the index: which vendors have current coverage for the period, which services are exposed by a lapse, which new files are complete and correctly linked, which renewals are outstanding, and who owns each exception.

Quality checks that help include asking whether every active vendor flagged as insurance required maps to a covering certificate and coverage type, whether any certificate is truncated or unreadable, whether any expiration left new work exposed without a flag, whether any name variance was resolved with an explicit approval, and whether any bill was approved for payment after its coverage had clearly lapsed.

The QBO cleanup and catch-up VA service frames how document organization support should remain separate from risk acceptance. For general close discipline, pair this with the QuickBooks month-end close packet.

What good looks like

Good looks like vendors dispatched only after their coverage is confirmed, renewal requests sent before expiration, lapses holding invoices where the business decided to hold them, and the file ready before anyone asks. AP does not discover coverage problems from an incident report. And the VA never has to decide alone whether a crew can work without its general liability current.

Next step

Pilot the index on ten vendors that represent the mix: two that present a certificate package, three that owe a renewal this quarter, two recently active vendors with no file, and three that illustrate the exception patterns above. Build coverage rows, check legibility and name match, surface exceptions, and draft one concise question per flagged vendor that would let the owner decide without rework. Review the index for readability. Keep fields that made coverage obvious, remove fields that added noise, and reuse the approved index on the normal monthly or quarterly rhythm. That careful start turns a scattered certificate folder into a controlled AP workflow without changing coverage approval in QuickBooks Online.