Confiban
FinanceConfiban is the Belgian IBAN and company name verification product of Isabel Group, published on Ibanity as the Checkr API. Agents confirm that a Belgian IBAN belongs to the company being paid and screen Peppol e-invoices for fraud signals before money moves.
What This Integration Enables
Confiban is built for one moment: the instant before a Belgian payment leaves, when the bank details on an invoice are the only thing standing between your supplier and someone impersonating them. It is Isabel Group's IBAN and company name verification product, published on Ibanity as the Checkr API, and it answers two questions. Does this IBAN belong to the company on the invoice? Does this Peppol e-invoice carry the signals that come before a fraud?
What makes it worth wiring into an agent is that it refuses to round doubt up to a pass. A close name match (CMTC) is not a match, and an AMBER invoice is not a pass. The connector carries that discipline through: its convenience flags are true only for a full match and only for GREEN. An agent running payment-control checks therefore does not have to decide what "close enough" means. It treats every non-MTCH and non-GREEN result as one of its automation exceptions. Each one goes to a person through human-in-the-loop escalation, which is the default you want on the one step in accounts payable that cannot be recalled. The connector is built and verified against Ibanity's official API documentation. Scope is Belgium only: Belgian IBANs and Belgian enterprise numbers checked against the KBO/BCE register.
Without FlowRunner
With FlowRunner
Flows you can build with Confiban
-
Re-verifying a supplier's bank change before the next payment run
A change of bank details is the moment invoice redirection fraud is normally attempted. When a supplier email lands in the AP mailbox through Gmail, the agent pulls out the new IBAN, the company name as written on the supplier's invoices and the enterprise number, then calls Check Beneficiary. Confiban answers with two codes, one for the name and one for the enterprise number. A double MTCH lets the agent write both codes onto the supplier's account in Exact Online with Update Account, so the audit trail shows what was checked and when. Anything else, including CMTC, NMTC and NOAP, holds the supplier out of the next payment run and goes to the AP lead.
-
Screening every inbound Peppol invoice by individual check, not by headline
Invoices arriving through Peppol E-Invoicing are read with List Received Documents and Get Document UBL, and the UBL XML goes straight into Check Peppol Invoice. GREEN invoices continue to the approval queue. For everything else the agent reads
failing_checksentry by entry rather than trusting the overall light. A RED result can carry AMBER entries. An AMBER result can hide a supplier the register lists as under liquidation (cbe_status_warning), or one that recently changed Peppol provider (peppol_provider_updated). The agent posts the specific failing checks, with the offending field values, to the finance channel in Slack. An invoice that comes back UNKNOWN is treated as unscreened, never as clean. -
Catching an expired certificate before it silently stops the screening
Ibanity requires a mutual TLS client certificate on every call, and a missing or expired certificate does not return a readable error. The connection simply drops. A scheduled flow calls Verify Connection each morning, which exercises the certificate, the private key and the client credentials without consuming a check. If the handshake fails, the agent sends a direct message in Slack to the integration owner naming the failure, and the screening flows switch to holding payments rather than releasing them unchecked. A check that could not run is never read as a check that passed.
Human-in-Loop Highlight
The gate sits on the payment, not on Confiban, because Confiban only reads and the payment is the thing that cannot be recalled. When Check Beneficiary returns CMTC on the name for a supplier whose IBAN changed this week, the agent does not decide whether "Acme Logistics" and "Acme Logistics Belgium BV" are the same company. Confiban cannot tell a trading name from a lookalike, and a close match is exactly what a careful fraudster aims for. The agent posts to the AP lead in Slack: "Acme Logistics changed its IBAN by email on Monday. Confiban returns CMTC on the name and MTCH on the enterprise number for the new account. Their invoice is in today's payment batch. Hold it while you confirm by phone, or release?" The message carries the old and new IBAN and the contact number from the supplier master, not the one in the change email. The agent waits, records who answered and what they chose, and only then releases or holds the batch line.
Agent Capabilities
3 actionsVerification
2- Check Beneficiary Asks Confiban whether a Belgian IBAN belongs to the company you intend to pay, matching on the company name as written on the invoice, the Belgian enterprise number, or both. The agent uses it whenever bank details are new or changed, and before a payment batch is released. It accepts the IBAN and enterprise number as people actually write them, with spaces, dots or a BE prefix. The answer is MTCH, CMTC, NMTC or NOAP for the name, and MTCH, NMTC or NOAP for the enterprise number. Only MTCH counts as a match.
- Check Peppol Invoice Screens a complete Peppol UBL e-invoice, supplied as XML or as a URL, and returns a single traffic light plus every individual check that failed. In one call Confiban runs the beneficiary check on the invoice's own IBAN and supplier name and verifies the BIC against the IBAN. It also looks the supplier up in KBO/BCE, checks the Peppol address and scans the document for malware. The agent uses it on every inbound invoice and routes on each failing check's own severity, since only GREEN is a pass.
Diagnostics
1- Verify Connection Performs the mutual TLS handshake and the OAuth2 client credentials exchange against Ibanity and reports whether both succeeded, without returning the token and without consuming a verification. The agent runs it on a schedule or as the first step of a payment-control flow. An expired client certificate is the most likely way this integration breaks, and it breaks as a dropped connection rather than an API error.
Frequently asked questions
What can FlowRunner do with Confiban?
FlowRunner agents can run Check Beneficiary, Check Peppol Invoice, and Verify Connection in Confiban.
Does connecting Confiban to FlowRunner require OAuth?
Yes. Confiban connects to FlowRunner with OAuth 2.0, so agents authenticate without handling raw credentials.
Can Confiban trigger a FlowRunner workflow automatically?
Confiban doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Confiban
Free plan, no card required. Connect in minutes.