Skip ahead to the main page
Partner Huddle
Pages

New York sales tax audit, 4 state publications to read

Partner Huddle Editorial Team · Published · 12 min read

Before a New York sales tax audit, read the state's recordkeeping bulletin, then the four publications it names. The client may have a bookkeeper, a point-of-sale system, a folder of supplier invoices, and a letter asking for records. The natural impulse is to start pulling reports right away. A better first step is to read what the state itself says about the records a registered vendor must keep.

Key takeaways

  • Read the state's recordkeeping bulletin first, and save a dated copy to the file.
  • Ask for records of both sales and purchases in the same request.
  • Read page 40 of Publication 750 before building the record map.
  • Export system data in its original form, and keep an untouched copy.
  • Read Publication 131 and Tax Bulletin TB-ST-805 with the client before any meeting with the auditor.

This post covers four New York State publications that belong in the front of every sales tax audit file. For each one, it explains what it is for, what it can and cannot do for your team, and where it fits in the order of work. It also suggests a practical way to build the file so that the records, the explanations, and the client's questions stay organized from the first call to the last request from the auditor.

What the state expects a registered vendor to keep

Start with the duty itself. The New York State Department of Taxation and Finance states it plainly in its bulletin on recordkeeping requirements for sales tax vendors: "As a registered sales tax vendor, you are required to keep accurate records of all sales and purchases that you make." That sentence sets the scope of the file. The auditor is not only interested in the sales the client reported on its returns. Purchases count too, so the file has to cover both sides of the books.

For a small firm, this changes the first meeting with the client. Ask for records of sales and records of purchases in the same request. A file that holds only sales reports will look incomplete, even if the sales totals are correct. Many owners think of the audit as a question about what they earned. The state's wording points to a broader question: can the client show what it sold and what it bought, and can those records be matched to what was filed? The Accounting Client Intake Checklist for a Clear Handoff can help structure that first meeting.

The same bulletin lists the Tax Law sections it relies on: Sections 1132(c); 1135; 1138(a); 1142(5); and 1145(i), (j), (k). Copy that list onto the first page of the audit file so that anyone who opens the file later can see where the recordkeeping duty comes from.

The bulletin also sends readers to the guides discussed below. Instead of searching the state's website for each publication, the firm can start from one page and follow its pointers in order. Save a copy of the bulletin in the file with the date you saved it, because state pages change and the file should show which version the team relied on.

Publication 750: the broad guide to read first

Publication 750, A Guide to Sales Tax in New York State, is the wide reference. The recordkeeping bulletin cites it in two ways. It names the publication as the place for more information, and it directs readers to the information beginning on page 40 of that publication. So the first read is shorter than the whole publication. Go to page 40, read the recordkeeping material closely, and then read the rest as the client's business requires.

Resist the urge to summarize the whole publication for the client in one email. Instead, use it to build a working map. On one page, write down the kinds of sales the client makes, the kinds of purchases it makes, and the records each one produces. A retail client might list register reports, online order exports, card processor statements, and supplier invoices. A restaurant might add delivery platform reports and purchase records for food and supplies. The map is not a tax conclusion. It is a list that shows the team which records exist and which are missing, before the auditor asks for them.

The map also helps with the return side of the file. For each sales source, ask which figure on the filed returns it feeds. For each purchase source, ask how it was handled when the return was prepared. Gaps here are normal in a first pass. Mark them as open questions rather than settling them before the facts are confirmed.

Keep the map next to the publication. Note the page or section that answered each question beside the item on the map. The next person who reviews the file can then see the reasoning without rebuilding it.

Be careful about the limits of this step. The map tells you what records to collect and how they relate. It does not decide how a particular transaction should be taxed. For those questions, a licensed tax professional who knows the client's facts should review the answer before the firm relies on it in a response to the state.

Comparing the four publications side by side

The four publications answer different questions, so it helps to see them next to each other before the team opens any of them. The table lines up each guide's subject with when it is most useful in the file.

GuideSubjectRead it when
Publication 750, A Guide to Sales Tax in New York StateGeneral sales tax guidance, including page 40 on recordkeeping First, before building the record map
Publication 132, Computer-Assisted Audits - Guidelines and Procedures for Sales Tax Audits Procedures for computer-assisted sales tax auditsWhen sales or purchase records come from computer systems
Publication 131, Your Rights and Obligations Under the Tax LawThe client's rights and obligations under the Tax LawBefore the first call or meeting with the auditor
Tax Bulletin TB-ST-805, Sales and Use Tax PenaltiesSales and use tax penaltiesAlongside Publication 131, before anyone discusses possible exposure

The order in the table is a starting point, not a rule. Some firms will move through the guides in a different sequence, especially if the client already keeps clean records. What matters is keeping the questions separate. Publication 750 explains the rules. Publication 132 explains computer-assisted audits. Publication 131 explains the client's rights, and the penalty bulletin explains the penalties. When those questions get mixed together in a meeting, the client leaves with more worry and less clarity than before.

Publication 132: when the records live in a computer

Publication 132, Computer-Assisted Audits - Guidelines and Procedures for Sales Tax Audits, is the guide for the part of the audit that depends on data. The recordkeeping bulletin points readers to it directly. Read it with the client's systems in front of you, because its questions are easier to answer with real screens and real exports than with memory. For a closer look at what a usable sales record needs, see Sales tax records: 3 qualities your files need.

For a small firm, the practical question changes. Instead of asking what records the client has, ask which systems produced them. Make a two-column list. On one side, list every system that records sales: the register, the online store, the invoicing package, and any payment processor that holds transaction history. On the other side, list every system that records purchases: the accounts payable tool, bank and card statements, and the folder of supplier invoices. Next to each system, note who can export its data, what date range the export covers, and whether its totals line up with the figures on the returns.

