Overview of the sales tax audit process

Introduction

A tax audit is a formal review conducted by a taxing jurisdiction to verify that a business has correctly calculated, collected, and remitted sales tax or VAT. Audits can be triggered by a variety of factors, including filing inconsistencies, nexus establishment, or routine jurisdiction-wide reviews.

This guide outlines the traditional flow of a state, city, or country tax audit — covering both US sales tax and international VAT — and explains how Anrok supports you at each stage of the process.

Tip CleanShot_2024-04-30_at_15.47.03_2x-removebg-preview.png

Anrok does not provide audit assistance services directly. However, Anrok can connect you with a taxability partner who can help. Complete this form to kick off the process. Once we receive your submission, we'll use the information to connect you with the partner best suited to assist.

 


 

Pre-audit preparation

Even before a state reaches out, there are a few things that are always a good idea for a finance or tax department to have on hand or know exactly where to go for updated information. From a best practice perspective, it is recommended to conduct a quick quarterly review to ensure the latest versions of documents are accessible and lists are up to date, so you are not scrambling when the time comes.

Here are checklists of information that should commonly be obtained in preparation of an audit:

①   Stackholders ②   Company ③   Financials ④   Invoices

The following outlines the key internal and external parties involved in supporting the audit process. Identifying these stakeholders early ensures that the right people are engaged at the right time and that accountability is clearly established across teams.

  • Internal stakeholders — Who are the internal contacts/owners needed to pull certain information and support the audit? Generally, the tax team will “own” an audit, but may also require data gathered from finance, legal, and other operations team(s).
  • External stakeholders — Tax advisors, auditors, tax engine, and legal counsel who supported decisions around tax registrations.

The following materials provide a comprehensive snapshot of the organization's legal structure, operational activities, physical presence, and technical systems. Together, these documents establish the foundational context needed to understand how the business is organized, where it operates, and the systems that support its day-to-day functions.

  • Current organization chart — Latest copy of the corporate organization chart, including details about subsidiary relationships and ownership percentages.
  • Business operations — A brief document that summarizes each entity’s operations, product/service descriptions, revenue streams, and customer types.
  • Geographic footprint — All locations where business is conducted (offices, warehouses, employees)
  • System documentation — Tax engine configurations, ERP system setup, automation rules.

These are standard documents that any auditor will request, so it is important to know where these documents are stored. Delays in responding to auditors' initial information requests can lead to penalties and damage goodwill. Having the information readily accessible will help the team move quickly toward a successful resolution.

  • Financial records — General ledger, trial balance, revenue by jurisdiction for the past 3-5 years.
  • Tax returns — All filed sales tax/VAT returns by jurisdiction.
  • Registration documentation — A list of everywhere the entities are registered for tax (payroll, income, and sales taxes)

Invoice details are the core of any audit, and copies of invoices are the supporting details that auditors request to support all requested reports. Therefore, accurate addresses and invoice templates set up from day one will set a company up for success and make this detailed information gathering as painless as possible.

  • Full address collection — For customers in the SaaS or digital space, collecting addresses may not have been a priority when initially setting up a billing system, since a physical delivery is not relevant. However, as a company begins to roll out sales tax, address details are mandatory. Especially in the US, where there are over 10,000 taxing jurisdictions between cities, counties, and special districts, the more address data you collect, the better.
  • VAT ID collection — For any company looking to sell, or eventually expand into non-US markets, a field to collect VAT IDs from customers is a must-have.
  • Exemption certificate collection — If a company sells to non-profits, governments, resellers, etc., they will need to collect exemptions from these customers to support the non-taxable or reduced taxability charged to these customers. Exemption certificates are always requested by auditors to support non-taxable customer sales.

How can Anrok help with pre-audit preparation?

