Avalara

View saved version →

---
name: avalara
description: Review and manage Avalara AvaTax transactions, exemptions and certificates, nexus, Managed Returns, filing calendars, and reports through the Avalara portal in desktop-local Work or browser-enabled desktop Codex. Use for Avalara account review, troubleshooting, and requested changes, with explicit approval for consequential actions. Not for unrelated tax portals, Avalara API or MCP integration, or tax advice.
---

# Avalara

Use the Avalara portal through the supported local browser. Browser interaction is the
intended implementation; do not substitute an API or MCP integration. Available workflows
depend on the signed-in product, company, role, and permissions.

Support the user's compliance work without providing tax or legal advice, certifying a
filing, or attesting that a calculation is correct. Use the user's or authorized tax
owner's determinations for exemption eligibility, jurisdictions, effective dates, and tax
treatment. A request to review, investigate, explain, or draft does not authorize changes.

## Operating mode

Live account access requires desktop-local Work or desktop Codex with a supported local
Browser runtime. Confirm the execution target from explicit runtime context; a desktop
window or a tool named `local` does not establish local execution. Web, mobile, and
cloud-backed tasks are unsupported for live access, even with a signed-in cloud browser.

In Chat or an unsupported or unverified runtime:

- Answer explanations and analyze user-supplied material directly; no handoff is needed.
- For live work, direct the user to ChatGPT Desktop with local execution or browser-enabled
  desktop Codex. Use an exposed native Work handoff only when its live schema and explicit
  runtime context establish a supported desktop-local destination, before starting account
  work. The tool supplies the mode-choice confirmation; do not repeat it in prose.
- Resume only after acceptance and verification of the desktop-local target. Preserve
  company, product, period, and jurisdiction scope. A mode switch authorizes nothing else.
- If the handoff is unavailable, inapplicable, or fails, explain the supported setup. If
  declined, do not repeat the offer that turn. Do not start sign-in or account work in an
  unsupported runtime.

In desktop-local Work or desktop Codex, skip the handoff. Load the available Browser skill
before browser actions and follow its runtime documentation, authentication guidance,
approvals, and site restrictions. Use the supported local browser, such as IAB; preserve
the user's chosen browser, tab, account, and environment. Do not substitute a cloud browser
or copy sessions into another runtime. If access is unavailable or disallowed, explain
the specific limitation and supported path without bypassing policy or inventing tools.

## Sign in and establish context

Before sign-in or account work, read [data handling](references/data-handling.md) and
[context verification](references/context-verification.md). Before selecting a portal,
read [portal surfaces](references/portal-surfaces.md). Reuse a matching tab or the user's
explicit official URL. The portal reference identifies production, sandbox, and official
product sign-in routes; never guess a product URL or silently change environments.

Use secure authentication or manual handoff. In IAB, show and preserve the tab through
the documented handoff lifecycle. End the turn for user-controlled sign-in or MFA; do
not inspect or interact during authentication. Resume only when the user asks, then
verify the final page. Credentials, codes, cookies, and session tokens stay in the browser.

Confirm environment, account, company, product, and role before reading records. Use the
smallest useful period, jurisdiction, and record scope. Ask about missing or conflicting
context without browsing other companies to resolve it. Recheck context before every write.

## Load the relevant workflow

Read only the references needed for the tas

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 10 — file references are metadata, not package contents.