Niches · Tax calculation & compliance

Record a final sale, refund or correction for filing

One company's docs show a full fit.

1companies, full fit
9companies, fit with a limit
10companies carry the tag
18share of the category's work
5first-hand accounts

What counts as done

The transaction recorded once under the caller's id (a retry returns the same record), refunds and corrections linked to the original, and a clear error when the period is already filed, naming the route to correct it.

How agents ask for it: record this sale for tax, the invoice is final, commit it, refund the tax on this return, fix the tax on last month's invoice

Does the job 1

The docs show it meets the test above, and nothing we read says otherwise.

ListingWhy
Anrok B
Anrok, Inc.
createOrUpdate records under the caller's transaction id and overwrites on a repeat; createNegation reverses, void cancels, and a filed transaction returns transactionFrozenForFiling, with negation plus a new id as the documented correction. source

Does the job, with a limit 9

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

ListingWhy
Avalara AvaTax BB
Avalara, Inc.
CreateOrAdjustTransaction is documented for idempotent creates by code, RefundTransaction links refunds, and a filed transaction returns CannotModifyLockedTransaction. acc-13 found adjustTransaction failing silently through the JS SDK when the code contained #. source
Fonoa E
Fonoa Technologies Limited
A calculation is committed to revenue tracking by id, and e-invoicing transactions are credited, adjusted or cancelled against the original; a repeated transaction_id is not processed again (context note). No filed-period error is documented because Fonoa does not file returns. source
Kintsugi C
Kintsugi AI, Inc.
Transactions carry externalId, a repeat with the same externalId and source returns the stored record (context note), and credit notes link refunds to the sale. Creates answer 202, and no filed-period lock error or correction route was found. source
Numeral D
Numeral Two, Inc.
POST /tax/transactions records the sale under reference_order_id, POST /tax/refunds and refund reversals link to it. Idempotency-Key is ignored, so retry safety rests on the duplicate-order error (context note), and no filed-period error or correction route was found. source
Quaderno C
Recrea Systems, SL
POST /transactions records a sale, credits link refunds to the invoice and invoices are corrected by credit note (DELETE returns 410). There is no idempotency key, so a retry needs a lookup by processor_id first, and no filed-period error is documented. source
TaxCloud D
The Federal Tax Authority, LLC (d/b/a TaxCloud)
carts/orders converts a cart into a filed order, refunds take an idempotencyKey that returns the original refund, and void frees the orderId. Converting the same cart twice creates a duplicate liability, and voids close at midnight Eastern on the 10th of the next month with 422. source
TaxJar C
TPS Unlimited, Inc. (d/b/a TaxJar, a wholly owned subsidiary of Stripe, Inc.)
Orders are created under the caller's transaction_id and a repeat returns 422, refunds reference the original, and PUT updates. No filed-period lock or correction route is documented, and acc-20 saw an ERP invoice fail when recalculated TaxJar rows tripped validation. source
Vertex O Series D
Vertex, Inc.
INVOICE posts to the Tax Journal under the caller's transaction id, with reversal, rollback and delete by id. No idempotency key: the agent calls transaction-exists before retrying, and Cloud reversals close 90 days after calculation (context note). source
Zamp D
Zamp Inc.
POST /transactions with the caller's id (25 characters) returns 409 CONFLICT on a repeat, and refunds are new transactions with parentId. No filed-period lock or correction route was found, and DELETE removes a transaction permanently. source

What stops agents finishing

  • no idempotency key, so a retried commit can double a liability
  • filed-period lock with no documented correction
  • billing system rejects the tax provider's response (acc-21)

Around it

Before: tax.checkout-quote, accounting.invoice-final. After: tax.period-report, tax.filing-status.

Where this comes from

Weight 18 of 100 in Tax calculation & compliance: 5 of 29 accounts (acc-13, acc-20, acc-21, acc-02, acc-03); fewer reports than checkout but every filing depends on it

The same as data: /api/v1/use-cases/tax.commit-transaction.json, or the MCP tool get_use_case with id tax.commit-transaction. Other jobs in this category: /api/v1/niches?category=tax.

Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person. A mark says what the docs show, not what a run measured.

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.