How to Reduce California Taxes When Your SaaS Business Is Based Outside California

In August 2025, a client called me. SaaS company, about $6 million in gross revenue, headquartered outside California, customers spread across roughly 30 states. They had nexus in most of them — that's what happens when you grow fast and nobody's watching the state registration question closely enough.

He wasn't calling about an IRS problem. He wasn't behind on filings. He called because his California tax exposure had become a real number, and he wanted to understand whether it had to be that big.

California had reached in. That part wasn't in dispute. Under R&TC § 23101(b), once your California sales cross $654,321 — or 25% of total revenue — you're doing business in California regardless of where you're physically located. He was well past that threshold. California had its hook.

But having the hook isn't the same as reeling in every dollar.

When I looked at his structure, his entire revenue base was being sourced to California. Every dollar. Not because California had a legal claim to all of it — but because no one had ever looked at the sourcing question. The default billing-address presumption under Cal. Code Regs. tit. 18, § 25136-2(c)(2) had been doing its quiet work for years, and nobody had challenged it.

Thirty states worth of customers. Thirty states worth of economic activity happening outside California. And California collecting as if it all happened there.

Based on my reading of R&TC § 25136, that's not how market-based sourcing works. Revenue is sourced to where the customer receives the benefit — not to the vendor's state, and not automatically to the billing address when the contract says otherwise. In this case, the potential re-sourcing of $3.5 million of that revenue — the portion attributable to customers genuinely operating outside California — had real numbers attached.

At a combined rate of roughly 15% on the marginal dollar, that's approximately $78,000–$105,000 in annual California tax savings. And that was before we looked at entity structure or intercompany service agreements.

There are three levers. None of them are simple. All of them require a qualified attorney in each relevant state before any structure goes in place. But they're grounded in the code, and in the right situation the math is hard to ignore.

For a broader overview of California tax strategies for business owners, including multi-state issues, see our tax strategies page. And if you're a trade contractor wondering how California's reach affects your business structure, the bid2bank blog covers those scenarios in depth.

Does My Out-of-State SaaS Company Actually Owe California Income Tax?

Most out-of-state founders assume California can't tax them because they're not there. Here's where it gets counterintuitive — California doesn't require you to be there.

Under R&TC § 23101(b), California's factor presence nexus standard, you're considered "doing business" in California if your California sales exceed the lesser of $654,321 (2025 indexed threshold) or 25% of total sales. Physical presence is irrelevant. No office required. No employees. No servers on California soil.

For a SaaS company doing $6 million with any meaningful California customer base, you're almost certainly over that threshold. Nexus exists. California has a claim.

But the nexus question and the sourcing question are different questions. Nexus determines whether California can tax you at all. Sourcing determines how much of your revenue falls into California's base. Most advisors answer the first question and stop. The second question is where the money is.

Under R&TC § 25136, California's market-based sourcing rule, service revenue is assigned to California only if the benefit of the service is received in California. Not where you performed the work. Not where your servers are. Where the customer derives value from what you sold them.

If your customers are Texas-based businesses operating from Houston offices — or multi-state firms where primary use happens outside California — there is a statutory argument that a significant portion of your revenue should be sourced outside California's reach. The default billing-address presumption pulls the other direction, but it can be overridden.

Under R&TC § 23101(b), a business is "doing business" in California if California sales exceed the lesser of $654,321 (2025 threshold) or 25% of total sales — regardless of physical presence. Nexus is the threshold. Sourcing is the amount.

Can Contract Language Override How California Sources Your SaaS Revenue?

What most advisors miss is that the override isn't just theoretical — it's written directly into the regulation. The question is whether you've used it.

This is the most powerful lever, and the most overlooked one.

Under Cal. Code Regs. tit. 18, § 25136-2(c)(2), the default billing-address presumption can be overridden in two independent ways: by the terms of a contract between you and your customer, or by books and records kept in the ordinary course of business. The regulation uses "or" — based on my reading, that means contracts alone can do the job, without requiring supporting records.

What does a defensible contract override look like in practice? A Terms of Service agreement should:

