Check a transaction's tax line by line in AvaTax

**Objective:** Review the tax on AvaTax transaction `{transaction-code}` and flag anything that looks wrong. If `{company}` is given, restrict the search to that company.

**Step 1: Find the transaction**

Call `avalara-avatax-get-transaction` filtered by `code` = `{transaction-code}` (and `company` if provided). If it matches more than one transaction, list the matches (code, company, document-type, date, status) and stop so the user can choose.

**Step 2: Read the lines**

Take the transaction `id` and call `avalara-avatax-get-transaction-line` with `transaction-id` set to it.

**Step 3: Check the numbers**

* Do the line `line-amount` values add up to the header `total-amount`, and the line `tax` values to `total-tax`?
* Flag lines with `tax` of 0 where `taxable-amount` is above 0 and `exempt-amount` does not explain it.
* Flag lines with an `exemption-number` but no exempt amount, and lines with no `tax-code`.
* Flag a `discount-amount` that exceeds the line amount.

**Step 4: Report**

Give a header summary (code, document-type, status, customer-code, date, totals), a table of the lines with their tax, and a list of findings ranked by size. End with a one-line verdict: looks right, or needs review and why.

**Validation:**

* If nothing matches `{transaction-code}`, say so and suggest checking the company and whether the code is spelled as in the source system.

**Rules & Guidelines:**

* This prompt is read-only. Call only the `avalara-avatax-get-*` tools named above. Never call any avalara-avatax tool that adds, updates, deletes, commits, uncommits, voids, unvoids, adjusts, refunds, locks, settles or creates anything.
* Report what the data shows. Do not guess values the tools did not return, and say so when a field came back empty.
* Use `max-records` to keep each read small, and say when a result may be truncated by it.