While Anrok may not have everything an auditor will request, it can serve as a valuable source of truth and consolidation of the vast majority of requests made under a typical audit. Meaning, for many of the documents above, you can take a hands-off approach and rest assured that Anrok will have everything you need if and when the time comes for a jurisdiction audit. Specifically:

  1. Financial records — While the GL and trial balance may be stored in your accounting software, from Anrok, you can easily export on demand sales by jurisdiction using our audit-ready Transaction Report, which includes applicable VAT ID validation data where applicable. See Export your transactions.
  2. Tax returns — Anrok stores all returns filed in your Anrok instance. No need for hard drive folders that constantly need updating; you can always come to Anrok for copies of your returns. In addition, Anrok has audit-ready return detail exports, with each individual transaction reported on a return and applicable currency conversion. See Best practices for reviewing filed returns.
  3. Registration documentation — Within Anrok, you can easily view where you are registered for sales tax/VAT, and when you started collecting, filing, and remitting. All in one quick snapshot. See Review remitting jurisdictions.
  4. Robust address resolution — While full addresses are always best, Anrok can calculate tax with just a country in most non-US jurisdictions and just a zip code in the US. This limits potential out-of-pocket exposure for customers who have entered incomplete addresses. See Address information required to calculate tax.
  5. Unprocessed transaction tracker — For customers who may not have been diligent about address collection, Anrok identifies these transactions and surfaces them to users. This allows customers to quickly identify who they need to contact for updated address information and where they have potential audit risk before an audit occurs. See Resolve unprocessed transactions.
  6. VAT ID validation — Anrok automatically validates VAT IDs passed through our integrations. All you have to do is collect them, and Anrok will take care of the validation, accurate tax calculation, and provide a robust audit trail for international jurisdictions. See Manually enable VAT ID validation in global jurisdictions.
  7. Exemption certificate management — Anrok supports a variety of ways to upload exemptions, ensuring a single place of storage and accurate, transparent tax calculations. See Manage your exemption certificates.

 


 

Phase 1

Nexus review

Any audit will begin with the jurisdiction looking at when an entity established nexus (US) or met the registration threshold (international) with that jurisdiction. For an international jurisdiction audit, the document(s) and questions will typically be around economic thresholds, VAT ID collection, and potential local supply triggers for physical good sellers.

Based on the information provided, the jurisdiction will determine the date on which the entity established nexus/met the registration threshold. From there, we move to the next phase, in which the audit will seek to determine which liability was not paid from that period onward.

①   Nexus establishment ②   VAT & cross-border obligations

The following documents the basis for the company's taxable presence across US jurisdictions, covering both physical nexus and economic nexus based on sales volume. Given that lookback periods can extend to inception, comprehensive historical records are essential.

  • Physical nexus — Where you have offices, warehouses, or inventory, and when were they established. Also includes, where you have employees, employees of affiliated entities, and/or contractors doing work on behalf of the company.
  • Economic nexus — Provide a list of all sales made into the jurisdiction for the past X years. The lookback period here can be all the way back to an entity’s inception, so be prepared with records dating as far back as applicable.

The following documents the company's exposure and compliance position across international tax regimes, covering sales thresholds, customer VAT ID validation, warehouse and fulfillment locations, and where services are delivered. Together, these records establish where VAT obligations arise and how they have been managed.

  • Distance selling thresholds — Provide a list of all B2C (and B2B in certain countries where such sales are taxable) sales into the jurisdiction.
  • VAT ID collection — Provide a record of all sales where VAT was not charged because the customer provided a valid VAT ID. This report should at a minimum, include the customer name, address, VAT ID provided, and its validation method outcome.
  • Local supply triggers — The locations where your warehouse and fulfillment centers are located.
  • Service establishment — The locations where services are provided.

How can Anrok help with nexus review?

For companies with all their applicable sales and HR data in Anrok, Anrok simplifies this step. Customers can quickly log in to Anrok to pull:

  1. Physical recorded manually — Physical presence recorded in the state is viewable by the jurisdiction in Anrok, making it easily provided to an auditor. If you have manually recorded other key events, e.g., office establishment, warehouse, etc., in the Anrok physical nexus box, they will be easily viewable as well. See Manage physical nexus information.
  2. Physical presence detected through HRIS — If you have connected your HR system to Anrok, you can see the date/name of your first hire as well as subsequent hire dates in each jurisdiction. See Integrate Anrok & your HRIS.
  3. Economic threshold monitoring — Economic nexus/Registration threshold is automatically calculated in Anrok, so you can validate the auditor’s assessment and understand potential exposure even before receiving the audit assessment. See Monitor your nexus status in jurisdictions.
  4. Historical transaction impact — If you have imported all of your historical transactions into Anrok, the jurisdiction view will show the exact date you met the economic nexus or registration threshold. See Manually backfill your historical transactions.
  5. Transaction report by jurisdiction — The Anrok transaction report is an audit-ready report that provides all revenue by jurisdiction for the requested date range, which is always the first report requested by any auditor. See Export your transactions.

 


 

Phase 2

Taxability analysis

