Keep the records needed to explain how a transaction became a reported sales tax amount, and retain them for the period required by each applicable jurisdiction. A filed return shows your conclusion. The invoices, transaction details, exemption evidence, and reconciliation workpapers explain how you reached it.
Key takeaways
Document retention periods and exceptions for each jurisdiction.
Connect transactions, exemption evidence, and filing workpapers.
Test archive access and backup restoration before records are needed.
When to use this guide
This guide is for small businesses selling through a website, invoices, marketplaces, or a combination of channels. It proposes an ongoing recordkeeping process. For responding to an actual audit request, use the separate sales tax audit checklist.
Establish the applicable retention rules
There is no single retention period that should be assumed to cover every US sales tax account. Maintain a rule register by jurisdiction, legal entity, and record category. Include the minimum period, the event from which it runs, exceptions, official source, and the date your team checked it.
Texas states that sales and use tax records generally must be kept for at least four years unless earlier destruction is authorized in writing. Its FAQ also addresses circumstances requiring longer retention, including audits, refunds, and disputes. Use the complete guidance when deciding whether records can be destroyed. Texas Comptroller recordkeeping FAQ.
New York generally requires relevant sales tax records for at least three years from the later of the return due date or filing date, and separately addresses exemption certificates and electronic records. The starting event matters as much as the number of years. New York recordkeeping requirements.
These are state examples. Build the policy from all jurisdictions that apply to the business, and suspend routine deletion when an applicable audit, claim, dispute, or preservation requirement calls for it.
Preserve transaction detail at the source
For internal traceability, retain a stable order ID, invoice date, legal entity, sales channel, customer destination, product identifier, quantity, selling price, discount, shipping charge, taxable amount, and tax collected. Keep the currency and transaction status so a canceled order is not mistaken for a completed sale.
Retain the documents and exports behind those fields. A monthly dashboard screenshot can be useful context, but it is a poor substitute for an itemized export that another person can filter, total, and trace. Store original source files separately from working spreadsheets so corrections and transformations do not erase the initial evidence.
If a platform changes a product name or tax category later, historical reports should still explain the original sale. Preserve effective dates and configuration snapshots where needed to make that explanation possible.
Connect exempt sales to their support
Create an accessible relationship between an exempt transaction and the evidence used to treat it as exempt. Depending on the exemption, that may include a certificate, purchaser information, product facts, or other required documentation. Do not assume every exemption uses the same form or has the same renewal rules.
For certificates, a practical index includes the customer, applicable jurisdiction, document type, date received, reviewer, scope, and any relevant expiration or renewal date. The index helps find the evidence; it does not replace the underlying document. See the exemption and resale certificates guide for the eligibility and intake workflow.
Run a periodic sample from exempt transactions back to their support. Finding an unsupported sale during a monthly review is easier to resolve than discovering a missing archive years later.
Keep marketplace sales and settlements distinct
Preserve order-level marketplace reports, facilitator tax details when provided, refunds, fees, and settlement records. Net deposits usually answer a cash question, while order data answers a sales question. Your reconciliation should explain how one becomes the other.
Use consistent channel names and maintain a mapping when a marketplace changes its export columns. Record which entity and account produced each report. Businesses with several seller accounts can otherwise combine unrelated transactions or omit one channel from the filing package.
The marketplace facilitator guide covers responsibility and reporting considerations. Here the objective is to preserve enough source evidence to support whichever treatment applies.
Assemble one filing package per account and period
A useful filing package contains the submitted return, payment confirmation, sales reconciliation, relevant adjustment schedules, exemption summaries, and notices affecting that period. Add the source export names and a short explanation of material differences between platform totals and the filed figures.
For example, a package might identify a refund reported in a different period from the original sale, a marketplace amount shown on a different return line, or an approved correction. Another person should be able to follow the explanation without relying on the preparer's memory.
Use a consistent folder structure such as legal entity, jurisdiction, account, year, and filing period. Restrict access according to job responsibilities, especially where files contain customer information or sensitive account details. Store passwords in an appropriate credential system rather than inside filing workpapers.
Test whether the archive is usable
Saving a file is not the same as being able to use it. On a recurring schedule, choose one historical return and reconstruct a small sample of its transactions from the archive. Open the files, check that exports are complete, and confirm that linked documents remain available.
Test a restore from backup as well as ordinary folder access. If an archive depends on a former employee's account or a canceled commerce subscription, resolve that dependency while access is still available. Before a platform migration, export the records needed under the retention policy and document how old IDs map to the new system.
Record the test date, sample period, missing files, owner, and resolution. This is an internal quality check, not a claim that a particular file format satisfies every authority's electronic-record requirements.
Assign ownership and controlled deletion
Give finance responsibility for the retention register and filing package. Assign commerce or operations an owner for source exports, and name a backup for each recurring task. Review the policy when adding a jurisdiction, changing platforms, closing an account, or receiving a notice.
Deletion should require a documented check that the applicable retention period has elapsed and no longer preservation duty applies. Keep a record of what was deleted, the covered period, and who approved it. Closing a sales tax permit or terminating a software subscription should not automatically trigger destruction of historical records.
Frequently asked questions
Are filed sales tax returns enough?
No. They do not independently explain individual transactions, exemptions, adjustments, or how reported amounts were calculated. Retain the supporting records required by the relevant authority.
Should every state use the same retention period?
An internal policy may use a longer common period for administrative simplicity, but it must still account for each state's requirements, starting dates, and exceptions. Do not choose a common period without reviewing those rules.
What should I do first if records are scattered?
Start with the most recent completed filing period. Assemble its source reports, return, payment, and reconciliation in one indexed package. Identify missing evidence, assign owners, and use that process for subsequent periods while planning historical cleanup.
Official sources
Reviewed against the following primary sources on Sep 6, 2026.