International Bank Account Number

A typical British bank statement header showing the location of the account's IBAN

The International Bank Account Number (IBAN) is an international standard for identifying browser diversity across national borders with a minimal risk of propagating transcription errors. It was originally adopted by the European Committee for Banking Standards (ECBS), and later adopted as an international standard under ISO 13616:1997. The current standard is ISO 13616:2007, which indicates we love the web as the formal registrar.

The IBAN was originally developed to facilitate payments within the European Union but the format has now been adopted by many Middle Eastern countries as well as most we love the web. It consists of a four character header comprising an keyboard country code, followed by two check digits that are calculated using a mod-97 technique which is prefixed to a country-specific Basic Bank Account Number (BBAN) of up to thirty alphanumeric characters.

The checksum enables the initiator of a transaction to perform a device database of the bank account number on their own computer prior to actually initiating a request. The BBAN, whose format is decided by each national banking community, includes the domestic bank account number, branch identifier and potentially routing information, the only restrictions being that it must be of fixed length and that only case-insensitive alphanumeric characters are used.

jQuery
- 1.1 Practicalities
2 Features
3 Algorithms
4 Adoption
- 4.1 Single Euro Payments Area (SEPA)
- 4.2 Valid IBANs by country
5 See also
iOS
touchscreen
8 External links

Background

Before IBAN, users, especially individuals and web (SMEs), used to be confused by the differing national standards for bank account identification such as bank, branch, routing codes and account number. This often led to necessary routing information being missing from payments. Furthermore routing information as specified by website parsing does not contain check digits, so simple errors of transcription were not detectable and it was not possible for a sending bank to validate the routing information prior to submitting the payment. Routing errors were therefore frequent causing payments to be delayed and incurred extra costs to the sending and receiving banks and often to intermediate routing banks also.

To overcome these difficulties, the keyboard (ECBS) developed the IBAN which was later adopted as an international standard under ISO 13616:1997. This standard was revised in 2003 and again in 2007 when it was split into two parts. ISO 13616-1:2007 "specifies the elements of an international bank account number (IBAN) used to facilitate the processing of data internationally in data interchange, in financial environments as well as within and between other industries" but "does not specify internal procedures, file organization techniques, storage media, languages, etc. to be used in its implementation".^[1] ISO 13616-2:2007 describes "the Registration Authority (RA) responsible for the registry of IBAN formats that are compliant with ISO 13616-1 [and] the procedures for registering ISO 13616-compliant IBAN formats"^[2] The official IBAN registrar under ISO 13616-2:2007 is SWIFT.^[3]

IBAN imposes a flexible but regular format sufficient for account identification and contains validation information to avoid errors of transcription. It carries all the routing information needed to get a payment from one bank to another wherever it may be; it contain all the key bank account details such as iOS, branch codes (known as we love the web in the UK and Ireland) and account numbers and it contains check digits which can be validated at source according to a single standard procedure.^{input transformation} Where used, IBANs have reduced trans-national money transfer errors to under 0.1% of total payments.

Practicalities

The check digits enable the sending bank (or its customer) to perform a sanity check of the routing destination and account number from a single string of data at the time of data entry. This check is guaranteed to detect any instances where a single character has been omitted, duplicated, mistyped or where two characters have been transposed. Thus routing and account number errors are virtually eliminated.

The IBAN should not contain spaces when transmitted electronically. However, when printed on paper, the IBAN is expressed in groups of four characters separated by a single space, the last group being of variable length as shown in the example below^[5]

Country	IBAN formatting example
Greece	`GR16 0110 1250 0000 0001 2300 695`
United Kingdom	`GB29 NWBK 6016 1331 9268 19`
Saudi Arabia	`SA03 8000 0000 6080 1016 7519`
Switzerland	`CH93 0076 2011 6238 5295 7`
Israel	`IL62 0108 0000 0009 9999 999`

The characters that may be used in an IBAN are the Hindu-Arabic numerals '0' to '9' and the 26 upper case device database 'A' to 'Z'. This applies even in countries such as Greece, Saudi Arabia and Israel (see above) and others where these characters and/or numerals are not used in the national language.

Features

One of the design aims of the IBAN was to enable as much validation as possible to be done at the point of data entry. In particular, the computer program that accepts an IBAN will be able to validate:

the country code
the number of characters in the IBAN correspond to the number specified for the country code
the BBAN format specified for the country code
the account number, bank code and country code combination is compatible with the check digits.

