Credits vs Seats vs Usage: Tax Implications of Hybrid SaaS Pricing

If your product mixes seats, credits, and usage in one plan, you are not just designing pricing. You are also deciding how those sales will be taxed.

Hybrid pricing is good for matching price to value. It also drops you into one of the messiest parts of U.S. sales and use tax.

States do not see these charges the way founders do. A seat based subscription might be treated as SaaS. Usage can be data processing or information services. Credits might be prepayments, stored value, or part of a bundle.

If you want to experiment with pricing without getting blindsided by state rules, Afternoon’s bookkeeping and tax services can help you map each pricing component to a tax category and stay audit ready as you scale.

This article is general information, not tax or legal advice. Always confirm your facts with a tax professional.

---

Quick facts

For a typical AI or SaaS platform selling into the U.S.:

---

Why pricing models matter for tax

From a product view, seats, credits, and usage are just different ways to price access. From a tax view, they can be completely different transactions.

States care about three main things:

• What the customer is actually buying, often called the “true object”
• Whether a charge is for software access, automated data processing, or something else
• How tightly you bundle pieces together, one SKU or clearly separated lines

Once you mix models in a single plan, you are in mixed transaction country. That is where auditors look closely at how you priced, described, and documented the deal.

---

Breaking down each pricing model

Seat based pricing

Seat based pricing is the easiest pattern for most states to understand.

• The customer pays a fixed amount per named or active user
• The value is ongoing access to your hosted software
• In many states, this is remote access to prewritten software and is taxable if the state taxes SaaS

Key SaaS states today include:

• Washington, which treats many online platforms as digital automated services or remote access software under its digital products rules
• New York, which taxes prewritten computer software whether it is delivered on a disk, downloaded, or accessed remotely, see New York Tax Bulletin TB ST 128 Computer Software
• Texas, which often treats SaaS as taxable data processing with a 20 percent exclusion built in
• Massachusetts, which taxes prewritten software, including many remote access models, under its computer industry rules

If most of your revenue is per seat SaaS, assume the base subscription is taxable in those states once you have nexus.

Usage based pricing

Usage pricing covers things like:

• API calls
• Compute time, in seconds, units, or credits
• Data processed, stored, or transferred

States often slot this into categories such as:

• Data processing services
• Electronic information services
• Access to online platforms that use automated systems to process customer data

A couple of common patterns:

• Texas treats many usage based services as taxable data processing and allows only a partial exclusion from tax
• Ohio continues to tax automatic data processing and electronic information services sold to businesses

If your product is pure usage with no separate platform fee, the entire charge can look like data processing in states that tax that service.

Credit based pricing

Credit models are where things start to bend.

Credits can be:

• Prepayment for future taxable services, for example API calls
• Stored value that can be used across several products
• A right to receive taxable software or digital services later

Many states take this view:

• Stored value credits are not taxed when sold
• Tax is due when the credits are redeemed and the underlying service is delivered

New York can be stricter. In some advisory opinions, the state treats the sale of a right to access taxable information services or software as taxable at purchase when the credit only buys taxable services. That follows the approach in 20 NYCRR 527.3 on information services.

In practice that means:

• Selling $1,000 of credits might not be the taxable moment in some states
• In others, tax is computed when you sell the credits, not when customers spend them

If you lean hard on credits, for example “$20 per month includes $18 in credits,” you need a clear policy on when you calculate tax and how you track credit usage.

---

The bundling problem: mixed transactions

Now combine the pieces. Say you sell a plan with:

• 5 seats at $50 per month
• 10,000 API calls included
• Overages at $0.001 per call
• Credits that can be used for premium features or higher priority workloads

The core tax question is simple to ask and hard to answer. Are you selling one thing or several?

True object and bundling tests

Most states start with some version of a “true object” or primary purpose test.

Roughly:

• If the main thing the customer wants is platform access and usage is a side benefit, they may treat the whole charge as SaaS
• If the main thing is automated data processing or consumption of compute, the whole amount can be treated as data processing in states that tax that category

