See one collections exposure across NetSuite and Stripe

**Objective:** Show what the customer with email `{customer-email}` owes across NetSuite and Stripe, and how risky the balance is.

**Step 1: NetSuite receivables**

Call `netsuite-get-customer` (netsuite server) with `email` set to `{customer-email}` and take `internal-id`, `name` and `balance`. Then call `netsuite-get-aropenitem` (netsuite server) with `customer` set to the name. Note `document-number`, `due-date`, `amount`, `amount-applied`.

**Step 2: Stripe receivables**

Call `stripe-get-invoice` (stripe server) with `customer-email` set to `{customer-email}` and `status` set to open. Note `number`, `due-date`, `amount-remaining`. Call `stripe-get-customer` (stripe server) with `email` for `delinquent` and `balance`, and `stripe-get-upcoming-invoice` (stripe server) with that `customer-id` for the next bill.

**Step 3: Signals**

Call `stripe-get-charge` (stripe server) with `customer-email` and `status` set to failed, and `stripe-get-dispute` (stripe server) with that `customer-id`, to count recent failures and disputes.

**Step 4: Report**

Give total outstanding in each system, flag any Stripe invoice number that also appears in NetSuite so it is not counted twice, list items past due by age, and state failed charges, disputes and the upcoming invoice. Close with a one-line risk read (low, medium, high) and why.

**Rules & Guidelines:**

* `netsuite-*` tools are on the netsuite MCP server and `stripe-*` tools are on the stripe MCP server. Both servers must be connected.
* This prompt is read-only. Call only the `netsuite-get-*` and `stripe-get-*` tools named above. Never create, update, refund, void or delete anything in either system.
* Pass only filters the tool actually has. Never guess an id.
**Validation:**

* If the customer exists in only one system, report that side only.
* Do not add the two totals when the same invoice appears in both.