Offshore BookkeepersPowered by StealthAgentsPlan my role
Offshore Bookkeepers guide

A vendor W-9 collection log that keeps payments moving

A practical log for collecting vendor W-9s, so a missing form does not stall a payment or a year-end filing.

A practical log for collecting vendor W-9s, so a missing form does not stall a payment or a year-end filing.
Table of contents

The short answer

  • Record the vendor, the request date, the follow-up, and the form status.
  • Separate a new vendor from an existing vendor who needs an updated form.
  • Do not release a payment that the form blocks without the owner's approval.
  • Review the open forms monthly and escalate before year-end.

A new vendor sends an invoice and the payment is ready to run. The W-9 is missing, the request is buried in an email, and the payment waits. The delay is not the form; it is the lack of a record that shows who asked, when, and what happened next.

A W-9 collection log keeps the request and the form visible. It is a short list, and it prevents a routine form from becoming a payment or filing problem at the worst time.

Start the log when the vendor is set up

Create the entry when the vendor record is created, not when the first invoice arrives. Record the vendor, the contact, the date of the first request, and the channel. An entry that starts late has already lost the first request. State whether the vendor is new or existing. An existing vendor may need an updated form after a name or entity change. The reason for the request should be visible in the entry.

Use a small set of statuses

Use statuses such as requested, reminded, received, reviewed, and blocked. A status should say what happens next, not only what happened. A general "pending" hides whether the next move belongs to the vendor or the team. Record the date the status changed and the owner. A status that is not dated cannot show how long the form has been open. The age is the useful signal.

Separate the form from the vendor record

Store the form in the vendor file and link to it from the log. Do not copy the tax identifier into a broad tracker. The log is an index, not a second copy of sensitive data. Record the review date and the reviewer. A received form still needs a check for the name, the entity type, and the signature. A form that was received but not reviewed is not complete.

Follow up on a schedule

Set a follow-up cadence that matches the business's policy, such as every five business days. Record each attempt and the channel. A single reminder followed by silence is how the form gets lost. If the vendor does not respond, escalate to the relationship owner. Record the escalation and the new date. The owner may have a contact route that the bookkeeper does not.

Handle a payment that is blocked

If the payment cannot run without the form, record the block and the owner. Tell the vendor what is needed and when the payment can resume. Do not let the payment sit in the queue without an explanation. If the owner approves an exception, record the decision and the reason. The exception should have an expiry and a follow-up. An exception without a follow-up becomes the new normal.

Review the log before year-end

At least a month before the filing deadline, review the open forms and the vendors with missing data. Prioritize the vendors with payments above the reporting threshold. Record the plan for each open item. Do not wait for the filing week to chase the forms. A form requested in December may not arrive in time. The review should start early enough to act.

Protect the tax information

The form contains a tax identifier and other sensitive data. Keep it in the vendor file and limit access to the people who need it. Do not send a copy in a broad email or a group chat. Set a retention period with the business's records policy. Keep the form long enough to support the filing requirement and no more. Remove duplicate copies when they are no longer needed.

Review the log monthly

At the end of each month, review the open forms and the time to receive. Look for vendors who were asked once and never followed up. The pattern is more useful than a single missing form. Change one step based on the review. A clearer request message or a firmer follow-up date is often enough. Record the change and the date.

Keep the request easy to complete

Send the form link and a one-line explanation of why it is needed. A request that requires a portal login or a printer is slower to complete. Record the link and the channel in the log so the next follow-up is consistent. A consistent message is easier for the vendor to act on.

Review the blocked vendors with the owner

Bring the blocked payments and the open forms to the owner review. Ask which vendors need an exception and which can wait. The conversation should produce a decision and a date. Record both.

Key takeaways

  • Start the entry when the vendor is set up, not when the invoice arrives.
  • Use dated statuses that name the next owner.
  • Follow up on a schedule and record each attempt.
  • Review the open forms before year-end and protect the tax data.

A W-9 log is a small vendor control. It keeps payments moving and makes the year-end filing less of a scramble. A short note with the form link saves a round of email. It also makes the follow-up easier to write. For related workflows, see the duplicate payment review and the accounts payable support overview.

Questions owners ask

Can a vendor be paid before the W-9 arrives?

Follow the business's policy. The log should record the decision and the owner who approved it rather than leaving the payment unexplained.

Who should request the form?

The person who owns the vendor relationship or the accounts payable team. The bookkeeper can track the request and the follow-up.

How often should the log be reviewed?

At least monthly, and more often before year-end filing. A short review keeps the open forms visible.

Keep planning

Sources

  1. IRS, Form W-9
  2. U.S. Small Business Administration, Manage your business