SaaS Gross Receipts Tripwires

If you run a remote SaaS or service business and think state gross receipts taxes are a problem for big box retailers, I have two words for you: think again. States love taxing activity, not profit, and they have gotten very good at deciding your cloud product is their business. This field guide walks you through four frequent fliers that snag remote SaaS companies: Washington B&O, Oregon CAT, Ohio CAT, and Nevada Commerce Tax. We will cover nexus triggers, what counts as gross receipts, how revenue is sourced, practical apportionment moves, and the tripwires that get even seasoned operators sideways.

Washington B&O Basics

Washington’s Business and Occupation tax is a gross receipts tax that applies to the privilege of doing business in the state. For remote SaaS, the key is economic nexus and accurate classification.

Nexus triggers. You have economic nexus if you have more than 100,000 dollars in Washington-sourced gross receipts in the current or prior year. Physical presence also works the old-fashioned way: employees in Washington, owned or leased property, or inventory. Using a third-party data center alone usually does not create nexus by itself, but owning or leasing server hardware in Washington can count as property in-state. Once you cross the receipts threshold or establish physical nexus, you must register with the Department of Revenue and start filing.

What counts as gross receipts. Under B&O, it is the gross income of the business. No deduction for cost of goods sold, hosting, support, R&D, or your heroic burn rate. For SaaS, classification matters. Many cloud-delivered products are treated as digital automated services for retail sales tax, which typically puts the B&O under the Retailing classification. Other subscription or custom services may land in Service and Other Activities. Rate and sourcing rules differ by classification, so do not wing it. If you bill Washington customers for remote access software, support, or bundled services, assume the receipts are taxable unless a clear exemption applies.

Sales tax interplay. If your SaaS is a taxable digital automated service, you may owe retail sales tax collection in addition to B&O. Hitting the same 100,000 dollar sales threshold with Washington customers can trigger both sales tax and B&O. You can have B&O even where the sale is not retail-taxable, so check both fronts.

Sourcing and apportionment. For apportionable activities, Washington uses a receipts factor that relies on market-based sourcing. The default is where the customer receives the benefit. If you are taxable in multiple jurisdictions, you apportion by Washington receipts over total worldwide receipts, with special throw-out rules for receipts not taxable anywhere. If you do not get the sourcing right, you either overpay in Washington or, more painfully, underpay and owe back tax plus penalties.

Pitfalls I see all the time:

- Assuming incorporation in another state sidesteps B&O. It does not.

- Treating remote employees in Washington as a harmless lifestyle perk. That is physical nexus with consequences.

- Misclassifying SaaS and missing sales tax on digital automated services. B&O is not your only exposure.

- Not registering right after crossing 100,000 dollars. The meter starts when you pass the threshold, not when your accountant notices.

Oregon CAT Essentials

Oregon’s Corporate Activity Tax is not an income tax. It is a tax on Oregon commercial activity with a subtraction for certain costs and is aimed squarely at revenue.

Thresholds. There are three steps:

- If Oregon commercial activity is 750,000 dollars or less during the year, you are out of scope and do not register.

- Once you exceed 750,000 dollars, you must register.

- Filing and paying start when taxable Oregon commercial activity exceeds 1,000,000 dollars.

How it is calculated. The tax is 250 dollars plus 0.57 percent of Oregon taxable commercial activity over 1,000,000 dollars. Taxable commercial activity starts with Oregon commercial activity, which is essentially gross receipts from business done in Oregon, and then you subtract 35 percent of the greater of cost inputs or labor costs. That subtraction must be apportioned if you operate in and out of Oregon, generally using the ratio of Oregon commercial activity to everywhere commercial activity. The subtraction cannot reduce more than 95 percent of Oregon commercial activity.

What counts and what is excluded. Commercial activity is the total amount realized from business transactions in the regular course of business. Think subscription fees, implementation services, support, and add-ons. Some items are excluded by statute, such as certain interest income or pass-throughs in agency capacity. Refunds and discounts generally reduce commercial activity only if shown as such to the buyer. If you grant credits or free months, document it.

Sourcing for SaaS and services. Oregon sources service revenue to Oregon when the buyer receives the benefit in Oregon. If your customer is headquartered in Oregon but uses the product across multiple states, you may need usage data or a reasonable method backed by documentation to allocate the benefit. If you cannot track seat-by-seat usage, consider contract terms, billing addresses, or where users log in from, and then apply a consistent method.

