Backup withholding on exhibitor payments and the paperwork gap that triggers it

A sales agent who brought fourteen stands to your March show invoices for commission in April. Accounts payable pays it, and the agent calls because the payment is 2,880 short on a 12,000 invoice. Backup withholding on exhibitor payments has done exactly what it is supposed to do: the payee record carries no valid taxpayer identification number, so 24 per cent came off the top and went to the IRS.

The call takes forty minutes. The agent is annoyed, the account manager is embarrassed, and the missing piece is a one-page form that somebody could have collected in January when the agent signed the referral agreement.

Where the 24 per cent comes from

IRS Publication 1281, revised December 2023 and titled Backup Withholding for Missing and Incorrect Name/TIN(s), states the rate as 24 per cent, effective for all subject payments after 31 December 2017. The Instructions for the Requester of Form W-9 (IRS, March 2024) put the same figure in the payer's language: a payer must deduct, withhold and deposit with the IRS 24 per cent of reportable payments made to that payee until the cause of the backup withholding is remedied.

Two words in that sentence carry the operational weight. Reportable, because it limits which payments are in scope at all. And until, because withholding does not attach to a single transaction. It attaches to the payee and stays attached until the paperwork is fixed.

The publication also lists what can be subject to it, including rents, royalties, commissions and non-employee compensation, and it lists categories that are excluded. The trouble for an event business starts upstream of the rate, at the step where somebody decides which category a payment belongs to.

Which exhibitor payments are actually reportable?

Most organisers pay their exhibitors far more often than they think, and the payments fall into two groups that behave completely differently.

The first group is a return of the exhibitor's own money. A refund of a deposit on cancelled space, a credit note against an overcharge, a rebate of a service charge you billed in error. These are generally a return of funds and not income to the exhibitor, so no information return follows and no withholding question arises. An organiser who blocks every payment on a missing form will stop these too, which produces a queue of finance tickets for no compliance benefit at all.

The second group is money the exhibitor or a related party earned. Commissions to a sales agent. Speaker and moderator fees. Prize money for an awards programme. Co-operative marketing payments where the exhibitor invoices you for activity they ran. Payments to a contractor who built your feature area. These sit squarely inside the reportable category and every one of them needs a form on file before the first payment.

That split is the whole design problem. Your vendor master has one field for the exhibitor and no field for which kind of payment is about to run through it.

Where the gap opens in the vendor master

The sequence that produces the 40 minute phone call is depressingly consistent.

An exhibitor cancels a stand in October. Finance sets up a payee record to issue the refund, and because the refund is a return of their deposit nobody asks for a tax form. The record now exists, has bank details, and looks complete on screen. In April the same legal entity gets paid a commission through the same record, and the first reportable payment of the relationship inherits a record that was created for a non-reportable one.

Nobody made a mistake at any individual step. The defect is structural: the payee record carries no flag saying which category of payment it was opened for, so the second payment cannot tell that the first one skipped a check it did not need.

The fix is a field, and it costs a morning. Every payee record gets a reportable-payment flag with three states: never yet used for a reportable payment, cleared with a form on file, or blocked. The refund path sets the first state and passes. The commission path demands the second and blocks on the third. What you have then is a control that behaves differently by payment type instead of a blunt hold that finance will route around by the second week.

Refunds also need to land correctly in the numbers, which is a separate argument about how a revenue bridge treats returned money and a good reason to keep the two payment groups distinguishable in the ledger as well as in the control.

What does the notice cycle actually look like?

When the check is skipped, the correction arrives on the IRS timetable and the timetable runs on business days.

Publication 1281 sets out the sequence. A CP2100 or CP2100A notice lists the returns you filed with a missing, incorrect or not currently issued number. For an incorrect name and number combination that agrees with your own records, the first B notice, a Form W-9 and an optional reply envelope go to the payee within 15 business days of the notice date or the date you received it, whichever is later, and the notice itself must be dated no later than 30 business days after that same reference date.