With the nexus established and the audit scope defined, the focus turns to analyzing the transactions and products that fall within the audit period. This section walks through how auditors approach transaction data — including when and why statistical sampling is used — and how they evaluate the taxability of your products or services, including the role a tax advisor can play in supporting your positions.

①   Transaction scope & sampling ②   Product taxability review

Once a jurisdiction has determined that you have nexus/crossed the filing threshold and when, the deep dive into the transactions within that period begins. For sellers with high transaction volumes, the auditor may request statistical sampling, as reviewing large data volumes is impractical.

When performing their taxability analysis, an auditor will commonly request transaction details at the product/SKU level. From there, they will bucket products by volume and work their way through the list. For example, if you sell 5 products, Product A, B, C, D, and E, with A making up 75% of your sales and B making up 10%, and the rest a smaller portion, they are going to deep dive most heavily into A and B.

Auditors will review any applicable documentation about your product(s). They may request further discussions with someone in the business to fully understand the product(s) and services being sold. Once they have gathered all applicable information, they will determine how the product is defined for tax purposes and whether it is taxable in their jurisdiction.

Depending on what is being sold, a taxability analysis by a tax advisor can be very beneficial here if your product(s) don't fall neatly into a clear category as defined by the jurisdiction. This is most common in the digital space, where, in the US in particular, definitions and guidance are often unclear. That analysis can be provided to the auditor as support for the tax rules you have chosen to apply to your product.

How can Anrok help with taxability analysis?

Anrok equips customers with the reporting and expert support needed to navigate product-level taxability reviews with confidence:

  1. Product ID-level reporting — Anrok has an audit-ready report for this purpose. Customers can download all transactions at the Product ID level, allowing for a quick summary of sales by product to provide the auditor and taxability within the jurisdiction by product ID.
  2. Product ID export with taxability mapping — From the jurisdiction detail page in Anrok, you can easily see a list of all of your Product IDs with the corresponding tax category you have assigned to them, as well as whether they are taxable/non-taxable in the jurisdiction.
  3. Tax experts monitoring taxability — Anrok has a team of US-based tax experts who are monitoring all legislative changes affecting the Anrok product catalog. Anrok proactively notifies customers in case of taxability changes, so when the time for an audit comes, Anrok has accurate tax determinations across the globe.
  4. Custom tax codes — Anrok recognizes that some customers may have unique products that don’t fit neatly into existing Anrok Product IDs, or have special arrangements with certain jurisdictions. Anrok makes it simple to set up and manage a custom Product ID, so customers can set taxability to fit their needs.

 


 

Phase 3

Exempt & Reverse charge sales mapping

Now that the audit has further whittled down the scope of transactions in scope to include only those with taxable products, the next step is to assess whether there is any reason tax should not have been assessed on these taxable products. The two main reasons tax is not applied to an otherwise taxable sale are exempt sales and sales subject to reverse charge.

①   Exempt sales ②   Reverse charge sales

Exempt sales are primarily a US concept, whereby a seller makes a sale to a customer who provides a valid exemption certificate showing that the purchaser has a valid reason for the seller not charging them tax on the transaction. Common examples of exempt sales include sales to a reseller, a non-profit, or a government agency. To support an exempt treatment, the seller must have a valid exemption certificate from their customer that has not expired and includes all applicable fields. 

On audit, the seller will ask for all exempt sales and copies of the applicable exemption certificate to support those sales and the non-tax treatment afforded to them. This is a common time in an audit when sellers find shortfalls in their documentation, often due to expired certificates or customers who were “clearly” exempt or said they were, but no certificate was obtained. 

While states are often generous in giving companies time to return to their customers to collect those certificates, this can be a significant administrative and time-consuming burden, as well as a less-than-ideal experience for your customers. Furthermore, locating customers that have churned or are no longer in business can often be fruitless, and without a certificate to document the exemption, states will require tax to be paid on those transactions.

Reverse charge sales are an international VAT concept in which cross-border sales to an enterprise (i.e., a B2B sale) are not subject to tax on the invoice if the purchaser provides the seller with a valid VAT ID. By doing so, the seller is relieved of the obligation to charge VAT, and the purchaser affirms they will self-remit the VAT due on the purchase. Reverse charge happens because a valid VAT ID is provided. So even if all of a company’s sales are B2B, that will not excuse a failure to collect VAT IDs in support of the reverse charge. 

