Procurement-Friendly Invoicing: W9s, COIs, and NET-30 Terms

If someone just asked a photographer or video vendor for a W9 and a COI and got a blank look back, this is the fast version: a W9 is a tax form, a COI is proof of insurance, and a corporate finance system usually will not release payment without both on file. Below is what each document actually is, what else procurement tends to ask for, and the order to send it in so a small vendor does not lose a week to paperwork that has nothing to do with the photography.

W9 and COI are two of the documents a corporate finance or procurement team asks a small vendor for before it will pay an invoice. A W9 is a U.S. tax form that reports who the vendor is for tax purposes. A COI, a certificate of insurance, is proof the vendor carries liability coverage, usually naming the client as additional insured. Most corporate bookings also want a short vendor agreement, entry into a vendor onboarding portal, and a purchase order issued before the invoice goes out.

What Do W9 and COI Mean?

A W9 is IRS Form W-9, Request for Taxpayer Identification Number and Certification. It tells a client's accounts payable department who the vendor is for tax-reporting purposes, nothing more. A COI, certificate of insurance, is a one-page document from an insurance broker or carrier that proves a vendor's policy is active and shows the coverage amounts. It does not add coverage on its own; it is proof that coverage already exists.

Both documents get asked for together so often that the two abbreviations start to blur, but they answer two different questions. The W9 is about tax reporting. The COI is about liability, and it is usually issued naming the client, and sometimes the venue, as an additional insured on the vendor's existing policy.

Neither document says anything about the quality of the work. A marketing or events manager who hears "we need your W9 and COI" from their own finance team is hearing a routine compliance step, not a red flag on the vendor.

The Vendor Document Checklist: What Gets Requested

Most corporate procurement processes ask for some or all of the same five items. Knowing the list before the first email lands means a vendor can start gathering documents the same day, not the day before the shoot.

• A completed W9, the vendor's legal name, business type, and taxpayer ID, for the client's tax reporting.
• A certificate of insurance, proof of liability coverage, naming the client as additional insured.
• A separate COI for the venue, if the shoot happens somewhere the client does not own or control.
• A short vendor agreement or MSA, the document that actually spells out scope, payment terms, and liability language.
• Registration in a vendor onboarding portal, if the company routes new vendors through one instead of email.

A boutique studio can usually turn around the W9 the same day and the agreement within a few days. The COI depends on the insurance carrier's own turnaround, so it is worth asking for early rather than after the date is already set.

Certificate of Insurance: What Should Be Named on It?

A COI is only useful to the client or venue if it names the right party as additional insured, at a coverage limit they actually asked for. The vendor's own insurance broker issues the certificate; the client or venue's risk team sets the requirement.

The client and the venue are frequently two separate entities with two separate risk exposures, so a COI written for the client does not automatically satisfy a venue that has its own requirement. It is common for corporate and venue liability requests to sit in the $1 million per-occurrence range with a $2 million aggregate, though the exact figure varies by company and by venue and should always be confirmed rather than assumed.

The practical move is asking two questions up front: who needs to be named as additional insured, and what limit are they asking for. A broker can usually issue a certificate with the right names and numbers within a day or two once those two answers are in hand.

NET-30 Terms and a Deposit: How the Payment Structure Works

NET-30 and a deposit solve two different problems, and a small vendor can reasonably ask for both. NET-30 is the client's own payment cycle, set by their accounts payable system. A deposit protects the vendor's side, since holding a date means turning down other work whether or not that client ultimately pays on time.

A corporate client's standard terms are usually built around net payment after invoicing, and a single approver rarely has the authority to prepay a vendor in full outside that system. A common structure on the vendor side is roughly half the total collected as a deposit before the date, with the remaining balance invoiced against the purchase order once it exists, so the studio is not carrying the entire booking unpaid for a full billing cycle.

Raising this early, before the date is locked in, works better than assuming either side's default terms are the only option. Most procurement teams have handled a deposit-plus-NET-30 structure with a small vendor before.

Vendor Portals and Purchase Orders: Getting the Sequence Right

A vendor onboarding portal is the online system a company uses to collect W9s, COIs, and banking details before approving a vendor as a payee. The sequence that protects a small vendor is: documents submitted, PO issued, then the shoot date confirmed and the invoice sent against that PO number.

The portal itself is rarely the hard part. What adds time is the queue behind it: a profile that has to move through one or more internal approvers before it counts as active, on a timeline the vendor does not control and cannot speed up by hurrying.

Most corporate finance systems match an invoice against an already-approved PO. Sending an invoice for work that started before a PO existed can push that invoice into a manual exception instead of the normal payment run, which is one of the most common ways a paid, finished job still sits unpaid for weeks. Starting the portal and the PO request the same week the booking is discussed, rather than the week before the shoot, is the fix.

What to Put in the First Email to a Photo or Video Vendor

The first email should say plainly which documents the company requires, whether a portal is involved, and roughly how long internal approval tends to take. That one paragraph prevents more delay than anything sent later.

• Which documents are required: W9, COI (and for whom), vendor agreement, portal registration.
• Whether a vendor onboarding portal exists, and its name if so.
• A realistic estimate of internal approval time, even a rough one.
• Whether a PO will exist before the invoice is due, and who issues it.

A marketing or events manager who has been through their own company's process before already knows these answers. Passing them along on day one, before the date is even confirmed, gives a small studio the chance to start the W9 and COI request immediately instead of scrambling once the calendar is already tight.