Customer Wants a W-9 Before Paying Your Invoice

Send the W-9, same day, through the channel the customer named, and ask for a scheduled payment date in the same message. A customer asking for a Form W-9 before paying an invoice is running a standard vendor compliance step: their accounts payable system will not release a payment to a vendor record with no certified taxpayer identification number attached. Monk runs invoice to cash as one system, covering invoice delivery, AP portal submission, cash application and collections, which means a document request arrives as a blocker on a specific invoice with an owner and a deadline rather than as an email somebody will get to. The invoices that stall are the ones where nobody noticed a form was holding the cash.

The pattern is consistent. A collections thread that had been polite and unproductive suddenly produces a reply asking for a tax form, sometimes on an invoice that is already sixty days out. That reply is good news, because it tells you the invoice was on hold for a reason you can clear this afternoon. It is also a warning, because a vendor-level hold usually stops every open invoice from your company at once.

Why does accounts payable need a W-9 before it will pay you?

Because the reporting obligation sits with the payer rather than with you, and they cannot meet it without your certified legal name and taxpayer identification number.

Form W-9 is the IRS Request for Taxpayer Identification Number and Certification. Your customer collects it so they can issue the correct year-end information return, and so they can certify that backup withholding does not apply to payments they make you. The tax classification box is what tells them which of those obligations they have, since payments to some entity types are reportable and others are not. This is process description rather than tax advice, and the classification question belongs with your accountant once, in writing, so your AR team stops relitigating it.

Operationally the form lives in the vendor master record rather than with the invoice. That distinction explains most of the confusion. The invoice can be fully approved, matched to a purchase order and sitting in an approved queue, while the vendor record carries a compliance flag that stops the payment run from picking it up. Nobody in AP experiences this as a dispute, so nobody tells you.

Timing varies more than suppliers expect. Some buyers collect the form during onboarding before your first invoice. Others ask two years in, after an ERP migration, an internal audit of incomplete vendor records, or a change in who administers the vendor master. A request arriving against an aged invoice is a strong signal that the invoice has been parked the whole time.

Which fields get a W-9 rejected?

Almost every rejection comes from one of six fields, and five of them are avoidable by checking the form against your own tax records before you send it.

The name mismatch is by far the commonest. Many buyers run your line 1 name and TIN through the IRS matching service, and a trading name will come back as a mismatch even though every character you typed is a real fact about your business. Where the invoice carries the trading name and the W-9 carries the registered name, add the registered name to the invoice header so the two documents reconcile without a phone call.

What happens if you never send one?

Two things, and the second one costs real money: the invoice stays on vendor hold indefinitely, and any payment the buyer does make becomes subject to backup withholding at 24% of the gross amount.

Backup withholding is not a penalty the buyer chooses. Where they hold no certified TIN, they are required to withhold and remit that share to the IRS, and to report it. On an illustrative $50,000 invoice, that is $12,000 that leaves the buyer, never reaches your bank, and appears on your ledger as a short payment nobody warned you about. You can recover it as a credit against your own tax liability, so the long-run loss is smaller than the cash-flow shock, and the shock arrives in one payment run.

The more common outcome is simpler and quieter. Most enterprise AP systems will not process a payment at all against an uncertified vendor record, so the invoice ages without a dispute, without a rejection notice and without a status change you can see. On an ageing report it reads as an ordinary late payer. That is the same shape as three of its neighbours: an invoice the buyer never received, a contact whose mailbox is dead, and a purchase order that disagrees with your line items. See customer says the invoice was never received, what to do when an AP contact's email bounces and how to resolve a PO mismatch on an invoice.

What do non-US suppliers send instead?

A form from the W-8 series, and which one depends on your entity type and where the work was performed.

Form W-8BEN covers a non-US individual. Form W-8BEN-E covers a non-US entity and is the one most overseas suppliers need. W-8ECI applies where the income is effectively connected with a US trade or business, and W-8IMY applies to intermediaries and certain flow-through entities. Sending a W-9 when your entity is not a US person is a rejection, and sending the wrong W-8 typically adds several weeks because it goes back through a compliance queue rather than straight to your contact.

Two practical differences matter for AR planning. First, treaty benefits are claimed on the form itself, and an incomplete claim means the buyer applies the default statutory withholding rate to US-source payments. Second, W-8 forms expire, generally at the end of the third calendar year after the year they were signed, or earlier if your circumstances change. That expiry is a silent one. Your invoices stop paying and nobody sends a notice, so put the expiry date on the customer record the day you send the form.

How do you know the request is genuine, and how do you send it safely?

Verify the requester through a channel you already trust before you send anything, because a completed W-9 hands over your legal name, address, EIN and an authorised signature in one page.

That combination is enough to impersonate your business to your own customers, most often to send a convincing bank-detail change request to their AP team. The form is a phishing target for that reason, and requests spike around quarter end and after publicised funding announcements. Three checks catch nearly all of it. Confirm the request correlates to a real open invoice or a live onboarding. Read the sender domain character by character rather than glancing at the display name. Then reply to an address or portal you already hold in your own records instead of hitting reply on the message that arrived.

Where anything looks unusual, call the AP number printed on the customer's own website or on your signed contract, never a number inside the email. Prefer the buyer's supplier portal upload over an email attachment, since 92% of enterprise invoices must be submitted through a vendor portal or network anyway, and the same portal usually holds the tax document slot. Portals reject uploads for ordinary reasons such as file type and file size, which is covered in why AP portals reject your invoices.

