Suppliers Without Bank Details in Spendesk: A Dust Agent to Spot Blockers Before Month-End
A supplier without an IBAN in Spendesk means a blocked payment with no warning. A Dust agent shared across the whole AP team identifies affected suppliers in one question, in the web chat or in Slack.
The problem
The same scenario plays out every month-end: an invoice is approved, scheduled for payment, and at the moment the wire transfer should go out, Spendesk blocks it — the supplier has no IBAN configured. The payment doesn't go out, the supplier gets no notification, and the AP Manager has to handle the emergency at the worst possible time.
The problem is insidious because it is silent. Spendesk does not generate a proactive alert when an active supplier has no bank details on file. The gap only surfaces when you attempt to execute the payment — typically at month-end, under pressure.
For AP teams managing 200 to 500 active suppliers, manually verifying that every new supplier has provided bank details is practically impossible. Supplier onboarding is often handled by procurement or IT teams who don't think to fill in the bank account in Spendesk.
What a Dust agent connected to the Spendesk MCP changes
Once the Spendesk MCP is connected by the workspace admin, any published Dust agent can cross-reference suppliers with approved invoices against those missing an IBAN configuration. Unlike a skill installed individually by each user, this agent is available to the entire AP team as soon as it's published — no one needs to set it up on their own.
@Dust identify all suppliers with approved invoices but no IBAN configured in Spendesk.
I cross-referenced suppliers with at least one approved invoice against bank account data configured in Spendesk.
5 suppliers with no IBAN and approved invoices:
| Supplier | Approved Invoices | Total Amount | Latest Invoice | Risk |
|---|---|---|---|---|
| Cegid Group | 2 | €6,840.00 | 01/07/2026 | 🔴 High |
| Agicap SAS | 1 | €2,400.00 | 28/06/2026 | 🔴 High |
| Klaviyo Inc. | 1 | €1,980.00 | 25/06/2026 | 🟡 Medium |
| Pennylane | 3 | €4,320.00 | 30/06/2026 | 🔴 High |
| Sarbacane | 1 | €750.00 | 22/06/2026 | 🟡 Medium |
Would you like me to draft a template email to send to each of these suppliers requesting their bank details?
Going further: 2 additional use cases
Suppliers created this month with no bank details
Detecting newly created suppliers who haven't yet provided bank details allows you to act early — before the first invoice arrives. Asking in a shared Slack channel rather than a private message means the whole procurement team benefits from the answer, not just the person who asked.
@Dust which suppliers were created this month without bank details on file?
I analysed suppliers created in July 2026 (01/07–09/07).
7 suppliers created this month with no IBAN:
| Supplier | Created On | Created By | Category | IBAN |
|---|---|---|---|---|
| Legalstart SAS | 02/07/2026 | Lucas Bernard | Legal | ❌ Missing |
| Brevo (ex-Sendinblue) | 03/07/2026 | Camille Vidal | Marketing | ❌ Missing |
| Payfit Solutions | 04/07/2026 | HR Ops | HR & Payroll | ❌ Missing |
| Kandji Inc. | 05/07/2026 | IT Admin | IT/SaaS | ❌ Missing |
| Openclassrooms | 06/07/2026 | L&D Team | Training | ❌ Missing |
| Partoo | 07/07/2026 | Growth | Marketing | ❌ Missing |
| Surfe (ex-Leadjet) | 08/07/2026 | Sales Ops | Sales Tools | ❌ Missing |
Would you like me to generate a follow-up list grouped by the team that created each supplier?
Suppliers with bank details not updated in over 6 months
IBANs can become outdated after mergers, acquisitions, or bank changes. This use case is an approximation based on last-modified date — the MCP does not expose an explicit "verification date," but the supplier's last update timestamp serves as a useful proxy. This limitation is the same on Dust as on any other platform: it comes from the MCP server, not the agent.
@Dust list suppliers whose bank details haven't been updated in more than 6 months.
I identified suppliers whose profile was last created or modified more than 6 months ago (before 09/01/2026).
Top 4 strategic suppliers with data older than 6 months (ranked by annual payments):
| Supplier | Last Updated | Amount Paid (12 months) | Estimated Risk |
|---|---|---|---|
| Oracle France | 15/08/2025 | €48,200.00 | 🔴 High |
| SAP SE | 03/09/2025 | €36,500.00 | 🔴 High |
| Sopra Steria | 22/09/2025 | €24,100.00 | 🟡 Medium |
| Capgemini | 01/10/2025 | €18,750.00 | 🟡 Medium |
Would you like me to filter only suppliers with more than €20,000 in annual payments to prioritise the verification list?
What to remember
- A supplier without an IBAN silently blocks all their payments — there is no proactive alert in Spendesk, even via Dust.
- Combining
get_suppliers+get_payablessurfaces all potential payment blockers before month-end closes. - Up to 78% of newly created suppliers may be missing bank details — a systematic post-creation check is essential.
- A published Dust agent is usable by the whole AP team, in the web chat or by mentioning
@Dustin Slack — no per-person skill to reinstall. - To turn this check into a recurring automatic control, see the guide on Dust Triggers.
Related skills