Similar to the exemption certificate context above, jurisdictions often allow customers a grace period to collect VAT IDs from customers. As noted above, this is often a significant, administrative, and time-consuming process that can affect a company’s customer experience.

How can Anrok help with mapping exempt and reverse charge sales?

Anrok provides built-in tools to simplify two of the most documentation-heavy areas of an audit — exempt sales reporting and exemption certificate management:

  1. Exempt sale & VAT ID reporting — Anrok’s audit-ready transaction report identifies exempt sales, VAT IDs collected, and VAT ID validation method/validation status for quick provision to an auditor, rather than having to comb through individual transactions or customer records, saving time and headache. See Export your transactions.
  2. Exemption certificate managerAnrok has a robust exemption certificate tool and transaction associating logic that can make audit reporting on exempt sales easy. This allows customers to store exemptions, track certificate expiration dates, and request new certificates directly. Through Anrok, companies can export copies of exemption certificates for an auditor. See Manage your exemption certificates.

 


 

Phase 4

Tax rate application

At this point, the audit has settled on the list of transactions in scope: only those within the nexus or threshold period, only those with taxable products, and excluding any exempt or reverse charge transactions with valid supporting documentation. What remains is everything that should have been subject to tax. The next step is to determine the correct rate to apply to each transaction — an analysis that can carry more nuance than it first appears.

①   Reduced rates ②   Sourcing rules

While most taxable products and services are subject to the standard rate for the applicable address, certain jurisdictions apply alternate rates to specific product or service categories.

  • SaaS and digital products — Some jurisdictions impose reduced rates on software-as-a-service, data processing, or other digital products. For example, Texas applies a reduced rate to SaaS and certain data processing services.
  • E-books and publications — Outside the US in particular, e-books and physical books are commonly subject to a reduced VAT rate.
  • Luxury goods — Some jurisdictions impose higher rates on goods classified as luxury items.
  • Clothing — Certain jurisdictions apply reduced rates to clothing items below a specified price threshold.

While sales are generally sourced to the location where they are delivered, this is not always the case — particularly for non-physical goods and certain digital products.

  • Destination sourcing — For non-physical goods, states apply a cascading hierarchy of sourcing rules to determine where a sale is sourced and what rate applies. Companies should collect as accurate address information as possible to support this analysis.
  • Origin sourcing — For physical goods, and in some jurisdictions certain digital products, a handful of states source sales to the location the product is shipped or provided from, rather than where it is delivered.
  • Unique product sourcing — Certain product categories, such as certain leases, may have sourcing rules that depart from the jurisdiction's standard approach.

How can Anrok help with tax rate application?

Anrok handles rate complexity natively, so customers don't need to manually configure or maintain special rates or sourcing logic:

  1. Tax experts monitoring rate changes — Anrok has a team of US-based tax experts who monitor law and rate changes across the globe. Anrok proactively notifies customers of significant rate changes or changes related to special rates and sourcing rules.
  2. Built-in logic for special rates — Unlike tax engines that require customers to manually configure and maintain custom rates, Anrok has jurisdiction-specific rate logic built in by product ID. For example, Anrok automatically applies the Texas reduced rate to SaaS product codes.
  3. Built-in cascading sourcing logic — Anrok follows each jurisdiction's specific sourcing rules. If the first address in the jurisdiction's requirements is unavailable, Anrok works down the hierarchy until a valid address is found, ensuring tax is collected in the manner prescribed by the jurisdiction rather than returning no tax due to an incomplete address. Anrok also supports sourcing logic dictated by the customer to align with their billing practices.
  4. Built-in origin sourcing by product ID — Anrok natively supports origin sourcing for all product IDs that require it, with no custom setup required. Jurisdiction-specific rules for unique product categories are likewise applied automatically.
  5. Robust address resolution — Anrok can calculate tax with just a country in most non-US jurisdictions, and just a zip code in the US, limiting exposure for transactions with incomplete address data. See Address information required to calculate tax.

 


 

Phase 5

Assessment

Once the audit has progressed through the steps above, the auditor will compile their findings into a final report and issue an assessment. The assessment reflects the tax liability, penalties, and interest the jurisdiction has determined are owed based on the transactions reviewed.

Note CleanShot_2024-04-30_at_16.01.40_2x-removebg-preview.png

Even before you receive a notice from a jurisdiction, the Exposure modeling tool in Anrok can help you understand potential exposure and anticipate the size of any assessment. See Exposure modeling.

Can't find what you're looking for?

Submit a request to our customer care team!