Origin vs. Destination Sourcing: How Sales Tax Sourcing Rules Work
TL;DR
Origin-based sourcing taxes a sale at the seller's location, while destination-based sourcing taxes it at the buyer's location.
Origin rule: The seller's business address sets the rate, so the buyer's location does not change what you charge.
Destination rule: The ship-to address sets the rate, so the same product can carry different tax depending on where it lands.
Hybrid and exception states exist. Some states split the rate by component, and a few flip their own rule based on whether the seller is local or remote.
The location waterfall is where errors start. Systems source a transaction by ship-to address first, billing second, and headquarters last, so bad address data sends tax to the wrong jurisdiction regardless of the underlying rule.
What origin-based and destination-based sourcing mean
Origin-based sourcing taxes a sale at the seller's location, and destination-based sourcing taxes it at the buyer's location. In an origin state, the rate follows the address where the seller operates, so a customer across the state pays the seller's local rate. In a destination state, the rate follows the address where the goods arrive or the service is used, so the same seller charges different rates to buyers in different jurisdictions.
States split on this because each one decides whether the seller or the buyer defines the taxable point of sale. Most states use destination sourcing, which ties revenue to where consumption happens rather than where a business happens to sit.
A handful of states, roughly a dozen, use origin sourcing. The rest, including Washington, D.C., use destination sourcing, and California runs a hybrid of both.
Texas: a clean origin-based example
Texas taxes an in-state sale at the seller's location, which makes it the clearest example of origin sourcing. Say you run a shop in Austin and sell a desk to a customer in Houston. The rate that applies is the combined state and local rate at your Austin store, not the rate where the buyer lives. Houston's local rate never enters the calculation, because the sale is sourced to where you operate.
That single rule is what "origin-based" means in practice. The seller's address sets the jurisdiction, so you charge the same rate to a buyer across the street and a buyer four hours away. You track one rate for your location instead of looking up the buyer's rate on every order.
Missouri and Virginia follow the same origin logic for in-state sales, so a seller there also charges based on its own business location. The mechanics match Texas even though the specific rates differ. The value of these examples is confirmation that origin sourcing is a real category with several states in it, not a Texas quirk.
Keep one limit in mind. This clean version holds for sales inside the origin state. Once goods cross a state line, the destination state's own rules take over, and Texas cannot force its origin approach onto another jurisdiction.
Washington: a clean destination-based example
Washington taxes every sale at the buyer's location, which makes it the mirror image of Texas. Run the same transaction. A Seattle retailer ships a $1,000 order to a customer in Spokane. Spokane's combined rate applies, not Seattle's, because destination sourcing looks only at where the goods land.
Flip the shipment and the logic holds. If that same Seattle seller ships to a buyer in Tacoma, the Tacoma rate governs. The seller's own storefront rate never enters the calculation for an in-state destination sale. Whichever jurisdiction the buyer sits in sets the number.
Destination sourcing is the more common approach across states, so Washington's rule describes how most states treat an in-state sale. That prevalence is also why address quality matters so much, a point the location waterfall section develops. When the buyer's location drives the rate, a wrong shipping address sends tax to the wrong jurisdiction. Texas forgives that error on in-state sales because the seller's fixed location decides everything. Washington does not.
The contrast between these two states is the cleanest way to fix the concept. Origin looks at the seller. Destination looks at the buyer. Real states then complicate both, as California and Arizona show.
California's hybrid rule: state and county follow the seller, district follows the buyer
California proves that a single origin-or-destination label often fails to describe how a state actually calculates tax. The state splits its own rate by component. The statewide rate and the county rate follow the seller's business location, while the district rate, a local add-on layered on top, follows the buyer's location.
Consider a seller in Los Angeles County shipping to a buyer in San Francisco. The statewide portion and the Los Angeles County portion source to the seller, so those parts of the rate reflect the seller's address. The district rate stacks on top based on where the buyer takes delivery, so the San Francisco district add-on applies even though the seller never operates there. The buyer's final rate combines a seller-sourced base and a buyer-sourced district surcharge.
That split matters because it means you cannot resolve California with one lookup keyed to a single address. You need both the seller's location for the state and county components and the buyer's location for the district component, and you have to stack them correctly for every transaction.
California is the clearest reason to stop treating sourcing as a per-state flag. Sourcing is frequently a per-component rule, where different parts of the same tax rate answer to different addresses within one sale. A state can be origin-based for some of its rate and destination-based for the rest, and California is the case that makes the distinction unavoidable.
Arizona's remote-seller exception: when a state's own rule flips
Arizona applies origin sourcing to sellers physically located inside the state, then switches to destination sourcing when the seller is remote or out-of-state. A Phoenix shop selling to a customer in Tucson charges tax based on the shop's own location. An out-of-state seller shipping into Arizona charges tax based on where the buyer receives the goods. Same state, two different sourcing rules, and the difference comes down to who the seller is.
Most guides on this topic miss that distinction entirely. They assign each state a single fixed label, origin or destination, and stop there. Arizona shows why that model is wrong. A state's sourcing method can depend on the seller's status, not just the state's identity, and treating the label as static will produce the wrong rate for a whole class of transactions.
The practical effect hits remote sellers hardest. If you sell into Arizona from another state and assume its origin-based reputation applies to you, you will source to the wrong jurisdiction and collect the wrong amount. The rule that governs your sale is the one for remote sellers, which points to the buyer's address.
The Arizona Department of Revenue confirms this split directly, treating remote sellers as a distinct category from in-state sellers for sourcing purposes. The general pattern, a local rule that flips for remote sellers, is what you should carry into every state you evaluate.
The location waterfall: why sourcing errors actually happen
Most sourcing errors trace back to a single question the tax engine has to answer for every transaction. Which address governs this sale? The answer follows a strict priority order, and each fallback exists because the more reliable data point was missing.
The ship-to address comes first, or for services, the place where the goods or services are actually used. That location reflects where the customer takes possession, which is what destination sourcing depends on and what most jurisdictions treat as authoritative. When the ship-to is unknown, the engine drops to the billing address, on the reasoning that a payment address usually sits near the customer even if it isn't the delivery point. Company headquarters sits last, used only when neither the ship-to nor the billing address is available, because HQ often has nothing to do with where the customer received the sale.
Each step down the waterfall trades accuracy for a usable answer, and that trade is where errors enter. A missing suite number, a billing address in a different tax district than the delivery point, or a defaulted HQ address all push the calculation into the wrong jurisdiction. That failure happens regardless of whether the state is origin, destination, or hybrid. Bad address data corrupts the input before the sourcing rule ever runs, so the rule applies correctly to the wrong location.
How Taxwire handles origin, destination, and hybrid sourcing
Tracking which of the fifty state approaches applies, then layering in hybrids and remote-seller flips, is where manual sourcing breaks down. Taxwire removes that burden by resolving the sourcing method for every transaction as part of its standard calculation, not as a separate step you configure per state. The engine reads the ship-to and seller addresses, determines whether the sale is origin-, destination-, or hybrid-sourced, and applies the correct rate at rooftop-level accuracy.
When a rule depends on seller status rather than state identity, Taxwire accounts for it automatically. An out-of-state seller shipping into Arizona gets destination sourcing, while a local Arizona seller gets origin sourcing, without you flagging the difference. The same logic splits California correctly, sourcing the state and county rate to the seller and the district rate to the buyer.
Sourcing and nexus are adjacent problems that finance teams often confuse. Sourcing decides which jurisdiction's rate applies once you owe tax somewhere. Nexus decides whether you owe tax in that state at all. Our planned Sales Tax Nexus by State guide will cover where obligations begin, so you can pair it with this piece to see the full picture.
FAQs
Do sourcing rules differ for services versus goods? Sourcing for services usually follows where the service is performed or used rather than where a physical product ships. Taxwire applies the correct rule per line item, so a mixed invoice with goods and services can source each component differently. Getting this right prevents undertaxing a service delivered in a jurisdiction with a higher rate.
Do marketplace facilitator sales change sourcing? Marketplace facilitator laws shift who collects and remits the tax, not which address governs the rate. The underlying sourcing rule still applies based on the buyer's or seller's location. Taxwire calculates the correct sourced rate whether you sell directly or through a facilitated channel.
How does sourcing interact with nexus? Nexus decides whether you owe tax in a state at all, while sourcing decides which local rate applies once you do. You can have nexus in a state and still calculate the wrong amount if you source the transaction to the wrong jurisdiction. Our forthcoming Sales Tax Nexus by State guide covers the nexus side in detail.