What the Beeline Ruling Means for AI Agents Selling Bundled SaaS in New York

A Forvis Mazars analysis published this week (April 23) walks through the New York Appellate Division's January 15 decision in Matter of Beeline.com, Inc. v. N.Y.S. Tax App. Trib. (CV-24-1494, 3d Dep't). The ruling itself is a few months old. The reason it is back in front of practitioners — and the reason AI agent operators with New York customers should care — is that the analysis layer is finally catching up to what Beeline actually constrains: the "primary function" defense for bundled SaaS-plus-services transactions.

If your AI agent invoices a New York customer for what you call a "research service," "managed analytics service," or "consulting deliverable," and that service is delivered through a hosted software interface or an API your customer is licensed to access, Beeline is now the case the New York Department of Taxation and Finance will lean on when they assess you.

The Facts

Beeline.com sells a vendor management system (VMS) — a hosted platform that helps enterprises source, onboard, manage, and pay temporary labor. Customers do not download anything. They pay subscription and transaction fees to use Beeline's platform alongside human-delivered onboarding, account management, and consulting services that come with the contract.

Beeline argued that what it actually sells is a labor management service. The VMS, in its framing, was the delivery mechanism, not the product. Under the True Object Test (which New York calls the "primary function" test), the predominant purpose of the transaction was service, not software.

The Tribunal disagreed. The Appellate Division affirmed.

What the Court Held

Three findings drive the outcome:

• Granting access to prewritten software is a transfer of tangible personal property. Even though customers never received a download or a physical copy, Beeline granted them the right to use the VMS. New York has classified prewritten computer software as TPP since the 1990s, and that classification reaches hosted access. NY Tax Law § 1101(b)(6).

• The software was not custom. Beeline argued the VMS was customized for each client's onboarding workflow. The court pointed to the contract language: the underlying VMS code was not modified, and customers used it in a "standard fashion." Configuration is not customization. That distinction matters.

• The "primary function" defense was constrained, not eliminated. The court did not throw out the True Object Test. It held that on these facts, the VMS was central — not incidental — to the services. Once the software is the primary delivery mechanism through which the value flows, bundling additional services around it does not unbundle the tax.

The Tribunal had reached the same conclusion in 2024. The Appellate Division's affirmance is now binding precedent in the Third Department, with persuasive weight statewide.

Why This Matters for AI Agents

AI agents sit squarely in the bundle. A typical agent revenue model looks something like this:

• Customer signs a master services agreement

• Customer pays a monthly subscription for "access" plus per-call charges for "AI processing"

• Optional add-ons: "managed prompt engineering," "model fine-tuning consulting," "custom workflow integration"

• The whole thing runs through an API or a hosted dashboard

If your customer is in New York, every one of those revenue lines just got harder to characterize as nontaxable services.

Three concrete risk patterns:

1. SaaS dressed as a service. If the API access is the actual deliverable and the "consulting" or "managed service" wrapper exists primarily to support customer use of the platform, Beeline says the entire bundle is taxable as prewritten software. The Section 1101(b)(6) classification reaches the wrapper.

2. Per-call AI inference invoiced as data processing. New York has historically treated data processing services as nontaxable when they meet the criteria of TSB-A-15(7)S and similar guidance. Beeline narrows the daylight: if the customer is actually paying to access the model (which is software) rather than to receive a discrete output that the seller produced through its own staff, the data processing characterization gets harder to defend.

3. Custom-development carve-outs are narrow. If you offer "custom AI agent development" alongside a hosted platform, the carve-out for custom software (NY Tax Law § 1115(o)) only protects the portion of the contract that is genuinely custom development, separately stated, and does not give the customer ongoing rights to standard platform code. Configuration of standard models for a client's use case is unlikely to qualify.

What New York Will Argue

If New York audits an AI agent operator post-Beeline, the playbook is now well-rehearsed:

• "Your customer pays to access your hosted software." Yes.

• "Your customer uses your software in a standard fashion to obtain its outputs." Almost always yes.

• "The services you describe in the contract are ancillary to the customer's use of the software." This is where the operator either has substance or doesn't.

The defense the court accepted in Beeline's favor — none — is instructive. Operators who want to preserve a primary-function argument need contracts, invoices, and operational reality that show the human-delivered or output-delivered service component is genuinely the predominant purpose. Generic "managed service" language stitched around a SaaS subscription will not survive contact with auditor scrutiny.

Practical Action Items

For any AI agent operator with New York customers or a reasonable expectation of New York customers in the next twelve months:

• Re-read your standard MSA and order forms. Look for language that contradicts the substance. If your contract says the customer is paying for "access to the AgentCo Platform," do not also tell auditors the platform is incidental.

• Separate stated services from access. If you sell genuine human-delivered services alongside platform access, separately state and price them. Bundled invoices favor the state.

• Map your revenue lines to a tax classification. Each line: TPP-equivalent (SaaS access), nontaxable service, custom development, or data processing. Document the position with a memo.

• Reserve appropriately on the bundle. When in doubt, reserve at the combined NY state-plus-local rate (up to 8.875% in NYC) for the gross bundle, not just the line you have characterized as software. AgentTax defaults to the higher reserve when the classification is contested.

• Watch the AgentTax Decision Center. The "true object test" question is one of the policy positions we surface as a "watch" item — the law is developing, and Beeline is the most recent data point. We will not pick the position for you, but we will tell you what the engine is assuming and let you change it.

What to Watch Next

The Third Department decision is binding within its district. New York's First, Second, and Fourth Departments have not yet weighed in on a fact pattern that squarely tests the same question for an AI agent platform. Expect the Department of Taxation and Finance to push the Beeline framing in audits across all departments before the next case resolves the split (if there is one).

The harder question — whether NIST's AI agent standards work or any future federal preemption changes how states classify AI-mediated transactions — is years away. For New York-exposed AI operators, the planning question is now, not later.

For the engine view of how AgentTax classifies bundled SaaS-plus-service transactions in New York, run the calculation against https://agenttax.io/api/v1/calculate with state: "NY" and category: "saas" or "data_processing" and compare. Sign up at agenttax.io to get an API key with 100 free calls per month.

This analysis is for informational purposes only and does not constitute legal or tax advice. Consult a licensed tax professional for compliance decisions.