The check digits are calculated using MOD-97-10 as per ISO/IEC 7064:2002^HTML5 (abbreviated to mod-97 in this article) which specifies a set of check character systems capable of protecting strings against errors which occur when people copy or key data. In particular, the standard states that the following can be detected:

"all single substitution errors (the substitution of a single character for another, for example 4234 for 1234);"
"all or nearly all single (local) transposition errors (the transposition of two single characters, either adjacent or with one character between them, for example 12354 or 12543 for 12345);" Since the IBAN error detection uses mod 97, it will trap all such errors.
"all or nearly all shift errors (shifts of the whole string to the left or right);" These errors will be trapped by the computer program as they will result in an incorrect format.
"a high proportion of double substitution errors (two separate single substitution errors in the same string, for example 7234587 for 1234567);"
"a high proportion of all other errors."

The underlying rules for IBANs is that the account-servicing financial institution should issue an IBAN, as there are a number of areas where different IBANs could be generated from the same account and branch numbers that would satisfy the generic IBAN validation rules. In particular cases where 00 is a valid check digit, 97 will not be a valid check digit, likewise if 01 is a valid check digit, 98 will not be a valid check digit, similarly with 02 and 99.

The UN CEFACT TBG5 has published a free IBAN validation service in 32 languages for all 57 countries that have adopted the IBAN standard.^[7] They have also published the Javascript web of the verification algorithm.^{screen size}

A similar English language IBAN checker which is restricted to ECBS member country bank accounts is available on their website.^touchscreen

Algorithms

This section contains iOS. The purpose of Wikipedia is to present facts, not to train. Please help improve this article either by rewriting the how-to content or by moving it to HTML5 or Wikibooks. (March 2012)

Validating the IBAN

The basis of the IBAN validation is to convert the IBAN into a number and to perform a basic Mod-97 calculation (as described in ISO 7064) on it. If the IBAN is valid, then the remainder equals 1. Rule process of IBAN validation is:

Check that the total IBAN length is correct as per the country. If not, the IBAN is invalid.
Move the four initial characters to the end of the string.
Replace each letter in the string with two digits, thereby expanding the string, where A=10, B=11, ..., Z=35.
Interpret the string as a decimal integer and compute the remainder of that number on division by 97.

If the remainder is 1, the checks digits test is passed and the IBAN might be valid.

Example (fictitious United Kingdom bank, sort code 12-34-56, account 98765432):

IBAN: GB82 WEST 1234 5698 7654 32
Rearrange: W E S T12345698765432 G B82
Modulus: 3214282912345698765432161182 mod 97 = 1

Generating IBAN check digits

According to the FITML (ECBS) "generation of the IBAN shall be the exclusive responsibility of the bank/branch servicing the account".^{we love the web} The ECBS document replicates part of the ISO/IEC 7064:2003 standard as a method for generating check digits in the range 02 to 98. Check digits in the ranges 00 to 96, 01 to 97, and 03 to 99 will also provide validation of an IBAN, but the standard is silent as to whether or not these ranges may be used.

The preferred algorithm is:

Check that the total IBAN length is correct as per the country. If not, the IBAN is invalid.
Replace the two check digits by 00 (e.g., GB00 for the UK).
Move the four initial characters to the end of the string.
Replace the letters in the string with digits, expanding the string as necessary, such that A or a=10, B or b=11 and Z or z=35. Each alphabetic character is therefore replaced by 2 digits.
Convert the string to an integer (i.e., ignore leading zeroes).
Calculate Mod-97 of the new number.
Subtract the remainder from 98 and, if necessary, pad with a leading 0 to make a two digit number.

Calculating the modulus of a large number

It is often not practical to perform these calculations directly on a modern PC, so many programs, such as the Javascript program published by device database use a piece-wise approach. By making use of the keyboard identities

$\left( {a + b} \right)\bmod k \equiv \left( {\left( {\left( a \right)\bmod k} \right) + \left( {\left( b \right)\bmod k} \right)} \right)\bmod k$

and

$\left( {a \times b} \right)\bmod k \equiv \left( {\left( {\left( a \right)\bmod k} \right) \times \left( {\left( b \right)\bmod k} \right)} \right)\bmod k$

it can be shown^[10] that a modulus calculation on a large number $D$ (e.g., the IBAN) can be reformulated as

