See Dynamics GP customers in states with no AvaTax nexus

**Objective:** List the Dynamics GP customers in state `{state}` and report whether Avalara AvaTax shows tax nexus for that state, so the user can see where sales may be going to a jurisdiction the company has not registered in. If `{country}` is empty, use US.

**Step 1: Check nexus in Avalara AvaTax**

Call `avalara-avatax-get-nexus` with `region` set to `{state}` and `country` set to `{country}` (US if empty). Keep `jurisdiction-name`, `nexus-type`, `tax-type-group`, `effective-date` and `end-date`. Treat a nexus record whose `end-date` is in the past as ended. Say plainly whether the state has active nexus, ended nexus, or none.

**Step 2: List the customers in Dynamics GP**

Call `dynamics-gp-get-rm-customer` with `state` set to `{state}` and `inactive` set to false. Keep `customer-id`, `customer-name`, `city` and `customer-balance`. Then call `dynamics-gp-get-rm-sales-trx` for the five customers with the highest `customer-balance`, using `customer-id` and a `document-date.from` of 12 months ago, to show their recent sales and `tax-amount`.

**Step 3: Report**

State the nexus finding first, then the customer count, the five largest customers with their 12-month document totals and tax collected, and a one-line note on whether tax was collected where no active nexus exists.
**Rules & Guidelines:**

* Tools whose names start with avalara-avatax- are on the avalara-avatax MCP server; tools whose names start with dynamics-gp- are on the dynamics-gp MCP server. Both servers must be connected.
* This prompt is read-only. Never call any create, update, delete, add, void, commit, adjust, post or other action tool on either server.
* Report what the two systems show. Do not present results as tax advice or as a filed return.

**Validation:**

* If AvaTax has no nexus record for the state, say that no nexus is on record; do not say the company has no obligation.
* If Dynamics GP has no customers in the state, say so and stop after the nexus finding.