A sales tax audit is easier when the business can reproduce each return from transaction-level evidence. Preparation should focus on data completeness, reconciliations, documented interpretations, controlled communication, and a clear record of every item provided.
Key takeaways
Read the notice and preserve the requested periods before changing systems.
Reconcile returns to orders, accounting, exemptions, and payments.
Provide complete, scoped, reproducible data through one response owner.
Track potential exposure and corrective actions separately from the audit dialogue.
Read the notice and establish control
Identify the legal entity, tax type, periods, response date, auditor, requested records, and whether the review is desk-based, field-based, or computer-assisted. Route the notice to tax, finance, legal, and the authorized representative.
Create a request log and communication protocol. One coordinator should approve submissions so incomplete, inconsistent, duplicate, or privileged material is not sent informally by different teams.
- Confirm entity, periods, and deadline.
- Preserve the original notice and envelope.
- Name a response owner and backup.
- Document every call, request, and submission.
Preserve systems and source data
Freeze relevant order, invoice, payment, marketplace, exemption, inventory, tax-engine, and general-ledger data. If systems changed during the audit period, preserve exports, field definitions, configuration versions, and migration mappings.
New York guidance expects transaction-level detail sufficient to determine taxability and tax collected; summary reports alone may be inadequate. Ensure archived electronic records remain readable and reproducible.
- Export transaction-level records.
- Preserve legacy-system data.
- Document fields and transformation logic.
- Secure files with controlled access.
Reconcile filed returns before submission
Tie gross sales to books and order systems, then reconcile deductions, exempt sales, marketplace sales, taxable sales, tax collected, payments, credits, and amendments. Explain differences by period and jurisdiction.
Do not force totals to match with an undocumented plug. Timing, refunds, chargebacks, marketplace settlements, and currency can create valid differences, but each one needs evidence.
- Build a return-to-ledger bridge.
- Trace deductions to transaction populations.
- Tie payments to confirmations and bank activity.
- Explain every material variance.
Review exemptions and marketplace evidence
Sample exempt transactions and verify the certificate, customer, state, product, date, signature, registration number, and scope. Identify missing or invalid documents early and follow the jurisdiction’s rules for late support.
For facilitated sales, retain agreements, platform tax reports, and evidence that the facilitator was responsible. Net settlement statements alone do not prove gross sales or tax handling.
- Index certificates to transactions.
- Separate resale and entity exemptions.
- Preserve facilitator responsibility documents.
- Track missing evidence without altering history.
Prepare for sampling and interviews
Auditors may use sampling when transaction volumes are large. Understand the population, period, strata, exclusions, projection method, and treatment of credits before agreeing to a sample.
Prepare staff to answer factually and within their role. Product demonstrations and system walkthroughs should use consistent documentation and avoid unsupported guesses about legal conclusions.
- Validate the audit population.
- Review sample methodology with an adviser.
- Prepare system and product walkthroughs.
- Correct factual misunderstandings promptly.
Manage findings and remediation
Track proposed findings by state, period, issue, amount, authority, evidence, owner, and response date. Separate agreed factual corrections from disputed legal interpretations and calculation errors.
Whether or not an assessment results, fix root causes such as missing product mappings, weak certificate controls, unregistered states, or unreconciled marketplace tax. Preserve appeal and payment deadlines while remediation proceeds.
- Maintain an issue and exposure log.
- Respond with evidence and authority.
- Track appeal, refund, and payment dates.
- Implement preventive controls after closure.
Frequently asked questions
What records are commonly requested in a sales tax audit?
Returns, sales and purchase data, invoices, general-ledger records, exemption certificates, marketplace reports, tax configurations, payment evidence, and documentation supporting deductions are common.
Are summary reports enough?
Often not. Authorities can require transaction-level, electronically readable records that allow taxability and tax collected to be independently tested.
Should a business change historical data before giving it to an auditor?
No. Preserve original records and document corrections separately. Altering history can destroy the audit trail.
Can a representative help during an audit?
Yes. Jurisdiction procedures typically allow authorized representation; use the required power-of-attorney process and clarify who communicates with the auditor.
Official sources
Reviewed against the following primary sources on Aug 8, 2026.