Basic Bank Account Number (BBAN)


Contents
A Basic Bank Account Number (BBAN) is the country-specific portion of an International Bank Account Number (IBAN) that identifies a bank account within a national banking system. Its length and component fields depend on the country's format.
How does a BBAN identify an account nationally?
The issuing country's format tells you where to find the financial institution and the individual account in a BBAN. Without that layout, the characters alone do not identify the fields.
Which bank and account details can a BBAN contain?
Every registered BBAN includes a bank identifier and an account identifier. Its national format fixes each field's position, length and permitted characters. Some formats also identify a branch or domestic routing unit separately. For example, the registered GB format names a branch identifier, while the German format has no separate branch field. The Swift IBAN Registry records these boundaries by country; its field labels show how to read an unfamiliar BBAN.
A national control field may be another component. In France, the BBAN includes a bank code, branch code, account number and two-digit clé RIB (RIB key), as Banque de France explains. That key belongs to the French national portion; it is distinct from the two IBAN check digits that precede the BBAN. When identifying fields in an unfamiliar number, use the issuing country's registered format and its field labels. Grouping a printed number into blocks does not establish where one field ends and the next begins.
How is a BBAN different from a local account number?
The local account number can be just one field within the BBAN. In the UK format, an eight-digit account number follows a four-letter bank code and a six-digit sort code. Someone who knows only their eight-digit account number therefore lacks the other fields of the UK BBAN; the account number alone cannot fill a field requesting that BBAN. Pay.UK's format standard labels each component separately.
US domestic bank instructions also distinguish a routing number from an account number. That pair is domestic payment information, not a US IBAN format: Bank of America says the US does not currently participate in IBAN, and the Swift registry has no registered US format. Do not treat a US routing number as a bank-code field in a generic BBAN template.
The issuing country supplies the missing context for an unlabeled BBAN. ISO's Technical Committee 68 explains that the country code in an IBAN resolves ambiguity between countries' national identifiers and selects the relevant length and field structure. Characters in a standalone BBAN cannot reliably tell you which country's layout to apply. If a payment form asks for an IBAN and the recipient has supplied only local account details, ask for the issuing country and the recipient's bank-issued full IBAN instead of assembling one from those details.
Where does the BBAN sit in an IBAN?
An IBAN places four international characters before the national account identifier. Its country code tells you which BBAN layout to use.
Which characters belong to the BBAN?
The first two IBAN characters are the country code, and the next two are numeric IBAN check digits. The BBAN starts at character five of the electronic number. In the Swift IBAN Registry's illustrative example GB29NWBK60161331926819, the boundary is GB29 | NWBK60161331926819: GB identifies the country, 29 is the IBAN check-digit pair, and the characters after the bar are the BBAN. This is a format example, not a recipient's payment instruction.
Printed IBANs may group characters with spaces for readability. Those spaces do not change the boundary or count as identifier characters; Pay.UK's standard shows the electronic form without them. After locating the BBAN, use the country code to select its registered field layout. A national control field can sit inside that BBAN, as the French RIB key does, while the two IBAN check digits remain outside it.
How do UK and German BBANs differ?
Both registered formats have an 18-character BBAN inside a 22-character IBAN, according to the Swift IBAN Registry. The GB BBAN begins with a four-letter bank code, followed by a six-digit sort code and an eight-digit account number. Those three fields have distinct positions in the UK format specified by Pay.UK.
The German BBAN is entirely numeric: an eight-digit bank sort code followed by a ten-digit account number. Deutsche Bundesbank explains that shorter account numbers generally receive leading zeros in that ten-digit field. It also describes institution-specific rules that can affect conversion from domestic bank and account numbers to an IBAN. Keep the issued digits, including zeros, and do not assume that joining visible domestic fields always reproduces the bank's issued IBAN.

