Customer Requests a Certificate of Insurance Before Paying

When a customer asks for a certificate of insurance before paying, treat it as a compliance blocker on the vendor record rather than a stalling tactic, and get a certificate from your broker naming the exact contracting entity within a day. Monk is an AI-native invoice-to-cash platform that runs invoicing, AP portal submission, collections and cash application as one system, so a document request of this kind is tracked against the invoice it is holding up rather than lost in a mailbox. The request is routine. What costs money is the fortnight that passes while it sits unanswered, the certificate returns naming the wrong entity, and the invoice rolls into the next ageing bucket.

A typical sequence runs like this. You invoice on net 30, and on day nine a vendor compliance analyst asks for a current certificate of insurance. You forward the request to your broker, who replies four days later with last year's certificate. The buyer rejects it because the certificate holder is the parent company rather than the operating subsidiary on the purchase order. By the time a corrected certificate is accepted the invoice is 45 days old and has missed two payment runs.

What is a certificate of insurance and why does payment depend on it?

A certificate of insurance is a one page summary of your policies issued by your broker, and buyers make payment conditional on it because their contract requires evidence of cover before they take on the risk of your work.

The standard form in the United States is the ACORD 25, Certificate of Liability Insurance. It lists the producer, the named insured, each insurer with its NAIC number, the policy numbers, the effective and expiry dates, and the limits for each line of cover. It is evidence of a policy rather than the policy itself, which is why buyers who care about risk transfer also ask for the endorsement pages behind it.

Three motives sit behind the request. Risk transfer comes first: if your work damages property or injures somebody, the buyer wants your insurer to respond rather than theirs. Contractual compliance comes second, because the insurance schedule in the master services agreement usually makes evidence of cover a condition of payment. Vendor onboarding is third, since the certificate unlocks the supplier record alongside the W-9, the bank verification and the signed terms.

The practical effect is a flag on your vendor master record. Where insurance is marked expired or missing, the invoice fails the compliance check and the payment proposal excludes it. Nobody at the buyer has decided against paying you. Their system will not let the payment through.

Which fields does the buyer's compliance team check?

Reviewers work through a short and predictable list, and a certificate failing any one item is returned without the rest being read.

Larger buyers do not review this by hand. Certificates are uploaded into a compliance platform such as myCOI, TrustLayer, Avetta, ISNetworld or Veriforce, or into the risk module inside SAP Ariba or Coupa, and the platform grades the certificate against the contract profile. A fail generates an automated rejection naming the deficient item, which is useful to you because it tells your broker what to fix.

Ask for the insurance schedule from the contract before you go to your broker. Section headings vary, and the requirements usually sit in an exhibit rather than the body of the agreement. Sending your broker the exhibit rather than a paraphrase removes a full round trip.

Why does a certificate naming the wrong legal entity get rejected?

The certificate is a legal document the buyer relies on in a claim, so a certificate holder that does not match the contracting entity gives them nothing to rely on.

Group structures cause most of these rejections. The purchase order comes from an operating subsidiary, the contract was signed by a holding company, and the invoice goes to a shared service centre in a third country. Your broker, given none of that, issues the certificate to the brand name everybody uses. The platform compares the certificate holder string against the contract profile and returns a mismatch.

The same problem appears on your own side. If the named insured is your parent company and the invoice comes from an operating subsidiary, the reviewer cannot confirm that the entity doing the work is insured. Where you invoice through multiple entities, tell your broker which one is on the contract.

Get the exact strings from the source documents rather than from memory. The certificate holder name and address should be copied from the contract signature block or the purchase order header, character for character, including the legal suffix and the suite number. Put the purchase order number in the description of operations box so the reviewer can match it to the file.

How do you get a corrected certificate from your broker quickly?

Send your broker one message containing the insurance exhibit, the exact certificate holder details and the endorsements requested, and ask for the certificate with its endorsement pages attached.

Brokers can usually issue a certificate the same day when the request is complete, because the policies already exist and the certificate is generated from their system. Delay comes from incomplete requests. A message saying the client needs a certificate starts a chain of questions. A message giving the named insured, the certificate holder name and address, the contract reference, the required lines and limits, and the specific endorsement forms produces a document that passes first time.

Endorsements deserve separate attention. Additional insured status, primary and non-contributory wording and waiver of subrogation are policy amendments rather than tick boxes, and some carriers charge for them or decline them on certain classes of business. Where an endorsement is not available, find out early, because you then have a commercial conversation rather than a document problem, and that belongs with your account owner and their contract manager.

Ask your broker to set a renewal reminder that issues fresh certificates to every certificate holder before the policy expiry date. Most brokerages do this as standard if asked, which turns an annual scramble into a scheduled task.

What happens to the invoice while the certificate is outstanding?

It ages invisibly, because the hold sits on the vendor record rather than the invoice, so your collections notes show no dispute and no promise to pay.

Keep the invoice moving on two tracks. On the first, confirm in writing that the invoice itself is approved and only the compliance flag is outstanding, and ask which payment run it falls into once the certificate is accepted. That question gives you a date, and it reveals cases where a second problem is hiding behind the first, such as a missing purchase order.

On the second track, work the document. Send the corrected certificate through the channel the buyer uses for compliance, usually the portal or the compliance platform rather than email. Across the receivables Monk manages, 92% of enterprise invoices must be submitted through a vendor portal or network rather than paid from an emailed invoice, and the same holds for the documents that release them. Note the reference number in your reply.

