Using Bank.dat and BankBranch.dat (Step-by-Step Guide)
In Oracle Fusion HCM, bank and bank branch records are commonly required for payroll implementations, employee payment methods, and external bank integrations.
Instead of manually creating bank and branch records in the UI, Oracle provides a faster method using HCM Data Loader (HDL).
In this guide, you’ll learn:
-
How to load Bank using
Bank.dat -
How to load Bank Branch using
BankBranch.dat -
Sample HDL templates
-
Best practices, common issues, FAQs
✅ Prerequisites
Before loading bank data using HDL, ensure:
-
You have access to HCM Data Loader
-
You have required roles to load banking data
-
You have correct details like:
-
Bank Name
-
Country Code
-
Bank Number
-
Branch Number
-
Swift Code (optional)
-
📌 Important Note
✔ Always load Bank first, then load Bank Branch.
Because Bank Branch uses BankName as a reference.
🏦 Part 1: Load Bank Details Using Bank.dat
Step 1: Create Bank.dat file
Use the below HDL template:
✅ Sample HDL File for Bank
Field Explanation (Quick)
-
BankName → Bank name as required in Fusion
-
CountryCode → Example: US, IN, AE
-
BankNumber → Unique identifier for the bank
-
SourceSystemOwner → Your HDL source (example XXTEST)
-
SourceSystemId → Unique record ID (must be unique)
Step 2: Zip and Upload
-
Save file name as: Bank.dat
-
Compress into zip file:
-
Example:
Bank.zip
-
-
Navigate to:
My Client Groups → Data Exchange → HCM Data Loader → Import and Load
-
Upload ZIP and load
🏦 Part 2: Load Bank Branch Details Using BankBranch.dat
Once Bank is created successfully, load branches.
Step 1: Create BankBranch.dat file
✅ Sample HDL File for Bank Branch
Field Explanation (Quick)
-
BankName → Must match the bank name already loaded
-
BankBranchNumber → Branch identifier
-
BankBranchName → Branch name
-
CountryCode → Same as bank country
-
EftSwiftCode → Optional (Swift/BIC code)
-
SourceSystemId → Unique record ID
Step 2: Zip and Upload
-
Save file name as: BankBranch.dat
-
Zip it:
-
Example:
BankBranch.zip
-
-
Upload using:
My Client Groups → Data Exchange → HCM Data Loader → Import and Load
✅ Best Practices (Highly Recommended)
-
Always load Bank first, then BankBranch
-
Keep SourceSystemId unique for every record
-
Use meaningful SourceSystemId naming like:
-
XX_BANK_US_001 -
XX_BRANCH_US_001
-
-
Maintain a tracker Excel for:
-
Bank Name
-
Bank Number
-
Branch Number
-
Swift Code
-
-
Validate country code is correct (ISO format)
⚠️ Common Issues and Fixes
Issue 1: Bank Branch fails with “Bank not found”
✅ Fix:
Bank must exist before branch load. Load Bank.dat first.
Check Bank reference in Bank Branch file is correct.
Issue 2: Duplicate record error
✅ Fix:
Change SourceSystemId and ensure it is unique.
Issue 3: CountryCode mismatch
✅ Fix:
CountryCode in BankBranch must match the Bank’s country.
⭐ FAQ
1. Which HDL files are used to load bank and bank branches?
You should use:
-
Bank.dat for bank records
-
BankBranch.dat for branch records
2. Do we need to load bank before bank branch?
Yes. Bank must exist first because bank branch references the bank name.
3. Can we load multiple banks in one HDL file?
Yes. Add multiple MERGE lines:
4. Can we load multiple branches for the same bank?
Yes. Add multiple MERGE lines in BankBranch.dat.
5. Is Swift Code mandatory in BankBranch.dat?
No. It is optional, but recommended if required for EFT / international payments.
6. Where can we verify banks and branches in Fusion?
You can verify from:
Setup and Maintenance → Manage Banks
(or Bank-related setup tasks depending on your configuration)
