Introduction
One of the most common challenges during Oracle Fusion HCM implementations is configuring employee bank accounts, supplier bank accounts, and payroll direct deposits across multiple countries.
Although Oracle Fusion stores bank information using a common data model, the field labels, mandatory fields, validation rules, and formats vary by country.
For example:
-
India uses IFSC Code
-
United Kingdom uses Sort Code
-
United States uses Routing Transit Number
-
Australia uses BSB
-
Germany uses BLZ
-
Canada uses Institution Number + Transit Number
This guide explains the complete global mapping of Oracle Fusion Bank and Bank Branch fields across more than 65 delivered countries.
Note
This article focuses on Oracle Fusion UI behavior and country mapping only.
HDL loading for Employee Bank Accounts is covered in a separate guide.
Oracle Fusion Global Bank Data Model
Internally Oracle stores bank information using the same attributes worldwide.
The screen labels change according to the selected country.
| Screen Label | Oracle Attribute | Description |
| Bank | BANK_NAME | Financial Institution |
| Bank Code | BANK_CODE | National Bank Identifier |
| Bank Branch | BRANCH_NAME | Branch Name |
| Branch Number | BRANCH_NUMBER | Routing Identifier |
| Account Number | ACCOUNT_NUMBER | Customer Account |
| IBAN | IBAN | International Bank Account |
| BIC | BIC | SWIFT Code |
| Check Digit | CHECK_DIGIT | Validation Digit |
| Secondary Account Reference | SEC_ACCT_REF | Country Specific Extra Identifier |
What Changes by Country?
Oracle changes several things automatically depending on country.
| Feature | Changes? |
| UI label for Branch Number (e.g. "Sort Code" vs "Routing Number") | ✅ Yes |
| Whether Bank Code is required | ✅ Yes |
| Whether Branch Number is required | ✅ Yes |
| Format validation (length, check digit, numeric only) | ✅ Yes |
| Whether IBAN is mandatory on employee accounts | ✅ Yes |
| Underlying attribute names (BANK_CODE, BRANCH_NUMBER) | ❌ No — always the same |
How Oracle Applies Country Rules
Oracle uses the delivered configuration table:
This table determines
-
Required fields
-
Hidden fields
-
UI labels
-
Country validations
-
IBAN rules
-
Routing validations
Default Behavior
If Oracle doesn't deliver country-specific rules, these defaults are used.
| Attribute | Displayed? | Required? |
| Account Number | Yes | Yes |
| Bank Name | Yes | No |
| Bank Code | Yes | No |
| Branch Name | Yes | No |
| Branch Number | Yes | No |
| BIC | Yes | No |
| IBAN | Yes | No |
| Account Suffix | No | No |
Countries with Delivered Custom Rules
Oracle ships predefined rules for 65 countries (listed in the full table below). All other countries use the default behaviour above.
Validation vs Display Rules
Two separate layers apply:
UI Rules — Which fields are shown and marked required on the employee bank account screen.
Cash Management Validation — Format checks on Bank Code, Branch Number, Account Number, Check Digit, and IBAN (length, numeric, check algorithms).
You can disable format validation using profile option CE_DISABLE_BANK_VAL. UI required/display rules are not affected by this profile.
Global Identifier Patterns by Region
This is the quickest way to understand what value belongs in Bank Code vs Branch Number globally.
North America
| Country | Code | Bank Code | Branch Number | Notes |
| Canada | CA | Institution Number (3 digits, e.g. 004) | Routing Transit Number (institution + 5-digit transit, e.g. 00400012) | Both required on employee UI |
| United States | US | Not used | Routing Transit Number (9-digit ABA) | Mod-10 check digit on routing number |
| Mexico | MX | Not used on standard UI | Not used on standard UI | CLABE (18 digits) captured in Secondary Account Reference |
Europe
| Country | Code | Bank Code | Branch Number | IBAN Required? |
| Germany | DE | BLZ (5 digits) | Optional (must match BLZ if entered) | Yes |
| France | FR | Bank Code (5 digits) | Branch Code (5 digits) | Yes |
| Netherlands | NL | Not used | Not used | Yes |
| Belgium | BE | Not used | Not used | Yes |
| Ireland | IE | Not used | Not used | Yes |
| Italy | IT | Not used | Not used | Yes |
| Spain | ES | Bank Code (4 digits) | Branch Code (4 digits) | Yes |
| Portugal | PT | Bank Code (4 digits) | Branch Code (4 digits) | Yes — both required on UI |
| Austria | AT | Bank Code (5 digits) | Branch Code (5 digits) | Yes |
| Finland | FI | Not used | Not used | Yes |
| Greece | GR | Not used | Not used | Yes (+ BIC required on UI) |
| Sweden | SE | Optional | Optional | No — if both entered, must match |
| Norway | NO | Not used | Branch Number (displayed) | No |
| Denmark | DK | Registreringsnummer (4 digits) | Not used | No |
| Switzerland | CH | Clearing Number (3–5 digits) | Not used | No |
| Poland | PL | Not used | Not used | Yes |
| Czech Republic | CZ | Not used | Not used | Yes (+ BIC required) |
| Romania | RO | Not used | Not used | Yes (+ BIC required) |
| Hungary | HU | Not used | Not used | No — Bank Name required |
| Turkey | TR | Not used | Not used | IBAN used for payments |
United Kingdom and Crown Dependencies
| Country | Code | Bank Code | Branch Number | Notes |
| United Kingdom | GB | Not used | Sort Code (6 digits) | Sort Code required; Roll Number in Secondary Account Reference for building societies |
| Guernsey | GG | Optional | Sort Code (6 digits) | Sort Code required |
| Jersey | JE | Optional | Sort Code (6 digits) | Sort Code required |
| Isle of Man | IM | Optional | Sort Code (6 digits) | Sort Code required |
Asia Pacific
| Country | Code | Bank Code | Branch Number | Notes |
| India | IN | Optional | IFSC Code (11 chars: AAAA0BBBBBB) | Bank Name + Branch Name required; IFSC in Branch Number field |
| Australia | AU | 2–3 digit bank code | BSB (6 digits combined with bank code) | BSB required; account 5–10 characters |
| New Zealand | NZ | Bank ID | Branch Number | Both required |
| Japan | JP | Bank Code (4 digits) | Branch Code (3 digits) | Bank + Branch Name and Number all required |
| China | CN | Optional | Not used | Bank Name + Branch Name required |
| Hong Kong | HK | Bank Code | Branch Number | Both required |
| Singapore | SG | Bank Code | Branch Number | Both required |
| Malaysia | MY | Bank Code | Branch Number | Bank + Branch Name required |
| Philippines | PH | Bank Code | Branch Number | Bank + Branch Name required |
| Republic of Korea | KR | Bank Code | Branch Number | Both required |
| Vietnam | VN | Optional | Not used | Bank Name required only |
| Pakistan | PK | Optional | Not used | Bank Name required |
Middle East
| Country | Code | Bank Code | Branch Number | IBAN Required? |
| United Arab Emirates | AE | Optional | Branch Number | Yes |
| Saudi Arabia | SA | Optional | Not used | Yes |
| Bahrain | BH | Not used | Not used | Yes |
| Kuwait | KW | Not used | Not used | Yes |
| Qatar | QA | Not used | Not used | Yes |
| Oman | OM | Not used | Branch Number (displayed) | No |
| Egypt | EG | Not used | Not used | Yes (+ BIC required) |
| South Africa | ZA | Not used | Branch Number | No — Branch Number required |
| Morocco | MA | Not used | Not used | No — Bank Name required |
| Sudan | SD | Not used | Not used | No — Bank Name required |
Latin America
| Country | Code | Bank Code | Branch Number | Notes |
| Brazil | BR | Bank Code (3 digits) | Branch (4 digits) + check digit | Both required; Company Code in Secondary Account Reference |
| Argentina | AR | Bank ID | Branch Number | Both required; CBU in Secondary Account Reference |
| Chile | CL | Not used | Not used | Bank Name + Account Type required |
| Colombia | CO | Not used | Not used | Bank Name + Branch Name required |
High Impact Country Mapping
Canada (CA)
| Field | UI Label | Required | Format / Rule |
| Bank Code | Institution Number | Yes | 3-digit institution number (e.g. 004 = TD) |
| Branch Number | Routing Transit Number | Yes | Institution + 5-digit transit (e.g. 00400012) |
| Account Number | Account Number | Yes | Required |
| IBAN | IBAN | No | Optional |
| BIC | BIC Code | No | Optional for domestic EFT |
United States (US)
| Field | UI Label | Required | Format / Rule | | Bank Code | Bank Code | No | Not typically used | | Branch Number | Routing Transit Number | Yes | 9 numeric digits; Mod-10 check digit validation | | Account Number | Account Number | Yes | Required | | Account Type | Account Type | Yes | Checking or Savings |
|
|
|---|
Routing Number Check: The 9th digit is a check digit calculated from the first 8 digits using a Modulus 10 algorithm with weighting factors 3-7-1-3-7-1-3-7.
United Kingdom (GB)
| Field | UI Label | Required | Format / Rule | | Bank Code | Bank Code | No | Not typically used | | Branch Number | Sort Code | Yes | 6 numeric digits (e.g. 200415) | | Account Number | Account Number | Yes | Required | | Secondary Account Reference | Building Society Roll Number | No | Used for building society accounts | | IBAN | IBAN | No | Optional |
|
|
|---|
|
|
|
|
India (IN)
| Field | UI Label | Required | Format / Rule | | Bank Name | Bank | Yes | Required | | Branch Name | Bank Branch | Yes | Required | | Bank Code | Bank Code | No | Optional | | Branch Number | IFSC Code | No (displayed) | 11 characters: 4 alpha + 0 + 6 alphanumeric (e.g. HDFC0001234) | | Account Number | Account Number | Yes | Required | | Account Type | Account Type | Yes | Required |
|
|
|---|
|
|
Australia (AU)
| Field | UI Label | Required | Format / Rule |
| Bank Code | Bank Code | No | 2 or 3 numeric digits if entered |
| Branch Number | Bank State Branch (BSB) | Yes | Bank Code + Branch Number combined = 6 numeric digits |
| Account Number | Account Number | Yes | 5–10 characters; numeric for AUD |
BSB Example: Bank Code 062 + Branch 000 = BSB 062000
Germany (DE)
| Field | UI Label | Required | Format / Rule |
| Bank Code | Bank Code (BLZ) | No | 5 numeric digits |
| Branch Number | Branch Number | No | 5 numeric digits; must match Bank Code if both entered |
| IBAN | IBAN | Yes | 22 characters; DE + 20 digits |
| BIC | BIC Code | No | Optional |
Brazil (BR)
| Field | UI Label | Required | Format / Rule |
| Bank Name | Bank | Yes | Required |
| Bank Code | Bank Code | Yes | 3 numeric digits |
| Branch Number | Branch Number | Yes | 4 numeric digits + check digit |
| Secondary Account Reference | Company Code | No | Company code for corporate accounts |
Complete Country Mapping
Need the complete mapping document? Please leave a comment below, and I'll be happy to share it with you
Quick Lookup: Branch Number Label by Country
| UI Label | Countries |
| Routing Transit Number | Canada, United States |
| Sort Code | United Kingdom, Guernsey, Jersey, Isle of Man |
| Bank State Branch (BSB) | Australia |
| IFSC Code | India |
| Registreringsnummer | Denmark (on Bank Code, not Branch) |
| Bank ID | Argentina, New Zealand |
| Clearing Number | Switzerland (on Bank Code) |
| Branch Number (generic) | Brazil, Japan, Singapore, Hong Kong, Korea, South Africa, and others |
Important Oracle Profile Options
CE_USE_EXISTING_BANK_BRANCH
Default
Allows users to create new banks and branches during entry.
Yes
Users must select from existing banks and branches.
CE_DISABLE_BANK_VAL
Default
Oracle validates:
-
IBAN
-
Routing Number
-
IFSC
-
Branch Code
-
Account Number
Yes
Skips country-specific validation (recommended only for controlled data migrations).
Best Practices
✔ Load bank master data before employee bank accounts.
✔ Enable existing bank selection in production.
✔ Validate IFSC, BSB, Routing Number, and Sort Code before migration.
✔ Use IBAN where supported.
✔ Keep Oracle profile options consistent across environments.
✔ Perform reconciliation after migration.
Common Implementation Mistakes
-
Entering IFSC in the Bank Code field instead of Branch Number (India).
-
Using an ABA Routing Number as the Account Number (US).
-
Omitting the Sort Code for UK accounts.
-
Missing Institution Number in Canada.
-
Incorrect IBAN length for European countries.
-
Disabling validations without reviewing migrated data.
Related Articles
You may also like:
Frequently Asked Questions (FAQ)
Q1. Does Oracle use the same bank fields for all countries?
Yes. The underlying attributes remain the same, but labels and validations vary by country.
Q2. Where is the IFSC Code stored in Oracle Fusion?
For India, the IFSC Code is entered in the Branch Number field.
Q3. What is the Branch Number in the United Kingdom?
It represents the Sort Code.
Q4. What is the Branch Number in Australia?
It represents the Bank State Branch (BSB).
Q5. Does Oracle validate IBAN?
Yes, unless the CE_DISABLE_BANK_VAL profile option is enabled.
Q6. Which table controls country-specific UI behaviour?
CE_CTRY_SPECIFIC_UI_RULES.
Q7. Can bank validation be disabled?
Yes, using the CE_DISABLE_BANK_VAL profile option.
Q8. Is IBAN mandatory for every country?
No. It is required only for countries where Oracle enforces IBAN validation.
Summary of Blog
Feedback Section
Was this guide helpful?
If this article helped you understand Oracle Fusion Global Bank and Branch Mapping, please:
-
Share it with your colleagues and implementation team.
-
Leave a comment with any country-specific scenarios or questions.
-
Subscribe to the blog for more Oracle Fusion HCM, Payroll, HDL, HCM Extracts, BI Publisher, OTBI, and technical implementation guides.
-
If you need end-to-end Oracle Fusion HCM technical training with real-time scenarios, HDL, Reports, and HCM Extracts, feel free to get in touch through the training form on this blog.