Log all of it against the invoice, with the request date, the rejection reason, and the date the corrected certificate was accepted. An invoice held for a document is a different problem from an invoice held for a dispute, and mixing the two makes your ageing report tell you the wrong story.

Why keep a current certificate on file per customer?

Because a certificate requested per invoice is late by definition, while one held per customer and refreshed at renewal is never the reason a payment slips.

Build a register with one row per customer: the contracting entity, the certificate holder name and address exactly as contracted, the required lines, limits and endorsements, the compliance platform they use, the upload route, the current expiry date, and the name and email of the reviewer. Attach the accepted certificate to the customer record.

Set two reminders against each row, one thirty days before the policy expiry and one thirty days before contract renewal. Buyers frequently change their requirements at renewal, and learning that in advance is cheaper than learning it from a rejection notice on an invoice you needed paid this month.

Fold the certificate into onboarding. When you set a customer up, collect the insurance exhibit, the certificate holder details and the compliance route at the same time as the purchase order requirements, remittance instructions and the accounts payable contact. Each of those is a document that can hold a payment, and gathering them at the start costs one conversation.

How does Monk handle this?

Monk keeps document requirements attached to the customer and the invoice, so a certificate request is worked as a tracked exception with an owner.

When a buyer replies asking for a certificate, Monk's Intelligent Collections reads the message and treats it as a document exception on the invoices it affects rather than as a payment refusal. Julia, Monk's AI agent for Intelligent Collections, ingests the context of the conversation, so follow ups reference the request that was made instead of repeating a generic reminder. Julia sees a 24% higher response rate than standard dunning, and 90% of collections are resolved with zero human intervention.

Edge cases such as this cause 39% of cash flow slowdown, which is why they belong in the same system as the invoicing and the cash. Monk's AI cash application matches 80% of receipts automatically, rising to 95% with suggested matching rules, and connects to QuickBooks, NetSuite, Salesforce, HubSpot, Stripe, Slack, Gmail and Docusign. Monk is SOC 2 Type II compliant and manages $2B+ in accounts receivable. Teams report a 40% average reduction in DSO and 26 hours a month saved.

Where should you start?

Run this checklist against your five largest customers and see how many rows you can complete without asking anybody.

For each customer, write down the contracting entity on the contract, the certificate holder name and address as contracted, the lines of cover and limits their insurance exhibit requires, the endorsements named in it, the platform used for upload, the current expiry date, and the reviewer's name and email. Then check your open invoices against the vendor record status.

Any row you cannot complete is a payment that will stall the next time a compliance analyst runs a review. Send the gaps to your broker in one message, ask for certificates issued to each customer's correct entity, and put the expiry dates in a calendar. To see document exceptions tracked automatically against the invoices they hold up, book a demo.

Frequently Asked Questions

Can a customer legally withhold payment until they receive a certificate of insurance?

In most cases yes, where the contract makes evidence of insurance a condition of payment or a condition of performing the work at all. Insurance schedules are drafted that way so the buyer has a lever for collecting the document. Check the payment clause and the insurance exhibit before pushing back, because the answer is usually written down. Where the contract is silent, you have a stronger case for asking that the invoice be paid while the certificate is produced.

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

A straightforward certificate against existing policies is often issued the same day, since it is generated from the broker's system rather than underwritten afresh. Requests needing new endorsements take longer, because the carrier has to agree the amendment and issue the pages. Send the insurance exhibit and the exact certificate holder details in your first message to avoid a round trip. Where an endorsement may be refused, ask for that in writing quickly.

What is the difference between being named as certificate holder and additional insured?

The certificate holder is the party receiving the document, which by itself gives them no rights under your policy. An additional insured has cover under your policy for liability arising from your work, granted by an endorsement such as CG 20 10 or CG 20 37. Buyers who understand the difference ask for both and require the endorsement pages as proof. A ticked additional insured box with no endorsement attached is the most common rejection reason.

Why was our certificate rejected when the cover looks correct?

Most rejections concern identity and paperwork rather than the cover itself. Common causes are a certificate holder named as the parent rather than the contracting subsidiary, a missing waiver of subrogation on workers compensation, no endorsement pages behind the additional insured box, or a policy period that expires before the project completes. Compliance platforms name the failed item in the rejection notice, so read it before contacting your broker.

Should we send a certificate with every invoice?

No, and doing so creates confusion, because certificates belong on the vendor record rather than the invoice. Supply one accepted certificate per customer, keep it current, and refresh it before the policy expiry date. Where a buyer's platform requires an upload, keep the reference number for the accepted document so you can quote it if an invoice is queried. Reserve invoice level attachments for documents about that invoice.

Who at the customer reviews the certificate?

Rarely the accounts payable clerk who chased you for it. Review usually sits with a vendor compliance analyst, a risk manager or a contract manager, and on construction and field service work often with a site compliance coordinator employed by the general contractor. Ask who reviews it and send the document to that person directly as well as through the platform. Their name also gives you somebody to chase.

What should we do if our insurance cannot meet the customer's requirements?

Raise it immediately with your account owner and the buyer's contract manager rather than letting the invoice sit. Some requirements are boilerplate copied from a template and can be amended for the scope of work, particularly where a line of cover has no relevance to what you do. Others reflect a real risk position and mean buying additional cover, which is a cost to price into the contract.