⭐ HDL Template for External Bank Account Details in Oracle Fusion HCM
ExternalBankAccount.dat + ExternalBankAccountOwner.dat Step-by-Step Guide
In Oracle Fusion HCM, employee bank account details are required for payroll processing and payments.
Instead of entering bank accounts manually in the UI, you can load them in bulk using HCM Data Loader (HDL).
This blog explains how to load:
✅ External Bank Account (Account details)
✅ External Bank Account Owner (Employee mapping)
using ExternalBankAccount.dat.
For this use ExternalBankAccount.dat file.
You can see step by step video to load External Bank Account Details using this Link
✅ Prerequisite (Mandatory)
Before loading external bank accounts:
1) Bank and Bank Branch must already exist in Fusion
You must load:
📌 If Bank / Branch does not exist, the ExternalBankAccount load will fail.
✅ HDL File Used
For this requirement use:
📌 ExternalBankAccount.dat
✅ Business Objects Used
HDL requires these objects:
1) ExternalBankAccount
Stores bank account master information.
2) ExternalBankAccountOwner
Links the bank account to the employee/person.
Click here to find the sample bank details.
📌 Sample HDL Template (External Bank Account)
1) ExternalBankAccount (Bank Account Master)
-
AccountNumber must be valid format as per business rules
-
BankBranchName + BankName must match the existing bank setup
-
CountryCode / CurrencyCode should match bank country
2) ExternalBankAccountOwner (Link to Employee)
-
PersonNumber → Employee person number
-
ExternalBankAccountId(SourceSystemId) → must match the ExternalBankAccount SourceSystemId
-
BankNumber + BankBranchNumber → must match what you loaded in Bank.dat and BankBranch.dat
✅ Step-by-Step Process to Load External Bank Account Using HDL
Step 1: Prepare the ExternalBankAccount.dat file
Include both sections:
-
ExternalBankAccount
-
ExternalBankAccountOwner
Step 2: Save and ZIP the file
Save as:
✅ ExternalBankAccount.dat
Compress into:
✅ ExternalBankAccount.zip
Step 3: Upload via HDL
Go to:
My Client Groups → Data Exchange → HCM Data Loader → Import and Load
Upload and submit the ZIP file.
Step 4: Verify the results
After successful load, validate from UI:
Navigation (Common)
My Client Groups → Person Management → Search Person → Payment Methods / Bank Accounts
(Exact path depends on your security role.)
⭐ Best Practices (Recommended)
-
Always load Bank + Bank Branch first
-
Use meaningful SourceSystemId format like:
-
EXTBANK_E12345_01
-
EXTBANKOWNER_E12345_01
-
Ensure BankName and BankBranchName match exactly
-
Keep one bank account per row (avoid duplicates)
-
Maintain separate IDs for each person and account mapping
-
Use consistent CountryCode + CurrencyCode
⚠️ Common Errors and Fixes
❌ Error: “Bank branch not found”
✅ Fix:
Load BankBranch.dat first and ensure BankBranchName matches.
❌ Error: “Invalid PersonNumber”
✅ Fix:
Confirm the worker exists and PersonNumber is correct.
❌ Error: “ExternalBankAccountId not found”
✅ Fix:
Make sure:
ExternalBankAccountId(SourceSystemId) = SourceSystemId of ExternalBankAccount row.
❌ Error: “Duplicate bank account”
✅ Fix:
Use unique SourceSystemId for each account record.
🔗 Internal Links Section
Add this section near the end of the blog:
🔗 Related HDL Templates (Must Read)
(Replace these with your actual post links.)
❓ FAQ
1) Which HDL file is used to load external bank accounts in Oracle Fusion HCM?
External bank accounts are loaded using ExternalBankAccount.dat.
2) What is ExternalBankAccountOwner used for?
ExternalBankAccountOwner is used to link the bank account to a person (employee) using PersonNumber.
3) Can I load external bank account without loading bank and branch?
No. Bank and branch must exist first, otherwise HDL will fail.
4) What is the key linking field between account and owner?
The linking happens using:
ExternalBankAccountId(SourceSystemId)
5) Can I load multiple accounts for the same employee?
Yes. Create separate ExternalBankAccount and ExternalBankAccountOwner rows with unique SourceSystemId.
