How to Check an IBAN Before an Invoice Payment

Who this guide is useful for

People reviewing invoice payment details before copying an IBAN, BIC, amount, currency, and reference into a bank or payment provider workflow.

Start with the visible invoice details

Read the payee name, IBAN, BIC when supplied, amount, currency, due date, and payment reference from the same trusted invoice or payment instruction. Treat any changed or unexpected bank details as something to confirm outside the document before payment.

Compare the payee name with your expected supplier, customer, or recipient record.
Check that the reference belongs to the same invoice or request.
Review whether the amount and currency match the instruction you intend to pay.
Keep format checking separate from deciding whether a payment should be made.

What BankCodeKit can check

The IBAN Checker can normalize common separators, check the country code, expected country length, allowed characters, and checksum. The Invoice Formatter can create a readable payment-details block after local IBAN and BIC checks.

Confirm through a trusted channel

If payment details changed, arrived in an unexpected message, or feel inconsistent, confirm the instruction through a trusted channel already known to you. Do not rely only on the contact details inside the suspicious or changed instruction.

What BankCodeKit cannot check

BankCodeKit cannot verify that the invoice is genuine, that the IBAN belongs to the payee, that the account exists, or that a payment will be accepted or successful.

Practical invoice review example

A review flow can catch format mistakes without turning the format result into payment approval.

Copy the IBAN from the invoice and run a local IBAN format check.
Compare the print format shown by the checker with the invoice value.
Use the Invoice Formatter to assemble payee, IBAN, BIC, amount, currency, and reference for review.
Confirm changed or unexpected bank details through a trusted channel before sending money.

Important limitations

BankCodeKit checks format and reference data only. It does not confirm account existence, account ownership, bank connectivity, sanctions status, fraud risk, payment readiness, or payment success.

This guide is format-checking and review guidance only.
BankCodeKit does not verify invoice authenticity, account existence, or account ownership.
BankCodeKit does not confirm bank connectivity, sanctions status, fraud risk, payment readiness, or payment success.
Do not send money based only on a passed IBAN format check or a formatted payment-details block.

FAQ

Can BankCodeKit confirm an invoice IBAN belongs to the payee?

No. BankCodeKit checks IBAN format only and cannot confirm account ownership or payee identity.

Should I use the IBAN Checker before paying an invoice?

It can be useful as one format-checking step, but it does not replace trusted confirmation with the invoice issuer, recipient, bank, or payment provider.

What if the invoice says bank details changed?

Confirm the change through a trusted channel already known to you before sending money.

Can the Invoice Formatter approve a payment?

No. It only formats text from the fields you enter after local format checks and limitation acknowledgement.

Sources and update note

BankCodeKit uses local IBAN reference data and browser-local format rules for country, length, character, and checksum checks. The official Swift IBAN information is used as a reference source, but BankCodeKit does not query Swift or any bank while you use the tool. Reference data is reviewed periodically and does not imply live accuracy.

Swift IBAN Registry Reference information for IBAN structure, country support, and format rules.