Two habits make this work well. First, export the data in its original form and keep an untouched copy. Do not clean, sort, or edit the source file, because an altered file invites questions about why it changed. If the team needs a working copy, make it from the saved original and label it clearly.

Second, note the date and time of every export. If the client runs the same report twice and the totals differ, the notes explain why. A sale may have been entered after the first run, or a refund may have posted late. Without notes, the team has to reconstruct the sequence from memory.

Where the client lacks a system that produces clean data, say so in the file. Describe what the client does have, such as handwritten daily totals or hand-built spreadsheets, and describe how those figures were produced. Do not present a manual record as if it came from a system. The auditor will ask how each figure was produced, and the file should answer that directly.

Publication 131 and the penalty bulletin

Publication 131, Your Rights and Obligations Under the Tax Law, frames the client's side of the audit. The recordkeeping bulletin pairs it with Tax Bulletin TB-ST-805, Sales and Use Tax Penalties, which is cited in the same place. One explains the client's rights and obligations. The other covers the penalties that can apply to sales and use tax matters. Reading one without the other gives an incomplete picture.

Read both with the client before the first meeting with the auditor. Many owners hear the word "audit" and start guessing about the worst case. The publications give everyone the same starting facts, so the conversation begins from the rules instead of rumors. Use the reading to settle three practical matters: who speaks with the auditor, who gathers the records, and which questions go to the firm's own tax specialist or to the client's attorney, if the client has one.

Write these decisions down. A short memo that names the point of contact, the people who collect records, and the people who review each response prevents three people from sending three different answers.

Do not use the penalty bulletin to estimate what the client might owe on a first call. How the penalty rules apply depends on the facts in the file, and a figure guessed on the phone can become the number the client remembers. If the client asks for an estimate, explain that the team will work it out from the records and report back once the file is complete.

Finally, make sure the client understands the firm's role. The firm organizes the records, explains what they show, and keeps the process moving. Decisions about how to respond to the state, and about any legal representation, belong to the client and to whoever represents the client in the matter.

Putting the file in order

A workable order for the file looks like this. Each step builds on the one before it, so skipping ahead usually means redoing work.

  1. Confirm that the client is a registered sales tax vendor, and put the registration details on the first page of the file.
  2. Save the recordkeeping bulletin with the date you saved it, and place the Tax Law section list at the front.
  3. Read page 40 of Publication 750, then read the rest of the publication as the client's business requires.
  4. Build the record map of sales sources and purchase sources, and note the page or section behind each entry.
  5. Inventory the systems that produced the records, using the approach in Publication 132, and export the data in original form.
  6. Compare the exports with the filed returns. Where a difference appears, write down the difference and its likely cause, even if the cause is still unknown.
  7. Read Publication 131 and the penalty bulletin with the client, and record the decisions about contacts and responsibilities.
  8. Set up a single log for every request from the auditor and every response the firm sends.

The comparison in step six is where most of the real work happens. Totals that do not match are not automatically a problem. They may reflect timing differences, returns or refunds posted in a different period, or a system that counts transactions in a way the firm did not expect. Find the reason for each difference and show it in the file. A reconciliation with a short note for each difference is more persuasive than one that balances on the surface but has no explanations behind it.

Keep the reconciliation simple enough that a second person can follow it. Use plain labels, put the source of each figure beside it, and avoid burying adjustments in formulas that only the preparer understands.

Illustrative example: one reconciliation difference

Suppose a client has 3 sales sources and 2 purchase sources. The register reports, the online order export and the card processor statement cover the sales side. The supplier invoices and card statements cover purchases. The team writes down the difference, checks for a cause such as a refund posted in a later period, and leaves the item open until the cause is confirmed.

Keeping the file clean during the audit

Once the auditor is involved, the file becomes a running record of what was asked and what was given. Every request should go into a log with the date received, a plain description of the request, the person handling it, and the date the answer went out. Keep a copy of every document sent. If the auditor later says a document was not received, the log and the copy settle the question.

Avoid answering from memory. When a question arrives that the team cannot answer from the records, reply that the firm will confirm and follow up, then do so. A quick guess that turns out to be wrong costs more time than a short delay.

Agree on the firm's position before each meeting with the auditor. Decide what the firm will bring, what it will leave for follow-up, and who will take notes. Write the notes into the log the same day. If the auditor asks for something the team did not expect, record the request exactly as it was made, and do not agree to a deadline the team has not confirmed internally.

Set a schedule for client updates at the start, such as a short written summary at set points in the process. That keeps the client informed without flooding the team with calls.

When the audit is complete, do not discard the working files. Store the original exports, the reconciliation, the log, and the memo about roles together, with a note of where each one came from. The next notice will then start from a complete file.

Wrapping up

The four publications are a small part of the work, but they shape the rest of it. The recordkeeping bulletin makes clear that a registered vendor must keep accurate records of sales and purchases. Publication 750 explains the rules, beginning with page 40. Publication 132 is the guide to use when the records come out of computer systems. Publication 131 and the penalty bulletin frame the client's rights and the consequences that can follow. A firm that works through them in order, and keeps the questions separate, ends up with a file that is easier to explain and easier to defend.

State publications are updated from time to time, so confirm that you have the current version of each one before you rely on it. Anything the team concludes from the guides should be checked against the client's facts by someone with the authority to advise on them.

Next step for today: pull the recordkeeping bulletin, save a dated copy to the client file, and list the sales and purchase records the client already keeps.

General information, not legal or tax advice.

Sources