• Require the customer to represent and warrant that the service is accessed and the benefit is received outside California
• Prohibit California access by contract, or specify a non-California location as the place of benefit
• Allocate liability — indemnification — to the customer if those representations turn out to be false

For a phone-based or access-code service where IP tracking isn't available, the contract language carries even more weight. The regulation's focus is on economic reality, not technical proxies. If the contract specifies that the service is being accessed from a Texas call center or an out-of-state office, and the customer's operational reality backs that up, the billing-address presumption is overridden.

Supplement with books and records — customer service addresses on file, annual certifications, call detail records with originating area codes — and the position becomes harder for the FTB to challenge on substance-over-form grounds.

This type of multi-state tax planning requires the same documentation discipline we apply to any California controversy position — build the record before the notice arrives, not after.

Risk disclosure: This is an aggressive position. The contract-override reading is grounded in the regulation's plain text, but the FTB can and will challenge it if the economic reality doesn't match the contracts. Customer certifications, service address data, and operational records are not optional — they're what holds the position under audit. Legal review in each relevant state is required before implementation.

Under Cal. Code Regs. tit. 18, § 25136-2(c)(2), the billing-address presumption may be overridden by "the terms of a contract between the taxpayer and its customer, or by the taxpayer's books and records." The use of "or" establishes contracts as an independent override path — not requiring corroborating records, though records strengthen the position.

Can an Out-of-State IP Holding Company Reduce the California Income That Remains?

The sourcing position limits what California can reach. But whatever income remains in California's base — you can still reduce it. That's where entity structure comes in.

Once you've done everything you can on the sourcing side, the next question is: of the revenue California does get to tax, what can you deduct against it?

Based on my reading of IRC § 482 and R&TC § 25137, a California-nexus operating entity can pay arm's-length royalties to an out-of-state IP holding company for the use of proprietary software or patents. Those royalties are deductible expenses, reducing the California entity's taxable income. If the IP holding company is in Texas or another no-income-tax state, the income that flows there isn't taxed at the state level.

For software or patented technology with no known direct competitor, arm's-length royalty rates under standard transfer pricing benchmarks can range from 8% to 30% of gross receipts. Layer in a management services agreement — the Texas entity provides back-office functions, marketing, customer support — and you can shift an additional 5–10% of gross receipts. Together, 15–25% of revenue may be deductible against the California tax base.

On the portion of $6M that California retains nexus over — say $2.5M after sourcing re-allocation — a 20% combined deduction is $500,000 shifted. At 15% blended rate: approximately $75,000 in additional annual reduction.

The catch is unitary combined reporting. Under R&TC § 25101, if the FTB determines the California and Texas entities are functionally integrated — shared management, shared customers, common ownership with integrated operations — California can pull everything back into one combined return and disallow the intercompany deductions entirely.

Substance is not optional. The Texas entity needs its own employees doing real work, its own bank accounts, its own contracts with third parties. A shell that exists only to receive intercompany checks will not survive FTB scrutiny.

The IP structure question comes up frequently in our fractional CFO engagements — it's the kind of structural decision that needs to be made before revenue scales, not after the FTB notice arrives.

Risk disclosure: This is an aggressive to unsettled position depending on execution. Requires a formal transfer pricing analysis, properly documented intercompany agreements, and review by a qualified tax attorney in Texas and California before any structure is put in place.

Under IRC § 482 and R&TC § 25137, related-party transactions must reflect arm's-length pricing. FTB can reallocate income if royalty or management fee rates are not defensible against market comparables. Under R&TC § 25101, California can force combined reporting if entities are found to be unitary.

California's reach is broad. But broad isn't the same as unlimited. The code tells you exactly where the line is — and exactly what documentation you need to stand on your side of it.

What Happens If the FTB Challenges Your Sourcing Position?

Most people planning these structures think about the upside. What most advisors don't walk clients through is what an FTB challenge actually looks like — and how it gets resolved.

In my experience, FTB challenges on multi-state sourcing positions don't start with a phone call. They start with a piece of mail.

