Picture two competing SaaS companies, each earning $10 million in pretax profit. Both are headquartered in Austin, both employ 80% of their staff in Texas, and both sell software subscriptions to customers in all 50 states. One of them pays $300,000 in California state income tax this year. The other pays nothing. Same revenue, same expenses, same product — radically different tax bills.
The reason has almost nothing to do with what those companies do and almost everything to do with how each state divides up their income. Welcome to the world of state corporate income tax apportionment in 2026, where the choice of formula, the definition of "market," and a handful of technical sourcing rules can swing your effective tax rate by several percentage points.
If you sell services or software across state lines, this is the single most important tax topic you are probably not paying enough attention to.
The Big Picture: Two Decades of Quiet Revolution
There are 44 states (plus D.C.) that levy a corporate income tax. To collect that tax fairly from multistate businesses, each state has to answer one question: of all the income a company earns nationwide, how much is "ours"?
For most of the 20th century, the answer was a three-factor formula. States looked at where a company's property sat, where its employees worked, and where its customers bought — averaged the three, and taxed that share.
That world is largely gone. Today, 34 of the 44 corporate-tax states use single sales factor (SSF) apportionment as their primary formula. Only sales matter. Property and payroll are ignored. The trend is so strong that the remaining three-factor states are increasingly outliers.
Layered on top of that shift is a second, equally important change: how states source sales of services and intangibles. Historically, services were sourced under the "cost of performance" (COP) rule — the sale went to the state where the work was done. Now, market-based sourcing is the majority rule. The sale goes to where the customer is. Kansas and Arkansas both flipped to market-based sourcing effective January 1, 2025, and California finalized sweeping new market-based sourcing regulations that take effect for tax years beginning on or after January 1, 2026.
Combined, these two trends mean one thing for software and service companies: where your customers live now matters far more than where your office, your servers, or your engineers do.
How Apportionment Actually Works
The mechanics are straightforward once you see the math.
Imagine an S-corp or C-corp with $10 million in apportionable business income. To figure out what one state taxes, you compute that state's "apportionment factor" — a fraction between 0 and 1 — and multiply it by the $10 million.
Three-Factor Formula
The classic three-factor formula averages three ratios:
- Property factor: in-state property ÷ total property
- Payroll factor: in-state payroll ÷ total payroll
- Sales factor: in-state sales ÷ total sales
If a company has 20% of its property in State A, 25% of its payroll, and 10% of its sales, its apportionment factor is (20 + 25 + 10) / 3 = 18.3%. State A taxes 18.3% of the $10 million, or $1.83 million of income.
Single Sales Factor
Under SSF, only sales count. Same company, same numbers — the apportionment factor is just 10%. State A now taxes $1 million instead of $1.83 million. That's why states moved to SSF: it shifts the tax burden away from companies that build factories, offices, and jobs inside the state and onto out-of-state sellers who only ship products in.
Double-Weighted Sales
Several states still use a hybrid: a three-factor formula with the sales factor counted twice. The math becomes (property + payroll + 2 × sales) / 4. It's a halfway house between the old world and the new one.
Cost of Performance vs. Market-Based Sourcing
Apportionment formulas tell you how much weight to give each factor. Sourcing rules tell you which sales count as "in-state" in the first place. For physical goods, that question is easy — sales go to the destination state. For services and intangibles, it has been a battlefield for two decades.
The Old Rule: Cost of Performance
Under COP, a service sale was sourced to wherever the income-producing activity occurred — usually, the seller's office. A Boston-based consulting firm advising a Chicago client would source the revenue to Massachusetts (if a majority of the work happened there). This favored states with lots of service providers but few customers.
The New Rule: Market-Based Sourcing
Market-based sourcing flips the logic. The sale goes to where the customer receives the benefit. The Boston consultant's revenue from the Chicago client now belongs to Illinois. For SaaS providers, the receipt is generally sourced to where the customer uses the software — though the practical answer often depends on a cascading set of fallback rules.
Most states adopting market-based sourcing use a hierarchy that looks roughly like this:
- Where the customer actually receives the benefit, based on contract or substance.
- Where the customer's operations using the service are located.
- Where the customer placed the order.
- The customer's billing address.
The first rules carry the most audit weight. The billing address is meant to be a last resort. State auditors have grown skeptical of taxpayers who jump straight to billing address sourcing without trying to identify the real location of use.
What's New in 2026
A handful of changes are worth flagging for any multistate service business.
California's Final Market-Based Sourcing Regulations
The California Franchise Tax Board finalized long-debated amendments to its sourcing regulations, effective for tax years beginning on or after January 1, 2026. The regulations tighten rules for services and intangibles, and they allow billing-address sourcing only in narrow circumstances — generally limited to professional service providers with more than 250 customers for a given service, with carveouts for large customers. SaaS companies relying on billing-address sourcing in California should review their methodology immediately.
Kansas's Phased Transition
Kansas enacted single sales factor apportionment and market-based sourcing in 2024. SSF kicked in first, and market-based sourcing for services, sales of intangibles, interest from loans, and dividends becomes effective for tax years beginning after December 31, 2026. Kansas is now aligning with most of its neighbors.
Throwback and Throwout Rules Continue to Recede
Roughly 23 states still impose a throwback or throwout rule — both designed to capture "nowhere income" that a seller earns in a state where it has no tax nexus. A throwback rule adds those sales back to the home state's numerator; a throwout rule removes them from the denominator. Either way, the in-state apportionment factor rises. The trend has been strongly against these rules, and several states have repealed or weakened theirs over the past five years. Maintaining a throwback rule increasingly disadvantages a state, as companies relocate sales activities or restructure to avoid it.
Industry-Specific Carveouts
A growing number of states allow or require special apportionment formulas for specific industries — financial institutions, broadcasters, airlines, and transportation companies most commonly. California, for example, is in the process of moving financial institutions to single sales factor. SaaS companies have occasionally argued for and won classification as "manufacturers" in states like Massachusetts, qualifying them for more favorable single-factor treatment.
Why SaaS and Service Companies Pay the Price
The math is simple but the consequences are not. A SaaS company headquartered in a low-tax state with a national customer base used to be able to keep most of its income out of high-tax states by pointing to where its servers and engineers sat (cost of performance). Under modern market-based sourcing, that strategy is dead. If 12% of your customers are in California, roughly 12% of your services revenue is now California-sourced.
Three structural realities make this hit hardest for software and service businesses:
- No physical anchor: A cloud company has no factories or warehouses. Under three-factor formulas, that was an advantage. Under SSF + market-based sourcing, location of property is irrelevant — only customer location matters.
- High-tax customer markets: California, New York, New Jersey, Illinois, and Massachusetts are all major customer markets for B2B software. Even a Texas- or Florida-based SaaS company will owe income tax in those states once nexus and apportionment kick in.
- Economic nexus thresholds: After the Wayfair decision, virtually every corporate-tax state has adopted economic nexus standards — typically $500,000 of in-state receipts triggers an income tax filing requirement. Sourcing rules determine whether you cross that threshold.
The combined effect: a software company doing meaningful business in 20+ states must file 20+ state returns, each with its own apportionment formula, sourcing rule, throwback policy, and definition of "benefit." Compliance costs alone can run six figures annually for mid-market companies.
The Audit Trap: "Benefit Received" Disputes
The phrase "where the benefit is received" sounds simple. In practice, it's the most litigated term in state income tax.
Consider a software company that licenses a tool to a national retailer. The retailer is headquartered in Arkansas. It uses the software in stores across all 50 states. Where is the "benefit" received?
- The auditor's likely answer: at each of the 50 store locations, in proportion to use.
- The taxpayer's preferred answer: at the customer's headquarters, in Arkansas.
- The fallback answer: at the customer's billing address.
Each of these positions can be defended, but they produce wildly different results. States increasingly demand "look-through" sourcing — meaning the taxpayer must look past the contracting entity to the underlying users. That requires data SaaS providers don't always collect: user IP addresses, headcounts by location, usage metrics by region.
The practical upshot: documentation matters more than ever. The taxpayer carries the burden of proving where the benefit was received. If you can't produce supporting data on audit, the state will often impose its own reasonable assumption — usually one that maximizes its share.
Five Strategies to Reduce Apportionment Risk
You can't change the rules, but you can manage your exposure.
1. Map Your Customer Base by State
The single highest-value exercise is a clean inventory of where your customers actually use your product, not just where they pay from. Pull data from your CRM and product analytics. Identify customers with multi-location operations and decide whether contract terms or usage data drive sourcing.
2. Update Contracts to Support Your Sourcing Position
A well-written master services agreement can clarify where the benefit of a service is received. Stating that the customer accesses and uses the product "primarily at the customer's principal place of business" can support sourcing to a single state. Vague contracts leave you exposed to state-favorable interpretations.
3. Reconsider Entity Structure
Some companies operate through a single entity that contracts with every customer. Others use separate entities by product line or geography. The right structure depends on your facts, but apportionment is one input. A separately incorporated entity that only operates in low-tax states may be worth considering — but watch for unitary business doctrines that can pull related entities into combined reporting.
4. Track Throwback and Nowhere Income Carefully
If your home state has a throwback rule, every sale into a no-nexus state increases your home-state tax. Determining nexus correctly in each state — and creating it where doing so reduces total tax — is a legitimate planning lever. Some companies intentionally create nexus in low-rate states to neutralize throwback.
5. File Petitions for Alternative Apportionment Where Justified
Every state with corporate income tax has a provision allowing taxpayers (and the state) to request an alternative apportionment method when the standard formula doesn't fairly reflect business activity in the state. The bar is high, but for unusual fact patterns — heavy R&D investment, asset-light service businesses, or industries with mismatched cost and revenue geographies — alternative apportionment can deliver real savings.
The Bookkeeping Foundation You Can't Skip
None of these strategies work without strong financial records. State auditors will ask for revenue by customer by state, by month or quarter. They will want supporting documentation tying contracts to the revenue. They will expect you to be able to reconcile your apportionment workpapers back to your general ledger.
Companies that maintain clean books — with revenue tagged by customer, location, and product line — survive audits with minimal adjustment. Companies that try to reconstruct sourcing positions years later, from emails and bank statements, lose. The cost of getting this right is small; the cost of getting it wrong, including penalties and interest, can be several times the underlying tax.
If you handle multistate operations, your ledger should already capture:
- Revenue by customer entity and product line
- Customer addresses (legal, billing, and primary use location)
- Contract terms documenting where services are delivered
- Allocations of indirect revenue (royalties, licenses, intangibles) by jurisdiction
These data points are not just for state tax — they support sales tax compliance, SOC audits, and acquirer due diligence too.
Looking Ahead
The direction of travel is clear. By the end of the decade, single sales factor with market-based sourcing will be near-universal. Throwback rules will continue to fall. Look-through sourcing will spread. And data demands on taxpayers will keep growing as state revenue departments invest in audit analytics and information-sharing arrangements.
For SaaS, fintech, professional services, and other asset-light companies, this is a long-term shift in the economics of doing business across state lines. The companies that adapt early — with the right contracts, the right entity structure, and the right financial systems — will pay less tax and spend less time defending audits.
Those that ignore it will keep getting surprised by tax bills from states they barely think about.
Keep Your Multistate Finances Audit-Ready
Apportionment is fundamentally a data problem: the tax follows the customer, the documentation follows the data, and the audit follows the documentation. Building clean, queryable financial records from day one is the single best investment you can make in defending future positions. Beancount.io offers plain-text accounting that's transparent, version-controlled, and AI-ready — making it easy to tag revenue by customer, location, and product line so you can support any sourcing position on audit. Get started for free and see why developers and finance teams trust plain-text accounting for multistate operations.