Skip ahead to the main page
Partner Huddle
Pages

Sales tax records: 3 qualities your files need

Partner Huddle Editorial Team · Published · 11 min read

Retained sales tax records should support the return, preserve a traceable history, and remain protected and retrievable when a state requests them.

Key takeaways

  • Complete enough to support the return. The records must let someone recalculate the tax and tie each reported amount to support.
  • Traceable and unaltered. Each record needs a trail showing where it came from and whether it has changed.
  • Controlled and retrievable. The firm must be able to protect the records and produce them when asked.

Why the file has to do more than the return

Retained sales tax records are the sales journals, invoices, purchase documents, and system reports a business keeps to show how each figure on its return was built.

The filed return is the visible result of a lot of work, but it is rarely the first thing a state reviews. When a state asks to look at a client's sales tax position, it usually wants the records behind the numbers. For a small firm supporting many clients, that request often arrives with little warning. Someone has to find the files, confirm they are the right ones, and produce them in a form a reviewer can use.

Rules are written state by state. This post draws its examples from California, whose sales and use tax regulation shows clearly what a state can expect. Treat it as a model for thinking, not a rule for every client. If your clients are registered elsewhere, check each state's requirements directly.

Quality one: complete enough to support the return

The duty starts with the regulation's own wording. A taxpayer "shall maintain and make available for examination on request by the Board or its authorized representative, all records necessary to determine the correct tax liability under the Sales and Use Tax Law and all records necessary for the proper completion of the sales and use tax return."

That sentence contains two tests, and both are practical.

The first test is whether the calculation can be rebuilt. Ask whether a reviewer holding only the client's files could recalculate the tax for the period. If a sales report is missing, a supporting invoice sits in someone's inbox, or adjustments exist only in an unsaved working spreadsheet, the file fails.

The second test is the link to the return. Each reported amount should have support somewhere in the file. Pick a filed return, choose several figures, and trace each to a source document. Where the trail stops, you have found a gap while there is still time to close it. Repeat this across clients, not only the simplest one, because messy files are where gaps hide.

The duty also reaches further than many firms assume. The regulation defines a taxpayer to include "every lessor and lessee of tangible personal property for use in this state," along with sellers and people storing or using purchased goods. A firm reviewing a client's purchases, leases, or equipment use should not assume the obligations stop at the sales records.

Completeness is not about volume. A file that holds every email ever sent about a client is not thereby complete. It is one where the records needed for the calculation and the return are present, labeled, and easy to find. A reviewer who must search unrelated material to find a sales journal has not been handed a complete file in any useful sense.

Quality two: traceable and unaltered

Traceability concerns the trail behind each record. The regulation treats electronic records as records in their own right: "electronic records are considered records under Revenue and Taxation Code sections 7053 and 7054." A point-of-sale export, a cloud accounting record, or a database report carries the same expectations as a box of paper invoices. Living in a system does not exempt a record.

Paper still counts. Hardcopy is defined as "any document, record, report or other data maintained in a paper format." The firm must manage both kinds. What matters is not the format but whether the firm can show what a record is, where it came from, and whether it has changed since.

Sales and purchase data often moves between systems without anyone retyping it. The regulation's definition of electronic data interchange describes "the computer to computer exchange of business transactions in a standardized structured electronic format." When orders arrive in one system and flow into the accounting package, the firm must know which system holds the record of origin. If that is unclear, the file cannot prove where a figure started.

The regulation also allows some flexibility in what must be kept: "The taxpayer may capture the information necessary to satisfy subdivision (c)(2)(A) at any level within the accounting system and need not retain the original EDI transaction records provided the audit trail, authenticity, and integrity of the retained records can be established."

  • audit trail: how data moved and changed, from entry into the system to its appearance in the books.
  • authenticity: evidence that the record is what it claims to be, from the source it claims.
  • integrity: evidence that the record has not been altered since it was captured.

The condition has teeth. A firm that discards original transaction files because the books look right has not met it, since the books alone do not show the trail. A firm that documents its import process, keeps the mapping between systems, and can show when and how a record entered the books stands on much firmer ground.

Audit logs deserve the same attention, and they are easy to lose. Confirm retention settings rather than assuming defaults meet the client's needs. A firm should confirm the retention policy covers every period a state might ask about, and that the logs are kept alongside the sales data they describe. Use the related guide to audit log retention settings when reviewing those settings.

Start with an inventory. List each system touching a client's sales and purchase data and name the one that is the record of origin. Keep import logs and mapping rules. When a figure is adjusted by hand, record who changed it, when, and why. Most of these steps make deliberate use of what existing systems already do, not new software.

Traceability has a human side too. Know who enters, corrects, and approves transactions. If a reviewer asks who posted a particular adjustment, the answer should come from the file, not from memory.

The trail must also survive period close. When a period is archived, its import logs and change history should travel with the sales data. An archive that holds the numbers but not their history has lost part of its evidence, even though the figures look intact.

Quality three: controlled, convertible, and reachable

The third quality covers how records are kept and produced. It has three parts: control over changes, conversion to a usable format, and a workable way for the state to reach the records.

