See where a 2Checkout customer differs from Dynamics GP

**Objective:** Compare the 2Checkout customer with email `{customer-email}` against its Dynamics GP customer record (company `{company}`, default is the server default) and report every field that disagrees.

**Step 1: Find the customer in 2Checkout**

Call `2checkout-get-customer` with `email` = `{customer-email}`. If more than one customer matches, list them (`customer-reference`, `first-name`, `last-name`, `company`) and stop. If none match, report that and stop.

**Step 2: Find the customer in Dynamics GP**

Take `company` (or, for a person with no company, `first-name` plus `last-name`) from step 1 and call `dynamics-gp-get-rm-customer` with it as `customer-name`. If the exact match returns nothing, retry with `customer-name.contains` using the first word of the name. If several match, list `customer-id`, `customer-name`, `city` and `main-email-address` and stop. If none match, report the customer as present in 2Checkout and absent from Dynamics GP.

**Step 3: Report**

Show a table with one row per attribute: name, email (compare with `main-email-address`), address 1, city, country or state, credit limit (`credit-limit` against `credit-limit-amount`), and active state (`enabled` against `inactive`, which is inverted). Mark each row Match or Differs and show both values.

**Rules & Guidelines:**

* `2checkout-get-customer` is on the 2checkout server; `dynamics-gp-get-rm-customer` is on the dynamics-gp server.
* This prompt is read-only. Do not call `2checkout-customer-update`, `2checkout-customer-add`, `dynamics-gp-rm-customer-update`, `dynamics-gp-rm-customer-add` or `dynamics-gp-rm-customer-note`.

**Validation:**

* Compare names ignoring case and punctuation; state which values were normalized.
* If the two systems use different currencies for the credit limit, say so instead of calling it a mismatch.