well_check_supplier_bank_details

io.github.WellApp-ai/well-mcp · Verify this server

Check one bank account (IBAN) against what Well knows of one supplier: the supplier's known bank accounts, the day each first appeared, and the payments made to each. It draws no card. Use it when a person forwards new or changed bank details for a supplier ("our supplier changed bank", "nouveau RIB"), from a mail, an invoice or a typed message, before they pay. Pass the supplier's `company_id` and the IBAN as given; spaces and lower case are fine. The IBAN is compared exactly, across every currency pocket of the account. `status`: - `never_seen`: the supplier is known and none of its known accounts has this IBAN. - `already_paid_there`: the IBAN is a known account of the supplier and payments to it are on file. - `known_never_paid`: the IBAN is a known account of the supplier, with no payment to it on file. - `own_account`: the IBAN is one of the workspace's own accounts, not a supplier's. - `unknown_supplier`: the `company_id` names no company this workspace can read. Nothing is known about its accounts. - `invalid_iban`: the value is not a valid IBAN. Nothing was read. `checked_iban` gives the checked IBAN's first-seen day and payment count when the supplier has it. `accounts` lists every known account of the supplier by the last four characters of its IBAN, the checked one first: the day it first appeared (its first payment, or the day Well recorded it when that is earlier), the payment count, the totals per currency and the 10 most recent payments. `known_payment_count` is every payment to the supplier Well knows; a small number means a thin history, so say how many payments the answer rests on. `payments_without_known_account` counts payments to the supplier with no known account. `accounts_truncated: true` means the oldest accounts were not read; the checked IBAN is always read, so `never_seen` still holds. The check gives facts and never blocks a payment. Never call new bank details safe from this answer alone. When the token authorizes one workspace, call this directly — no workspace call is needed first. When it authorizes several, this read will not guess which one you mean: pass `workspace_id` on the call.