Then state specific rules pile on.

New York often says that when one price covers taxable and non taxable components, the entire fee is taxable unless the non taxable part is tiny or separately stated. The state applies this logic in many information service and software cases that rely on 20 NYCRR 527.3 and TB ST 128.

California uses a true object test in bundled tech and telecom deals. In a well known cell phone case, the court allowed tax on the full bundled price of a subsidized phone plus service, because the phone was a main object of the sale, not a throw in. The California Department of Tax and Fee Administration explains how it looks at internet and remote sales in CDTFA Publication 109 Internet Sales.

Texas wants a reasonable allocation between taxable and non taxable parts when both live inside one combined charge. You cannot just guess later. You need a method you apply every time.

If your pricing page says “$500 per month, all in” and your invoice is one line for that amount, you are making it easier for a state to say that 100 percent of the charge is taxable.

---

Practical examples

Scenario 1: Slack style seat pricing

• Base plan at $8 per user per month
• Overage at $0.50 per guest user above a set limit

In most SaaS taxing states, this is all SaaS. The overage is still tied to user count, not to a separate data processing activity. The entire charge usually lands in the same tax bucket.

Scenario 2: OpenAI style credits

• $20 per month plan that includes $18 in credits
• Extra credits sold at standard rates

In many states, this looks like two related items:

• A platform subscription for account access and settings
• Credits used later for taxable services such as API calls or embeddings

Some states tax both streams at the same time. Others focus on the moment credits are redeemed. The more clearly you separate “platform fee” from “usage credits” on invoices, the easier it is to defend different tax treatment. In New York, you will want to tie your approach back to how the state treats prewritten software under TB ST 128 and information services under 20 NYCRR 527.3.

Scenario 3: Snowflake style consumption

• $25 minimum monthly commitment
• All charges based on compute usage

Here, many states treat the full amount as data processing or a similar taxable service when that category is in scope. The minimum commitment looks like a prepayment against future usage, not a separate non taxable subscription.

---

---

Structuring pricing for tax efficiency

You do not have to rebuild your product to reduce tax friction. You may want to adjust how you present, invoice, and document pricing.

Option 1: Separate line items

On invoices and in your billing system, break out:

• Platform access, seats, or subscription
• Usage charges, such as API, compute, or storage
• Support or professional services

This approach:

• Lets you apply different tax rules to each piece
• Makes it easier to exclude clearly non taxable services, like separately stated consulting
• Gives you better data for modeling effective tax rates by plan and by state

Option 2: Single SKU with documented allocation

If you want a simple one line price to show customers, you can still do the work behind the scenes.

You can:

• Allocate that fee across components, for example 60 percent platform, 30 percent data processing, 10 percent support
• Write that allocation into an internal tax memo or policy
• Apply the same ratio every time you calculate tax and recognize revenue

Auditors can still challenge your split. Having a method is much better than having no method.

Option 3: Geographic pricing

Some companies vary prices by region to reflect higher tax cost in certain states or cities, such as Chicago.

If you try this:

• Document that regional prices reflect local tax and compliance costs along with other business factors
• Avoid setups where you quietly “eat” tax in high tax states without adjusting list prices at all

---

State specific gotchas

Washington

• Washington taxes many digital automated services and remote access software under its digital products rules
• Even if sales tax is not charged on a specific transaction, the state B and O tax often still applies to gross receipts
• Hybrid pricing can fall into different B and O classifications, such as service or retail, depending on how you frame the offer

Massachusetts

• Massachusetts computer industry rules explain how tax applies to prewritten software, SaaS style models, and related services
• Separately stated personal or professional services can be exempt
• Once you bundle those services into one charge with taxable software access, the entire fee can become taxable unless you can support a real allocation

New York