Filing rhythm. If you expect to owe 5,000 dollars or more of CAT for the year, Oregon wants quarterly estimated payments. The annual return is due the following year. There is no proration of thresholds in a short year, so a mid-year split still counts the full receipts.

Common misses:

- Waiting to register until you exceed 1,000,000 dollars. Registration kicks in at 750,000 dollars.

- Treating the 35 percent subtraction like a blanket 35 percent. It must be the greater of cost inputs or labor, and then apportioned.

- Mixing up where the benefit is received. Oregon looks to the buyer’s in-state use, not where your team wrote the code.

Ohio CAT Changes

Ohio’s CAT applies broadly but has undergone big threshold changes that are friendly to smaller players while still holding larger sellers to account.

Nexus and bright-line presence. You have CAT nexus if any of the following hits:

- 500,000 dollars or more in Ohio taxable gross receipts during the year

- 50,000 dollars of property in Ohio

- 50,000 dollars of payroll in Ohio

- 25 percent or more of your total property, payroll, or receipts in Ohio

Exclusion thresholds. Here is the twist that trips planning:

- For 2024, if your Ohio taxable gross receipts are less than 3,000,000 dollars, you are not subject to CAT.

- For 2025 and later years, the exclusion rises to 6,000,000 dollars.

So you can have bright-line presence because you cleared 500,000 dollars of Ohio receipts, but if you are still under the exclusion threshold for the year, you owe no CAT and generally have no filing obligation. The state also eliminated the old minimum annual tax as of 2024. Translation: many small to mid-size sellers are out of CAT, at least for now.

What counts as taxable gross receipts. This is the whole amount you receive, before expenses. For services, Ohio uses where the purchaser receives the benefit. If your SaaS primarily supports an Ohio workforce, those receipts are Ohio. If the Ohio parent buys for a multi-state org, you may allocate based on the proportion of usage or benefit in Ohio. Document your method and apply it consistently.

Filing cadence. If you exceed the exclusion threshold, you file returns. Frequency depends on volume, and some taxpayers may file quarterly. Many groups must register on a combined or consolidated basis, so do not silo related entities to duck the bright-line tests. Ohio is not amused by that trick.

Frequent errors:

- Assuming a customer’s billing address drives sourcing. It is about where the value is enjoyed.

- Missing aggregation across related entities that share revenue streams into Ohio.

- Forgetting that crossing 3,000,000 dollars in November still makes the entire year subject to CAT.

Nevada Commerce Tax

Nevada has no corporate income tax, which sounds great until you meet the Commerce Tax. It targets Nevada-sourced gross revenue across industries, with rates tied to NAICS codes.

Threshold and timing. If you have more than 4,000,000 dollars of Nevada-sourced gross revenue in the state fiscal year that ends June 30, you must file and pay Commerce Tax. The return is due 45 days after June 30. If you are under the threshold, no Commerce Tax return is required.

What counts as Nevada-sourced revenue. Revenue from services performed for Nevada customers, sales delivered to Nevada, and other receipts attributable to Nevada. For SaaS, the state will look at where your customer receives the benefit. If your largest enterprise client’s users are all in Las Vegas, that is a Nevada bucket. If usage is multi-state, you can reasonably source based on customer records, user counts, or actual log-in data if available.

Rates by NAICS. Your industry classification sets the rate. Misclassifying yourself can move the rate and lead to back tax. If you are truly a software publisher or data processing host, pick the proper NAICS and keep support for it.

A quick planning note. Commerce Tax paid can generate a credit against Nevada’s payroll-based Modified Business Tax, which can soften the blow for in-state employers. Remote SaaS without Nevada payroll will not see much relief from that credit.

Sourcing And Apportionment Tips

States increasingly use market-based sourcing for services and intangibles, which puts the spotlight on customer benefit. You do not need perfect telemetry, but you do need a method you can explain without sweating.

Start with your contract. What does it say about where the product is used, where users are located, or where services are delivered? If the contract is silent, use billing addresses, usage analytics, seat allocations, or implementation project records. Apply reasonable assumptions, document them, and stick with them.

Mind the differences:

- Washington uses a receipts factor for apportionable activities and has a hierarchy for customer location, benefit, and throw-out if you cannot reasonably determine a state.

- Oregon is laser-focused on where the buyer receives the benefit. Your 35 percent subtraction is apportioned using the ratio of Oregon commercial activity to everywhere.

- Ohio also hinges on benefit location, not where you performed the work or where your servers live.