One rule is worth making absolute. Never send tax documentation and bank details in the same thread. Bank changes should travel on a separate, verified channel with a callback, and telling your customer that in writing protects both of you.

How do you keep a current W-9 on file for every customer?

Hold one signed, dated master copy in a place your AR team can reach without an approval chain, and keep a register of which customers have it, when, and through which channel.

The master copy is the easy half. One authorised signatory signs it, it is stored where a collections analyst can retrieve it at four in the afternoon, and it is re-signed on a fixed annual date so nothing ever looks stale. Refresh it immediately on a legal name change, an address change, an entity conversion, a new EIN, or an acquisition, because a superseded form circulating at fifty customers produces fifty mismatches later.

The register is the half most teams skip. Record the customer, the date sent, the recipient, the channel, the invoice it unblocked, and whatever refresh cycle that buyer runs. When the same customer asks again after their next system migration, or a second business unit asks next quarter, the answer takes a minute. The register also tells you which customers are due for re-verification before they stop paying rather than after.

Underneath both sits a single discipline. A document request is a receivable event. It has an invoice number attached, a dollar value, an owner and a deadline, and it belongs on the invoice record alongside disputes and short payments rather than in an inbox. Treated that way, the response is measurable and the recurrence is preventable. Treated as admin, it is invisible until the ageing report gets uncomfortable. If you are building that layer generally, start with what accounts receivable automation covers.

How does Monk handle this?

Monk treats a request for a document as a blocker on a named invoice, with an owner and a due date, rather than as correspondence.

Monk's Intelligent Collections ingests the context of each customer conversation, so a reply asking for a tax form is handled as an obstacle to clear rather than as non-payment to chase harder. Julia, Monk's AI agent for Intelligent Collections, achieves a 24% higher response rate than standard dunning, and 90% of collections resolve with zero human intervention, which leaves your team on the requests that need a signature or a judgement call.

Around 39% of cash flow slowdown is caused by edge cases of this kind. Across $2B+ in receivables under management, customers see a 40% average reduction in DSO and save 26 hours a month on receivables work. AI cash application matches 80% of receipts automatically and 95% with suggested matching rules, so a payment that arrives short because of withholding is visible as an exception rather than a mystery. Monk is SOC 2 Type II compliant, integrates with QuickBooks, NetSuite, Salesforce, HubSpot and Stripe, and onboarding takes less than one week. Monk files invoices into 600-plus AP portals, roughly 87% of them autonomously, with Coupa and Ariba the two our customers use most.

Where should you start?

Spend twenty minutes this week finding out whether a document is holding cash you have already earned.

Take your top twenty customers by open balance and answer three questions for each. Does that customer hold a current, signed W-9 from you, and on what date did they receive it. Is the legal name on that form identical to the remit-to name on your invoices. Does the buyer run a re-verification cycle, and when does it next fall. Anything you cannot answer is an unmanaged risk on an account that is already material to you.

Then check whether any open invoice on those accounts is sitting on a vendor hold rather than in an approval queue, because the two look identical from outside and only one of them is your problem to fix. To see document requests, portal submissions and collections follow-up managed on the same invoice record, book a demo.

Frequently Asked Questions

Can I refuse to send a W-9 to a customer?

You can decline, and most accounts payable systems will then leave the invoice on hold indefinitely, since they cannot certify your taxpayer identification number. Any payment they do release may be subject to backup withholding at 24%. Whether your company should provide one, and on what terms, is a decision for your finance or legal owner rather than for an AR analyst.

Is it safe to email a W-9?

A completed W-9 carries your legal name, address, EIN and a signature, which is enough to impersonate your business to your own customers. Verify the requester through a channel you already hold before sending, and prefer the buyer's supplier portal or a secure link over an email attachment. Never send tax documentation and bank details in the same thread.

Why did the customer reject the W-9 I sent?

Usually because line 1 carries a trading name rather than the registered legal name, so the name and TIN combination does not agree with IRS records. The other frequent causes are a wrong tax classification box, an unsigned certification, transposed digits in the EIN, and a stale address. Check the form against your IRS confirmation letter before resending.

How often will a customer ask for a new W-9?

Many buyers re-verify vendor records every year or two, and almost all of them re-request after an ERP migration or a compliance audit. Send an updated form yourself whenever your legal name, address, entity type or taxpayer identification number changes. Keeping the refresh date on the customer record means you find out before the invoices stop paying.

What if my company is not a US entity?

You will be asked for a form from the W-8 series instead, most often W-8BEN-E for a non-US entity or W-8BEN for a non-US individual. Treaty benefits are claimed on the form, and an incomplete claim means default withholding applies. W-8 forms expire, generally at the end of the third calendar year after signature, so diary the expiry when you send it.

Will the invoice pay as soon as I send the form?

No. The invoice rejoins the buyer's normal approval and payment cycle rather than jumping to the front of it, so a net 30 invoice held for three weeks does not pay the same afternoon. Ask for a scheduled payment date in the message that carries the form, and ask whether other invoices from your company sat behind the same vendor hold.

Who should sign the W-9?

Someone authorised to bind the entity, which in most companies means a finance leader. Decide once, keep a signed and dated copy where your AR team can reach it without chasing an approval chain, and re-sign it on a fixed annual date. A form signed by a person without authority is treated as uncertified and quietly ignored.