Most B2B sellers treat exemption certificates as a formality. A customer claims they are buying for resale, the rep collects a form, the deal closes. That works fine until an auditor arrives and asks to see the certificate behind every untaxed transaction in a four-year window.
The liability sits with the seller, not the buyer. If a certificate is invalid, the seller owes the uncollected tax plus interest and penalties, regardless of what the customer told them. And the way auditors calculate that liability is what makes certificate problems so expensive: they sample your records, find the error rate, and project it across the full audit period. A 15% error rate in a 100-transaction sample applied to $3 million in exempt sales over three years produces $450,000 in assessed deficiencies before penalties and interest. A handful of paperwork gaps becomes a six-figure number through that extrapolation alone.
Missing certificates are the most straightforward. A sale was coded exempt in the system, but there is nothing on file to support it. This happens most often when a customer verbally claims exempt status, the rep overrides the tax, and the paperwork never follows.
Expired certificates are the most avoidable. Florida exemption certificates expire five years from issuance under Fla. Stat. §212.084. Other states have no hard expiration but expect periodic re-verification. A certificate that was valid when collected can be worthless at audit time if it lapsed midway through the period under review.
Incomplete certificates are defective on their face: missing buyer name, blank address, no tax ID, unsigned, or no stated reason for exemption. These defects are easy to catch at intake and almost impossible to fix years later.
Wrong form for the wrong state scales as a problem with geographic expansion. The MTC Uniform Certificate is accepted in 36 states with varying conditions. The SST certificate covers 24 member jurisdictions. States outside those frameworks require their own forms. Using the MTC certificate for a Texas customer when Form 01-339 is required is the same as having nothing on file.
Certificate-to-transaction mismatch is the failure auditors find in sophisticated operations. A resale certificate does not cover manufacturing, nonprofit, government, or project exemptions. If a customer's certificate claims resale but the items were used in production, the exemption fails even if the certificate itself looks complete.
Because expiration rules differ by state, a seller operating in multiple jurisdictions cannot apply a single renewal schedule to their entire certificate library.
Sellers who accept an invalid certificate in good faith are generally protected from liability, but good faith has real requirements. It means the certificate appeared valid on its face and was collected at or near the time of the sale, from a buyer whose business plausibly supported the exemption claimed.
It does not protect a seller who accepted a certificate with visible defects. It does not protect a certificate collected after the audit notice arrived. And in states that require it, failing to verify the buyer's registration number can strip the good faith defense even if everything else looks correct. SST member states apply a relaxed good faith standard, giving sellers a somewhat lower bar for acceptance in those jurisdictions.
Four things separate a certificate library that survives an audit from one that generates an assessment.
If a review of your current library reveals gaps, proactive remediation before an audit opens is significantly cheaper than addressing them after. Many states, including Texas, California, and New York, allow certificates collected during an open audit to be considered before the final assessment is issued, but that window is narrower and less reliable than acting before the auditor arrives.
Do you know what an auditor would find in your certificate library today? Most certificate gaps are invisible until an auditor samples them and projects the error rate across years of exempt sales. Ceretax manages the full exemption certificate lifecycle: collection at point of sale, validation, expiration tracking with renewal alerts, and an audit-ready library that connects every certificate to its transactions.
Published September 2, 2026
CereTax for Stripe Billing is now available. Companies that invoice through Stripe can calculate accurate, audit-ready sales tax on every invoice in real time, without leaving the Stripe dashboard.
Stripe runs billing for companies at every stage, from early startups to multi-entity enterprises. Sales tax follows that growth: new states, new jurisdictions, new product lines, and new exemption certificates, each with its own rules. Most billing teams keep up with manual adjustments and a standing plan to fix it properly later. Every manual fix adds audit exposure, and the volume of fixes grows with the business.
This integration puts the CereTax calculation engine directly in the invoice flow. Tax gets calculated correctly at the moment the invoice is created, so there is nothing to clean up after.
Connect the CereTax for Stripe app to your Stripe account, enter your license key, and add the webhook endpoint in your Stripe dashboard. Sandbox and production environments are both supported, so your team can test before anything touches a live invoice.
This is the same CereTax platform that more than 200 companies rely on across communications, energy, fuel, software, manufacturing, retail, ecommerce, and more. CereTax integrates with platforms that move more than $4 trillion in transactions each year, and Stripe Billing now joins that list.
The engine behind this connector maintains 98k+ active tax rates, 67M+ taxability decisions, and 5.9M exemption decisions, researched and kept current by our in-house tax team. Every one of them is available on a Stripe invoice through a product and service code. When your catalog grows past plainly taxable goods, into communications services, energy charges, bundled digital and physical products, or items with state-by-state exemption rules, the calculation already knows what to do. Behind it all sits rooftop-level precision and real people who answer the phone when you call.
If you bill through Stripe and sales tax has become a line item on someone's calendar, we should talk. Request a demo to talk to a sales tax expert. Existing customers can connect today using the setup guide.
The appeal of drop shipping as a fulfillment model is straightforward: the manufacturer holds the inventory, ships directly to the end customer, and the retailer never touches the goods. The logistics are simple. The sales tax is not.
A drop shipment creates two legally distinct sales transactions from a tax perspective, not one. The first is the sale from the manufacturer to the retailer, which should be a wholesale sale for resale and therefore exempt from tax. The second is the sale from the retailer to the end customer, which is a taxable retail sale if the retailer has nexus in the delivery state and the goods are taxable there. The problem is that these two transactions do not have the same parties, the same nexus analysis, or the same documentation requirements, and they take place simultaneously in a single shipment.
For manufacturers, the complication starts when the retailer does not have nexus in the delivery state. If the manufacturer does have nexus there, and the retailer cannot produce a valid resale certificate accepted by that state, the manufacturer can become the party responsible for collecting and remitting sales tax on a sale they had every reason to treat as wholesale. This is not a hypothetical edge case. Roughly a third of states with a sales tax treat the manufacturer as the default collector when the retailer is unregistered, and approximately ten of them will not accept any resale certificate from a retailer that is not registered in the delivery state. That combination creates real, ongoing exposure for manufacturers operating multi-state distribution relationships.
The foundational rule in drop shipment tax is that each leg of the transaction is analyzed independently. The first leg, manufacturer to retailer, is evaluated under the rules of the delivery state. If that sale qualifies as a sale for resale, meaning the manufacturer holds a valid resale certificate from the retailer and the certificate meets the delivery state's requirements, the manufacturer owes no tax on that leg. The second leg, retailer to end customer, is a retail sale taxed based on whether the retailer has nexus in the delivery state and whether the product is taxable there.
The nexus analysis for each party runs independently. A retailer with nexus in the delivery state collects tax from the customer, provides the manufacturer a resale certificate, and the manufacturer's sale is exempt. A retailer without nexus in the delivery state owes no tax on its sale to the customer. But if the manufacturer has nexus in that delivery state, the manufacturer now faces the wholesale leg as a taxable event unless the resale certificate is valid and accepted. The question that drives the entire analysis is whether the retailer can produce documentation that the delivery state will accept.
The three key scenarios and their outcomes:
The resale certificate is the document that converts the manufacturer-to-retailer transaction from a taxable sale into an exempt wholesale transaction. The challenge is that no single certificate format is accepted everywhere, and the requirements vary significantly by state.
The Multistate Tax Commission publishes a Uniform Sales and Use Tax Resale Certificate accepted by approximately 36 states with varying conditions. The retailer lists its registration numbers for the states where it is registered, and one form covers those states. The Streamlined Sales Tax exemption certificate works across SST member states under a similar framework. Under the SST rules, a retailer can issue a resale certificate to the drop shipper even if the retailer is not registered in the delivery state, and the supplier is protected from liability as long as it received the certificate in good faith.
The problem is the states that fall outside these frameworks. About ten states are particularly strict and require their own registration number on their own state-specific form before they will honor a resale exemption on a drop-shipped sale. California is the most consequential example. The California Department of Tax and Fee Administration's Publication 121 on Drop Shipments states clearly that if the true retailer does not hold a California seller's permit, the drop shipper is responsible for reporting and paying California tax, calculated on the amount the retailer invoices the California customer. An out-of-state resale certificate is not sufficient. The retailer must hold a California seller's permit and issue a California resale certificate to the manufacturer.
Other states with similarly strict requirements that will not accept an unregistered retailer's certificate include Connecticut, Florida, Georgia, Hawaii, Illinois, Indiana, Louisiana, Maine, and Massachusetts. For manufacturers shipping into any of these states, the practical implication is that every retailer in the distribution relationship either needs to be registered in the delivery state or the manufacturer needs a documented process for what happens when they are not.
The default collector question is the most financially consequential issue for manufacturers in drop shipping arrangements. It arises specifically when three conditions converge: the manufacturer has nexus in the delivery state, the retailer does not have nexus there, and the retailer cannot provide a resale certificate that the delivery state accepts.
In that situation, most delivery states treat the manufacturer's sale to the retailer as a taxable retail sale rather than a wholesale transaction. The manufacturer is then required to charge the retailer sales tax based on the retail price the retailer charges the end customer, not the wholesale price the manufacturer charges the retailer. This is the rule under California Regulation 1706, which specifies that the drop shipper in this situation should charge the true retailer tax based on the retail amount and report and pay it to the CDTFA. The retailer may then seek reimbursement from the end customer, but that reimbursement is the retailer's problem to solve, not the manufacturer's.
The use tax backstop is the alternative when no sales tax is collected. If neither the retailer nor the manufacturer has nexus in the delivery state and no tax is collected, the end customer technically owes use tax on the purchase. States have increasingly sophisticated mechanisms for identifying these transactions through marketplace data, payment processor reports, and information-sharing agreements. Use tax self-assessment compliance rates among consumers are low, which means the gap between what should be collected and what is collected tends to surface in audits rather than self-reported returns.
The compliance burden in drop shipping is heaviest for manufacturers who ship into many states at the direction of retailers whose own nexus footprint is not fully known. The standard that protects a manufacturer is good-faith acceptance of a valid certificate, but good faith requires that the certificate was timely received, meets the delivery state's requirements, and covers the type of property being sold.
The practical standard for a defensible process has three components. First, require a resale certificate from every retailer before the first shipment, not after. Retroactive certificates obtained during an audit carry less evidentiary weight than certificates obtained contemporaneously with the transaction. Second, maintain a state-by-state matrix of which certificate formats each delivery state will accept, including whether the state requires in-state registration or will accept the MTC uniform certificate or the retailer's home-state form. The Sales Tax Institute's drop shipment FAQ and the MTC Uniform Certificate itself both provide guidance on state-by-state acceptance rules. Third, build a process for the strict-state scenario: if a retailer cannot provide a California seller's permit for California deliveries, the manufacturer's system should either flag the transaction for tax collection or require the retailer to register before orders are processed.
Certificates also expire. Many states require resale certificates to be renewed every one to three years, and an expired certificate makes the supplier's sale taxable on audit even if it was valid when originally issued. A certificate renewal calendar tied to the delivery states in the manufacturer's distribution network is part of the ongoing compliance infrastructure, not a one-time setup task.
Post-Wayfair, economic nexus changes the drop shipment analysis in two ways that manufacturers need to track. First, a manufacturer's own economic nexus footprint determines in which states its wholesale leg is exposed when a retailer cannot produce a valid certificate. As a manufacturer's direct sales or distribution activity into a state crosses the $100,000 threshold, it acquires nexus there and the default collector risk attached to that nexus activates for every unregistered retailer it ships for in that state.
Second, several states include wholesale and exempt sales in the economic nexus threshold calculation, not just taxable retail sales. California, Washington, New York, and Pennsylvania all count gross receipts broadly. A manufacturer that ships $80,000 of taxable goods and $30,000 of wholesale exempt goods into California in a year has crossed the $100,000 nexus threshold based on gross receipts, even though the exempt portion generated no collection obligation on its own. This means nexus can be established faster than a review of only taxable transactions would suggest, which has downstream consequences for how the manufacturer's wholesale leg obligations are analyzed in that state.
Drop shipping across state lines? Your tax exposure is already running. The manufacturer-to-customer transaction looks simple on a shipping label and complicated in every state tax code it crosses. CereTax automates drop shipment tax determination at the transaction level, tracking who owes what in each delivery state, flagging resale certificate gaps, and keeping your nexus map current as your distribution footprint grows.
Every generation of technology arrives faster than the tax code can absorb it. Prewritten software took decades to settle. SaaS still has no uniform treatment across the fifty states. Artificial intelligence as a commercial product is moving faster than either, and the compliance implications are landing now, not in three years when guidance catches up.
The fundamental problem is that AI products do not fit cleanly into any category that state tax law was designed to capture. A traditional SaaS subscription involves a customer accessing prewritten software hosted on a vendor's servers. AI products involve a customer accessing a model, a system that generates outputs dynamically based on training data and prompts, which may or may not constitute software in the legal sense depending on whose definition you apply. The customer is not buying a program. They are buying inference, prediction, generation, or automation. States are actively debating whether that is a sale of software, a data processing service, an information service, or an entirely nontaxable professional service, and they are reaching different answers.
For companies selling AI products, this is not a theoretical compliance question. Major AI providers are already collecting sales tax on API usage in states where they have determined a collection obligation exists. The question is whether your product is being taxed correctly in the states where your customers are, and whether your billing system has been configured for a classification framework that is actively evolving. If you have not asked that question yet, the answer is probably sitting in your billing system right now, waiting to be found in an audit.
States do not have AI-specific tax categories. They are applying existing frameworks to new products, and the framework that applies to your AI product depends on how your product is structured and how the relevant state has chosen to classify the closest analog.
Before you can answer whether your AI product is taxable, you need to know which framework a given state uses to evaluate it. That determines everything that follows. The four classification categories that appear most frequently in 2025 and 2026 rulings are prewritten software, data processing services, information services, and nontaxable professional or consulting services. Each carries different taxability consequences. Prewritten software is taxable in roughly half of U.S. states including New York, Pennsylvania, Texas, and Washington. Data processing services are taxable in Texas at 80% of the charge under Tax Code Section 151.0035. Information services occupy a complex middle category in New York, taxable if delivered electronically but exempt if the information is personal or professional in nature. Nontaxable services are exempt in states that do not tax services generally, which covers most states for most service categories.
The classification question for AI is which of these categories the product falls into, and the answer depends on a fact pattern analysis that requires examining what the customer actually receives: access to a software application, the output of a data manipulation process, a tailored informational product, or a service performed by a system that the customer never controls or owns.
The rulings issued in 2025 and early 2026 illustrate the divergence directly and show that identical products can reach opposite conclusions depending on the state.
Indiana issued Revenue Ruling 2025-02-RST in July 2025, addressing the taxability of a generative AI chatbot subscription accessed via web or API. The Indiana Department of Revenue ruled that the service is not subject to sales tax because SaaS is not taxable in Indiana when the customer accesses software remotely without any permanent ownership interest. The ruling extended this logic explicitly to AI: because the AI is accessed electronically with no permanent ownership aspect, it is not subject to sales tax. The true object of the transaction, in Indiana's analysis, is the output generated by the AI, not the software itself.
Kentucky reached the opposite conclusion. Kentucky Tax Facts issued January 20, 2026, states that SaaS is considered a taxable 'prewritten computer access service' in Kentucky, and that this classification applies even with artificial intelligence components. Kentucky is not analyzing whether the AI constitutes software in a traditional sense. It is applying its existing prewritten software access framework to AI-enabled platforms and treating the AI components as part of the taxable access service rather than as a distinct, potentially exempt category.
Illinois presents a split outcome at the state versus local level that is particularly consequential for any company with customers in Chicago. At the Illinois state level, the Department of Revenue examined an AI-powered chatbot in 2025 and ruled that because no software was transferred or owned by the customer, the service is nontaxable under Illinois's general rule that cloud-hosted software accessed without ownership is exempt at the state level. Chicago, however, has imposed its 9% Personal Property Lease Transaction Tax on charges for the use of AI platforms since October 1, 2023. A transaction that is completely nontaxable under Illinois state law carries a 9% Chicago local tax on the same facts.
New York has not issued a specific AI ruling, but the New York Department of Taxation and Finance's existing position under Tax Bulletin ST-128 treats remotely accessed prewritten software as taxable tangible personal property through constructive possession. As confirmed by Moffa Tax Law's 2025 analysis, New York extends this position to AI platforms. If the AI is used primarily to deliver information, it may also fall under New York's taxable information services category. Either way, AI products delivered to New York customers are taxable under existing guidance applied to the technology.
If you sell AI products to Texas customers and have not reviewed your configuration since April 2025, your billing system is probably wrong. Texas does not classify AI as software at all. Instead, it taxes AI inference and related services as data processing under Tax Code Section 151.0035, which covers computerized entry, retrieval, search, compilation, manipulation, or storage of data. Under the Texas Comptroller's April 2025 amendments to Rule 3.330, the scope of taxable data processing services was significantly expanded, and many AI products that were previously treated as nontaxable now fall squarely within it.
The amended rule introduced an ancillary test. If the seller's primary activity constitutes data processing, the entire bundled service charge is taxable as data processing even if other nontaxable components are included. AI inference services, meaning providing predictions, recommendations, or generated content via API, fall within this framework. The tax applies to 80% of the service charge, with a 20% exemption, and the effective combined rate reaches approximately 8.25% when local rates are added. For AI companies bundling inference with professional services or implementation, the Texas rule is clear: the entire charge is taxable unless the AI component is demonstrably ancillary and has no separate value. The burden of proving ancillarity sits with the taxpayer.
Texas's bundling rule adds an important wrinkle for AI companies that bundle inference with professional services, consulting, or implementation. Under the amended Rule 3.330, a data processing service sold for a single charge with another service is not taxable only if the data processing service does not have a separate value and is ancillary to the other service. The burden is on the taxpayer to demonstrate ancillarity. If the AI component is the core deliverable, as it typically is in an AI SaaS product, the entire charge is taxable.
The practical consequence of this divergence is that a single AI product sold to customers across multiple states requires multiple taxability determinations that cannot be resolved by a single classification applied uniformly. An AI chatbot subscription that is nontaxable in Indiana, taxable as prewritten software in Kentucky and New York, taxable as data processing at 80% of the charge in Texas, and taxable at 9% in Chicago but nontaxable at the Illinois state level requires the billing system to classify each transaction based on the customer's location and the applicable state's framework.
AI agents, systems that autonomously execute multi-step business processes, introduce a classification layer beyond subscription chatbots or inference APIs. An AI agent that handles accounts payable, manages customer service queues, or executes procurement workflows is not simply providing software access or generating a text response. It is performing a function that, if performed by a human, would be a nontaxable professional service in most states.
The EverydayCPE analysis of the Indiana ruling makes this question concrete: an AI agent that handles an entire accounts payable function is arguably performing a service, not delivering software. The true object test, which Indiana applied in its chatbot ruling, could support a nontaxable outcome in states that use it. But states that classify by the seller's activity rather than the buyer's intent, as Texas does under its ancillary test, may reach a taxable result regardless of how agentic the workflow is.
No state has issued a ruling specifically addressing AI agents as a distinct product category as of July 2026. The Snell and Wilmer analysis from November 2025 confirms that state and local tax authorities will continue to revisit these issues as AI becomes more embedded in business operations, and that continued administrative and judicial developments will shape how AI is classified across jurisdictions. For companies selling or using agentic AI products, the absence of guidance is not a green light. It is an open classification question that an auditor will resolve using the nearest applicable framework, which may or may not align with how the product is currently being taxed.
The immediate priority is classification, not rate lookup. Most billing systems for AI products were configured either by treating AI as equivalent to standard SaaS, or by applying no tax at all on the assumption that AI outputs are nontaxable services. Both approaches are wrong in a meaningful subset of states, and the state-by-state picture is becoming less favorable to the nontaxable position as more guidance is issued.
The practical steps that define a defensible current position are a state-by-state taxability analysis of your specific AI product, which requires mapping how your product would be classified under each state's existing framework for prewritten software, data processing, information services, and nontaxable services. Texas's data processing framework, Kentucky's prewritten access service classification, and New York's constructive possession standard each require a different fact pattern analysis. A product that is clearly nontaxable in one framework may be clearly taxable in another.
For companies with significant Texas revenue, the April 2025 Rule 3.330 amendments are the most urgent compliance review item. The expanded scope of taxable data processing services and the new bundling ancillary test affect AI products that were previously treated as nontaxable or partially taxable. The effective date of April 2, 2025 means that liability may already be accruing for companies that have not updated their Texas configuration. For companies with Chicago customers, the 9% Personal Property Lease Transaction Tax on AI platforms has been in effect since October 2023, predating most AI compliance reviews. If your billing system is applying Illinois state rates to Chicago transactions involving AI access, it is applying the wrong rate to a separate, higher-rate local obligation.
Does yourAI product have a sales tax problem you have not found yet? State-by-state AI taxability is actively being litigated, ruled on, and revised. The classification your billing system applies today may be wrong in three states by this time next year. CereTax tracks AI and digital service taxability changes in real time, applies the right classification at the transaction level, and gives you the audit trail to defend every decision.
A three-day sales tax holiday can create a three-week compliance headache if the rules are not built into your tax and ecommerce systems correctly.
That is particularly true for firearms, ammunition, and hunting retailers. Mississippi and Louisiana both offer annual Second Amendment sales tax holidays, but the states take different approaches to eligible products, transaction timing, returns, and reporting.
For 2026, Mississippi's holiday ran from August 28 through August 30, while Louisiana's holiday runs from September 4 through September 6. Mississippi also expanded its holiday this year to include firearm safes.
The lesson for retailers is straightforward: a holiday rule should be treated as a transaction-level tax configuration, not a promotional switch.
Both states remove sales tax from qualifying consumer purchases during their respective holiday periods, but their eligible product lists are not identical.
Louisiana's exemption covers firearms, ammunition, and a broad range of hunting supplies, including archery equipment, hunting apparel, hunting footwear, firearm cases and accessories, optics, hearing protection, holsters, slings, and other qualifying hunting gear.
Mississippi's holiday covers firearms, ammunition, and specifically defined hunting supplies. For 2026, the state also added firearm safes to the exempt category.
Neither state applies a price ceiling to qualifying items.
For Louisiana, the exemption applies to consumer purchases, not business or commercial purchases.
That distinction matters for retailers serving both individual customers and commercial buyers. A blanket "tax-free" rule applied to every customer could produce incorrect results.
The biggest risk is assuming that everything associated with hunting or firearms is automatically exempt.
Louisiana's rules, for example, specifically identify qualifying hunting products. They include archery items, hunting apparel, hunting footwear, bags, tools, firearm cases and accessories, range finders, optics, hearing protection, holsters, belts and slings, among other products. But the state also specifically excludes items such as hunting animals, animal feed, off-road vehicles, motor vehicles, heavy equipment, and certain vessels.
Mississippi similarly uses a defined list rather than a broad "anything used for hunting" standard.
That means product classification needs to happen at the SKU level.
A retailer selling both qualifying hunting gear and general outdoor merchandise should not rely on a broad category such as "hunting" or "outdoor equipment" to determine taxability.
This is one of the most important operational issues because the customer may place an order during the holiday but receive it later.
Mississippi's guidance allows qualifying mail, telephone, and internet purchases to receive the exemption when the customer orders and pays during the holiday and the seller accepts the order for immediate shipment. Eligibility can be lost if the customer requests or causes delayed shipment.
Louisiana takes a related approach. Its guidance allows qualifying property ordered for immediate delivery during the holiday to qualify even when shipment or delivery occurs later, provided the customer did not request the delay.
For ecommerce retailers, that means the tax engine needs to evaluate when the qualifying transaction occurred, not simply when the package leaves the warehouse.
Returns can create problems after the tax holiday has ended.
Mississippi distinguishes between exchanging an eligible item for the same item and returning it for credit toward a different product. A qualifying same-item exchange can remain exempt even when it occurs after the holiday. But when the customer uses the credit to purchase a different item after the holiday, sales tax applies to the new purchase.
Louisiana follows a similar distinction. An essentially identical replacement can retain the exemption, while a return followed by the purchase of a different item is taxable. Louisiana also has specific rules for refunds or credits issued within 60 days after the holiday when the customer can show that sales tax was actually paid on the original purchase.
This is exactly the kind of scenario where a simple "holiday = tax free" configuration breaks down.
Retailers also need to think beyond standard checkout transactions.
Mississippi's guidance states that when eligible and non-eligible products are bundled together, the non-eligible items need to be separately itemized and taxed. Otherwise, the entire transaction can become taxable. Mississippi also excludes layaway sales from the holiday.
Louisiana's rules are different. The state allows qualifying property to be placed on layaway during the holiday, as well as final payments on qualifying property previously placed on layaway.
That difference is easy to miss when retailers use the same ecommerce or POS logic across multiple states.
The same promotion does not mean the same tax rule.
The most effective approach is to separate the holiday into four configuration questions:
Product: Is the item specifically eligible?
Customer: Is this a qualifying consumer purchase?
Timing: Did the transaction occur within the state's holiday window under its rules?
Transaction type: Is this a standard sale, online order, layaway, return, exchange, or bundled transaction?
A retailer should test each scenario before the holiday begins rather than relying on a single tax override.
This becomes particularly important for businesses selling across state lines. A single product may be exempt in Louisiana during its September holiday, taxable in Mississippi outside its August holiday, and subject to completely different treatment in another state.
The compliance work does not end when the holiday does.
Louisiana specifically requires retailers to report exempt Second Amendment holiday sales on Schedule A-1 of Form R-1029, using exemption code 5088. Direct marketers have separate reporting requirements and use the same code for qualifying exempt sales.
Retailers should also review:
The last point is easy to overlook. A temporary exemption that remains active after the holiday can create just as much exposure as one that was never activated.
Mississippi and Louisiana may offer attractive tax savings to consumers, but the compliance rules behind those savings are highly specific.
Mississippi's 2026 holiday introduced a new exempt category for firearm safes. Louisiana's holiday covers a broader range of hunting supplies and has its own rules for layaway, returns, exchanges, and reporting. Both states also have no price cap on qualifying products.
For retailers, the safest strategy is to treat each holiday as a state-specific transaction rule.
That means identifying eligible products, configuring the correct dates, testing online and in-store scenarios, and building return and reporting logic into the same workflow.
The tax holiday may last three days.
Your compliance controls need to work before, during, and after those three days.
Ready to take the guesswork out of sales tax holidays? CereTax helps retailers manage temporary exemptions and changing state rules at the transaction level, so product eligibility, timing, customer information, and tax calculation work together.
👉🏻 Book a Strategy Call with CereTax to review your sales tax holiday configuration and reduce the risk of post-holiday corrections.
Most states that tax software and digital services draw a line somewhere: SaaS is taxable, but custom development is not, or digital goods are taxable, but services delivered primarily through human effort are exempt. Washington has never been content with those distinctions, and in 2025 it moved further than any other state to close them.
Washington has taxed SaaS, remote access software, and digital goods broadly since 2010 under its Digital Automated Services framework, treating these products as retail sales regardless of how they are accessed, downloaded, streamed, or subscription-based. The state's base sales tax rate is 6.5%, but local rates push the combined rate to between 6.5 and 10.6% depending on the customer's address, making destination-based sourcing not just a best practice but a legal requirement. On top of that, Washington levies a Business and Occupation gross receipts tax on the same transactions, meaning digital service providers face a dual obligation that no other major state replicates quite the same way.
Then on October 1, 2025, Engrossed Substitute Senate Bill 5814 took effect, and the compliance picture for digital service providers changed materially. Services that were previously excluded from retail sales tax, including IT support, custom software development, digital advertising, data processing, and any service delivered through digital automated means regardless of how much human effort it involved, became taxable retail sales. If your billing system was calibrated before October 2025, it is almost certainly applying the wrong tax treatment to at least some of your Washington transactions.
The Digital Automated Services classification is Washington's primary mechanism for taxing software and digital products, and it is broader than its name implies. Under Washington law, a DAS is any service that is delivered electronically using one or more software applications. The Washington DOR has confirmed that the access method does not change the classification: downloads, streams, subscriptions, and remotely accessed software all qualify. What matters is that the service is transferred electronically and involves software.
SaaS subscriptions, remote access software, cloud-based platforms, and digital goods such as e-books, music, video, and software downloads are all taxable under the DAS framework. A 2026 Washington DOR determination confirmed that professional implementation services and associated travel reimbursements are also subject to retail sales tax when provided exclusively in connection with a DAS, meaning the taxability of the core product extends to time-and-materials charges billed alongside it.
ESSB 5814 significantly expanded what qualifies as a DAS by repealing the exclusion for services involving primarily human effort. Before October 2025, a service that used software as a vehicle but was primarily delivered through human work could avoid DAS classification. That exclusion is gone. Any service that is at least in part transferred electronically using software applications now falls within the DAS definition, regardless of the human contribution. The DOR has provided interim guidance stating that pure professional services, such as legal, accounting, and engineering work, remain subject to service B&O tax rather than retailing B&O, but only where the service does not substantially involve automated delivery. Where automation is central to the product, such as an AI-powered legal research platform billed at a flat rate per response, the DOR has confirmed the service is taxable as a DAS.
Beyond expanding the DAS framework, ESSB 5814 added several discrete service categories to Washington's definition of a retail sale, effective October 1, 2025. Each carries its own sourcing rules and compliance considerations.
IT services became taxable as a catch-all category covering any service that supports or assists information technology infrastructure. This includes network assessments, planning, design, migration, network security, system upgrades, help desk services, onboarding and offboarding support, and software troubleshooting. IT services are sourced to where the services are received by the purchaser, meaning the customer's Washington address governs. Excluded from the IT services category are web hosting, domain registration, and payment processing, which are separately classified.
Custom software development and software maintenance contracts were explicitly added to the taxable base. Previously, custom software occupied an ambiguous position because it was not prewritten software and was not clearly a DAS. ESSB 5814 removed that ambiguity. Advertising services, defined broadly to include the creation, preparation, production, or dissemination of advertisements in digital or non-digital form, are now taxable. This covers graphic design, search engine marketing, and lead generation optimization. The only advertising categories excluded are newspaper, television, radio, and billboard advertising.
ESSB 5814 also extended retail sales tax to temporary staffing services and live presentations including webinars, seminars, and in-person training, categories that are relevant to SaaS companies that bill separately for customer onboarding sessions or training programs delivered outside the core subscription.
Existing contracts signed and executed before October 1, 2025, received a transitional grace period. Providers with pre-existing contracts who had not yet been paid could continue reporting under the prior B&O service classification through March 31, 2026. From April 1, 2026, all gross income received under those contracts must be reported under retailing B&O and subjected to retail sales tax.
One important condition applies: if an existing contract is altered after October 1, 2025, it immediately loses its transitional status and becomes fully subject to ESSB 5814 from that point forward. Alterations include changes to the parties, the underlying activities, rights and obligations, or the term and amount of the contract. Any amendment, even a minor one, ends the transition treatment.
The Washington DOR also launched a temporary ESSB 5814 Penalty Relief Program covering uncollected or unpaid retail sales and use taxes caused by the October 2025 changes. For providers who have not been fully compliant since the effective date, this program offers a path to correct historical gaps without full penalty exposure. Details are available through the Washington DOR.
The compliance burden in Washington is not just about collecting retail sales tax from customers. Digital service providers crossing the $100,000 economic nexus threshold, which is measured against total gross receipts including exempt and wholesale transactions in the current or prior calendar year, are simultaneously obligated to register for and remit Business and Occupation tax. B&O is a gross receipts tax assessed on the provider without deductions for costs or expenses.
ESSB 5814 also restructured B&O rates for service businesses. From October 1, 2025, service businesses are subject to progressive B&O rates based on affiliated group gross income: 1.5% for income below $1 million, 1.75 % for $1 million to $5 million, and 2.1% for income exceeding $5 million. An additional 0.5% surcharge applies to businesses with taxable income exceeding $250 million annually, effective January 1, 2026. Advanced computing businesses face a separate and substantially higher surcharge: effective January 1, 2026, the advanced computing business surcharge increased from 1.22% to 7.5%.
The practical consequence is that a digital service provider selling $500,000 into Washington owes both retail sales tax collected from customers at the applicable local combined rate and B&O tax on that same $500,000 of gross receipts at the applicable progressive rate, paid directly by the provider. Both obligations flow through the Washington DOR's My DOR portal, both require registration using the same Business License Application and Unified Business Identifier, and both are subject to Washington's late filing penalties, which begin at 9% and escalate to 29% by the end of the second month following the due date.
If you sell any form of digital service into Washington and have not reviewed your product catalog against ESSB 5814's October 2025 changes, the immediate priority is classification, not rate lookup. Rates in Washington are determined at the customer address level, and the DOR's Tax Rate Lookup tool provides the address-specific combined rate your billing system needs. But the rate is only relevant once you have confirmed which of your services are now taxable that were not before.
It is also worth noting that effective July 1, 2026, Washington introduced new exclusions and exemptions under ESSB 5814, including new exclusions for certain live presentations and a new sales and use tax exemption for purchases of qualifying retail services by schools and libraries. If any of those categories are relevant to your customer base, a review of the July 2026 changes is warranted alongside the October 2025 framework.
For providers with existing contracts executed before October 1, 2025, the April 1, 2026 deadline to begin collecting and remitting on those contracts under the new rules is either already passed or imminent. Providers who have not updated their billing for pre-existing contracts are now accruing unremitted tax liability on every Washington invoice issued under those arrangements. The DOR has noted it is involved in ongoing legal proceedings regarding ESSB 5814, and has acknowledged that courts will ultimately assess its constitutionality, but under Washington law, statutes are presumed constitutional and the DOR cannot refrain from enforcing them pending that outcome.
One forward-looking development is worth planning around now. In March 2026, Washington enacted additional legislation that partially rolls back ESSB 5814. Effective January 1, 2029, custom software, customization of prewritten software, and IT consulting, training, and support services will no longer be subject to retail sales tax, provided a court of final jurisdiction does not invalidate Washington's income tax before that date. That sunset provision does not reduce current obligations through 2028, but it is a relevant factor for companies making long-term decisions about contract structures, pricing, and system configurations tied to Washington compliance.
Washington's combination of broad DAS taxability, the expanded ESSB 5814 categories, progressive B&O rates, local destination-based sourcing, and aggressive audit enforcement makes it one of the highest-complexity digital tax environments in the country. The businesses managing it well are not the ones that know Washington's rules from memory. They are the ones that have built compliance infrastructure capable of applying those rules at the transaction level, automatically, every time.
Selling digital services into Washington? Your compliance clock is running. Between DAS taxability, ESSB 5814's expanded service categories, dual B&O and sales tax obligations, and local rates that swing up to 10.6% by address, Washington is one of the most complex digital tax environments in the country. CereTax handles Washington sales tax calculation at the transaction level, with real-time rate lookup, product classification logic, and the audit trail your team needs when the DOR comes calling.
👉🏻 Book a Strategy Call with CereTax to review your Washington digital services tax setup and identify potential exposure.
A customer says, “We are tax exempt.”
That sounds simple. The compliance process is not.
In a B2B transaction, a buyer may qualify for an exemption because it is purchasing goods for resale, qualifies as an exempt organization, or meets another exemption allowed under the applicable state's law. But a seller generally cannot treat every tax-free B2B purchase as automatically exempt.
The seller needs support for the decision.
That is where an exemption certificate comes in. It gives the seller documentation showing why sales tax was not collected on a transaction that might otherwise have been taxable. The exact requirements vary by state and exemption type.
For finance and tax teams, the real value of an exemption certificate is not the piece of paper itself. It is the evidence behind the tax decision.
An exemption certificate is a document provided by a purchaser to support a claim that a taxable purchase qualifies for an exemption.
The certificate typically identifies the purchaser, describes what is being purchased, and explains the basis for the exemption. Depending on the state and exemption, it may also require a tax or seller's permit number, the purchaser's address, a signature, and other information.
The important point is that there is no universal exemption certificate that works identically everywhere.
States can have different requirements for:
That creates a familiar problem for businesses selling across multiple states: the customer may be the same, but the documentation requirements can change.
Not exactly.
A resale certificate is one common type of documentation used to support a sales tax exemption. It generally applies when a business purchases taxable property for resale in the normal course of business.
For example, a retailer buying inventory from a wholesaler may provide a resale certificate instead of paying sales tax on the purchase. The retailer then generally collects and remits sales tax when it sells the goods to its customer.
The terminology varies by state, so businesses should always follow the rules applicable to the transaction rather than assuming one certificate works everywhere.
Receiving a certificate is not the same as validating it.
A seller should have enough information to determine that the certificate is relevant to the transaction and appears valid under the applicable rules.
For example, California requires a valid exemption certificate to include information such as the purchaser's name and address, seller's permit information or an explanation of why one is not required, a description of the property, the date, signature, and a statement explaining how the property will be used to qualify for the exemption.
For resale certificates, California also requires the purchaser to state that the property is being purchased for resale. Simply writing “tax exempt” or “nontaxable” is not enough.
That distinction matters because a certificate should support a specific tax position, not simply provide a reason to leave tax off an invoice.
The risk does not always sit with the seller.
If a purchaser knowingly uses a resale certificate to buy property it intends to use rather than resell, the purchaser can become responsible for the tax and potentially face penalties. California, for example, imposes liability and penalties for improper use of resale certificates.
For sellers, however, accepting an invalid or inappropriate certificate can create a different problem: the seller may not have adequate documentation to support why tax was not collected.
That is why “the customer gave us a certificate” is not a sufficient compliance control.
The better question is:
Did we receive the right certificate, for the right transaction, and can we prove it later?
Auditors often work backward from transactions where sales tax was not collected.
If the seller cannot demonstrate why the transaction was exempt, the sale can become difficult to defend.
A properly maintained certificate creates a clear link between:
Customer → Transaction → Exemption Reason → Supporting Documentation
That connection becomes particularly important as transaction volumes grow.
A company processing a few hundred exempt transactions may be able to manage certificates manually. A company processing tens of thousands of B2B transactions across multiple states has a very different problem.
Certificates can expire. Customer information can change. Different states can require different documentation. A single customer may also have several exemption reasons depending on what it purchases.
This is where exemption certificate management becomes a process rather than a filing task.
The goal should not simply be to collect certificates. It should be to make sure the certificate remains connected to the transactions it supports.
A practical exemption workflow should answer four questions:
Automation can help by routing certificates for review, flagging missing information, tracking expiration dates, and connecting approved exemption status to transaction processing.
That last step matters most.
If the certificate sits in one system while tax calculation happens in another, teams may still have to reconcile the two manually. That creates another opportunity for an approved exemption not to be applied correctly, or for an expired certificate to remain active.
No.
A sales tax holiday is a temporary state-authorized period during which qualifying products may be exempt from sales tax. An exemption certificate, by contrast, supports a specific purchaser's or transaction's eligibility for an exemption.
They solve different compliance problems.
A sales tax holiday generally changes the tax treatment of qualifying transactions during a defined period. An exemption certificate provides documentation for why tax was not collected on a particular transaction.
For businesses, keeping these concepts separate is important when designing tax rules and compliance workflows.
Exemption certificate management becomes harder when it is treated as paperwork rather than part of the tax process.
B2B sellers should establish clear rules for collecting certificates, validating them, tracking expiration dates, applying exemptions to transactions, and retaining supporting documentation. They should also review how those processes work across states, products, customers, and business units.
The objective is simple: when tax is not collected, the business should be able to explain exactly why.
That explanation should not depend on someone searching through an inbox or an old spreadsheet during an audit.
Ready to make exemption management less manual? Exemption certificates are supposed to reduce tax exposure, not create another compliance headache.
CereTax helps businesses connect exemption management with tax determination, so exemption decisions can be applied consistently while supporting a more audit-ready compliance process.
👉🏻 Book a Strategy Call with CereTax to see how smarter exemption management can reduce manual work and strengthen your sales tax controls.
For most SaaS companies, California has historically been one of the easier states to deal with from a sales tax perspective. Electronically delivered and remotely accessed software was generally not subject to California sales tax.
That changes on January 1, 2027.
SB 122, signed by Governor Gavin Newsom on June 29, 2026, brings qualifying prewritten software into California's sales and use tax system. That includes software delivered electronically and software customers access remotely, which puts many SaaS products directly in scope.
For software companies, this is not simply a matter of adding a tax rate to invoices.
You may need to revisit how your products are classified, where customer transactions are sourced, whether you need to register, how your billing system calculates tax, and how your contracts handle tax. If you invoice through Stripe, CereTax for Stripe Billing adds that calculation directly to your invoices.
The January 1 effective date also means there is a limited window to make these changes.
The basic rule is easier than it first sounds:
Prewritten computer software will generally be taxable regardless of how the customer receives or accesses it.
That includes software delivered on physical media, downloaded electronically, or accessed through the cloud.
For SaaS companies, the important question is whether the software is prewritten or custom.
Prewritten software is developed for general or repeated sale. Custom software is created specifically for one customer's requirements and remains exempt under the new rules.
A useful way to think about it is this:
If you sell substantially the same software to many customers, it is likely prewritten software. If you build software specifically for one customer, it may qualify as custom software.
Separately stated modifications to prewritten software can receive different treatment, so companies that sell both standard software and custom development should review how those charges appear on their invoices.
Not every digital product becomes taxable under SB 122. The law specifically excludes several categories, so companies should review their individual products rather than assuming every digital offering is now taxable.
Additional California guidance is also important for businesses with products that sit between these categories.
Once a SaaS transaction becomes taxable, the next question is:
SB 122 establishes an order for determining the customer's location for electronically delivered and remotely accessed software.
The starting point is generally the customer's billing address. If that information is unavailable or does not provide a California location, other addresses can be considered, including the shipping or delivery address and certain payment or mailing addresses.
Why does that matter? Because California has local district taxes in addition to its statewide rate. The total tax rate can therefore vary depending on where the transaction is sourced.
For a SaaS company with customers throughout California, this means using one California tax rate for every customer may not be enough.
This can become more complicated when one customer has offices, employees, or operations across multiple California locations.
A company might have one billing address but thousands of users spread across the state. How that transaction should be sourced in every situation is an area where additional guidance will be important.
For now, companies with large enterprise accounts should review the location information they maintain for customers and understand how that information feeds into their tax calculation process.
SB 122 also creates a special rule for certain large purchases.
When a customer purchases more than $5 million of qualifying digital products from a retailer during the applicable period, the customer may become responsible for paying the use tax directly rather than having the retailer collect it.
That means large SaaS providers need to know which customers could reach this threshold and understand what documentation is required.
A billing or tax system that only asks, "Is this customer in California?" may not be enough.
It may also need to answer, "How much taxable digital product has this customer purchased from us?"
California's existing economic nexus rules are another important piece of the change.
Once qualifying SaaS and prewritten software become taxable, those sales can count toward California's $500,000 economic nexus threshold.
For example, a SaaS company generating $600,000 in qualifying California sales may now have a California sales tax registration and collection obligation even though it previously did not collect tax on those software sales.
The important point is that the new law can change the answer to a question many SaaS companies have already asked:
"Do we have to collect California sales tax?"
Businesses should review both economic and physical nexus before January 1. A company with employees, contractors, property, or other physical connections to California may have obligations regardless of whether it meets the economic threshold.
If registration is required, companies should leave enough time for the registration process rather than waiting until the effective date.
Preparing for California's SaaS tax change is not one task. It is a series of connected decisions.
The easiest way to manage it is to work through them in order.
The sequence matters.
You cannot configure the right tax treatment until you know which products are taxable. You cannot source transactions correctly without reliable customer information. And you cannot communicate the right treatment to customers until you understand how the new rules affect their transactions.
SB 122 provides the framework, but some practical questions still need additional guidance.
Bundled offerings are one of the biggest issues for SaaS companies. A subscription may include software, implementation, professional services, support, or infrastructure. Businesses need to understand how California will treat these combinations, particularly when taxable and nontaxable components are sold together.
Services involving human effort are another area to watch. SaaS companies that combine automated software with consulting or other human-delivered services may need to determine how those components should be treated.
Contracts that cross January 1, 2027 also deserve attention. A prepaid annual subscription or multi-year agreement signed before the effective date may require a closer review to determine how the new tax applies to the portion of the contract occurring after January 1.
The practical approach is simple: make the decisions you can make today, document your assumptions, and revisit areas that depend on additional California guidance.
California's new SaaS tax is more than a new line on an invoice.
It can affect what you sell, how you classify it, where you source it, whether you need to register, how your billing system calculates tax, and what your customers see on their invoices.
That may sound like a lot. It is.
But breaking the work into manageable steps makes the transition much easier.
Start with your products. Then review nexus. Then sourcing, registration, billing, contracts, and customer communications.
The companies that start now will have time to test their systems and resolve the gray areas before the first taxable transaction hits.
California has set the date. January 1, 2027 is when the new rules begin. Your tax systems should be ready before then.
👉🏻 Book a Strategy Call with CereTax to assess your California SaaS tax readiness and prepare for the 2027 changes.
If your Connecticut tax configuration still uses last year's rules, it is time for an update.
Connecticut's annual Sales Tax Free Week runs for seven days, with qualifying clothing and footwear exempt from the state's 6.35% sales tax. But 2026 brings a major change: the per-item threshold has increased from $100 to $300.
That changes the treatment of a lot of products.
A $175 pair of sneakers that was taxable during last year's holiday can now qualify for the exemption. A $250 coat that previously exceeded the threshold can also qualify.
There is another change retailers need to know about. Beginning July 1, 2026, Connecticut introduced a permanent exemption for certain nonelectronic school supplies, including backpacks, notebooks, pens, pencils, crayons, rulers, and lunch boxes. That exemption is separate from Tax-Free Week and continues throughout the year.
So this year's sales tax holiday is not simply a repeat of 2025 with a new date. Retailers need to make sure their systems reflect both the higher threshold and the new permanent exemption.
The most important rule is simple:
A qualifying item priced below $300 is exempt. An item priced at exactly $300 is taxable.
There is no partial exemption. The entire price is either exempt or taxable.
The $300 limit also applies per item, not to the total transaction. A customer can purchase ten qualifying items, each priced below $300, and all ten can be exempt even if the total purchase is well above $300.
The higher threshold does not mean every product under $300 qualifies. Product type still matters.
One category deserves particular attention: athletic footwear.
Regular sneakers and athletic shoes can qualify when they are priced below $300. Football cleats, baseball spikes, soccer cleats, and similar footwear designed specifically for a sport remain taxable regardless of price.
In other words, a $150 pair of running shoes can be exempt while a $150 pair of soccer cleats is taxable.
That distinction needs to be reflected in your product classification.
Backpacks and certain nonelectronic school supplies have a different story.
Connecticut's permanent exemption took effect July 1, 2026, before Tax-Free Week begins. Items such as backpacks, notebooks, pens, pencils, crayons, and lunch boxes can therefore remain exempt outside the holiday as well.
During Tax-Free Week, some of these products can fall under both the permanent exemption and the holiday exemption.
For retailers, the practical takeaway is important: do not build the school supply exemption as a seven-day rule. If an item qualifies for the permanent exemption, your system should continue treating it as exempt after August 22.
Retailers should also monitor Connecticut DRS guidance for any additional clarification on how the two exemptions interact.
Yes.
The holiday applies to qualifying online purchases as well as in-store sales. For online orders, the key date is when the customer pays, not when the item is shipped or delivered.
For example, an eligible item purchased and paid for on August 20 can qualify even if it is delivered after August 22.
But an item delivered during Tax-Free Week does not qualify if the customer paid for it before the holiday started.
That means ecommerce retailers need the holiday rules active across the entire August 16 through August 22 window, not just over the weekend.
For footwear retailers, the threshold increase is particularly significant.
Under the previous $100 threshold, many mainstream sneakers and athletic shoes fell outside the holiday exemption simply because they cost more than $100.
That changes in 2026.
A large portion of footwear priced between $100 and $300 can now qualify. At the same time, sport-specific footwear such as cleats remains excluded.
That creates a product-classification challenge that retailers cannot solve with a simple price rule.
Your system needs to be able to distinguish between:
$150 everyday sneakers = exempt
$150 soccer cleats = taxable
Connecticut's 6.35% sales tax is statewide, and the state does not have local sales taxes. That removes some of the jurisdictional complexity retailers face in other states, but product-level classification still needs to be right.
The sales tax holiday applies to online sellers with Connecticut sales tax obligations too.
Connecticut's economic nexus rules require a remote seller to exceed both $100,000 in Connecticut gross receipts and 200 transactions during the applicable 12-month period.
If your business has Connecticut nexus, qualifying transactions during August 16 through August 22 need to receive the same holiday treatment as qualifying in-store transactions.
For remote sellers, that means checking three things before the sales tax holiday:
A configuration built around last year's $100 threshold can result in tax being charged on qualifying purchases between $100 and $299.99.
Connecticut's 2026 Tax-Free Week gives shoppers a bigger exemption, but it also gives retailers more rules to get right.
The threshold has increased from $100 to $300. Certain school supplies are now permanently exempt. Online purchases depend on payment timing. And products such as cleated footwear remain taxable regardless of price.
The safest approach is to test the rules against the products and transactions your business actually processes.
Do not wait until the first customer checks out. Review your product classifications, update the $300 threshold, confirm your school supply rules, test online transactions, and make sure excluded products remain taxable. CereTax helps retailers apply sales tax rules at the transaction level, including product-specific exemptions, price thresholds, and changing state requirements.
👉🏻 Book a Strategy Call with CereTax to pressure-test your Connecticut sales tax configuration before Tax-Free Week begins.
Illinois last ran a back-to-school sales tax holiday in 2022. For the four years between then and now, retailers selling clothing and school supplies in Illinois applied the standard combined state and local rate to every transaction. On June 16, 2026, Governor Pritzker signed Public Act 104-0468 as part of the FY27 budget package, reinstating the holiday with 52 days' notice before its August 7 start date.
That 52-day window is the compliance problem. A retailer that built its Illinois tax configuration once and has not revisited it since 2022 has a system calibrated for a world where no holiday exists. Reactivating the holiday requires more than turning on a switch. Illinois's holiday is not a zero-rate event. It is a reduced-rate event: the state's 6.25% portion drops to 1.25%, but every local tax imposed on top of the state rate remains in full effect. In Chicago, where the combined state and local rate is 10.25%, a qualifying item during the holiday is taxed at 5.25%, not zero. A billing system configured to apply zero tax to qualifying items is as wrong as one that applies full tax. The correct outcome is full local rate minus 5 percentage points of state reduction, calculated at the specific combined rate applicable to each customer's location.
The Illinois Department of Revenue published Informational Bulletin FY 2026-30 to govern retailer obligations during the holiday. Illinois also requires qualifying sales to be reported on a new form, Schedule K-12, filed alongside the standard Form ST-1. There is no equivalent form in any other state's holiday compliance, and retailers who do not know Schedule K-12 exists will file an incomplete August return.
The holiday covers two categories with different rules attached. Clothing and footwear must be priced at less than $125 per item at retail selling price. School supplies must be used by students in the course of study but carry no dollar cap. Within each category, the IDOR's FY 2026-30 bulletin provides explicit qualifying and nonqualifying item lists.
Three exclusions deserve specific attention for retailers who may assume they qualify. Computers and computer supplies are explicitly excluded, including printers, printer cartridges, flash drives, external drives, and computer cables. Unlike Massachusetts or Missouri, Illinois does not extend its holiday to computers. Art supplies including acrylic, tempera, and oil paints, paintbrushes, sketch pads, clay, and watercolors are excluded even though general school supplies qualify. And athletic footwear designed for specific activities, including cleated shoes, ballet shoes, tap shoes, roller skates, ice skates, ski boots, waders, and fins, is excluded even though general footwear under $125 qualifies.
Illinois's sales tax holiday is often misunderstood because it is not a tax-free event. Only the state portion of the sales tax is reduced, dropping from 6.25% to 1.25% on qualifying purchases. Every county, city, transit, and special district tax remains fully in effect.
That means there is no single holiday tax rate across Illinois. The correct rate depends on the combined state and local rate that applies at the customer's location.
For example, if the normal combined sales tax rate is 10.25%, qualifying purchases during the holiday are taxed at 5.25%. In locations where the combined rate is 6.50%, the holiday rate becomes 1.50%. Jurisdictions with no local taxes apply the minimum 1.25% rate.
Rather than applying a flat statewide percentage, retailers should calculate the reduced rate using the combined rate applicable to each transaction. This is especially important for businesses operating across multiple store locations or selling throughout Illinois.
The same principle applies to remote sellers with Illinois sales tax obligations. Holiday tax should be calculated using the customer's delivery address, since local rates vary by jurisdiction. A shipment to Chicago may require a different holiday rate than one delivered elsewhere in the state, making accurate address-level tax calculation essential.
Beyond qualifying products and reduced rates, Illinois also applies specific rules to common retail scenarios. These situations can easily result in incorrect tax collection if they are not handled properly.
One of the biggest changes in the 2026 holiday is the introduction of Schedule K-12, a reporting schedule that accompanies the standard Form ST-1 and, where applicable, Form ST-2. Retailers making qualifying holiday sales must include this schedule when filing their August return.
Rather than excluding qualifying sales from the return, retailers continue reporting taxable sales through the normal ST-1 process. Schedule K-12 is then used to calculate the credit for the reduced state tax that was not collected during the holiday. This approach preserves accurate sales reporting while ensuring the reduced state portion is reflected correctly.
Retailers who do not file Schedule K-12 are over-reporting their tax liability. Those who file it correctly receive the credit that reflects the state portion they were not permitted to collect during the holiday. Likewise, businesses that collected tax in error at the full rate during the holiday must remit that tax and file Form ST-1-X, Amended Sales and Use Tax Return, along with Schedule K-12, to claim the credit for amounts subsequently refunded to customers.
A successful Illinois sales tax holiday setup comes down to three configuration checks.
Apply the correct holiday rate. Tax logic should reduce only the state portion of the combined sales tax rate while leaving local taxes unchanged. Because local rates vary across Illinois, the correct holiday rate must be calculated for every transaction based on the customer's location.
Map products at the SKU level. Product eligibility is more nuanced than broad merchandise categories. Clothing generally qualifies, but specialized athletic footwear does not. School supplies qualify, while computers and art supplies remain taxable. Accurate SKU-level mapping is the most reliable way to avoid incorrect tax treatment.
Prepare your filing workflow. Businesses making qualifying holiday sales should ensure Schedule K-12 is incorporated into their August filing process so the reduced state tax is reported correctly and the appropriate credit is claimed.
Is your Illinois tax rate configuration ready for August 7? Illinois's holiday is not a zero-rate event. Every transaction involving a qualifying item needs the state portion reduced by exactly 5 percentage points, with local taxes left intact. That is a configuration that most billing systems require an explicit update to handle correctly. CereTax applies the reduced rate at the transaction level, handles the Schedule K-12 reporting, and keeps the local tax layer untouched throughout the ten-day window.
👉🏻 Book a Strategy Call with CereTax to see how CereTax automatically applies the correct reduced rate, keeps local taxes intact, and simplifies holiday reporting.
Most back-to-school sales tax holidays cap exemptions at $100 per clothing item and $50 per school supply. A parent saving $6.25 on a $100 backpack is a nice benefit. A family buying a $2,200 laptop, a $1,800 refrigerator, and $2,400 worth of furniture in a single weekend is saving over $400 in state sales tax on purchases they were already planning to make.
That is the financial reality behind the Massachusetts 2026 Sales Tax Holiday, which runs Saturday August 8 and Sunday August 9. The $2,500 per-item cap set by Massachusetts under 830 CMR 64H.1.8 is the highest in any state running a holiday this summer, and unlike most back-to-school states that restrict qualifying items to clothing and school supplies, Massachusetts exempts most tangible personal property. That means electronics, appliances, furniture, sporting goods, home improvement items, and computers all qualify as long as the individual item is priced at $2,500 or less.
For retailers in these categories, the holiday is not just a marketing event. It is a mandatory compliance event. The Massachusetts Department of Revenue makes clear that all businesses that normally make taxable sales of tangible personal property in Massachusetts and are open during the holiday dates must participate. There is no opt-out. A retailer that continues collecting the 6.25% state tax on qualifying items during the window is over-collecting, and the DOR requires that any tax erroneously collected must be remitted to the DOR and refunded to the customer.
The per-item cap is the most operationally important rule in the Massachusetts holiday and the one most commonly misapplied in high-volume retail environments. The $2,500 limit applies to each individual item, not to the transaction total. A customer can purchase 10 qualifying items each priced under $2,500 in a single transaction and pay zero tax on all of them, even if the total exceeds $25,000. There is no transaction-level cap. There is only an item-level cap.
The flip side is equally important. If a single item is priced at more than $2,500, the entire purchase price of that item is taxable, not just the amount above the threshold. A $2,600 laptop carries the full 6.25% tax on $2,600, not just on the $100 that exceeds the cap. Retailers selling high-ticket items need their systems to evaluate each line item independently against the $2,500 threshold, apply zero tax if the item falls at or below the cap, and apply full tax if the item exceeds it. A system that evaluates the transaction total rather than individual items will produce wrong results in both directions.
Clothing in Massachusetts has an additional layer because of the state's permanent clothing exemption. Massachusetts permanently exempts the first $175 of each clothing item from sales tax even outside the holiday. During the holiday, if a clothing item is priced at $2,500 or less, the entire price is exempt. If a clothing item exceeds $2,500, only the first $175 is permanently exempt, and the rest is taxable during and outside the holiday. A $2,800 coat is taxable on $2,625 during the holiday, not on the full $2,800.
The Massachusetts holiday covers most retail items of tangible personal property priced at $2,500 or less purchased for personal use. The qualifier on personal use is the boundary that most compliance configurations miss. Purchases by corporations or other businesses and purchases by individuals for business use remain fully taxable during the holiday regardless of the item's price. A sole proprietor buying a $1,500 laptop for their freelance work owes the full 6.25%. The same person buying the same laptop for their college student pays zero.
Massachusetts confirms on its official FAQ page that online purchases qualify for the holiday exemption if the order is placed and paid for during the weekend in Eastern Daylight Time. Delivery after August 9 does not affect eligibility. The operative date is the transaction date, not the delivery date.
For ecommerce retailers with Massachusetts customers, this creates two specific configuration requirements. First, the billing system needs to apply the zero-rate exemption to Massachusetts transactions during the August 8-9 window based on when the order is placed, not when it ships. Second, the system needs to evaluate each line item in the cart against the $2,500 threshold independently. A cart containing a $1,800 monitor and a $2,800 desktop computer should apply zero tax to the monitor and full tax to the desktop. A system that applies a blanket holiday exemption to the full cart without item-level price checks is applying the rules incorrectly.
The DOR also confirms that if a retailer erroneously collects sales tax on a qualifying item during the holiday, any tax collected in error must still be remitted to the DOR. The retailer must refund the customer. If the tax has already been remitted, the retailer can file an amended August Sales and Use Tax Return to recover the refunded amounts. This creates an administrative burden that is entirely avoidable with correct pre-holiday configuration.
Three transaction types produce compliance questions that the Massachusetts DOR FAQ addresses specifically, and each has a rule that differs from what most retailers assume.
The Massachusetts DOR specifies exactly how holiday-period sales appear on the August Sales and Use Tax Return. Retailers report the sales amount of items not charged tax during the two-day holiday on Line 2 of the return, labeled Exempt Sales. This is a standard line used for all exempt sales and is not a special holiday-only reporting mechanism. The correct reporting separates the exempt holiday sales from taxable sales within the same August filing period, since the holiday covers only two days within the month.
For retailers with high-volume Massachusetts operations, particularly those in electronics, appliances, and furniture, the holiday weekend often represents a disproportionately large share of August revenue. Accurate Line 2 reporting requires that transaction records from the holiday weekend are tagged with the correct exempt status so they can be pulled cleanly into the return without manual reconciliation. A billing system that did not tag transactions correctly during the weekend will require manual review of every August 8 and 9 transaction before the return is filed.
Participation is mandatory, the $2,500 cap is per-item not per-transaction, online orders qualify by payment date not delivery date, layaway is excluded, and erroneously collected tax creates both a refund obligation and an amended return requirement. Every one of these rules is operational, not theoretical, and each one affects how the billing system needs to behave during a 48-hour window starting at midnight on August 8.
Is your Massachusetts tax configuration ready for August 8 and 9? The Massachusetts holiday requires mandatory participation. Retailers who collect the 6.25% state tax on qualifying items during the window have over-collected and face an obligation to refund and amend. CereTax configures the exemption correctly at the transaction level, flags the nine excluded categories automatically, and keeps your August return reporting ready from the first transaction.
Most back-to-school sales tax holidays cover clothing, school supplies, and sometimes technology. Oklahoma does not. Per the Oklahoma Tax Commission, the state's annual holiday exempts only articles of clothing and footwear designed to be worn on or about the human body, priced under $100 per item, from state and local sales tax. School supplies are explicitly excluded. Notebooks, pencils, pens, scissors, binders, and every other classroom essential remain fully taxable throughout the three-day window.
That narrow scope is precisely what creates the compliance problem. A tax system configured with a broad back-to-school holiday exemption applies the wrong treatment to half the items in a typical back-to-school cart in Oklahoma. The backpack qualifies. The composition notebook does not. The $85 sneakers qualify. The football cleats do not. A system that cannot draw those lines at the SKU level is either undertaxing taxable items or overtaxing exempt ones, and in a high-volume three-day window, both errors compound fast.
Since 2007, Oklahoma has run this holiday annually on the first Friday through Sunday in August. The 2026 window is August 7 through 9. The 4.5% state sales tax and all applicable local and municipal taxes are suspended on qualifying items during the period.
The table below is the full compliance reference. Each item is evaluated independently against the $100 threshold. There is no transaction-level cap.
The footwear distinction is the most operationally difficult item in this table. A shoe department may carry both qualifying casual sneakers and non-qualifying cleated athletic shoes at similar price points. The difference in tax treatment is determined by the shoe's intended use, not its price or brand. A $75 casual running shoe worn as everyday footwear qualifies. A $75 pair of baseball spikes does not. Both need separate product tax codes configured before the holiday opens.
Two distinctions worth noting for retailers. On discounts: a store promotion that brings a $105 item down to $95 makes that item eligible for the exemption because the final selling price, not the original price, determines qualification. On manufacturer coupons: because the retailer is reimbursed by the manufacturer, the selling price is not considered reduced for tax purposes, and the original price governs the threshold calculation.
Oklahoma's sales tax holiday does not require complex multi-category logic. It requires precise binary logic at the SKU level: does this specific item fall within the statutory definition of clothing or footwear, and is its price under $100. Two conditions, both must be true. School supplies fail the first condition and are taxable throughout. Athletic footwear designed for sport-specific use fails the first condition by exclusion and is taxable throughout. Accessories fail the first condition and are taxable throughout.
A system applying a category-level exemption to anything labeled "back to school" or "apparel" will catch the easy cases and miss the hard ones. The hard ones, cleats vs. sneakers, backpack vs. notebook, are exactly the items most commonly purchased together in August by Oklahoma families.
For multi-state retailers running back-to-school configurations across Oklahoma, Texas, Florida, and other participating states simultaneously, the Oklahoma configuration is the most restrictive and the most likely to be overapplied. Texas exempts school supplies under $100. Florida exempts school supplies under $50. A system that inherits those broader configurations and applies them to Oklahoma transactions will exempt items in Oklahoma that are explicitly taxable there.
Ready to get Oklahoma right before August 7? CereTax handles sales tax holiday configuration at the SKU level, with state-specific exemption logic that distinguishes qualifying clothing from excluded accessories, casual footwear from athletic footwear, and correctly applies taxability to school supplies that remain fully taxable in Oklahoma while exempt in neighboring states running simultaneous holidays.
If your current setup applies a broad back-to-school exemption without drawing the lines Oklahoma's holiday requires, it is misconfiguring the event before the first transaction.
👉🏻 Book a Strategy Call with CereTax team and see how we handle sales tax holidays end to end.
A 32-day zero-rate exemption window touching four product categories, suspending state and local tax simultaneously across every Florida county, is not a passive event for retailers. Under Florida law, dealer participation is mandatory. A dealer that charges sales tax on a qualifying transaction during the holiday is out of compliance with FDOR requirements, full stop.
The holiday was also codified as a permanent annual event under HB 7031E, passed by the Florida Legislature in June 2026, which means it is now a fixed item on every retailer's annual compliance calendar. The 2026 dates shifted from last year's August-only window to July 20 through August 20 to better align with school year start dates across Florida districts. Any system configured for prior year dates needs to be updated before July 20.
Each item is evaluated independently against its category threshold. There is no transaction-level cap and no blended treatment across the cart.
One rule worth flagging on computers: keyboards, mice, monitors, and other accessories are exempt individually, even when purchased without a computer base unit, as long as each item is at or below $1,500 and is for noncommercial home use.
The commercial use exclusion. The computer exemption is limited to noncommercial home or personal use. A $1,200 laptop sold to a consumer is exempt. The same laptop sold to a business is fully taxable at the standard rate during the same window. Most billing systems do not carry a customer use-type flag at the transaction level. Without one, the system applies the same treatment to both buyers and gets one of them wrong. Retailers selling technology products need a mechanism to capture buyer use type at checkout before the holiday opens.
Mixed carts. Consider a cart with a $95 backpack (exempt), a $45 pack of pencils (exempt), and a $110 handbag (taxable, over the $100 cap). A system applying basket-level exemption logic exempts the entire cart. A system taxing the whole cart over-collects on two qualifying items. The FDOR requires each item to be evaluated independently. Line-item tax logic is not optional here.
The county surtax. The holiday suspends both the state 6% rate and all county discretionary surtaxes on qualifying purchases. Florida counties levy surtaxes ranging from 0.5% to 1.5%. Tax engines applying state and local rates as separate calculations must suppress both layers on qualifying items, not only the state rate. A system that drops the 6% but continues applying the county surtax is over-collecting on every qualifying transaction in every county.
The transaction date governs online sales, not the delivery date. Retailers with deferred billing or installment options on computer purchases should confirm how their platform timestamps the acceptance event, because that timestamp determines exemption eligibility.
Ready to get Florida right before July 20? If your Florida tax configuration was last reviewed before July 20, it may be applying state and county tax to transactions that should be zero-rated right now. CereTax handles item-level exemption logic, suppresses both state and local rates on qualifying transactions, and applies the commercial use exclusion on computer purchases without manual override.
👉 Book a strategy call with the CereTax team and see how we handle sales tax holidays end to end.
Sales tax holidays in 2026 create short-term exemptions—but the operational lift behind them is anything but temporary. Eligibility thresholds, product categories, and local participation rules vary widely by state, increasing the risk of misclassification and missed exemptions.
This state-by-state snapshot captures confirmed and anticipated programs as of July 2026, helping tax and finance teams plan configurations, validate product mappings, and prepare for upcoming exemption windows.
Sales tax holidays are high-volume, high-risk events—where small configuration gaps can quickly turn into audit exposure or margin leakage. Staying ahead requires more than tracking dates; it demands accurate product taxability, jurisdiction-level awareness, and timely system updates.
Verify eligibility on state revenue websites before applying, and bookmark this guide for updates as legislative sessions finalize remaining programs.
Ready to pressure-test your sales tax holiday readiness?
If multiple states on this list are relevant to your business, it may be time to validate whether your tax setup can handle shifting thresholds, product rules, and local variations.
👉🏻 Talk to a CereTax Specialist
Prefer a practical reference instead?
👉🏻 Download the 2026 Sales Tax Holidays Guide for a state-by-state breakdown of holiday dates, qualifying purchases, exemption thresholds, and retailer compliance rules—all in one easy-to-use resource.
Economic nexus changed sales tax compliance permanently.
After South Dakota v. Wayfair, businesses no longer needed physical presence to trigger sales tax obligations in many states. Revenue thresholds, transaction counts, marketplace activity, remote employees, fulfillment relationships, and digital sales footprints all became part of the nexus conversation.
For finance teams, the challenge was never simply understanding the rules. It was operationalizing them across a business that keeps changing.
New states are entered quietly. Revenue scales gradually. Products evolve. Marketplace channels expand. Thresholds are crossed incrementally rather than dramatically.
That creates a dangerous dynamic.
Many companies can identify where nexus exists today. Far fewer can clearly explain how they reached those conclusions historically.
And during audit, that distinction matters.
Auditors increasingly expect businesses to demonstrate not just compliance outcomes, but the decision-making process behind them. If nexus determinations are undocumented, inconsistent, or dependent on tribal knowledge, even reasonable conclusions become difficult to defend.
The strongest nexus strategy is not simply accurate analysis. It is defensible documentation.
Most businesses treat nexus analysis as a registration exercise.
Auditors do not.
From an audit perspective, nexus determinations are evidence of governance discipline. States increasingly expect businesses to show:
This becomes especially important because nexus rules continue evolving across jurisdictions. Economic thresholds differ. Marketplace facilitator rules vary. State interpretations shift.
A company may ultimately reach a reasonable conclusion but still struggle during audit if it cannot demonstrate how that conclusion was reached operationally.
Documentation is what separates a deliberate compliance process from a reactive explanation assembled after exposure surfaces.
One of the most common mistakes businesses make is assuming nexus documentation means saving registration confirmations or filing records.
Those documents matter, but they are not the core of audit defense.
The stronger approach is documenting the nexus determination process itself.
That typically includes:
The objective is not merely retaining records. It is preserving the operational reasoning behind the compliance posture.
Because during audit, the historical reasoning often matters as much as the outcome.
Many businesses focus heavily on threshold monitoring software.
That is useful, but incomplete.
Threshold tracking identifies potential nexus triggers. It does not fully document how the company evaluated the resulting obligation.
For example:
Did marketplace sales count toward thresholds in that state at the time?
Were exempt sales included or excluded appropriately?
Did the business evaluate physical presence exposure separately?
Was the threshold exceeded temporarily or consistently?
Did the company reasonably anticipate future nexus before formal registration?
These judgment calls become increasingly important during audit reviews.
A spreadsheet showing revenue by state may support awareness. It does not independently demonstrate governance.
The audit issue is rarely whether the company had data. It is whether the company had a documented process for interpreting and acting on that data.
Nexus exposure compounds quietly because business growth rarely follows clean compliance milestones.
Revenue enters new jurisdictions gradually. Marketplace relationships expand over time. Remote hiring introduces physical presence unexpectedly. Product lines evolve in ways that change taxability.
Without documented review cycles, companies often attempt to reconstruct nexus timelines years later during audit.
That creates several problems simultaneously:
At that point, even technically reasonable compliance decisions become difficult to substantiate confidently.
Documentation reduces the need for reconstruction because the decision trail already exists.
Auditors increasingly evaluate nexus governance operationally rather than transactionally.
They want to understand whether the company had a systematic process for identifying obligations and responding consistently.
Common audit questions include:
How often were nexus reviews performed?
Who owned the process internally?
What systems were used to track thresholds?
How were marketplace sales treated?
Were nexus conclusions reviewed by advisors or internal tax leadership?
What controls existed to identify new state exposure?
This is why mature nexus governance increasingly resembles internal controls documentation rather than informal compliance monitoring.
The stronger the process documentation, the more defensible the compliance posture becomes.
Nexus determinations are rarely controlled entirely within tax teams.
Finance, ecommerce, operations, HR, marketplace teams, and IT functions all influence nexus exposure indirectly.
A remote employee hired without tax review may create physical presence nexus.
A new fulfillment arrangement may trigger inventory exposure.
A marketplace expansion strategy may alter threshold calculations.
If nexus governance exists only as a tax department exercise, operational changes may outpace compliance visibility.
The strongest businesses formalize nexus review processes across departments rather than treating nexus as a downstream filing issue.
Documentation becomes more reliable when operational ownership is clearly defined.
The businesses that manage nexus exposure most effectively usually implement several core practices consistently.
Most importantly, preserve the rationale behind decisions while they are being made rather than attempting to recreate them later.
Audit defensibility improves dramatically when documentation is contemporaneous rather than retrospective.
Nexus compliance is no longer just about determining where obligations exist.
It is about proving how those determinations were made over time.
As states continue expanding enforcement and refining economic nexus rules, undocumented assumptions become increasingly difficult to defend. The businesses that manage audits successfully are rarely the ones with perfect compliance histories.
They are the ones that can demonstrate a structured, well-documented process for evaluating nexus consistently as the business evolved.
Good nexus documentation does not eliminate exposure.
But it dramatically improves the ability to defend decisions before exposure becomes a larger operational problem.
Could your business clearly defend how and when nexus decisions were made if an audit began tomorrow? CereTax helps finance and tax teams build defensible nexus governance through automated threshold tracking, jurisdictional visibility, and audit-ready documentation workflows.
👉🏻 Book a Strategy Call with CereTax to evaluate whether your nexus determination process is truly built for audit readiness.
Sales tax holidays feel like a consumer story. Families save on back-to-school essentials, retailers see a lift in traffic, and everyone benefits. For the tax team and the billing stack behind those transactions, a sales tax holiday is a short, high-volume window where a single misconfigured product code generates a stream of incorrectly taxed transactions that have to be cleaned up after the fact.
Approximately 25 states will hold one or more tax holidays in 2026, and remote sellers must ensure proper configuration of product codes and checkout logic to apply exemptions correctly for each one. West Virginia is among those states, and its 2026 holiday carries specific price thresholds and eligibility rules that retailers need to have correctly loaded before the window opens.
The compliance question is not whether the holiday applies to your products. It is whether your tax engine knows which SKUs qualify, at which price points, and under which conditions, before the first transaction of July 31 is processed.
West Virginia's annual back-to-school sales tax holiday runs from Friday, July 31 through Monday, August 3, allowing families to avoid sales and use tax on certain purchases ahead of the new school year.
The qualification is determined at the individual item level, not the transaction total. There is no limit on the amount of the total purchase. Each item is evaluated independently against its applicable price threshold.
A single transaction containing both qualifying and non-qualifying items must apply the exemption to each qualifying item separately, not to a blended portion of the total. Certain clothing-adjacent items remain taxable throughout the holiday regardless of price, including jewelry, handbags, briefcases, hair accessories, cosmetics, costume masks, and sewing equipment. Items purchased for use in a trade or business are also explicitly excluded and taxable at the standard rate.
This is where most multi-channel retailers make mistakes. The rules for online orders are specific and timing-dependent. The controlling factor is when the order is placed and paid, not when it is delivered.
Out-of-state consumers purchasing from West Virginia retailers online are not eligible because the exemption follows the destination of the sale, not where the retailer is located. A West Virginia-based retailer shipping to a Pennsylvania address does not extend the WV holiday exemption to that transaction.
Retailers with split payment flows, deferred billing, or installment options on qualifying items need to evaluate how their checkout architecture handles the timestamp on payment acceptance. That timestamp determines exemption eligibility, and a mismatch between authorization and settlement timing can disqualify otherwise eligible transactions.
The practical compliance checklist for any retailer selling into West Virginia during the holiday window covers three areas.
Product code classification. Every SKU in the qualifying categories needs a product tax code that reflects the 2026 thresholds in the table above. That mapping needs to be in the tax engine before the first transaction, not patched in after the holiday opens.
Item-level vs. transaction-level logic. The holiday exemption applies per item, not per order. A tax engine that evaluates the cart total against a threshold rather than each line item independently will misapply the exemption on any mixed transaction. This is a configuration check, not an assumption to carry forward from last year.
Online order payment timing. Confirm how your payment processor timestamps the acceptance event and whether that timestamp is what the tax engine reads when evaluating holiday eligibility. If your platform captures authorization at checkout but settles payment after the holiday window closes, exemption eligibility may not apply.
West Virginia is one event in a wider compliance calendar. The table below covers states with confirmed 2026 back-to-school or general sales tax holidays most relevant to multi-state retailers, along with dates and primary qualifying categories.
Rules, dates, and qualifying categories are subject to change. Always verify against the state's official tax authority guidance before configuring your system.
The rules for sales tax holidays are also shifting in 2026. Some states have eliminated holidays to address budget shortfalls. Others are expanding their tax-free windows. Ohio reversed a previously approved expansion and reverted to its traditional three-day format. A tax engine that relies on manual updates for each state's holiday creates a configuration backlog that compounds across the summer filing calendar. The retailers with clean compliance records are the ones whose systems update exemptions automatically as state rules change.
Ready to handle sales tax holidays without the manual work? CereTax keeps your tax configuration current across every state and every exemption window, including sales tax holidays. Our engine applies item-level exemption logic, validates price thresholds against current state rules, and handles online order timing rules without manual intervention.
If your team is still updating product codes manually before each state's tax-free weekend, or if you are not certain your 2026 West Virginia thresholds are correctly loaded for the July 31 opening, it is time for a different conversation.
👉🏻 Book a strategy call with the CereTax team and see how we handle sales tax holidays and exemption management end to end.
Most businesses receiving a sales tax audit notice assume the process ends with a number they either pay or dispute in court. The reality is more nuanced, and more navigable, than that. A sales tax assessment is a constructed document. It is built from records the auditor could access, projected using methodology the auditor chose, and subject to challenge at multiple points before it becomes legally binding. The businesses that pay the smallest assessments are not always the ones with the cleanest compliance history. They are the ones that understood which parts of the process were contestable and acted at the right moments.
In 2026, state revenue agencies are auditing more aggressively than at any point since the post-Wayfair registration wave of 2019 to 2022. States that spent several years onboarding newly registered remote sellers are now cycling back through those registrants to verify that collection has been accurate. High-volume SaaS companies, ecommerce sellers, and multi-state service providers are disproportionately represented in current audit activity, and the audit periods being reviewed now frequently cover 2022 through 2024, when pricing models and product catalogs were expanding fastest and tax infrastructure was often not keeping pace.
An assessment begins before the auditor issues a single findings document. The first stage is scoping: the state issues an audit appointment letter identifying the audit period, the issues under review, and an initial Information Document Request (IDR). The IDR is effectively the auditor's shopping list, and what you provide in response, and how it is organized, shapes every calculation that follows.
For most businesses with meaningful transaction volume, auditors do not review every transaction. They select a sample period, commonly one to three months drawn from within the audit window, examine those transactions in detail, and then project the error rate from that sample across the entire audit period. This is where assessments can become dramatically disconnected from reality. If the sample period happens to include an unusually large exempt transaction that lacks complete documentation, or a period before a billing system upgrade that solved a systematic error, the projected error rate across four years can produce a number several times larger than actual noncompliance.
The look-back period itself varies by state and by circumstance. Most states audit back three years from the due date of the return. Ohio allows four years. Washington routinely covers four years plus the current period. If returns were not filed, or if fraud is alleged, many states have no statutory look-back limit at all. A business that did not register in a state until 2023 but had nexus from 2020 onward is exposed on the unregistered period without the protection of a standard limitations period.
The most important thing to understand about a sales tax assessment is that it has two forms: preliminary and final. The preliminary assessment is negotiable. The final assessment, once issued as a Notice of Determination or its equivalent in each state, carries a hard deadline, typically 30 to 60 days, to file a formal petition for redetermination or appeal. Missing that deadline is not a paperwork problem. It is the legal event that converts a negotiable estimate into an enforceable obligation.
Challenges to sampling methodology represent the highest-value intervention point in most audits. If the auditor selected a sample period that included anomalous transactions, a one-time large sale, a period of system transition, or a customer type not representative of your broader book of business, you can request that those transactions be assessed separately rather than folded into the projected error rate. Texas explicitly provides taxpayers the right to request reconciliation conferences and independent review conferences after the exit conference if disagreements remain. California's 30-day petition window after the Notice of Determination applies even if you intend to dispute only a portion of the assessment.
Exemption certificates are the second major challenge category. Auditors routinely flag transactions where the certificate on file has expired, contains an error, or was issued in a state-specific format the auditor does not recognize. In many states, you have the opportunity to produce corrected or supplementary documentation after the preliminary findings are issued. Certificates obtained after the fact, or corrected versions of flawed certificates, can remove flagged transactions from the taxable base before the final assessment is calculated. This window closes once the Notice of Determination is issued.
The third intervention point is vendor verification. If a customer self-assessed and paid use tax on the same transaction your auditor is flagging as untaxed, sales tax generally cannot be assessed again on the same transaction. Verifying whether customers paid use tax independently, and documenting it, can eliminate double-counting in the assessment.
A final assessment is not the end of the road. Every state with a sales tax provides formal appeal rights, and most offer at least two levels: an administrative appeal filed with the issuing agency, and a judicial appeal filed with the state's tax court or general court system. Administrative appeals are generally faster, lower-cost, and decided by people with subject matter expertise in the state's tax code. Judicial appeals are appropriate when the legal question at issue goes beyond the auditor's findings into statutory interpretation or constitutional questions.
The appeal timeline is the variable that catches businesses off guard. Most states require that an administrative appeal be filed within 30 to 90 days of the final assessment notice. Texas requires a written Statement of Grounds identifying disputed items. California requires a Petition for Redetermination within 30 days of the Notice of Determination. Filing on a preliminary basis, even before you have fully documented every dispute, is better than missing the deadline entirely. You can supplement the record after filing; you cannot reinstate appeal rights after the window closes.
Penalty waiver requests are a parallel track that operates independently of the appeal process in most states. Penalties can reach 25 to 40% of the tax due, and many states will consider waiving them for first-time audit situations, good-faith compliance efforts, or circumstances where the taxpayer demonstrated reasonable cause for the discrepancy. These requests are generally handled administratively and do not require a formal appeal to be pending.
The structure of a sales tax audit, its reliance on sampling, its sensitivity to documentation gaps, and its tight appeal windows, points toward a single practical conclusion: the actions that matter most happen years before the audit notice arrives. A business with transaction-level audit trails, current and complete exemption certificates, reconciled returns, and documented taxability decisions is not just better positioned to defend itself. It is genuinely less likely to be assessed at all, because auditors working from clean, well-organized records find fewer anomalies to project.
The businesses most vulnerable to inflated assessments are not necessarily the ones with the worst compliance. They are the ones whose compliance was inconsistent or undocumented, giving an auditor's sampling methodology the gaps it needs to extrapolate a small error into a large liability. Building the documentation infrastructure that closes those gaps is the most cost-effective audit defense strategy available, and it is the only one that works before the notice arrives.
Do not wait for a notice to find out where you stand. The businesses with the smallest audit assessments are not the ones with perfect records. They are the ones whose records were organized, reconciled, and audit-ready before the auditor arrived. CereTax builds that infrastructure for you, with transaction-level audit trails, exemption certificate management, and compliance monitoring across every state you operate in.
Most businesses discover their Texas sales tax obligation one of two ways: they receive a letter from the Texas Comptroller, or their accountant surfaces it during a nexus review. Neither is a good way to find out. Texas is the second-largest economy in the United States, and its sales tax enforcement has intensified significantly since the Wayfair decision opened the door to economic nexus rules in 2018. Remote sellers, SaaS companies, manufacturers, and ecommerce businesses selling into Texas are all operating under rules that are more nuanced than a single threshold number suggests.
The $500,000 economic nexus threshold is real, and it is among the highest in the country at a time when most states sit at $100,000. But what counts toward that threshold, when your obligation begins after crossing it, and how physical presence rules apply entirely independently of revenue are questions that create serious compliance gaps for businesses that only read the headline number.
Once nexus is established, the downstream obligations: calculating local tax correctly, preparing your return, hitting the right filing deadline, and recovering overpayments are each their own layer of complexity. This article focuses on nexus: how it is created in Texas, what triggers it, and what to do when it is already overdue.
Nexus is the legal connection between your business and Texas that creates a sales tax collection obligation. Before the U.S. Supreme Court's 2018 decision in South Dakota v. Wayfair, Inc., Texas could only require businesses with a physical presence in the state to collect and remit sales tax. Wayfair changed that, allowing states to impose obligations on sellers based purely on economic activity. Texas enacted its economic nexus rule effective October 1, 2019.
Once nexus is established, the obligations follow in sequence: register for a Texas sales tax permit, collect the correct state and local tax on all taxable sales shipped into Texas, file returns on the schedule the Comptroller assigns, and remit what was collected. The Comptroller conducts regular audits and has intensified its pursuit of online sellers and remote businesses across every major industry since Wayfair.
Texas establishes economic nexus when a remote seller's total Texas gross revenue exceeds $500,000 during the preceding 12 calendar months. Three features of this rule catch businesses off guard consistently.
The measurement period is rolling, not calendar-year. Texas does not reset the clock on January 1. The Comptroller evaluates the trailing 12 months at any point in time. A business that crosses $500,000 in June needs to act in June, not wait until year-end.
The threshold is exceptionally inclusive. Gross revenue for threshold purposes includes taxable sales, nontaxable sales, exempt sales, sales for resale, and marketplace sales, even when a marketplace facilitator collects and remits the tax on the seller's behalf. This is the detail that most surprises growing businesses. A company with $300,000 in direct Texas sales and $250,000 in Amazon marketplace sales has crossed the threshold, even though Amazon handled the tax on the marketplace portion. The registration obligation still applies to the direct-sales channel.
The registration deadline is not immediate. Once a remote seller exceeds $500,000, the Comptroller requires the business to obtain a permit and begin collecting tax no later than the first day of the fourth month after the month the threshold was exceeded. If a business crosses the threshold in May 2026, collection must begin by September 1, 2026. This grace period is not an excuse to wait. Permit applications, system configuration, and local rate setup each take time, and businesses that delay frequently miss the deadline regardless.
This is where most businesses undercount their Texas exposure. The threshold is not limited to taxable retail sales. Texas counts all of the following toward the $500,000 calculation: taxable sales, nontaxable sales, tax-exempt sales, sales for resale under a resale certificate, sales to exempt organizations including nonprofits and government entities, marketplace sales even when the facilitator collects the tax, and separately stated charges such as handling fees, transportation, and installation.
The practical implication is significant. A business with a primarily exempt or wholesale customer base in Texas may have crossed the threshold without ever collecting a dollar of sales tax from a Texas customer. The registration obligation does not wait for taxable revenue alone.
Physical nexus operates on an entirely different standard from economic nexus. There is no revenue threshold. Any qualifying physical presence creates an immediate collection obligation from the first taxable dollar sold into Texas, regardless of total revenue.
The Texas Comptroller defines physical presence broadly under 34 Texas Administrative Code Section 3.586. A business has physical nexus if it maintains an office, store, warehouse, distribution center, or any place of business in Texas. It also has physical nexus if it has employees, representatives, contractors, or agents operating in the state, including remote employees working from home offices anywhere in Texas. A single sales representative based in Houston creates statewide nexus for the entire business.
Several physical nexus triggers catch remote sellers by surprise in practice. Inventory stored in a Texas fulfillment center, including merchandise in Amazon FBA warehouses located in Texas, creates physical nexus regardless of whether the seller chose or even knew about the storage location. The Comptroller has pursued FBA sellers who were unaware their inventory had been routed to a Texas facility. Attending trade shows, conventions, or events in Texas, even for a single day, can also create physical nexus, and the Comptroller has initiated enforcement against out-of-state businesses discovered at Texas events without a permit.
Yes, under certain conditions, and this is one of the least-understood nexus triggers in the state.
Texas does not have a formal click-through nexus statute of the kind enacted by many other states. But the physical nexus rules under Section 3.586(d)(5) effectively capture many of the same relationships. Under that provision, an out-of-state business can establish physical nexus by having employees or representatives doing business in Texas on its behalf. Texas-based affiliates and influencers who actively promote and solicit sales for an out-of-state seller can qualify as representatives when their activity is sufficiently tied to the business's Texas sales operation.
The same provision extends to training, seminars, or lectures conducted in Texas by or on behalf of the business. If affiliates conduct promotional events or demonstrations in Texas as part of their arrangement with an out-of-state seller, the nexus analysis applies. Businesses that rely on in-state affiliate networks for Texas revenue need to evaluate this before an auditor does it for them.
Texas requires marketplace facilitators that have Texas nexus to collect and remit sales and use tax on all sales made through their platform, including sales by third-party sellers. When a marketplace certifies in writing that it is collecting and remitting Texas tax on the seller's behalf, the seller generally does not need a separate Texas permit for those marketplace sales.
But two complications apply. First, marketplace sales still count toward the seller's $500,000 threshold for purposes of determining economic nexus on direct sales. A seller with only marketplace sales and no direct Texas storefront may have no registration requirement, but as soon as any direct sales exist alongside the marketplace channel, the entire revenue base is counted. Second, marketplace providers themselves must use destination-based sourcing for all sales, not the Single Local Use Tax Rate option available to remote sellers. This creates different compliance workflows for sellers operating across both channels.
Register for a Texas Sales and Use Tax Permit through the Texas Comptroller's eSystems portal before the collection deadline. Registration is free, though the Comptroller may require a security bond for certain businesses. The application requires basic business entity information, a Federal Employer Identification Number, estimated annual Texas sales, and details about business activities in the state.
After registration, the Comptroller assigns a filing frequency based on estimated tax volume. The specific filing deadlines, payment method requirements, TEXNET rules, and the discount structure for timely filers are all covered in detail in How to Find Your Texas Sales Tax Return Due Date. For return preparation and reconciliation, see How to Prepare Your Texas Sales Tax Return.
Businesses that discover a missed Texas nexus obligation have a meaningful option before the Comptroller finds them first. Texas participates in voluntary disclosure, a process that allows businesses to come forward proactively, limit the lookback period for back taxes, and in most cases eliminate or substantially reduce penalties. Once the Comptroller initiates contact or an audit, the voluntary disclosure window closes permanently.
The lookback period for Texas sales tax assessments is generally four years. A business that discovers it missed registration two years ago faces a two-year back tax exposure under voluntary disclosure, compared to a potential four-year assessment if an audit initiates first. Interest accrues regardless, but the penalty reduction alone makes voluntary disclosure a significantly better outcome than waiting. Businesses in this position should involve qualified Texas sales and use tax counsel before making contact with the Comptroller. The terms of a voluntary disclosure agreement are negotiable within limits, and a misstep in the application can eliminate the program's benefits entirely.
Texas enforces a high economic nexus threshold relative to most states, but the rules around what counts toward it, how physical presence operates independently, how affiliate relationships are analyzed, and how marketplace sales interact with registration obligations are detailed enough that businesses frequently get them wrong. The combination of a rolling measurement period, an inclusive revenue calculation, and physical nexus that triggers from dollar one with any qualifying presence makes Texas one of the most consequential states in any multi-state compliance review.
Knowing the threshold is not the same as knowing your obligation. The gap between those two things is where most Texas nexus problems begin.
Not sure whether your business has a Texas sales tax nexus? CereTax helps businesses across retail, SaaS, manufacturing, and communications identify where they have nexus, register in the right states, and automate the right tax on every transaction — before the Comptroller asks.
👉🏻 Talk to a CereTax Specialist to evaluate your Texas nexus position today.