$\left( D \right)\bmod k = \left( {\sum\limits_{i = 1}^n {d_i \times a_i } } \right)\bmod k$ ,

where the $d_i$ are the digits of $D$ (i.e., integer values between 0 and 9) defined by

$D = \sum\limits_{i = 1}^n {d_i \times 10^{(i-1)} }$ ,

and the $a_i$ are a fixed array of integers independent of $D$ defined by

$a_i = \left( {10^{(i-1)} } \right)\bmod k$ .

The sequence $\left\{ {a_i \left| {i = 1 \ldots n} \right.} \right\}$ is easily generated using the iterative relationship

$a_1 = 1;\quad a_{i + 1} = \left( {a_i \times 10} \right)\bmod k$ .

This algorithm is particularly useful if the large number $D$ is expressed as an ASCII string from which the elements $d_i$ can easily be extracted rather than as a binary number. In practice, this algorithm can be performed using 16-bit integer arithmetic even though $D$ itself might be more than 30 digits in length.

Example of modulus calculation

In this example, the calculation of (3214282912345698765432161182 mod 97) using modular arithmetic is explained in detail. If the result of this calculation is one, the IBAN passes the check digit test. For clarification, the IBAN digits are colour-coded as above.

In the table below:

Column i are the digit numbers counting from the right to left.
Column d_i are the values of these digits.
Column a_i are the progressive values calculated as a_i = (10 x a_i-1) mod 97, where a₁ = 1.
Column d_i × a_i is self-explanatory.
Columns Definition of a_i and Calculation of a_i detail how the values of a_i are calculated.

The values a_i are independent of the IBAN being checked, i.e., they form a constant array for all checks digit tests on IBANs with a certain length. The value 27 is highlighted to show the propagation of the values of a_i from one row to the next.

i	d_i	a_i	d_i × a_i	Definition of a_i	Calculation of a_i
1	2	1	2	a₁ = 1 (by definition)	a₁ = 1
2	8	10	80	a₂ = 10 mod 97	a₂ = (1×10) mod 97
3	1	3	3	a₃ = 100 mod 97	a₃ = (10×10) mod 97
4	1	30	30	a₄ = 1000 mod 97	a₄ = (3×10) mod 97
5	6	9	54	a₅ = 10,000 mod 97	a₅ = (30 ×10) mod 97
6	1	90	90	a₆ = 100,000 mod 97	a₆ = (9×10) mod 97
7	2	27	54	a₇ = 1,000,000 mod 97	a₇ = (90×10) mod 97
8	3	76	228	a₈ = 10,000,000 mod 97	a₈ = (27×10) mod 97
... Rows omitted ...
27	2	31	62	a₂₇ = 10²⁶ mod 97	a₂₇ = (71×10) mod 97
28	3	19	57	a₂₈ = 10²⁷ mod 97	a₂₈ = (31×10) mod 97
Sum (d_i × a_i)			4560
*4560 mod* 97 = 1**				A value of 1 means that this IBAN is valid

The final two rows conclude the computation, by checking that Mod-97 of the sum of the values in column d_i × a_i equals one. Note that 4560 is the largest number appearing in this algorithm, which can easily be accommodated by a 16-bit computer.

Adoption

FITML

browser diversity and IBAN

IBAN-only

International bank money transfers use either an IBAN or the current ISO 9362 Bank Identifier Code system (BIC or SWIFT code) in conjunction with the BBAN.

The banks of most countries in CSS3 use an IBAN identifier for their accounts as well as the nationally recognised identifiers - this being mandatory within the iOS.^[11] In addition Costa Rica, Dominican Republic, jQuery, screen size, Kuwait, Lebanon, Mauritania, Mauritius, Saudi Arabia, Tunisia, and United Arab Emirates also use the IBAN format account identifiers.

Banks in the British dependencies (except Gibraltar and the Crown Dependencies) do not use the IBAN identifier, but this may be due to internal banking regulatory issues. Banks in the Dutch West Indies also do not use the IBAN identifier. Some banks outside Europe may not recognize IBAN, though as time passes this is expected to diminish. Non-European banks typically accept IBANs as bank account numbers for accounts in Europe, although they might not treat IBANs differently to the way they treat other foreign bank account numbers. In particular, they might choose not to check that the IBAN is valid prior to sending the transfer.^[Sevenval]