A notice arrives — typically a request for information or a proposed assessment — and you have a window to respond in writing with your documentation and legal position. Most cases get resolved at that level. The FTB picks a position, you respond with your contracts, your customer certifications, your service address data, and your legal analysis. If the documentation is solid, the case closes.

The ones that don't close at the notice level escalate to the Office of Tax Appeals. OTA is a formal administrative process — written briefs, panel review, a record that matters if things go further into the courts. It is not fast and it is not cheap. But it is the correct venue for complex structural questions where the legal argument has genuine merit.

The pattern I've seen across 25 years of California tax controversy: the FTB picks a position and waits to see if you have documentation or if you fold. The clients who fold are usually the ones who built the structure on paper and hoped no one looked closely. The clients who hold are the ones who had the substance — the agreements, the certifications, the records — before the notice arrived.

Here's what the FTB focuses on when they challenge a sourcing position:

• Economic reality vs. contract language. Does the customer actually use the service outside California? If 80% of your California-billed customers are physically operating in California, the contracts won't hold on substance-over-form grounds.
• Service address substantiation. Do you have service addresses on file? Annual certifications? Call detail records? The FTB will ask for all of it.
• Margin integrity for IP structures. If the California-nexus entity shows near-zero margins after intercompany payments, FTB will argue the pricing isn't arm's-length and reallocate income back.
• Unitary determination. Are the California and out-of-state entities genuinely separate, or functionally the same business with different addresses?

In my experience, the clients who survive FTB audit on sourcing positions are never the ones who had the most aggressive contracts. They're the ones who had the most complete records. A TOS clause is a starting position. Customer certifications, service address data, and call routing logs are what hold it.

Under IRC § 482 and R&TC § 25137, the burden of proof rests with the taxpayer to demonstrate that intercompany pricing is consistent with arm's-length standards. For sourcing positions, the FTB applies a substance-over-form standard — economic reality governs, not contract language alone.

Frequently Asked Questions

Does my SaaS company owe California income tax if I'm based in Texas?

Possibly. Under R&TC § 23101(b), California's economic nexus standard means you're considered "doing business" in California if your California sales exceed $654,321 (2025 threshold) or 25% of total sales — regardless of where you're physically located. Once nexus exists, California taxes the portion of revenue it can claim under its market-based sourcing rules. The key question isn't whether you owe — it's how much of your revenue California can actually reach.

Can contract language override California's default income sourcing rules for SaaS?

Based on my reading of Cal. Code Regs. tit. 18, § 25136-2(c)(2), yes — contracts can independently override the default billing-address presumption. The regulation uses "or," separating contract terms and books and records as two distinct override paths. If your Terms of Service require customers to represent that the service is accessed and the benefit received outside California, that contractual provision may be sufficient to re-source the revenue. This is an aggressive position that requires legal review before implementation.

Can an out-of-state SaaS company use an IP holding company to reduce California taxes?

In theory, yes. If the California-nexus entity pays arm's-length royalties to an out-of-state IP holding company under IRC § 482 and R&TC § 25137, those payments reduce the income California can tax. The structure requires real substance in the out-of-state entity — its own employees, bank accounts, and decision-making — or California will collapse it under unitary combined reporting rules. Legal counsel in each state is required before implementation.

What is California's economic nexus threshold for SaaS companies in 2025?

Under R&TC § 23101(b), a business is "doing business" in California if its California sales exceed the lesser of $654,321 (2025 indexed threshold) or 25% of total sales. This applies regardless of physical presence — no office, no employees, no servers in California required. For a SaaS company with even a modest California customer base, economic nexus is almost inevitable once you cross these thresholds.

What happens if the FTB challenges my income sourcing position?

FTB challenges typically arrive by mail — a notice requesting information or proposing an assessment. You respond in writing with your documentation and legal position. Most cases get resolved at that level. More complex disputes escalate to the Office of Tax Appeals, which is a formal administrative process involving written briefs and panel review. The clients who hold their position are the ones who built their documentation before the notice arrived, not after.