This report asks how a bookkeeping team can test whether the sales-tax exemption certificates on file actually cover the customers and transactions treated as exempt. The unit is one customer certificate matched to one transaction population. The output is a coverage schedule, an exception list, and a conclusion about which sales need follow-up. The review supports the tax preparer and does not replace state-specific tax advice.
The scope is the sales ledger, the customer master, the certificate file, and the invoice tax codes for one entity and one review period. The protocol assumes the team can obtain the certificates and the transaction detail. It does not assume that every certificate is valid, current, or applicable to every sale. A certificate is evidence to test, not a permanent exemption for every transaction.
A sales ledger can show that tax was not charged, but it cannot show why. The reason may be a valid exemption, a non-taxable product, or a coding mistake. The certificate file is supposed to explain the first case, yet many teams store certificates without linking them to the transactions they support. That gap makes the filing position harder to defend and harder to correct.
The review is deliberately bounded. It does not audit every invoice or interpret every state rule. It tests whether the certificate evidence is complete enough to support the exempt population selected for review. It also measures how much of that population has no usable document. The result is a practical list of what to fix before the next filing cycle.