If the payee does not return a signed form, backup withholding begins no later than 30 business days after that reference date, though you may begin the day after you receive the notice. Once the signed form arrives, you stop no later than 30 calendar days later, and you may stop at any point inside that window.

For a missing number the rules are blunter. Withholding begins on any reportable payment and continues until you receive a number. Publication 1281 is explicit that the 60 day exemption available on presentation of an awaiting-TIN certificate covers interest, dividends and certain readily tradable instruments only, and that non-employee compensation is subject to withholding immediately even if the payee has applied for a number and is waiting.

That last point catches organisers out constantly, because the intuition is that a payee who has applied is fine for now.

Doing the arithmetic on one blocked payment

Take the 12,000 commission from the opening.

With no valid form on file, 24 per cent of 12,000 is 2,880, and the agent receives 9,120. You deposit the 2,880 and report it on Form 945, the annual return of withheld federal income tax that Publication 1281 and the requester instructions both point payers towards for non-payroll withholding.

Now count what it costs to unwind. The agent chases, an account manager investigates, finance confirms the withholding was correct, someone explains that the money has gone to the IRS and cannot be released by you, and the agent has to recover it through their own return. Call that four people and three hours in your business, plus a commercial relationship that is now slightly worse, for a form that takes an exhibitor four minutes to complete.

Scale it to a portfolio. If eight shows each pay commission to an average of six agents, and one in five of those payee records has no valid form, that is 48 agents, roughly 10 defective records, and if the average commission is 8,000 then 19,200 of somebody else's money is sitting with the IRS by the end of the year. None of that money is yours, none of it is lost, and every bit of it generates a conversation.

Blocking at source without blocking everything

The rule worth adopting is narrow. Block a payment when the payment is reportable and the payee has no valid form, and let everything else through.

Implementing that needs three things you probably already have in some form. A payment type on every request, chosen from a short list rather than typed. A document state on every payee record, set by whoever accepts the form rather than by whoever files it. And a block that fires at request time in the exhibitor portal or the purchase requisition, several days before the payment run, so the exhibitor is asked while the request is still a draft.

The timing is what makes it tolerable. A block at payment run time turns into an escalation, because a payment run has a date and people are waiting on it. The same block a week earlier is an email.

I would go further and put the form request in the contract pack for anybody who could conceivably be paid, including exhibitors who have never been paid anything, on the grounds that collecting a form you never use costs four minutes and not having one costs the sequence above. The counter-argument, that you should not collect tax identifiers you do not need, is a real one and worth weighing against your own data retention position.

Where this stops

Everything above is United States federal practice, and it applies to payments a US payer makes. A UK or German organiser paying a UK agent is in a different system entirely, with different forms, different rates and different deadlines, and copying this workflow across a portfolio that spans both will produce a control that is wrong in one of them.

The rules also assume the payee is a US person. A foreign exhibitor or a foreign agent cannot provide a Form W-9 at all, which means the blocking rule above needs a second branch, and that branch has its own document set and its own default rate.

There is a limit inside the US case too. Deciding whether a payment is reportable is a tax judgement, and this workflow pushes that judgement onto whoever picks the payment type from a dropdown. Get the dropdown wrong and you have automated a misclassification at scale. The list should be short, written with your tax adviser, and reviewed once a year rather than extended casually by whoever needs a new option.

None of this makes an exhibitor happier about a short payment. It moves the conversation from April to January, when there is time for it.

Start by exporting every payee your finance system has paid across the last two show cycles, tagging each payment as a return of the payee's own money or as earned income, and counting how many payee records in the second group have no tax form on file. Cross the resulting list against the accounts that cancelled and were refunded, because that overlap is where the records opened for a refund and later used for something else are hiding. It is one query, one afternoon, and the answer sets the size of the block you are about to build in the onboarding workflow.