Keep a matrix of customers by state, annual billings, and any known seat counts or usage shares. For enterprise customers with multi-state footprints, get a representation letter or schedule from the buyer showing intended use proportions. Update annually. If your product is usage-based, export logs by user region once a year and keep them with your return workpapers.

Tripwires And Fixes

Things that blow up SaaS tax positions are boringly predictable:

- Contract year vs calendar year. Washington and Oregon thresholds care about receipts in a measurement year. A single enterprise contract that ramps in Q4 can push you over before you have time to register. Solution: monitor by state monthly and set alerts at 75 percent of each threshold.

- Misclassification in Washington. Many teams put all SaaS in Service and Other Activities and miss retail sales tax on digital automated services. Solution: review product features with WA DOR guidance and pick the correct B&O classification and sales tax treatment.

- Oregon registration timing. You must register once Oregon commercial activity exceeds 750,000 dollars even if you will not owe until you exceed 1,000,000 dollars. Solution: track and register proactively to avoid penalties.

- Ohio benefit blind spots. Out-of-state HQ with an Ohio plant using 70 percent of the seats puts most revenue in Ohio. Solution: map users or revenue allocation at onboarding and refresh annually.

- Nevada NAICS drift. Picking a lower-rate code without support is a penalty magnet. Solution: align your code with your dominant revenue line, keep documentation, and reevaluate if your product mix changes.

- Remote employees. A single Washington-based success engineer or an Oregon-based implementation lead can create physical nexus. Solution: keep a live nexus map of employee locations and contractors.

- Throw-out misunderstandings in Washington. Not all non-sourced receipts are thrown out. Solution: follow the apportionment hierarchy and confirm if you are taxable elsewhere before you toss receipts from the denominator.

Field Notes From Real Audits

The WA misclass trap. A SaaS company billed 3 million dollars to Washington customers and parked everything in Service and Other Activities. Washington said the core product was a digital automated service, which meant Retailing B&O plus retail sales tax on the subscription. Result: back sales tax, B&O reclass, and penalties. The fix would have been to identify taxable DAS up front, collect sales tax, and reserve Service and Other Activities only for non-retail custom services.

The Oregon registration miss. A founder assumed they were safe under 1,000,000 dollars and did not register. They hit 760,000 dollars in Oregon commercial activity by late summer and should have registered within 30 days of crossing. Oregon assessed a penalty for late registration and late estimates once they eventually owed. A simple state-by-state revenue tracker would have prevented it.

The Ohio benefit surprise. A company sold to a Delaware parent that billed out of New York. Usage logs showed 65 percent of users in Ohio manufacturing sites. The company had more than 3,000,000 dollars in Ohio receipts in 2024 and owed CAT, even though no one had ever set foot in Ohio. Documentation tied to the buyer’s user data helped reduce the percentage slightly, but the exposure remained material.

The Nevada rate flip. A software platform self-classified as data processing to grab a perceived lower rate. Audit concluded the NAICS should have been software publisher based on revenue mix and marketing materials. Rate changed, tax recalculated, and an accuracy penalty applied. Careful NAICS selection backed by revenue detail would have avoided the rate fight.

Quick Nexus Threshold Table

State | Tax | Nexus Trigger Highlight | Threshold To Watch

Washington | B&O and sales tax | Economic nexus at 100,000 dollars WA-sourced receipts or physical presence | 100,000 dollars WA receipts in current or prior year

Oregon | Corporate Activity Tax | Doing business in Oregon with commercial activity | Register at 750,000 dollars Oregon commercial activity; tax at 1,000,000 dollars

Ohio | Commercial Activity Tax | Bright-line presence at 500,000 dollars Ohio receipts or property/payroll tests; exclusion applies | 3,000,000 dollars exclusion in 2024, 6,000,000 dollars from 2025

Nevada | Commerce Tax | Doing business in Nevada with NV-sourced gross revenue | 4,000,000 dollars Nevada-sourced revenue in state fiscal year

Apportionment Playbook For SaaS

You do not need a PhD in sourcing to get apportionment right, but you do need discipline:

- Pick a primary sourcing signal. For most SaaS, that is user location or service-benefit location. Secondary signals include billing address or ship-to for tangibles bundled with your subscription.

- Bucket customers. Single-state customers are easy. Multi-state customers need an allocation method, ideally usage or seat counts. If you cannot get hard data, negotiate a reasonable state-by-state usage schedule in the MSA and revisit each year.

- Build a receipts map. Keep a spreadsheet of total gross receipts by state, then an apportionment tab where you calculate state receipts divided by total receipts. Store usage reports, representation letters, and allocation memos with the file.

