You sell the same product at the same price to two customers in different cities within Texas. One invoice shows 8.25% sales tax. The other shows 6.25%. Both are correct.
If that scenario makes you pause, let’s look at why sourcing rules matter. These rules determine which tax rate applies to a transaction, and they’re the reason your collected rate sometimes doesn’t match what you expected to see on an invoice.
Most states use destination-based sourcing. This means the tax rate depends on where your buyer receives the product. But a handful of states flip that logic. They base the rate on where you, the seller, are located. And some states, like California, use a hybrid approach that catches even experienced finance teams off guard.
Let’s break down how origin-based and destination-based sourcing actually work. We will cover which states follow which rules and why this distinction creates real compliance problems for multistate and e-commerce businesses. You will also learn how to check whether your tax software is configured correctly. Sourcing errors rarely surface in your day-to-day operations. They usually stay hidden until an audit.
What Sourcing Rules Actually Are
Think of sourcing rules like a GPS for your sales tax. They tell your billing system exactly which location’s tax rate to pull for a specific sale.
There are two main approaches:
Origin-based sourcing means the tax rate is based on the seller’s location. If your business operates from a warehouse in Dallas, you charge the Dallas rate regardless of where in Texas your customer lives.
Destination-based sourcing means the tax rate is based on where the buyer receives the product or service. If you ship from Dallas to a customer in Austin, you charge the Austin rate.
That’s the core distinction. The Texas example from the introduction? Texas is an origin-based state for in-state sellers. The rate difference came from two sellers in different cities, not two buyers in different cities. Once you understand which rule applies, the math makes sense.
The challenge is that a state like Texas looks at the seller’s location while a state like New York looks at the buyer’s doorstep. Sometimes a single state applies different rules depending on whether you are located in-state or selling remotely.
Destination-Based Sourcing: The Majority Rule
Most states use destination-based sourcing, especially for remote and online sales. If you’re an e-commerce business shipping to customers across the country, destination-based sourcing is the default you’ll encounter most often.
Here’s what “destination” means in practice: it’s the ship-to address, not the billing address. If a customer in Chicago buys from your website but has the order shipped to their office in Springfield, you charge the Springfield rate. The location where the product lands is what matters.
This applies whenever you put physical products in a box and ship them to a customer. For services and digital products, the rules get more nuanced. But the main idea remains the same: the buyer’s location drives the rate.
The Intrastate Exception
Some destination-based states carve out an exception for in-state sellers. If your business is physically located in the same state as your customer, the state may allow or require you to use origin-based sourcing for those transactions.
California is a common example of this, though California’s rules are more complex than a simple exception. We’ll cover that in the hybrid section below.
The practical effect: a business with a physical presence in a destination-based state may need to apply different sourcing logic for in-state sales versus out-of-state sales. Your tax configuration needs to account for both.
Origin-Based Sourcing: The Minority That Still Matters
Fewer than a dozen states use origin-based sourcing, but if you have a physical presence in any of them, you need to understand how they work.
States that use origin-based sourcing include:
- Arizona
- California (for state and county rates only)
- Illinois
- Mississippi
- Missouri
- Ohio
- Pennsylvania
- Tennessee
- Texas
- Utah
- Virginia
In these states, when you’re an in-state seller, the tax rate is determined by your business location rather than your customer’s address. A seller in downtown Phoenix charges the downtown Phoenix rate to customers anywhere in Arizona.
Why This Matters for Multistate Businesses
If you have nexus in twenty states, you’re likely applying destination-based sourcing in most of them. But if you also have a warehouse in Texas or an office in Pennsylvania, those states require origin-based sourcing for your in-state transactions.
This forces finance teams to juggle conflicting setups inside their billing systems. You might assume setting everything to “destination” solves the problem. Your tax software needs to know not just where you have nexus, but where you have physical locations that trigger origin-based rules. A uniform setup will produce incorrect rates in origin-based states.
For a deeper look at how Utah handles these rules, see our Utah sales tax guide.
Hybrid and Modified Rules
“Origin vs. destination” is a useful framework, but the real rule is often transaction-specific. Several states apply different sourcing logic depending on the type of seller, the type of product or both.
California’s Hybrid Approach
California deserves special attention because it’s one of the most common sources of undercollection errors.
Here’s how it works: California uses origin-based sourcing for state and county tax rates, but destination-based sourcing for district taxes. District taxes are the additional local taxes that vary by jurisdiction, and they can add 1% to 4% or more to the total rate.
Say you are located in a low-district-tax area but sell to customers in high-district-tax areas. If your system is configured for pure origin-based sourcing, you are undercollecting on every transaction. That gap adds up fast, and it’s exactly the kind of error that auditors look for.
For more detail on California’s specific rules, see our California sales tax guide.
Other Hybrid Scenarios
Some states apply different sourcing rules based on:
- Seller type: In-state sellers may use origin-based sourcing while remote sellers use destination-based sourcing for the same transaction type.
- Product type: Tangible goods may follow one rule while services or digital products follow another.
- Delivery method: Shipped goods may use destination-based sourcing while goods picked up in-store use origin-based sourcing.
The point isn’t to memorize every variation. It is easy to assume you can just pick one sourcing method and forget about it. But the truth is that the correct sourcing method depends entirely on the specific transaction.
Why This Trips Up Remote and Multistate Sellers
Managing sales tax gets tricky when your business expands into new states that enforce totally different sourcing rules.
The Common Failure Mode
A business establishes nexus in several states through economic activity. They set up their tax software, configure it for destination-based sourcing (since that’s the majority rule), and start collecting.
Later, they open a warehouse in Texas or hire a sales rep in Ohio. Now they have physical presence in an origin-based state, but their tax configuration hasn’t changed. Every in-state transaction in that origin-based state is being calculated incorrectly.
This error doesn’t announce itself. The invoices go out. The returns get filed. The numbers look reasonable. But the rates are wrong, and the liability accumulates until an auditor finds it.
The Nexus Connection
Where you pay tax dictates how you calculate tax. Every state where you have nexus is a state where you need to know the sourcing rules. And those rules can change based on whether your nexus is physical or economic.
For example, a state might require destination-based sourcing for remote sellers with only economic nexus, but origin-based sourcing for sellers with a physical location in the state. If your nexus type changes, your sourcing method may need to change with it.
This is one of the five multistate sales tax risks that catches growing businesses off guard. The more states you operate in, the more sourcing configurations you need to manage correctly.
What to Check in Your Own Setup
Sourcing errors are configuration errors. They’re fixable, but only if you know to look for them.
Verify Your Sourcing Settings by State
Log into whatever tax platform you use, whether that’s Avalara, TaxJar or another solution. Look at the sourcing configuration for each state where you have nexus. Confirm that origin-based states are set to origin-based sourcing and destination-based states are set to destination-based sourcing.
Check for Physical Presence in Origin-Based States
If you’ve added a warehouse, office, employee or other physical presence in an origin-based state, make sure your sourcing configuration reflects that. Economic nexus and physical nexus can trigger different sourcing requirements in the same state.
Review California Specifically
If you have nexus in California, confirm that your system is handling district taxes correctly. State and county rates should follow your origin location, but district rates should follow the destination. If your platform doesn’t support this hybrid logic, you may need a manual workaround or a different solution.
Test a Sample Transaction
Pick a transaction where you know the correct rate. Run it through your system and compare the output. If the rate doesn’t match, you have a configuration problem.
The Audit Reality
Sourcing errors often don’t surface until an audit. The state compares your collected rates against the rates that should have applied based on transaction details. If there’s a pattern of undercollection, you’ll owe the difference plus interest and potentially penalties.
A What’s Next call with a sales tax expert can help you identify these gaps before an auditor does. It’s a simple conversation that gives you clarity on where your configuration might be exposing you to risk.
Take the Guesswork Out of Your Sourcing Configuration
Sourcing rules sit at the intersection of where your business operates and where your customers receive what they buy. Getting them right means understanding that “origin vs. destination” is a starting point, not a complete answer. The correct rate depends on the state, your nexus type, the transaction details and sometimes all three.
You can fix these configuration issues today. Once you know which states require which sourcing method, you can configure your systems correctly and stop worrying about whether your invoices are accurate.
The real danger lies in assuming your software automatically adapts to new warehouse locations or remote hires. A business collecting at the wrong rate in an origin-based state accumulates liability with every transaction. That liability sits quietly until an audit surfaces it, along with interest and penalties that could have been avoided.
If you’re operating in multiple states, especially if you’ve recently added physical presence through a warehouse, employee or office, now is the time to review your sourcing setup. Check your tax platform configurations. Test sample transactions. And if California is in your nexus footprint, pay special attention to how district taxes are being calculated.
If you want to make sure your billing system is applying the right rates for your exact physical footprint, a conversation with a sales tax expert can identify gaps in your current configuration and give you a roadmap for fixing them. No fees, no pressure. We will just walk through what is actually happening in your setup and what needs to change.
Schedule a What’s Next call to review your sourcing configuration and make sure your rates are right before an auditor finds a problem you didn’t know existed.
The post Origin-Based vs. Destination-Based Sales Tax: How to Calculate the Right Rate appeared first on The Sales Tax People.