Customer Requests a Certificate of Insurance Before Paying? How to Clear It

Ask your broker for a certificate that names the customer exactly as they asked to be named, then send it through the channel they specified. A certificate of insurance, or COI, is a one-page summary of the policies you carry, and only your insurer or broker can issue one. That dependency on a third party is why this request adds days to an invoice that is otherwise approved and ready to pay. At Monk we see certificate requests hold invoices that already cleared every other approval in the buyer's system.

This post covers why buyers ask, what a certificate is and is not, the sequence to follow when the request arrives, and how to stop the same request from stalling your next invoice.

Why does a customer request a certificate of insurance before paying an invoice?

Buyers require proof of coverage from suppliers who work on their premises, handle their data, or otherwise carry risk on their behalf. Their risk or procurement team sets the requirement, and their AP system enforces it by holding payment against any vendor whose certificate is missing or expired. The hold is automatic, so the person who approved your work may have no idea the invoice is stuck.

Expiration is the most common trigger. A certificate you sent last year lapsed on its policy date, your vendor record flipped to non-compliant overnight, and the next invoice went on hold without a notice anyone at your company opened. Teams usually discover this when an invoice ages past 45 days for no visible reason.

What is a certificate of insurance and who issues it?

A certificate is a standardized one-page form summarizing the policies you hold: coverage types, limits, policy numbers, effective and expiration dates, and the parties named on it. Your insurer or your broker produces it. It reflects the coverage you already have and does not create any, so a request for a certificate showing something you do not carry is a request to change your policy.

This post describes the process of getting the document produced and delivered. What coverage you carry, which endorsements you agree to, and what any contract obligates you to provide are decisions for your broker, your risk owner, and your legal counsel. Get those answers in writing once and your AR team can handle every future request without escalating.

How do I get a certificate of insurance when a customer requests one before payment?

The sequence below is what a working process looks like when this request reaches an AR inbox. The first request from a given customer takes a few days because of the broker step; every request after that is administrative.

1. Capture the exact requirements in writing. Ask the buyer for the requirement as their risk team wrote it: coverage types, minimum limits, the exact legal name and address of the certificate holder, and any endorsements they want named. A certificate produced from a paraphrased request comes back rejected over a middle initial or a suite number more often than over the coverage itself.
2. Send the whole request to your broker in one message. Brokers turn around a standard certificate in a day or two when they have everything they need, and in a week when they have to come back to you twice for missing details. Include the invoice number and the date you need it by so the request is not queued behind routine renewals.
3. Check the certificate before you forward it. Compare the certificate holder name and address character for character against the request, confirm each limit meets or exceeds what was asked, and confirm the policy period covers the work you invoiced for. Two minutes of review here saves a rejection cycle that costs a week.
4. Flag anything your policy does not cover. If the request asks for a limit or an endorsement you do not carry, tell the buyer the same day rather than waiting for your broker to decline. Buyers frequently accept a lower limit or drop a requirement for a low-risk engagement, and they can only do that if someone raises it.
5. Deliver it the way the buyer specified. Some buyers want an upload to their AP or supplier portal, some route every certificate to a third-party compliance tracker, and some accept email to a monitored mailbox. Sending it to your day-to-day contact instead of the named destination is the single most common reason a certificate is never recorded against your vendor profile.
6. Record the expiration date and set a reminder. Put the policy expiration on the customer record with a reminder 45 days ahead, and do it for every customer holding a certificate. Renewing before expiry is what prevents the silent compliance hold that catches most finance teams once a year.
7. Confirm the hold cleared and get a payment date. Receipt of a certificate is a separate event from release of an invoice. Ask the buyer to confirm your vendor record now shows compliant and to give you the scheduled payment date for the specific invoice, since the record can clear while the invoice stays parked.

What do buyers commonly ask for on a certificate?

Requests use standard terminology that is worth recognizing, because the terms tell you who inside your company has to answer. The table below covers the six items that appear on almost every request.

What if the request arrives after the invoice is already overdue?

Treat it as a blocker with a deadline. Reply the same day acknowledging the request, tell the buyer the date your broker will produce the certificate, and ask them to schedule the invoice for the next payment run once the record clears rather than returning it to the back of the queue.

Ask in the same message whether other invoices from your company are on the same hold. Compliance holds apply at the vendor record rather than the invoice, so one expired certificate frequently stops everything you have open with that buyer. Finding that out now saves you repeating the whole exercise in two weeks.

How long does it take to get a certificate of insurance?

A standard certificate against coverage you already carry usually takes one to two business days from your broker. A certificate requiring a new endorsement takes longer, because the insurer has to approve the change, and a request for coverage you do not hold takes as long as buying that coverage.

Most of the delay comes from incomplete first requests rather than slow brokers. Teams that keep a standing list of each customer's insurance requirements on the account record get certificates back in a single cycle, because the broker never has to come back with questions.

How does Monk keep compliance requests from turning into aging?

A certificate request arrives looking like an email and behaves like a hold. It lands outside your ERP, it never appears on an aging report as a reason code, and it stops an invoice that passed every other approval. Our analysis shows around 39% of cash-flow slowdowns come from predictable, recurring exceptions of this kind.

Monk's intelligent collections ingests the context of each customer conversation and responds more effectively than standard dunning, so a reply asking for a certificate is handled as a blocker to clear instead of prompting another reminder. Across the $2B+ in receivables running on Monk, that approach produces about 24% higher response than standard dunning, resolves roughly 90% of collections without human intervention, and delivers an average DSO reduction of 40%.

Certificate holds cluster with the other document and data problems that park an approved invoice. If the buyer cannot locate the invoice at all, see customer says the invoice was never received. If the numbers on the invoice are the sticking point, see how to resolve a PO mismatch on an invoice, and for anything the buyer is contesting rather than missing, our guide to dispute resolution in AR covers the workflow. Monk goes live in 1 to 3 days and is SOC 2 Type II, so compliance documents move through a system your own risk team can approve.

Frequently asked questions

Can I issue my own certificate of insurance?

No. A certificate has to come from your insurer or your broker, because it attests to policies they hold. A document you produce yourself will be rejected by any buyer with a functioning compliance process.

Why is my invoice still on hold when I already sent a certificate?

The three usual causes are an expired policy period, delivery to the wrong destination, and a certificate holder name that does not match the buyer's records. Ask which specific field failed rather than resending the same document.

What does additional insured mean on a certificate request?

It is a request to extend certain coverage under your policy to the buyer. Whether to agree, and what it changes for you, is a decision for your broker and your legal owner rather than something an AR team should answer on its own.

How much does a certificate of insurance cost?

Brokers usually issue standard certificates against policies you already hold at no additional charge. Endorsements or higher limits can carry a premium, so ask your broker for the cost before you commit to a buyer's requirement.

How long is a certificate valid?

It is valid until the policy expiration printed on its face, which is why buyers re-verify at every renewal. Track the expiration date per customer, because an expired certificate flips your vendor record to non-compliant without any notice you will see.

Should I send a certificate before the customer asks?

For buyers that require one, providing it during onboarding avoids the first hold entirely. Ask during vendor setup whether a certificate is required and what the requirements are, then add the answer to the customer record.

What if the customer asks for coverage we do not carry?

Tell them the same day and ask whether a lower limit is acceptable for the scope of work. If they hold the line, buying the coverage becomes a commercial decision for your leadership, weighed against the value of the account.