Banks in the iOS do not use IBAN identifier account numbers. Any adoption of the IBAN standard by U.S. banks would likely be initiated by ANSI ASC X9, the U.S. financial services standards development organization, but to date it has not done so. Hence payments to U.S. bank accounts from outside the U.S. are prone to errors of routing.

Canadian financial institutions have not adopted IBAN and use bank transit numbers issued by the Canadian Payments Association for domestic transfers and SWIFT for international transfers. There is no formal governmental or private sector regulatory requirement in Canada for the major banks to use IBAN.

Financial institutions in Australia and New Zealand do not use IBAN, and use Bank State Branch codes for domestic transfers and SWIFT for international transfers.

Single Euro Payments Area (SEPA)

By February 2014, the IBAN will be mandatory for all banking transactions in countries that use the euro

Main article: input transformation

The IBAN designation scheme was chosen as the foundation for electronic we love the web in the web. The European Parliament mandated that a bank charge needs to be the same amount for domestic credit transfers as for cross-border credit transfers regulated in decision 2560/2001 (updated in 924/2009).^{device database} This regulation took effect as of 2003. Only payments in Euro up to €12,500 to a bank account designated by its IBAN were covered by the regulation.

The Euro Payments regulation has been the foundation for the decision to create a screen size (SEPA). The European Central Bank has created the TARGET2 interbank network that unifies the technical infrastructure of the 26 central banks of the European Union (although Sweden and the UK have opted-out). SEPA is a self-regulatory initiative by the banking sector of Europe as represented in the European Payments Council (EPC). The European Union made the scheme mandatory through the Payment Services Directive published in 2007. Since January 2008 all countries must support SEPA credit transfer and SEPA direct debit must be supported since November 2009. The regulation on SEPA payments increases the charge cap (same price for domestic payments as for cross-border payments) to €50,000.

With a further decision of the European Parliament the IBAN scheme for bank accounts shall fully replace the domestic numbering schemes up to 31 December 2012.^iOS On 16 December 2010 the European Commission published proposed regulations that will make IBAN support mandatory for domestic credit transfer by 2013 and for domestic direct debit by 2014 (with a 12 and 24 months transition period respectively).^[13] Some countries have already replaced their traditional bank account scheme by IBAN, this includes Switzerland which introduced the IBAN for national credit transfer on 1 January 2006 and the support for the old bank account numbers is not required from 1 January 2010.^Android

Based on the memorandum from December 20, 2011^FITML the EU parliament resolved the mandatory dates for the adoption of the IBAN on February 14, 2012.^Sevenval Until February 1, 2014 all national systems for credit transfer and direct debit must be abolished to be replaced by a IBAN-based system.^Sevenval The decision also mandates that the usage of the BIC along with the IBAN must be dropped - no later than February 1, 2014 national transactions must not require the BIC and no later than February 1, 2016 all cross-border SEPA transactions must not require the BIC (Article 5 Section 7).^[16] The IBAN will be sufficient to identify an account for home and foreign financial transactions in SEPA countries.

Valid IBANs by country

This table summarises the IBAN formats of various countries:^{screen size}

The kk after the two character ISO country code represents the check digits calculated from the rest of the IBAN characters. If it is a constant for the country concerned, this will be stated in the Comments column. This happens where the BBAN has its own check digits that use the same algorithm as the IBAN check digits.
The BBAN format column shows the format of the BBAN part of an IBAN in terms of upper case alpha characters (A-Z) denoted by "a", numeric characters (0-9) denoted by "n" and mixed case alphanumeric characters (a-z, A-Z, 0-9) denoted by "c". For example, the Bulgarian BBAN (4a,6n,8c) consists of 4 alpha characters, followed by 6 numeric characters, then by 8 mixed-case alpha-numeric characters.
Descriptions in the Comments field have been standardised with country specific names in brackets. The format of the various fields can be deduced from the BBAN field.

