AvalaraAvalaraDeveloperDeveloper
  • Productsdown arrow
      Calculations
      AvaTax
      AvaTax Brazil
      AvaTax for Communications
      AvaTax for Excise
      Avalara Tax Content
      E-invoicing
      Activation Service
      Avalara E-Invoicing and Live Reporting
      Brazil
      Brazil Customer Portal
      Tax Compliance (Brazil)
      Tax Central
      Data Staging
      Returns
      Avalara Managed Returns API
      Avalara Property Tax
      MyLodgeTax
      Avalara Returns Excise
      VAT Reporting
      Shared service
      Shared Services
      1099 & W-9
      Avalara 1099 & W-9
      Tax registrations and business licenses
      Avalara License Guidance
      Sales Tax Registrations
      Payroll tax registrations
      Avalara license filings
      ECM
      Exemption Certificate Management
      Avalara Cross-Border
      Automated Tariff Code Classification
      Self-Serve Tariff Code Classification
      Managed and Premium Tariff Code Classification
      AvaTax Cross-Border (Estimator + Calculator)
      Avalara Trade Compliance
      Avalara Trade and Tariff Library
  • Learndown arrow
      Integrations guides
      Refactor guides
      Get certified
  • Get starteddown arrow
      AvaTax 90 days free trial
      Playground
      Become a partner
      Build with Avalara using AI
      Versori Training
  • Developdown arrow
      APIs
      SDKs
      MCPs
      Agent to Agent (A2A)
      AI use cases
      API versioning
  • Resourcesdown arrow
      UTCS
      Avalara NEXT recordings
      Avalara Tech Talks
      Avalara University
      Knowledge Center
  • Support
MENU
Search Icon

No results found for

Profile
  • Sign In
Sign In
Search Icon

No results found for

  • Productsdown arrow
      Calculations
      AvaTax
      AvaTax Brazil
      AvaTax for Communications
      AvaTax for Excise
      Avalara Tax Content
      E-invoicing
      Activation Service
      Avalara E-Invoicing and Live Reporting
      Brazil
      Brazil Customer Portal
      Tax Compliance (Brazil)
      Tax Central
      Data Staging
      Returns
      Avalara Managed Returns API
      Avalara Property Tax
      MyLodgeTax
      Avalara Returns Excise
      VAT Reporting
      Shared service
      Shared Services
      1099 & W-9
      Avalara 1099 & W-9
      Tax registrations and business licenses
      Avalara License Guidance
      Sales Tax Registrations
      Payroll tax registrations
      Avalara license filings
      ECM
      Exemption Certificate Management
      Avalara Cross-Border
      Automated Tariff Code Classification
      Self-Serve Tariff Code Classification
      Managed and Premium Tariff Code Classification
      AvaTax Cross-Border (Estimator + Calculator)
      Avalara Trade Compliance
      Avalara Trade and Tariff Library
  • Learndown arrow
      Integrations guides
      Refactor guides
      Get certified
  • Get starteddown arrow
      AvaTax 90 days free trial
      Playground
      Become a partner
      Build with Avalara using AI
      Versori Training
  • Developdown arrow
      APIs
      SDKs
      MCPs
      Agent to Agent (A2A)
      AI use cases
      API versioning
  • Resourcesdown arrow
      UTCS
      Avalara NEXT recordings
      Avalara Tech Talks
      Avalara University
      Knowledge Center
  • Support
Profile
  • Sign In
Sign In
Sales (877) 282-5585
UTCS
Overview
Key takeaways
What UTCS is
How it works for developers
What it means for the market
Why Avalara is building it in the open
What developers can do now
FAQ
UTCS: What the new standard means for developers
Agents can check out. Can they comply?

AI agents now discover products, negotiate carts, and authorize payments on their own. The Universal Commerce Protocol (UCP), Agentic Commerce Protocol (ACP), and Agent Payments Protocol (AP2) made that possible, but each leaves a gap when it comes to tax compliance.

UCP carries tax as a single integer in its totals array. ACP declares tax out of scope. AP2 mandates have no notion of tax at all, and card-network agent-pay schemes don't touch it. The protocols sensibly built the parts that demo well first. But tax determines whether a transaction can legally close, and when agents execute thousands of orders an hour, a compliance error doesn't stay small. It accumulates at machine speed.

Key takeaways
  • A common layer for agentic commerce: Rather than forcing emerging commerce protocols to rebuild tax engines from scratch, UTCS provides a shared, protocol-agnostic compliance layer across UCP, ACP, AP2 and any other protocols.
  • Built for developers and AI agents: Ships with open JSON Schemas, OpenAPI 3.1 definitions, and native Model Context Protocol (MCP) tool bindings designed for automated discovery and machine-readable error recovery.
  • Open interface, trusted content: The UTCS specification is free and open-source under Apache 2.0, giving developers portability while allowing tax determination to run against proven, production-grade regulatory content.
 
