Most teams do not have a certificate problem. They have a timing problem that turns into a certificate problem.
The request goes out after the relationship is established, to the person who places orders, asking for something they have never heard of. It then takes four emails and a phone call. Repeat that across a few hundred exempt customers and the work becomes permanent, and the person doing it starts to think of certificates as inherently difficult. They are not. They are being asked for at the worst possible moment, of the wrong person, in the vaguest possible terms.
This guide is about the three things that fix most of it, none of which are software.
Ask while they still want something from you
There is exactly one moment when a new customer is maximally responsive to a document request, and it is while their credit application is open. They want the line, they expect paperwork, and someone on their side has been assigned to get you what you need. Every day after approval, the responsiveness decays.
A certificate requested at the first exempt order is a request made into a vacuum. Nobody at the customer is waiting for it, it competes with that person's actual job, and the only leverage you have left is the order itself — which turns a routine document request into a commercial argument you did not want to have.
The change is not effort, it is sequence: the certificate joins the credit application document set, alongside the W-9 and the references, rather than being chased later as its own small project.
The person who buys is rarely the person who can sign
An exemption certificate is a signed assertion about the buyer's tax status. The purchasing contact who places orders usually cannot make that assertion, is not authorised to sign it, and — reasonably — will not guess. So the request stalls, not because the customer is unwilling but because it landed on a desk that cannot action it.
Ask, in the application, for the tax or finance contact by name. It costs one field and it removes the most common cause of delay. Larger customers frequently have someone whose job includes exactly this, and who will turn a well-formed request around quickly; the difficulty is almost never at their end once the request reaches them.
- Capture a tax or finance contact separately from the purchasing contact at application time
- Address the certificate request to that person, not to the buyer, and say why they specifically were asked
- Name the states involved in the request itself, so they can answer once rather than iteratively
- Say what happens if no certificate is provided — tax gets charged — because that is the detail that gets it prioritised
A blanket certificate is worth asking for explicitly
Where a state and the circumstances allow one, a blanket certificate covers continuing purchases rather than a single transaction. The difference in operational load is not marginal: single-purchase certificates make the problem recur with every order, which is how teams end up with a filing cabinet that grows faster than the customer base.
Customers frequently send a single-purchase certificate simply because that is what they were asked for, or because the form defaulted that way. Asking explicitly for a blanket certificate, where it is available, is often the whole intervention.
It reduces the volume of the problem rather than its shape. A blanket certificate still has a validity question attached to it, and that is the subject of the next guide in this series.
When the wrong form arrives
Some proportion of what comes back will be wrong: the wrong state, an expired form, a missing registration number, the wrong exemption basis, or an unsigned copy. This is normal and it is not a sign of a difficult customer.
What determines the cost is when you notice. Checked on arrival, while the onboarding conversation is still live, a re-request is a two-line email and nobody minds. Discovered at audit, it is a conversation with a customer who has no memory of the original exchange, possibly no longer buys from you, and no particular incentive to help.
So the useful discipline is not a more elaborate review. It is any review at all, performed at the point of receipt rather than at the point of need.
Chasing is a symptom
If someone on the team spends a recurring part of their week chasing certificates, the problem is upstream of them. Requests are going out late, or to the wrong person, or without enough information to be answered in one pass. Adding a reminder cadence to a badly-formed request produces a well-organised version of the same problem.
The diagnostic is simple: look at the last twenty certificates you obtained and count how many exchanges each took. If the median is above two, the request is the thing to fix.
Where to check the rules yourself
Nothing here is tax advice, and the rules described in general terms vary by state and change over time. Work from the authorities rather than from summaries, including this one.
For anything consequential — a new state, an unusual exemption basis, a customer whose situation does not fit the pattern — the answer comes from your tax advisor or the state directly.
- The revenue department of each state you sell into, which publishes its own forms, validity periods and acceptance rules
- The Streamlined Sales Tax Governing Board, for the SSUTA certificate, its member states and the exemption reason codes it defines
- The Multistate Tax Commission, for the Uniform Sales & Use Tax Exemption Certificate and the conditions individual states attach to accepting it
- Your own tax function or external advisor, for anything that determines whether a transaction is actually exempt
About the author
SGUTTI · Founder, EFILOS
SGUTTI is the founder of EFILOS and the architect of SCREDIT, the trade-credit operating platform. He writes about credit operations, financial statement analysis, and receivables management based on the workflows SCREDIT is built around.
Connect on LinkedIn