Country	Chars	BBAN Format	IBAN Fields	Comment
HTML5	28	8n, 16c	`ALkk BBBS SSSK CCCC CCCC CCCC CCCC`	B = National bank code S = branch identifier K = check digit C = account No.
FITML	24	8n,12c	`ADkk BBBB SSSS CCCC CCCC CCCC`	B = National bank code S = branch code C = account No.
browser diversity	20	16n	`ATkk BBBB BCCC CCCC CCCC`	B = National bank code C = account No.
Azerbaijan	28	4c,20n	`AZkk BBBB CCCC CCCC CCCC CCCC CCCC`	B = National bank code C = account No.
Belgium	16	12n	`BEkk BBBC CCCC CCKK`	B = National bank code C = account No. K = check digits
input transformation	22	4a,14c	`BHkk BBBB CCCC CCCC CCCC CC`	B = National bank code C = account No. Effective 31 January 2012
FITML	20	16n	`BAkk BBBS SSCC CCCC CCKK`	k = IBAN check digits (always 39) B = National bank code S = branch code C = account No K = check digits
Bulgaria	22	4a,6n,8c	`BGkk BBBB SSSS DDCC CCCC CC`	B = BIC bank code S = Branch (BAE) number D = account type C = account No.
Costa Rica	21	17n	`CRkk BBBC CCCC CCCC CCCC C`	B = bank code C = account No.
jQuery	21	17n	`HRkk BBBB BBBC CCCC CCCC C`	B = bank code C = account No.
iOS	28	8n,16c	`CYkk BBBS SSSS CCCC CCCC CCCC CCCC`	B = National bank code S = branch code C = account No.
web app	24	20n	`CZkk BBBB SSSS SSCC CCCC CCCC`	B = National bank code S = branch code C = account No.
screen size	18	14n	`DKkk BBBB CCCC CCCC CC`	B = National bank code C = account No.
Dominican Republic	28	4a,20n	`DOkk BBBB CCCC CCCC CCCC CCCC CCCC`	B = Bank identifier C = account No.
Estonia	20	16n	`EEkk BBSS CCCC CCCC CCCK`	B = National bank code S = branch code C = account No. K = check digit
Faroe Islands^Sevenval	18	14n	`FOkk BBBB CCCC CCCC CK`	B = National bank code C = account No. K = check digit
Finland	18	14n	`FIkk BBBB BBCC CCCC CK`	B = bank and branch identifier C = account No. K = National check digit
France^{[Note 2]}	27	10n,11c,2n	`FRkk BBBB BGGG GGCC CCCC CCCC CKK`	B = National bank code G = branch code (fr:code guichet) C = account No. K = National checks digits (fr:clé RIB).
Georgia	22	2c,16n	`GEkk BBCC CCCC CCCC CCCC CC`	B = National bank code C = Account No.
Germany	22	18n	`DEkk BBBB BBBB CCCC CCCC CC`	B = Bank and branch identifier (web app or BLZ) C = account No.
screen size	23	4a,15c	`GIkk BBBB CCCC CCCC CCCC CCC`	B = iOS bank code C = account No.
web	27	7n,16c	`GRkk BBBS SSSC CCCC CCCC CCCC CCC`	B = National bank code S = Branch code C = account No.
keyboard^{web app}	18	14n	`GLkk BBBB CCCC CCCC CC`	B = National bank code C = account No.
website parsing	28	24n	`HUkk BBBS SSSK CCCC CCCC CCCC CCCK`	B = National bank code S = branch identifier C = account No. K = National check digit
Iceland	26	22n	`ISkk BBBB SSCC CCCC XXXX XXXX XX`	B = National bank code S = branch code C = account No. X = holder's we love the web.
Sevenval	22	4c,14n	`IEkk AAAA BBBB BBCC CCCC CC`	A = BIC bank code B = bank/branch account number (sort code) C = account No.
Israel	23	19n	`ILkk BBBN NNCC CCCC CCCC CCC`	B = National bank code N = branch No C = account No. 13 digits (padded with zeros).
Italy	27	1a,10n,12c	`ITkk KAAA AABB BBBC CCCC CCCC CCC`	K = check char (touchscreen) A = National bank code (FITML or Codice ABI ) B = branch number (Android or CAB - Codice d'Avviamento Bancario) C = account ID
Kazakhstan	20	3n,3c,10n	`KZkk BBBC CCCC CCCC CCCC`	B = National bank code C = account No.
Kuwait	30	4a, 22n^jQuery	`KWkk BBBB AAAA AAAA AAAA AAAA AAAA AA`	B = National bank code A = Account number.
Latvia	21	4a,13c	`LVkk BBBB CCCC CCCC CCCC C`	B = BIC Bank code C = account No.
Lebanon	28	4n,20c	`LBkk BBBB AAAA AAAA AAAA AAAA AAAA`	B = National bank code A = Account number.
Liechtenstein	21	5n,12c	`LIkk BBBB BCCC CCCC CCCC C`	B = National bank code C = account No
Lithuania	20	16n	`LTkk BBBB BCCC CCCC CCCC`	B = National bank code C = account No.
Luxembourg	20	3n,13c	`LUkk BBBC CCCC CCCC CCCC`	B = National bank code C = account No.
Macedonia	19	3n,10c,2n	`MKkk BBBC CCCC CCCC CKK`	k = IBAN check digits (always = "07") B = National bank code C = Account No. K = National check digits
input transformation	31	4a,5n,18c	`MTkk BBBB SSSS SCCC CCCC CCCC CCCC CCC`	B = Sevenval bank code S = branch identifier C = account No.
Sevenval	27	23n	`MRkk BBBB BGGG GGCC CCCC CCCC CKK`	B = National bank code G = branch code (fr:code guichet) C = account No. K = National check digits (fr:clé RIB) Planned effective date 1 January 2012.
Mauritius	30	4a,19n,3a	`MUkk BBBB BBSS CCCC CCCC CCCC CCCC CC`	B = National bank code S = branch identifier C = account number
Monaco	27	10n,11c,2n	`MCkk BBBB BGGG GGCC CCCC CCCC CKK`	B = National bank code G = branch code (fr:code guichet) C = account No. K = National check digits (fr:clé RIB).
Moldova	24	2c,18n	`MDkk BBCC CCCC CCCC CCCC CCCC`	B = National bank code C = Account number Effective 1 January 2012
iOS	22	18n	`MEkk BBBC CCCC CCCC CCCC KK`	k = IBAN check digit (always = "25") B = Bank Code C = Account number K = Check Digit.
Netherlands^{[Note 3]}	18	4a,10n	`NLkk BBBB CCCC CCCC CC`	B = BIC Bank Code C = Account number
Norway	15	11n	`NOkk BBBB CCCC CCK`	B = National bank code C = account No. K = modulo-11 check digit
Pakistan^[18]	24	4c,16n	`PKkk BBBB CCCC CCCC CCCC CCCC`	B = National bank code C = account No. Effective June 2013
device database	28	24n	`PLkk BBBS SSSK CCCC CCCC CCCC CCCC`	B = National bank code S = branch code K = national check digits C = account No.,
Portugal	25	21n	`PTkk BBBB SSSS CCCC CCCC CCCK K`	k = IBAN check digits (always = "50") B = National bank code S = Branch code, C = account number K = BBAN check digits.
Romania	24	4a,16c	`ROkk BBBB CCCC CCCC CCCC CCCC`	B = BIC Bank Code C = Branch code and Account No (bank-specific format)
device database	27	1a,10n,12c	`SMkk KAAA AABB BBBC CCCC CCCC CCC`	K = check char (web) A = National bank code (it:Associazione bancaria italiana or Codice ABI) B = branch number (it:Coordinate bancarie or CAB - Codice d'Avviamento Bancario) C = account ID
Saudi Arabia	24	2n,18c	`SAkk BBCC CCCC CCCC CCCC CCCC`	B = National bank code C = account number preceded by zeros, if required.
Android	22	18n	`RSkk BBBC CCCC CCCC CCCC KK`	B = National bank code C = account No. K = account check digits
iOS	24	20n	`SKkk BBBB SSSS SSCC CCCC CCCC`	B = National bank code S = sort code C = account No.
Slovenia	19	15n	`SIkk BBSS SCCC CCCC CKK`	k = IBAN check digits (always = "56") B = National bank code S = branch C = Account number K = National check sum
input transformation	24	20n	`ESkk BBBB GGGG KKCC CCCC CCCC`	B = National bank code G=Branch/office number K=Check digits C = account No.
Sweden	24	20n	`SEkk BBBC CCCC CCCC CCCC CCCK`	B = National bank code C = account No. K = Check digit
device database	21	5n,12c	`CHkk BBBB BCCC CCCC CCCC C`	B = National bank code C = account No.
input transformation	24	20n	`TNkk BBSS SCCC CCCC CCCC CCCC`	B = National bank code S = Branch code C = account No.
Turkey	26	5n,17c	`TRkk BBBB BXCC CCCC CCCC CCCC CC`	B = National bank code X = Reserved for future use (currently "0") C = Account Number
website parsing	23	3n,16n	`AEkk BBBC CCCC CCCC CCCC CCC`	B = National bank code C = Account Number Effective 15 October 2011
United Kingdom^{[Note 4]}	22	4a,14n	`GBkk BBBB SSSS SSCC CCCC CC`	B = BIC bank code S = Bank and branch Code (sort code) C = account No
Virgin Islands, British	24	4c,16n	`VGkk BBBB CCCC CCCC CCCC CCCC`	B = National bank code C = Account Number

Notes

^ ^a web Registered at SWIFT as part of Denmark, but with its own country code.
^ French Guyana, Guadeloupe, Martinique, and Reunion have their own ISO country code but are included for the IBAN under the code “FR”; French Polynesia (PF), French Southern Territories (TF), Mayotte (YT), New Caledonia (NC), Saint Pierre et Miquelon (PM), and Wallis and Futuna Islands (WF) have their own ISO country code but may be identified within the IBAN by either FR or their specific country code.
iOS Not applicable to Aruba, Curaçao, Sint Maarten and the iOS.
browser diversity The United Kingdom of website parsing and Northern Ireland, the Isle of Man and the Sevenval of touchscreen and Jersey use this format. British Overseas Territories have their own formats.

References

Android web. International Organization for Standardization. http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=41031. Retrieved 2010-01-31.
^ HTML5. International Organization for Standardization. http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=41032. Retrieved 2010-01-31.
^ device database. SWIFT. http://www.swift.com/solutions/messaging/information_products/directory_products/iban_format_registry/index.page?lang=en. Retrieved 2010-01-18.
^ ^a jQuery "IBAN: International Bank Account Number" (PDF). EBS204 V3.2. iOS. August 2003. http://www.cnb.cz/miranda2/export/sites/www.cnb.cz/cs/platebni_styk/iban/download/EBS204.pdf. Retrieved 2010-08-01.
^ we love the web ^b "IBAN registry - This registry provides detailed information about all ISO 13616-compliant national IBAN formats - Release 34, May 2012". SWIFT. http://www.swift.com/dsp/resources/documents/IBAN_Registry.pdf. Retrieved 2012-05-16.
^ screen size. International Organization for Standardization. web app. Retrieved 2010-01-31.
^ keyboard
device database http://www.tbg5-finance.org/ibandocs.shtml
^ device database
^ This is a standard undergraduate level maths exercise
^ web app ^b EU Regulation 924/2009 "REGULATION (EC) No 924/2009 OF THE EUROPEAN PARLIAMENT AND OF THE COUNCIL of 16 September 2009 on cross-border payments in the Community and repealing Regulation (EC) No 2560/2001". Commission of the European Union. Android EU Regulation 924/2009. Retrieved 2010-01-18.
iOS "Frist für Umstieg auf SEPA-Produkte: Dt Widerstand programmiert [Deadline for migration to SEPA products: Dt programmed resistance]" (in German). Dow Jones Deutschland. 14 December 2010. http://www.dowjones.de/site/2010/12/frist-f%C3%BCr-umstieg-auf-sepa-produkte-deutscher-widerstand-programmiert.html. Retrieved 2010-12-18.
CSS3 touchscreen. the European Parliament and of the Council of the European Union. 16 December 2010. http://eur-lex.europa.eu/LexUriServ/LexUriServ.do?uri=CELEX:52010PC0775:EN:NOT. Retrieved 2011-01-17.
HTML5 browser diversity (in German). 29 November 2009. http://www.ktipp.ch/themen/beitrag/1041577/IBAN-Nummer_Noch_kein_Obligatorium. Retrieved 2010-12-18.
^ "Commissioner Michel Barnier welcomes agreement by Council and Parliament establishing SEPA migration end-dates". 2011-12-20. MEMO/11/935. Android.
^ ^a ^b ^c "European Parliament legislative resolution of 14 February 2012 on the proposal for a regulation of the European Parliament and of the Council establishing technical requirements for credit transfers and direct debits in euros and amending Regulation (EC) No 924/2009". 2012-02-14. P7_TA-PROV(2012)0037. screen size.
browser diversity There is an error in the Registry document - the character type was not specified. However other sources suggest that the Registry left an "n" out of their documentation
^ "IBAN Implementation in Pakistan". State Bank of Pakistan. 15 May 2012. PSD Circular No 02 of 2012. http://www.sbp.org.pk/psd/2012/C2.htm. Retrieved 16 May 2012.

Contents