Is SaaS taxable in New York, and where is it used?
Edvin Givargis Published 5 minute read
The short answer
Yes, and where the users are. New York taxes sales of prewritten computer software, and its statute defines prewritten software as tangible personal property regardless of the medium by which it is conveyed, a definition written broadly enough that the Department has long applied it to software nobody conveys at all: the customer who logs into a vendor's platform is treated as receiving a license to use software, constructive possession of it, and the subscription fee is a taxable receipt even though nothing was downloaded and the servers sit in another state. For a software-as-a-service business, especially one headquartered far away selling into New York accounts, this produces the least intuitive sales tax exposure in its footprint: a company with no New York office, inventory, or shipments owes collection on its New York subscriptions once nexus exists. The measure question is where the modern fights actually happen. The taxable portion of a subscription is the portion used in New York, which the Department locates at the users, the seats, the people logging in, not at the billing address on the invoice, and the divergence between the two runs in both directions: a Manhattan-billed contract whose users all sit elsewhere is largely or entirely outside the tax, while a Connecticut-billed contract with a Manhattan user base is largely inside it. The sellers who get this right treat user location as a data field to be captured at sale, not a fact to be reconstructed under audit.
What is taxable, and what the invoice can separate
The platform subscription is the core taxable item: the recurring fee for access to the software, however the invoice denominates its quantity, months, seats, or a single annual line. Around it cluster charges that are not taxable when they are genuinely distinct and separately stated: professional services, consulting, custom research and analysis, implementation work that is not itself the sale of software, and similar service lines, which New York does not generally tax. Two disciplines keep the distinction alive. First, separation on the invoice: a single bundled price for platform plus services is an invitation to tax the whole charge, because an undifferentiated receipt takes the character of its taxable component in the examiner's hands, while separately stated service charges, priced with commercial reality, keep their own character. Second, honesty about primary function: relabeling the platform fee as a service does not change what the customer is buying, and descriptions on invoices are the first thing an auditor reads; the seller's product catalog, contracts, and invoices should tell one consistent story about which lines are access to software and which are human work, because inconsistency is resolved expensively. Custom software written for a single customer sits outside the prewritten definition entirely, but the exception is narrow and the modifications-to-standard-platform fact pattern rarely reaches it; a configured instance of a standard product is still prewritten software.
The user-location measure, and the billing-address trap
Where a customer's employees use the software both inside and outside New York, the Department's guidance taxes the portion of the receipt attributable to New York users, which makes the seat map the tax base. Almost no billing system captures it. Invoices carry a bill-to address, often a procurement office or headquarters with no relationship to where the licensed users sit, and both the seller's exposure and the seller's over-collection risk flow from treating that address as the answer. The recurring audit patterns: the seller who never collected anywhere discovers its New York-billed accounts and assumes the worst, though a user-level analysis pulls much of the base out of state; and the seller who collected on billing address discovers it has been taxing customers whose users are elsewhere while missing customers billed elsewhere whose users are in New York. The fix is contractual and administrative rather than legal. At sale, the order form or invoice should require the customer to state where the software will be used, a percentage or seat allocation by state, exactly as the largest software vendors do, and the seller should retain those declarations the way it retains resale certificates, because a customer's contemporaneous statement of use location is the document that both sets the collection and defends it later. Retrospectively, in an audit that has already arrived, the same information is gathered by customer letters, and the companion article on New York software audits covers that machinery, the verification letters that remove out-of-state use and customer-paid use tax from an assessment, in detail.
Practice notes
The compliance architecture for a SaaS seller with New York accounts has four pieces, all cheap relative to the assessment they prevent. Nexus first: post-Wayfair economic thresholds mean the New York collection obligation usually exists well before anyone asks, and the exposure clock runs from first taxable sale, not from discovery, which keeps voluntary disclosure on the table for the seller who is behind. Product taxonomy second: a standing memo mapping every SKU and invoice line to taxable software or nontaxable service, applied consistently in billing, so that the taxability of the catalog is a decision made once rather than invoice by invoice. User-location capture third: the declaration at sale, refreshed on renewal for accounts whose footprint moves, with the arithmetic applied to collection. And invoice hygiene last: separate statement of service lines, quantity fields that mean something, and descriptions an auditor can read without a meeting, because in a receipts tax the invoice is the return's supporting schedule whether or not anyone designed it that way. The seller who builds these four pieces has converted New York from its worst audit exposure into a computation; the seller who builds none of them meets the same rules in the audit posture the companion article describes.
This article states the law as of September 16, 2026
Statutes, rates, thresholds, and agency practice change, and a different set of facts can change the answer. Before acting on anything discussed above, contact G&G State Tax Group to confirm what has changed since this was written and how the rules apply to a specific situation.
G&G State Tax Group, LLC is a state and local tax advisory firm. The firm provides state and local tax consulting and representation in state and local tax controversies. G&G does not prepare or file tax returns, perform attest services, or provide bookkeeping, and is not a CPA firm.