IBAN, SWIFT/BIC & VAT Number Validator (bulk)

Clean your vendor and customer master data before it reaches NetSuite, SAP, Dynamics or your payment run. Paste hundreds or thousands of IBANs, SWIFT/BIC codes and VAT numbers and get back a row per item saying whether it is valid, why not, and – for VAT numbers – the officially registered company name and address.

Built by a NetSuite-certified consultant who got tired of payment files bouncing because of one mistyped IBAN.

What it checks

Type	Checks	Extra data returned
IBAN	Country code known, correct length for that country, mod-97 checksum	Formatted IBAN, BBAN, bank/branch/account numbers for DE, GB, FR, NL, ES, IT, AE, SA, EG
SWIFT / BIC	8 or 11 character structure, valid country	Bank code, location, branch, test/passive BIC flags
VAT (EU)	Format, then live VIES lookup	Registered name, address, VIES request date
VAT (UK)	Format, then live HMRC lookup	Registered name, address
VAT (other)	Format only	–

Types are auto-detected, so you can mix everything in one list.

Who uses it

• AP / procurement teams onboarding new vendors
• NetSuite & ERP admins cleaning data before CSV import
• Finance shared-service centers validating payment files
• E-commerce and SaaS billing teams checking B2B customers' VAT numbers for reverse-charge invoicing
• AI agents (via Apify MCP) that need a trustworthy validation tool

Input

Simple list:

{
    "items": ["DE89 3704 0044 0532 0130 00", "GB29NWBK60161331926819", "DEUTDEFF", "DE811907980", "IE6388047V"],
    "lookupVat": true
}

With your own reference IDs (so you can join results back to your vendor file):

{
    "items": [
        { "value": "FR7630006000011234567890189", "type": "iban", "reference": "VENDOR-1042" },
        { "value": "NL999999999B01", "type": "vat", "reference": "VENDOR-1042" }
    ]
}

Field	Description	Default
items	Strings or {value, type?, reference?} objects	–
defaultType	auto, iban, bic or vat	auto
lookupVat	Live VIES / HMRC registry lookup	true
maxItems	Safety cap	10000

Output

{
    "reference": "VENDOR-1042",
    "input": "DE89 3704 0044 0532 0130 00",
    "normalized": "DE89370400440532013000",
    "type": "iban",
    "valid": true,
    "status": "valid",
    "reason": null,
    "country": "DE",
    "details": {
        "checkDigits": "89",
        "bban": "370400440532013000",
        "formatted": "DE89 3704 0044 0532 0130 00",
        "bankCode": "37040044",
        "accountNumber": "0532013000"
    },
    "checkedAt": "2026-10-29T20:00:00.000Z"
}

status is one of valid, invalid, unknown_type or lookup_failed (registry temporarily unavailable – retry later; the format check still ran). Download as JSON, CSV or Excel from the run's dataset.

Pricing

Pay per event: a small amount per identifier validated. Set a maximum cost per run in the Apify Console and the Actor stops at your limit.

Use from code or AI agents

curl "https://api.apify.com/v2/acts/omararida~finance-id-validator/run-sync-get-dataset-items?token=<APIFY_TOKEN>" \
  -X POST -H 'Content-Type: application/json' \
  -d '{"items":["DE89370400440532013000","DE811907980"]}'

Works through the Apify MCP server for Claude, ChatGPT and other agents.

Notes & limits

• IBAN validation proves the number is well-formed, not that the account exists – no bank can confirm that publicly.
• VIES and HMRC are official but occasionally rate-limit or go down; such rows come back as lookup_failed so you can re-run only those.
• Nothing you submit is stored anywhere except your own run's dataset.

Support

Need another country's bank-code breakdown or a different registry? Open an issue on the Actor's Issues tab.