Can You Track Certificates of Insurance in QuickBooks?

Last updated July 2026.

No. QuickBooks Online has no native feature for tracking certificates of insurance or their expiration dates. QuickBooks Desktop does include basic subcontractor insurance-certificate tracking, but Intuit never carried it over to QBO. QuickBooks Online users rely on workarounds: custom fields on the vendor record, notes, or a purchase-order trick. None of them read a certificate, verify coverage, or chase a renewal.

This question comes up constantly in Intuit's own community forums, and the answer from Intuit support has been consistent for years: the feature is not there. If you are a bookkeeper, controller, or AP manager who already lives in QuickBooks, that is frustrating, because the vendor list you need to police is sitting right in front of you.

Here is exactly what QuickBooks can and cannot do, what the workarounds actually cost you, and where the line sits between a workaround and a real system.

What QuickBooks Online can and cannot do with COIs

Task	QuickBooks Online	QuickBooks Desktop
Store a COI PDF against a vendor	Yes, as an attachment	Yes, as an attachment
Record an expiration date	Only via a custom field or note	Yes, a built-in field
Warn you before a policy expires	No	Limited, on the vendor record
Read the COI and pull limits automatically	No	No
Check limits against your requirements	No	No
Verify additional insured or waiver of subrogation	No	No
Email a vendor for a renewed certificate	No	No
Produce a compliance report	No	No

The pattern is clear. QuickBooks is an accounting system, and it treats a certificate as a file you attached to a vendor, not as coverage you have to prove. Every part of the job that involves reading, judging, or chasing the certificate falls back on a person.

The three QuickBooks Online workarounds, and what each one really costs

1. Custom fields on the vendor record

QuickBooks Online Plus and Advanced let you add custom fields, so you can create an "Insurance expires" date field on each vendor. This is the cleanest workaround and the one most bookkeepers land on. You can then filter or export the vendor list by that date.

What it costs you: someone still opens each PDF, finds the expiration date, and types it in. The field holds whatever gets typed, including a typo or a date read off the wrong policy line. And nothing tells you when the date passes. You have to remember to run the report.

2. Notes on the vendor profile

You can drop the expiration date into the vendor's notes field. It takes seconds and works at very small scale.

What it costs you: notes are not a data field, so you cannot sort, filter, or report on them. At more than about ten vendors this stops being a system and becomes a place where information goes to be forgotten.

3. The purchase-order method

A workaround that circulates among construction bookkeepers: create a purchase order for each vendor's liability certificate, record the received and expiration dates, attach the PDF, and close the PO. It gives you a dated record you can search.

What it costs you: you are bending a purchasing document into a compliance log. It clutters your PO reports, confuses anyone who inherits the file, and still does not verify a single limit.

Why none of the workarounds solve the real problem

Every QuickBooks workaround stores a date. That is worth something, but storing a date is the easy 10 percent of COI tracking. The work that actually protects you is the other 90 percent:

Reading the certificate. An ACORD 25 has general liability, auto, umbrella, and workers compensation limits scattered across it, plus a description of operations box that carries the endorsement language. Someone has to read all of it.
Judging it. A stored certificate does not tell you the general liability limit is 500,000 dollars when your contract requires 1,000,000, or that the additional insured endorsement your lease demands is missing.
Chasing it. Vendors do not send renewals unprompted. Someone has to notice, email, and follow up, usually more than once.
Proving it. When a client, insurer, or auditor asks who is compliant right now, a custom field cannot answer. A person assembles the answer by hand.

This is why a vendor with a perfectly maintained QuickBooks expiration field can still end up with an uninsured subcontractor on a job. The date was tracked. The coverage was never verified.

How much does this actually matter?

It depends entirely on your exposure, and it is worth being honest about that rather than alarming you. If you use three vendors, they are all long-standing, and none of them set foot on a property you are responsible for, the custom-field workaround is genuinely fine. Do not buy software for that.

The calculus changes when any of these are true: you are a general contractor whose subs' coverage can be pulled into your workers compensation audit as your own payroll; you manage property and your lease requires you to name the owner as additional insured; you sign contracts with insurance requirements you have to be able to prove you enforced; or your vendor count is past roughly 20 and growing. At that point the manual reading is the bottleneck, not the storage.

Should you move COI tracking out of QuickBooks entirely?

Not entirely, and this is where a lot of advice goes wrong. QuickBooks should stay your system of record for who your vendors are, what you pay them, and what you file for them at year end. That is what it is good at. Vendor payment records also drive your year-end contractor filings, and the 1099-NEC threshold rose from 600 dollars to 2,000 dollars for payments made on or after January 1, 2026, so that side of the vendor file is getting its own attention this year.

What should move out is the compliance judgment. Dedicated COI tracking that runs alongside QuickBooks reads each certificate, checks it against the requirements you set, flags what is short or missing, and emails vendors before coverage lapses. QuickBooks keeps the money. The COI system keeps the proof. Neither has to pretend to be the other.

Frequently asked questions

Can you track certificates of insurance in QuickBooks Online?

Not natively. QuickBooks Online has no built-in certificate of insurance tracking. You can attach the PDF to a vendor and record an expiration date in a custom field on the Plus or Advanced plans, but QBO will not read the certificate, verify coverage limits, or alert you before a policy expires.

Does QuickBooks Desktop track subcontractor insurance certificates?

Yes, partially. QuickBooks Desktop includes a basic field for subcontractor insurance certificate dates on the vendor record, which QuickBooks Online does not have. It still only stores the date. It does not read the certificate, check limits against your requirements, or request a renewal from the vendor.

How do I set up a COI custom field in QuickBooks Online?

On QuickBooks Online Plus or Advanced, go to Settings, then Custom fields, and add a new field of type Date applied to Vendors. Name it something explicit such as "COI expires." You can then filter the vendor list by that field and export it. You will still need to enter and maintain every date by hand.

Is a spreadsheet better than QuickBooks for tracking COIs?

A spreadsheet is more flexible, because you can record limits, endorsements, and coverage types alongside the expiration date rather than a single custom field. It has the same core weakness: it stores whatever you type and verifies nothing. Both work at small scale and both break at volume. Our certificate of insurance tracking spreadsheet page covers where that line sits.

What is the best way to track vendor COIs if I use QuickBooks?

Keep vendor records and payments in QuickBooks, and run certificate compliance in a system built for it. The COI system handles collection, reading, verification against your limits, renewal chasing, and reporting, while QuickBooks stays your accounting record. Most teams past about 20 vendors find this split cheaper than the hours spent maintaining a manual field.

The short version

QuickBooks Online cannot track certificates of insurance, and no workaround changes what it fundamentally does not do: read a certificate and tell you whether the coverage is good. The custom-field approach is a reasonable stopgap for a handful of vendors. Past that, you are paying a person to do work that should be automatic, and the risk you are carrying is not the missing date. It is the coverage nobody checked.

PDF, JPG, PNG, BMP, HEIC, TIFF