• New York taxes prewritten software as tangible personal property whether it is delivered on media, downloaded, or accessed remotely, as explained in TB ST 128 Computer Software
• New York also taxes many information services under 20 NYCRR 527.3, which covers services that collect, compile, or analyze data and furnish reports
• Bundles that mix taxable software or information services with non taxable services often end up fully taxable if you do not clearly separate the pieces

A simple example is a plan that includes access to a hosted dashboard plus “consulting” that is never billed on its own. New York can treat the whole charge as taxable software or information services.

California

• California generally does not tax remote access software or pure SaaS when nothing tangible is delivered, so many SaaS and AI platforms see no state level sales tax on subscription fees
• The state still applies sales and use tax to many tangible items sold over the internet, and it explains this in CDTFA Publication 109 Internet Sales and related guides
• In bundled deals that mix hardware and service, California uses a true object approach and can tax the full price when the taxable hardware is a main object of the sale

For a hybrid pricing model, that means a “device plus cloud” plan in California can look very different tax wise from a “cloud only” SaaS plan.

Illinois and Chicago

• At the state level, many SaaS products are not subject to standard sales tax
• Chicago imposes a 9 percent tax on many cloud and streaming services through its lease and amusement tax rules
• These city rules are broad enough that common SaaS and platform offerings billed to Chicago customers can fall in scope even when state sales tax does not

If you have a real Chicago customer base, treat its local taxes as a separate risk, not an afterthought.

---

Documentation you need

To defend your pricing and tax positions, you need more than a Stripe export.

Plan to keep:

• A short plain language description of each pricing component, such as seats, usage, credits, and support
• An internal mapping of each component to a tax category, like SaaS, data processing, or professional services
• A simple cost and value analysis that backs up your allocation in bundled prices
• Standard contracts and terms that state what each fee covers
• Sample invoices that show separate line items or consistent allocation logic

If an auditor shows up, this is what you want to send first, not a spreadsheet you built that morning.

---

Audit risk with hybrid pricing

Mixed pricing models attract attention because they create room for interpretation.

Common audit triggers include:

• Credits that never expire and start to look like stored value or gift cards
• Usage based plans that are effectively unlimited and could be reclassified as flat subscriptions
• Bundles where the price is very close to the taxable component alone, with “free” non taxable services added on paper
• Inconsistent tax treatment for similar customers in the same state

You do not need to be perfect. You do need to be consistent, documented, and ready to explain your logic in clear terms.

---

Action items for founders and finance leads

Before you launch or overhaul a plan that mixes seats, credits, and usage:

1. Map each pricing component to a tax category.
2. Identify your top five to ten states by revenue and check how each category is treated there.
3. Decide which parts you will break out and which will stay bundled.
4. Update invoices and billing exports so you can see revenue by component and by state.
5. Write a short internal memo explaining your method and store it alongside contracts and policies.

It is much harder to fix pricing and tax after a few big customers are live.

---

How Afternoon.co can help

Afternoon works with SaaS and AI teams that:

• Sell seats, credits, and usage inside one plan
• Want their chart of accounts to reflect tax categories, not just product names
• Need monthly views of revenue and tax exposure by state and by component

We help you:

• Connect billing and product data into clean accounting records
• Spot pricing and bundling changes that could reduce tax friction
• Coordinate with your sales tax advisor so pricing, contracts, billing, and filings all match the same story

If you are rethinking your pricing model and want tax to be part of the design, not a surprise later, talk to Afternoon.

---

Sources

• Washington Department of Revenue – Digital Products and Digital Automated Services
• WAC 458 20 15503 – Digital Products and Digital Automated Services
• New York Tax Bulletin TB ST 128 – Computer Software
• 20 NYCRR 527.3 – Information Services
• New York State – Quick Reference Guide for Taxable and Exempt Property and Services
• California CDTFA Publication 109 – Internet Sales
• Massachusetts 830 CMR 64H.1.3 – Computer Industry Services and Products
• Texas Comptroller – Data Processing Services are Taxable
• Ohio Department of Taxation – Sales and Use Tax Information Releases
• City of Chicago – Personal Property Lease Transaction Tax