Caption: GB and DE each have an 18-character BBAN inside a 22-character IBAN, but their BBAN fields differ. These are format layouts, not account details to copy or instructions to construct an issued IBAN. Swift IBAN Registry, version 103 · Pay.UK, Standard Format of the IBAN Issued in the UK · Deutsche Bundesbank, IBAN rules
Equal overall lengths do not make the national fields interchangeable. The first four BBAN characters in the GB layout are a lettered bank code; the first eight in the German layout are a numeric bank sort code. Applying the GB field boundaries to a German number would misidentify its bank and account portions. When a payment requires an IBAN, use the recipient's bank-issued number or the bank's authorized calculation method rather than constructing one from this layout.
Is a BIC or SWIFT code part of the BBAN?
A full BIC, often called a SWIFT code on payment forms, is a separate identifier. It identifies a business party such as a financial institution; the BBAN identifies an individual account at an institution within a national format. Swift's BIC guidance describes an eight-character BIC with an optional three-character branch identifier. Neither version supplies the customer's account number, so a BIC cannot replace a BBAN.
In the GB format, the four-letter bank code uses the first four characters of the bank's BIC, according to Pay.UK. In the registry example above, NWBK is that GB bank-code field. It is only one part of the BBAN and is not the full BIC; copying an eight- or eleven-character BIC into that field would displace the sort code and account number.
SEPA names an area and schemes for euro credit transfers and direct debits, rather than an account or institution code. The word SEPA alone does not establish which identifier fields a particular payment form requires. If a form has separate IBAN and BIC/SWIFT fields, enter the recipient's bank-issued IBAN in its field and follow the provider's instructions for the BIC field.
How do you use or check the right number for a payment?
Start with the fields requested by the payment provider and the recipient's bank-issued details. The destination and payment route determine which identifier to provide; a format check is useful only after you have the right type of detail.
Which details should you provide for a payment?
If a form requests an IBAN, provide the recipient's complete, bank-issued IBAN. The BBAN is its national suffix, so entering that suffix alone leaves out the country code and two IBAN check digits shown in the Swift IBAN Registry. For a UK account, Pay.UK says the bank issues the IBAN to its customer, who can pass it to the payer. A format diagram shows where the fields sit; it does not supply the actual recipient's number.
Other destinations and routes can ask for local account and bank-routing details, or a BIC in a separate field. The US has no registered IBAN format; Chase's wire guidance gives a route-specific example for a US account: its domestic incoming wires use routing and account numbers, while incoming international wires use a BIC and account number. Follow the provider's labels for the particular payment and use the recipient bank's issued details. For an IBAN-using destination, if the recipient has supplied only a local account number while the form asks for an IBAN, request the full IBAN instead of trying to infer it from the BBAN layout.
Where can you find an issued IBAN or BBAN?
For your own account, check a bank statement or the authenticated account area. For example, Nationwide directs UK current-account customers to their monthly statement or internet bank for the IBAN. Banque de France says a French RIB, which includes the IBAN, can be obtained in the customer area or app, or at a bank counter. The available channel depends on the institution and account. A bank may show the full IBAN and domestic fields without a separately labeled “BBAN.”
For another person's account, ask that recipient for the bank-issued identifier required by the payment form. Under the UK IBAN standard, the beneficiary communicates their bank-issued IBAN to the payer. If they sent only local account details and the form asks for an IBAN, ask them to retrieve the full number from their bank rather than filling in missing characters from a format example.
For a German account, a third-party calculator may produce a plausible-looking IBAN yet miss institution-specific conversion rules. Deutsche Bundesbank documents such features when banks convert domestic bank and account numbers. Use the bank-issued IBAN or a calculation method authorized by that bank when conversion is needed.
What can a format check tell you?
An IBAN format check tests the number against its country's registered length and field structure, then checks the two IBAN check digits. The Swift IBAN Registry specifies those structures and the check-digit method. This can catch some transcription errors, such as a missing character or a mistyped digit. It cannot show that the account still exists: Pay.UK's verification standard explicitly limits what a valid-IBAN check establishes. A different, correctly formatted account identifier could also pass. Some national BBANs contain their own control field, separate from the two IBAN check digits.
A syntax check also cannot establish who owns the account. A separate service may compare a payee name with account records: for example, Pay.UK's Confirmation of Payee checks the name against sort code and account number for covered UK domestic payments. Its availability and result depend on the route and participating providers; it is not an IBAN format test. Before sending, compare the details with a trusted instruction from the intended recipient, even if the number passes a format check.
What if the supplied number appears wrong?
Pause before submitting the payment. A rejected format may point to a mistyped character, missing digit or wrong country prefix; compare the full identifier and its bank and account fields with the recipient's issued details. A number can also pass a format check yet belong to the wrong account. If the details conflict with an earlier instruction, or a payee-name check returns a mismatch, confirm them with the intended recipient through a previously known channel. For example, Banque de France advises calling a contact at their usual number before paying changed French bank details (RIB) sent by email; Pay.UK likewise advises contacting the intended recipient when a UK name check does not match.
If you have already instructed the payment with incorrect details, contact the bank or payment provider you used promptly and give them the transaction reference and details. Ask which cancellation, correction, tracing or recall steps are available for that payment. HSBC UK's guidance starts with contacting the sending bank and having the transaction details ready. Banque de France advises requesting a recall without delay in its false-RIB example, while making clear that recovery is not assured.