Sales tax sourcing answers where a transaction is taxed; it does not answer whether the product is taxable. A reliable result requires both decisions: classify the item or service, then apply the jurisdiction’s sourcing rule to the transaction facts.
Key takeaways
Do not use the seller’s headquarters or customer billing address as a universal sourcing rule.
Delivery, possession, pickup, product type, and seller presence can change the location.
ZIP codes are not reliable substitutes for tax boundaries.
Store the evidence used to choose the jurisdiction and rate.
Understand what sourcing controls
Sourcing determines the state and local jurisdiction associated with a sale. That location drives the applicable rule set, combined rate, local allocation, and sometimes the return schedule.
The same seller can have different sourcing outcomes for shipped goods, store pickup, delivered installation, remotely accessed software, and services. Begin with the actual transaction flow rather than a simplified origin-or-destination label.
- Identify the seller and purchaser.
- Record where delivery or possession occurs.
- Classify goods, software, and services separately.
- Check whether special sourcing rules apply.
Distinguish origin and destination concepts
Under a destination approach, the delivery or use location commonly drives the rate. New York guidance describes sales tax as a destination tax and focuses on where delivery or possession transfers. Other regimes can source certain sales to the seller’s location or use mixed rules.
A state can also distinguish in-state sellers from remote retailers or apply different local allocation rules. Never turn a high-level state label into a checkout rule without reviewing the current official instructions.
- Document the controlling state guidance.
- Separate state tax from local allocation.
- Record seller-presence assumptions.
- Version the rule by effective date.
Source common fulfillment scenarios
For a shipment by common carrier, the delivery destination often matters. For customer pickup, possession can transfer at the store or warehouse. Drop shipments add a supplier and may introduce special retailer rules. Installation or delivery by the seller can change the analysis.
Create scenario rules for warehouse shipment, store pickup, curbside delivery, digital delivery, marketplace fulfillment, and customer-arranged freight. Test them separately rather than relying on one address field.
- Map ship-from and ship-to locations.
- Record pickup and possession-transfer facts.
- Identify the importer or drop shipper where relevant.
- Keep carrier and delivery documentation.
Collect address data that can support the rate
Billing addresses, IP addresses, postal addresses, and user locations serve different purposes. For physical goods, a validated delivery address is usually more useful than billing data. For software or services, user or place-of-primary-use information may matter.
Normalize addresses before jurisdiction assignment and use boundary-aware data where local districts apply. A five-digit ZIP code can cover multiple cities or districts and should not be treated as a tax jurisdiction.
- Validate street, city, state, and postal fields.
- Preserve the original customer entry.
- Flag incomplete or conflicting locations.
- Retest address logic after provider changes.
Handle mixed and changing locations
Enterprise software, services, subscriptions, and equipment can be used in more than one location. Some jurisdictions provide allocation or multiple-points-of-use mechanisms, while others require a different method or documentation.
Build a customer-location workflow that can capture allocation percentages, effective dates, exemption documents, and changes. Do not let one headquarters address silently control every user or delivery.
- Ask for location detail when material.
- Validate allocation totals and dates.
- Link documentation to the customer account.
- Revisit sourcing when usage changes.
Test and reconcile sourcing decisions
Test addresses on both sides of local boundaries, pickup versus delivery, taxable versus exempt items, refunds, and address corrections. Review whether the jurisdiction code, combined rate, and return allocation all change as expected.
During filing, reconcile jurisdiction totals to order data. An unexplained concentration in one city, use of fallback ZIP rates, or transactions assigned to an unknown location can reveal sourcing defects before an audit.
- Create boundary and fallback test cases.
- Monitor orders with missing jurisdiction codes.
- Reconcile local allocations each filing period.
- Save rule versions and test evidence.
Frequently asked questions
Is sales tax based on billing or shipping address?
For shipped goods, the delivery location is often more relevant, but the answer depends on the jurisdiction, product, and transaction. Billing address is not a universal sourcing rule.
Are all states destination based?
No. States can use destination, origin, or mixed rules, and local allocation can differ for remote and in-state sellers.
Can a ZIP code determine the correct sales tax rate?
Not reliably by itself. ZIP codes can cross tax boundaries, so validated address and jurisdiction data are safer where local rates apply.
Does sourcing determine product taxability?
No. Product taxability and sourcing are separate analyses; both must be correct to calculate the tax.
Official sources
Reviewed against the following primary sources on Aug 8, 2026.