Tax execution
Read the exact action guide for prerequisites, identifier discovery, supported input, effects, captured successful and refused responses, verification and recovery. Synthetic fixture results do not authorize a live mutation or establish a provider outcome.
- List tax rates: List the workspace tax codes effective on a date, or request their complete effective-dated history for tax settings.
- Create tax rate: Add one effective-dated tax code with one or more ordered components. Later components can compound on the tax already calculated.
- Update tax rate: Change one tax code record, including its ordered components, effective percentage, classification and dates. Stored document tax amounts are not rewritten.
- Archive tax rate: Archive one tax rate record so new documents cannot select it; existing documents retain their stored tax.
- Restore tax rate: Restore an archived effective-dated tax rate for selection on documents whose issue date falls in its range.
Evidence
Actual Books route handlers and the exported Worker were exercised against five local SQLite D1 concern databases with all committed migrations, the real posting Durable Object and local R2. Route captures use synthetic verified Auth; Worker captures use synthetic Auth transports. Nexus, Brand, Notify, Pay, Mercury and Xero responses are explicitly simulated at the provider transport boundary. Captures prove local request/response behavior and canonical SDK projection, not live bank access, payment movement, email delivery, provider eligibility, tax compliance, encrypted custody, scheduled execution, deployment or production completion. Fixture identities, credentials, addresses and records authorize no live operation.