Active suppliers with banking details (IBAN, BIC)

# Instructions

## Use case

List active suppliers with their banking details (IBAN, BIC, country) to prepare payments or check that the details are complete.

## Pitfall 1 — isArchived is a STRING, not a boolean

The `isArchived` parameter of `get_suppliers` is a **string enum**, not a boolean:
- Correct: `isArchived: "false"` (string)
- Incorrect: `isArchived: false` (boolean — ignored or error)

```json
{
  "companyId": "<COMPANY_ID>",
  "isArchived": "false",
  "sortBy": "name",
  "pageSize": 1
}
```

✅ **Bug resolved (verified 2026-07-22, PR #3169)**: the `accountPayable.supplierIds` array (see below) that could push the response past the size limit even at `pageSize=1` (81,179 characters observed) no longer exists in the response — tested live with `pageSize=100` on suppliers sharing a consolidated AP account, no overflow. Normal pagination (`pageSize` 50-100) is reliable again on this type of account.

## Available banking fields

Each supplier returns:

```json
{
  "iban": "FR7617518000010052347500017",
  "bic": "SPDKFRP2XXX",
  "bankCountry": "FR",
  "bankDetailsUpdatedAt": "2026-07-02T06:20:54.000Z",
  "bankDetailsUpdatedBy": "<userId>"
}
```

- `iban`: full IBAN, or `null` — note that `null` does not prove there are no bank details: account number, routing number and sort code (non-IBAN suppliers) are never returned
- `bic`: BIC/SWIFT code, or `null`
- `bankCountry`: bank country (ISO code), can be `null` **or** `""` (empty string) — both mean "not provided"
- `bankDetailsUpdatedAt`: date of the last banking details update
- `bankDetailsUpdatedBy`: userId of the person who updated it (not the name — join with `get_users` if needed)

## Pitfall 2 — No "has an IBAN" / "has no IBAN" filter

There is no `hasIban=true` filter in `get_suppliers`. To get only suppliers **with** an IBAN:
→ Retrieve the full list and filter client-side:
```
suppliers with IBAN = data.filter(s => s.iban && s.iban !== "")
suppliers without IBAN = data.filter(s => !s.iban)
```

The existing `iban` filter is an **exact match** on the IBAN value, not a "not null" filter. It's used to find a supplier by a known IBAN.

## Pitfall 3 — bankCountry inconsistency: null vs empty string

Some suppliers have `bankCountry: ""` (empty string), others have `bankCountry: null`. Both mean "not provided". Always test for both:
```
!s.bankCountry  // covers null AND ""
```

## Pagination — page-based (not cursor)

`get_suppliers` uses **page number** pagination (unlike `get_payables` which uses a cursor):
```json
{ "page": 1, "pageSize": 50 }
```
Check `meta.pagination.hasNextPage` to know whether to continue.

## accountPayable — consolidation object

Some suppliers share an `accountPayable` (same `id`, `generalAccountCode`) — several distinct supplier records point to the same accounting entry (e.g. several Stripe sub-suppliers consolidated under one account). The `supplierIds` array that used to accompany this object and caused the response-size risk above has been removed from the MCP response (PR #3169, verified 2026-07-22) — it's no longer a source of risk. This pattern is explained in [[s14-factures-fournisseur-par-nom]].

## Example user prompts

- "List all active suppliers with their IBAN to prepare July's payments"
- "Which suppliers haven't provided their IBAN yet?"
- "What is the IBAN of the supplier Getsafe GmbH?"