Agent Tax Compliance: Four Things That Phrase Means, and Only One of Them Is Software

Search "agent tax compliance" and you get four unrelated bodies of law wearing the same word. Three of them are terms of art with specific statutory duties and specific people on the hook; the fourth is a piece of software that, as a matter of law, cannot hold any of those duties. Operators building autonomous systems keep landing in the first three by accident, so it is worth setting out what each one actually means and where an AI agent falls out of the frame.

1. Withholding agent — the one that actually bites

A withholding agent is defined by function, not by title. Under Treas. Reg. § 1.1441-7(a) the term means any person, U.S. or foreign, having the control, receipt, custody, disposal, or payment of an item of income of a foreign person subject to withholding. FATCA repeats the formulation at IRC § 1473(4) — any person, in whatever capacity, having control, receipt, custody, disposal, or payment of a withholdable payment. There is no election, no registration, and no threshold. You are one or you are not, based on what you touch.

The consequence is IRC § 1461: every person required to deduct and withhold is made liable for that tax. Not liable to collect it — liable for it. If you fail to withhold on a payment that required withholding, the government's claim runs against you, and whether the foreign payee ultimately paid its own tax is a separate question governed by § 1463.

Now put an agent in the middle of it. An agent operator paying a foreign model provider, a foreign tool API, or a foreign data vendor is making a payment to a foreign person. Whether it is subject to withholding turns on source and character, which is exactly the classification question we walked through in the 2025 Treasury regulations on AI transactions. Compensation for services is sourced to where the services are performed under IRC § 861(a)(3), so a foreign provider performing abroad generates foreign-source income and no § 1441 withholding. But royalties are sourced to the place of use under § 861(a)(4) — rentals or royalties for the privilege of using a copyright or similar property in the United States are U.S.-source. A licensing characterization and a services characterization on the same invoice produce opposite answers.

That distinction was manageable when a procurement team signed four vendor agreements a year. It is a different problem when an agent selects providers at runtime, mid-task, across a fleet, on x402 rails, thousands of times a month. The statutory definition is broad and long settled. Its application to agent-initiated micropayments is untested by any ruling I am aware of, and I would call an operator's ability to reach the right answer credible but untested — defensible with records, not with a policy. The practical exposure is not the 30 percent. It is that § 1461 liability is personal, attaches without notice, and does not care that a machine chose the payee.

2. Enrolled agent — the one an AI cannot be

An enrolled agent is a person enrolled to practice before the IRS under Circular 230 (31 C.F.R. part 10), admitted by examination or qualifying IRS experience. Practice before the Service is limited to the individuals listed in Circular 230 § 10.3 — attorneys, CPAs, enrolled agents, enrolled actuaries, and the rest. Every category is a natural person subject to individual discipline. So is the adjacent authority: Form 2848 grants a power of attorney to a named individual, and Form 8655 designates a reporting agent for payroll deposits and returns with a responsible party behind it.

None of this is a drafting oversight that will be patched. The regime is built on individual accountability, which is why OPR's first AI guidance — Alert 2026-19, issued June 24, 2026 — mapped existing Circular 230 duties onto AI-assisted work rather than creating a new category for the tool. A practitioner may use an AI agent. A practitioner may not become one, and the agent cannot hold the engagement.

3. Agent in the state sales tax sense — the one that decides who collects

State tax uses "agent" in the common law sense, and here the word carries real doctrinal weight. The Restatement (Third) of Agency § 1.01 defines agency as a fiduciary relationship arising when a principal manifests assent that another person act on the principal's behalf and subject to the principal's control, and the agent manifests assent or otherwise consents so to act. Two-way consent between two persons. Software does not consent.

That matters because attributional nexus is built on the agency relation. Scripto, Inc. v. Carson, 362 U.S. 207 (1960), imposed a use tax collection duty on an out-of-state seller based on in-state independent contractors soliciting on its behalf. Tyler Pipe Industries v. Washington State Department of Revenue, 483 U.S. 232 (1987), framed the test as whether activities performed in the state on the taxpayer's behalf are significantly associated with establishing and maintaining a market there. Both turn on what a representative did, and both presuppose that the representative is someone who can act on another's behalf.

An AI agent is not a representative under that framework. It is an instrumentality of its operator, closer to a server or a catalog than to a salesperson — which means the Scripto line neither attaches duties to the software nor, standing alone, attributes its activity to anyone else. That is not the relief it sounds like. Post-Wayfair economic nexus does not need an agency theory to reach a remote seller, so the attribution question rarely decides whether you have nexus. Where it still decides something is the harder case: whether an agent executing on infrastructure inside a state, or transacting through a shared platform, pulls its operator into that state. Our registry carries that as unsettled, and nothing since has moved it. Marketplace facilitator statutes are a separate track — they generally define the facilitator by what it does, not by whether it is anyone's agent, which is why a platform can owe collection duties without any agency relationship at all.

4. AI agent — the one with no duties of its own

Here is the throughline. In all three legal senses, the duty attaches to a person: the person who controls the payment, the person admitted to practice, the person on whose behalf someone acted. An AI agent is none of those, so no obligation ever lands on it. Every duty it generates lands on the operator, undiminished, and usually without the notice a human counterparty would have produced.

There is no IRS or state guidance classifying an AI agent as property, contractor, or employee, and the entire common law worker classification framework presupposes a human. AgentTax's engine defaults to contractor treatment for 1099-NEC tracking purposes, which is a practical bookkeeping default and not a legal conclusion — we treat that question as genuinely open and flag it as unsettled in the product.

What to do about it

Three things, in order of how quickly they will hurt.

Determine whether you are a withholding agent, once, in writing. Inventory your agents' payees. Any foreign vendor is a candidate. Get a valid Form W-8BEN-E on file before the first payment rather than after the first assessment, and record the character and source determination for each provider class. If your agents select providers dynamically, the determination has to be attached to the provider list, not to the transaction.

Do not let "our agent handles compliance" mean anything. It can prepare, calculate, and file through a person's credentials. It cannot hold the credential, and the individual behind it absorbs everything.

Separate the nexus questions. Economic nexus is arithmetic and you should be measuring it. Agency-based attribution is a different, unsettled question that turns on where your infrastructure sits and whose platform you transact on. Conflating them produces confident answers to the wrong one.

What to watch

Whether the IRS addresses withholding-agent status for automated payment systems is the item with the largest dollar consequence, and there is no indication it is imminent. Closer in: any state guidance on whether agent execution inside a state constitutes in-state activity attributable to the operator, and whether marketplace facilitator definitions get stretched to cover agent platforms, which we track as unsettled with HIGH consequence.

AgentTax computes sales and use tax by jurisdiction and tracks 1099 thresholds for agent-operated entities. It does not make § 1441 withholding determinations, and no tax engine should pretend to — that is a character-and-source analysis on your specific vendor contracts. See the per-state logic at agenttax.io, or start with the AI agent sales tax hub.

This analysis is for informational purposes only and does not constitute legal or tax advice. This post reflects AgentTax's current interpretation of evolving law. Consult a licensed tax professional for compliance decisions.