# Pull a period's transactions to reconcile or file elsewhere

> Pull a period's transactions to reconcile or file elsewhere: 2 companies fully do it, 6 with a limit, 10 carry the tag. Every listing in Tax calculation & compliance with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/tax.period-report/
- Markdown: https://www.anchorterminal.com/niches/tax.period-report/index.md (~1,100 tokens)
- Slim: https://www.anchorterminal.com/niches/tax.period-report/index.min.md (~280 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/tax.period-report/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

Two or three companies' docs show a full fit.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 2 | 6 | 10 | 10 | 4 |

## What counts as done

Every committed transaction in the period with jurisdiction, taxable amount and tax, paged to the end, or a report broken down by jurisdiction that totals to the same figures.

How agents ask for it: export last quarter's tax transactions; how much VAT did we collect in Germany; reconcile tax collected with Stripe; give me the OSS report

## Does the job

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

- **Kintsugi (Kintsugi AI, Inc.)**: GET /v1/transactions filters by date range, status (COMMITTED), refund and exemption status with paging; the default window is the last 12 months, so the agent must set dates.
- **Quaderno (Recrea Systems, SL)**: POST /reporting/requests runs a tax_summary, invoices_list or credits_list report for a date range, with state pending, succeeded or failed and a download URL when ready; invoice lists also page with created_before and limit up to 100.

## Does the job, with a limit

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.

- **Anrok (Anrok, Inc.)**: transactions/list pages committed transactions with filters including filing association, but it is a premium feature enabled on request.
- **Avalara AvaTax (Avalara, Inc.)**: ListTransactionsByCompany pages with top up to 1,000 and skip, and ExportDocumentLine report tasks export lines. acc-14 found the SDK's nextLink paging broken, and report exports are limited to 5 calls a minute (context note).
- **Fonoa (Fonoa Technologies Limited)**: GET /v1/transactions searches submitted e-invoicing transactions; whether it pages committed calculations by period with jurisdiction totals was not read.
- **Numeral (Numeral Two, Inc.)**: The REST API has no list-transactions call; the MCP reads transactions with per-jurisdiction tax and aggregated sales by month and destination, read-only, with paging limits not read.
- **TaxJar (TPS Unlimited, Inc. (d/b/a TaxJar, a wholly owned subsidiary of Stripe, Inc.))**: GET /v2/transactions/orders and refunds take a date range but return only transaction ids, so totals need one show call per order, each counting against the plan.
- **Zamp (Zamp Inc.)**: GET /transactions pages with limit up to 100 and nextCursor, but returns only transactions written with the same API key, so connector-synced sales are missing.

- not this job: TaxCloud (The Federal Tax Authority, LLC (d/b/a TaxCloud)): Orders are read one at a time by id; there is no list or report endpoint for a period.
- not this job: Vertex O Series (Vertex, Inc.): No list or report endpoint for posted transactions in this API; the Tax Journal is read through O Series reporting outside it.

## What stops agents finishing

- list transactions is a premium feature enabled on request
- report export limited to a few calls a minute

## Around it

Before: tax.commit-transaction. After: accounting.reconcile, spreadsheets.write-rows.

## Where this comes from

Weight 10 of 100 in Tax calculation & compliance: 4 of 29 accounts (acc-02, acc-03, acc-14, acc-27); sellers who file some returns themselves rebuild reports from transactions

As data: https://www.anchorterminal.com/api/v1/use-cases/tax.period-report.json, or the MCP tool get_use_case with id tax.period-report. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
