Supplier onboarding & data quality audit

# Supplier onboarding audit

## Purpose
Check the completeness of each active supplier's data: banking details (IBAN, BIC), contact, address, and consistency with actual activity. Helps identify blocking suppliers before the next payment run.

## Instructions

### Step 1 — Retrieve all active suppliers

⚠️ **Verified bug**: `get_suppliers` has **no** `status` parameter. The correct parameter is `isArchived`, a **string** (not a boolean): `isArchived: "false"`.

⚠️ **Verified bug — no `pageSize` is reliable, not even `pageSize=1`**: suppliers sharing a consolidated AP account (`accountPayable.supplierIds`) can blow up the response size — tested and confirmed failing even at `pageSize=1`. Since this skill inherently requires a full audit of the master data, it's structurally exposed: warn the user that some pages will fail consistently (not just "retry with a smaller pageSize") and flag them as unaudited rather than blocking the whole report.

```
Call get_suppliers with isArchived: "false" and pageSize: 1, paginating (meta.pagination.hasNextPage) and skipping pages that fail.
For each supplier: note id, name, iban, bic, bankCountry, email,
address, createdAt, updatedAt.
```

### Step 2 — Data completeness check
```
For each supplier, check:
  IBAN: present and non-empty → ✅ / ❌ "Missing IBAN"
  BIC: present and non-empty → ✅ / ❌ "Missing BIC"
  Email or contact: present → ✅ / ⚠️ "No contact"
  Address: present → ✅ / ⚠️ "Missing address"

Build a scorecard per supplier: 0 to 4 fields filled in.
```

### Step 3 — Cross-check with payment activity
```
For suppliers with a missing IBAN:
  Call get_payables with supplierId for the last 90 days
  If pending payables exist → BLOCKING (payment impossible without an IBAN)
  If no recent payable → inactive supplier (to be archived?)

For suppliers created within the last 30 days:
  Check whether they already have payables (normal activity) or none (onboarding in progress)
```

### Step 4 — Identifying suspicious suppliers
```
Flag as "To verify":
  - Supplier created < 7 days ago with a large invoice already submitted (fraud risk)
  - IBAN from a country different from the supplier's country (verification recommended)
  - Supplier updated very recently (bank details change — validation protocol?)
```

### Step 5 — Onboarding report
```
Present:
🔴 BLOCKING (missing IBAN with pending payables) — X suppliers, X€ blocked
🟡 INCOMPLETE (missing data, no urgent payable) — X suppliers
🟢 NEW TO VERIFY (created < 30 days) — X suppliers
⚠️ RECENT BANK DETAILS CHANGES (updatedAt < 7 days with a banking change) — X suppliers

Recommended action per category.
```

## Points to watch
- Never modify an IBAN without written confirmation from the supplier (wire transfer fraud)
- Archived suppliers do not appear with `isArchived: "false"` — use `isArchived: "true"` separately if needed
- Run this skill every week before the payment run

## Example prompts
- "Which suppliers have incomplete data that's blocking payments?"
- "Full audit of my supplier master data"
- "Are there any recent bank details changes I need to validate?"