Start with control. The regulation refers to "the internal controls used to prevent unauthorized addition, alteration, or deletion of retained records." For a small firm this need not mean a large compliance program. Limit edit rights in client systems to the people who need them, lock or review closed periods before changes, and check change logs regularly for unexplained edits or deletions.

Separate duties where you can. The person who enters sales should not be the only person able to change them after filing, and a second person should review significant adjustments. These are ordinary controls. Their value lies in making unauthorized changes harder to make and easier to spot.

Next comes conversion. The regulation requires that "the taxpayer's computer hardware or software shall accommodate the extraction and conversion of retained electronic records to a standard magnetic record format as provided in subdivision (c)(1)(B)." A record that is kept but cannot be exported in usable form may not serve the purpose of keeping it.

Test this before you need it. Run an export of a sample period from each client system, open the result on a different machine, and confirm the totals match the books. If the export is missing fields, uses unfamiliar codes, or works only on one person's computer, learn that in a calm week, not during a records request.

Access is the last piece. The regulation recognizes that the way a reviewer reaches electronic records can vary. It says access "may be satisfied through a variety of means that shall take into account a taxpayer's facts and circumstances through consultation with the taxpayer." More than one method may meet the requirement, and the right one depends on how the client's systems are set up. Because consultation is part of the picture, the firm has a role in shaping the approach rather than waiting to be told.

Know how each client's systems could be reviewed, what would be hard to provide, and why. Be ready to explain the arrangement plainly. A firm that can describe its access plan before a request arrives starts from preparation rather than improvisation.

Access planning also affects staffing. If one person alone knows how a client's system is set up or how to run its export, that person is a single point of failure during a request. Cross-train at least one other person on each export process and write the steps in plain language. A procedure a second person can follow is far more useful than a guide only its author understands.

Turning the three qualities into a file review

Run a file review for each client on a regular schedule. The goal is not perfection but finding weak spots while there is time to fix them. The table below sets out a simple sequence. For a new client, connect this review to your accounting client intake checklist.

StepWhat to checkEvidence to keep
ScopePeriods, tax types, and registrations the firm is responsible forA file index listing what is kept, where, and in what format
CompletenessReturns traced back to source recordsA list of unsupported figures, prioritized for follow-up
Traceability Where a sample transaction started and how it movedImport logs, mapping rules, and the record for any adjusted transaction
Control and conversion Who can edit or delete records, and whether the change log is readableOne export that opens and reconciles to the books
Access How a reviewer would reach each client's electronic recordsA short access note filed with the file index

Pay particular attention to figures corrected after filing. These often live in a separate workpaper, an email thread, or someone's verbal explanation. The reason for a correction and its supporting record should sit alongside the original return support.

Give each finding an owner and a due date. A list of gaps that nobody is assigned to fix is a record of a known problem, not a control.

Illustrative example: following an export difference

Trace the missing transactions to their source records, check the import logs and mapping rules, and document any correction. Export again and compare the totals. Matching totals address the difference; retain the trail showing how it was resolved.

Responding when a records request arrives

Even well-kept files need a response process. The best responses are calm and organized, and they follow steps written down in advance.

Read the request carefully and name one owner for the response. Confirm the scope: which client, which periods, which kinds of records. A vague request is often better clarified with a short call to the reviewer than guessed at. If the form of access is part of the discussion, raise it early, in keeping with the consultation the regulation expects.

Assemble records using the file index, not memory. Produce them in the requested format and, where there is a choice, pick the one that best shows the trail. If you convert a system export, keep a copy of what you sent, along with a record of what was provided and when.

Do not reorganize or rewrite client records to make them look tidier. If a figure needs explaining, write the explanation separately and label it as such. Changing the underlying books in response to a request is exactly the kind of change internal controls exist to make visible, and it undermines the response even when no harm was intended.

A short cover note helps. It should cover the items below.

Cover note itemWhy it matters
Client, periods, and tax typesFixes the scope so the reviewer and the firm are looking at the same thing
Records by name and formatLets the reviewer match what was sent against what was requested
Records not included, with a reason Stating what is missing is as important as listing what is provided

After the request closes, debrief. Note what took time, what was missing, and what would make the next response faster. Update the file index and the access note. A single request often reveals weak points that a routine review missed, because it shows exactly where the file breaks under pressure.

Start a file review today

Today, choose a filed return and trace a reported amount to its source document. Record any gap, assign an owner, and set a due date.

This article is general information, not legal advice. Involve a qualified adviser when a specific client's situation calls for one.

Related guides: Sales tax on collected bad debts: 3 rules to check · Florida sales tax filing frequency: 4 thresholds · Sales tax invoices: 3 checks before client billing.

Questions about retained sales tax records

Does keeping every email make a file complete?

No; completeness depends on keeping the records needed to support the calculation and return. Use a file index to make that support easy to find.

What should accompany an export?

Keep the import logs, mapping rules, and change history that explain the exported figures. Test that the export opens and reconciles to the books before a request arrives.

Sources