Know if finance will hold an order before you close the deal

**Objective:** Decide whether the opportunity `{opportunity-topic}` can be closed safely by checking its customer's credit position and overdue invoices in Business Central company `{company}` (default: the connector's default company when blank).

**Step 1: Find the opportunity in Dynamics 365 Sales**

Call `dynamics-365-sales-get-opportunities` with topic.contains set to `{opportunity-topic}`. If nothing comes back, report that no opportunity matched and stop. If more than one comes back, list each with topic, potential-customer, est-revenue, est-close-date and status, and stop so the user can pick one. Keep potential-customer and est-revenue.

**Step 2: Resolve the account in Dynamics 365 Sales**

Call `dynamics-365-sales-get-accounts` with account-name set to the opportunity's potential-customer. Keep account-number, account-name, email and credit-limit. If no account matches, the potential customer may be a contact; report that and continue with the potential-customer name only.

**Step 3: Find the customer in Business Central**

If the account has an account-number, call `business-central-get-customer` with customer-number set to it (and company set to `{company}` when given). If that returns nothing, or there is no account-number, call `business-central-get-customer` with name.contains set to the account name, and if email is known prefer the row whose email matches. If more than one customer still matches, list them and stop. If none matches, report the customer as present in Dynamics 365 Sales and absent from Business Central, recommend creating the customer before closing, and stop.

Keep customer-number, name, credit-limit, balance-due, balance, outstanding-orders, outstanding-invoices, blocked and payment-terms-code.

**Step 4: Read overdue invoices in Business Central**

Call `business-central-get-posted-sales-invoice` with sell-to-customer-number set to the customer-number, remaining-amount.min set to 0.01 and due-date.to set to yesterday's date. Sum remaining-amount and note the oldest due-date. Also call `business-central-get-reminder` with customer-number set to the customer-number to see whether reminders have been issued and at what reminder-level.

**Step 5: Report**

A short verdict first: CLEAR, CAUTION or HOLD.

* HOLD when the customer is blocked, or balance plus outstanding-orders plus the opportunity's est-revenue exceeds a non-zero Business Central credit-limit, or any invoice is more than 60 days overdue.
* CAUTION when anything is overdue at all, or a reminder exists.
* CLEAR otherwise.

Then a table: opportunity (topic, est-revenue, est-close-date), Business Central customer (number, name, credit-limit, balance, balance-due, outstanding-orders), headroom (credit-limit minus balance minus outstanding-orders minus est-revenue), overdue total and oldest overdue invoice, and the highest reminder-level. Note when the Dynamics 365 Sales account credit-limit differs from the Business Central credit-limit.

**Rules & Guidelines:**

* Tools named dynamics-365-sales-* are on the dynamics-365-sales server; tools named business-central-* are on the business-central server.
* This prompt is read-only. Do NOT call `dynamics-365-sales-update-opportunity`, `dynamics-365-sales-update-account`, `business-central-update-customer` or any other create or update tool on either server.
* Business Central's credit-limit is authoritative; a credit-limit of 0 means no limit is set, so say so rather than calling it exceeded.

**Validation:**

* If either server returns an error, report which server and which tool failed and do not guess the verdict.
* Account names often differ in punctuation or suffixes (Inc, Ltd, LLC) between the two systems; state which match rule you used.
* Report amounts in each system's currency; if currency-code differs from the opportunity's currency, say so rather than converting.