- Do not commingle categories. Separate digital automated services, professional services, and hardware. Washington classification and sales tax ride on these differences, and Oregon’s subtraction allocation can move with your mix.

- Respect throw-out rules. In Washington, you throw out receipts you cannot assign to any state after following the hierarchy and confirming you are not taxable in any jurisdiction on that receipt. Document your steps.

Practical Implementation Tips

- Forecast thresholds. If sales is about to sign a seven-figure deal with a Seattle logo, tax should know before the ink dries. Add a step to your sales ops checklist that flags big deals by state.

- Automate what you can. Your billing system should capture customer state for each invoice line. If it cannot, your tax exposure is already growing faster than ARR.

- Update NAICS and product taxonomy annually. If you ship a new module that changes your core activity, revisit your classifications and rates.

- Train customer success. The person who knows where the users sit is often not in finance. Give CS a one-page guide that explains why seat maps and implementation locations matter for tax.

- Keep quiet logs, loudly. Your future self will thank you for saving a yearly usage export, a copy of implementation SOWs by location, and a memo on how you sourced your top 20 customers.

FAQ

What if we are under Ohio’s exclusion but over the bright-line presence?

You have nexus, but if your Ohio taxable gross receipts for the year are below the exclusion amount, you generally do not owe CAT or need to file. Track carefully, because one big renewal can push you over the exclusion and make the full year taxable.

Does using AWS or another cloud provider in Washington create nexus?

Using a third-party host by itself typically does not create physical nexus. Owning or leasing your own servers or other property in Washington can. Nexus can also arise from employees or exceeding the 100,000 dollar receipts threshold.

For Oregon CAT, can we take both cost inputs and labor in the 35 percent subtraction?

No. You choose the greater of cost inputs or labor costs, then apportion that subtraction to Oregon using your Oregon commercial activity ratio. The subtraction cannot exceed 95 percent of your Oregon commercial activity.

Is all SaaS subject to Washington retail sales tax?

Not always. Many remote access software products are treated as digital automated services and are taxable for retail sales tax, but some custom services or non-automated elements are not. B&O still applies. Classification is fact-specific and worth confirming with WA DOR guidance.

If our Nevada-sourced receipts jump over 4,000,000 dollars late in the fiscal year, do we only owe on the part over the threshold?

You owe Commerce Tax for the Nevada fiscal year on Nevada-sourced gross revenue at your industry rate. The 4,000,000 dollar amount is a filing and liability threshold, not an exclusion that only taxes the excess.

How do we source multi-state enterprise deals when we do not have usage data?

Use a reasonable, consistent method backed by documentation. Start with seat allocations by location if the customer can provide them. If not, consider employee headcount by state for the covered business unit, implementation site lists, or a representation letter from the customer allocating use by state.

What is the fastest way to get burned in Washington?

Misclassify your SaaS as a pure service, skip retail sales tax on digital automated services, and forget to register after crossing 100,000 dollars. Washington auditors have seen that movie and know how it ends.

Action Plan You Can Start This Month

- Build a 12-month by-state revenue report and set alerts at 75 percent of each threshold: WA 100,000 dollars, OR 750,000 dollars and 1,000,000 dollars, OH 3,000,000 dollars for 2024 or 6,000,000 dollars from 2025, NV 4,000,000 dollars in the state fiscal year.

- Map physical nexus: list employees, contractors, and any owned or leased property by state.

- Decide a sourcing hierarchy for services and SaaS: usage data first, then contract schedules or customer letters, then billing address as a last resort.

- Review Washington product classification: identify any digital automated services subject to retail sales tax and align B&O classification accordingly.

- For Oregon, calculate the 35 percent subtraction with both cost inputs and labor, pick the larger, and apportion it. Set up quarterly estimates if you will owe 5,000 dollars or more.

- For Ohio, review combined or consolidated filing needs across related entities and model the exclusion threshold using benefit-based sourcing.

- For Nevada, confirm your NAICS code and track Nevada usage or customer locations against the July-to-June measurement period.

When in doubt, pull the state guidance:

- Washington DOR nexus and apportionment at dor.wa.gov

- Oregon CAT resources at oregon.gov/dor

- Ohio CAT guidance at tax.ohio.gov

- Nevada Commerce Tax at tax.nv.gov

If this felt like a lot, it is because it is. But it is still far cheaper than a back-tax bill with penalties. Keep receipts flowing, keep sourcing defensible, and let the thresholds work for you instead of against you.