What UTCS is

The Universal Tax Compliance Standard (UTCS) is a proposed open, protocol-agnostic standard for how tax compliance is performed in agentic commerce. Rather than asking every commerce protocol to rebuild jurisdiction lookup, determination, exemptions, and reporting, UTCS defines a horizontal compliance layer that any of them can call.

Think of it the way DNS relates to HTTP and SMTP. Those protocols depend on name resolution, but neither re-implements it. UTCS aims to play the same role for tax compliance: one shared layer, with many protocols on top. The specification is free and open under Apache License Version 2.0, so any provider can implement it and achieve full conformance.

 
How it works for developers

UTCS operates as a standalone core with protocol bindings underneath it. The core owns a canonical data model, REST and MCP transport bindings, an OpenAPI 3.1 definition, and a discovery manifest. Each commerce protocol is then expressed as a binding, starting with a UCP tax extension (dev.ucp.shopping.tax) and followed by ACP and AP2.

The v1.0 draft ships as concrete artifacts: JSON Schemas, OpenAPI 3.1, MCP tool definitions, a Streamlined Sales Tax (SST) profile, a UBL mapping for e-invoicing, and the UCP binding, complete with worked core and UCP binding examples that validate against the schemas. MCP is the most agent-native transport: agent frameworks can discover and call UTCS capabilities directly as tools.

A few design choices matter most in practice:

  • One call to start. Send addresses and line items; get back a full per-line, per-jurisdiction tax breakdown.
  • Preview vs. commit. A calculation at order time is advisory. The committed record, created when the order completes, carries attestation and compliance metadata.
  • Accuracy over availability. UTCS never returns a guess or a fallback rate. If tax can't be determined, the error says why and tells the agent how to fix the request.
  • Real-world edge cases. The model covers document types, marketplace liability, discount allocation, the non-taxable vs. exempt split, and flat statutory fees such as Colorado's retail delivery fee.

Phase 1 covers agent-facilitated consumer e-commerce; VAT, filing, and cross-border duty follow in later phases.

 
What it means for the market

McKinsey projects agentic commerce could reach $3–5 trillion globally by 2030. A shared standard means a developer integrates compliance once and reaches every protocol their agents use, instead of wiring tax separately into each checkout flow. Merchants get portability: any conformant provider can sit behind the interface.

 
Why Avalara is building it in the open

Our view is simple: the interface should be free, open, and portable across the entire ecosystem. Avalara is contributing to the initial specification based on what we have spent 22 years building. Millions of taxability rules, jurisdiction data for 190+ countries, exemption certificate networks, e-invoicing formats, and filing content.

An open standard invites the entire developer ecosystem to participate. Protocol creators (like UCP and ACP) refine bindings, agents and platform developers test real-world checkout edge cases, and tax providers build interoperable implementations without vendor lock-in.

We also don't think one company should own a compliance standard. Avalara will maintain the spec during its early period, with enhancement proposals open to a minimum 30-day community review, a public conformance test suite, and a planned move to a neutral standards body once it's stable and adopted.

 
What developers can do now

Check out this GitHub repo.

Universal Tax Compliance Standard on GitHub

If you're building agents, checkouts, or commerce protocols, read the draft spec and run the worked examples against your own flows. Tell us where the model breaks. A standard is only as strong as the edge cases its community surfaces, and the best time to shape one is before v1.0 is final.

 
FAQ

What concrete artifacts are included in the UTCS v1.0 draft?

The v1.0 draft ships with JSON Schemas, an OpenAPI 3.1 definition, MCP tool definitions, a Streamlined Sales Tax (SST) profile, a UBL mapping for VAT, and the UCP binding (dev.ucp.shopping.tax), complete with validated worked examples for both the core protocol and the UCP extension.

What scope does Phase 1 cover, and what is planned for future phases?

Phase 1 covers agent-facilitated consumer e-commerce. B2B transactions, tax filing, and cross-border duty will follow in later phases.

How does UTCS handle errors if an agent submits incomplete cart or location data?

UTCS prioritizes accuracy over availability and never returns estimated fallback rates or guesses. If tax cannot be determined, the response returns a structured error explaining the exact issue and providing actionable guidance so the calling agent can resolve the missing data before checkout closes.

Knowledge CenterDeveloper Support
Avalara.com|Terms of Use|Privacy Policy
© 2026 Avalara, Inc.