Find Chargebee payments missing from NetSuite

**Objective:** For payments dated between {date-from} and {date-to}, confirm each successful Chargebee payment has a matching NetSuite customer payment. Limit to one customer when {customer-email} is given.

**Step 1: Read Chargebee payments**

If {customer-email} is given, call `chargebee-get-customer` with `email` and take `id`. Call `chargebee-get-transaction` with `date.from`, `date.to`, `status` success, `type` payment (and `customer-id` when known). Keep `id`, `customer-id`, `amount`, `date`, `reference-number`, `gateway`.

**Step 2: Read NetSuite payments**

Call `netsuite-get-customerpayment` with `date.from` and `date.to` (and `customer-email` when given). Keep `document-number`, `customer-email`, `total`, `date`.

**Step 3: Match and report**

For each Chargebee payment, find a NetSuite payment with the same customer email, the same amount and a date within 3 days (or the same reference number in `document-number`). To get the email for a Chargebee `customer-id`, call `chargebee-get-customer` with `id`. Report payments collected but not in NetSuite, NetSuite payments with no Chargebee payment, and totals per side.

**Rules & Guidelines:**

* Tools whose names start with netsuite are on the netsuite server; tools whose names start with chargebee are on the chargebee server. Both servers must be connected.
* Read-only: never call any NetSuite add or update tool (for example `netsuite-add-invoice`, `netsuite-add-customerpayment`, `netsuite-update-invoice`, `netsuite-update-customer`). Chargebee has no write tools here. Report differences only; never fix them.
* A gateway payment may reach the ledger as one batched deposit; flag a possible batch when several Chargebee payments sum to one NetSuite payment.

**Validation:**

* If nothing is returned on either side, say so and stop.
* If dates or amounts differ slightly, show both values and let the reader judge; do not assume a match.