Error While Loading PersonalPaymentMethod Using HCM Data Loader
Introduction
Oracle Fusion HCM HCM Data Loader (HDL) is commonly used to load payroll-related data such as Personal Payment Methods. However, while loading PersonalPaymentMethod.dat, you may encounter validation errors related to bank account resolution.
One of the most common errors is:
HRC-1035539 – The values {attributes} are not valid for the attribute BankAccountId
This blog explains why this error occurs, the root causes, and multiple solutions to fix it using real project scenarios.
Cause Analysis
Cause 1: Missing BankAccountType
Consider a scenario where two bank accounts exist for the same person:
-
Bank Account 1 → No BankAccountType
-
Bank Account 2 → Has BankAccountType
In this case:
-
If you refer to Bank Account 1, HDL can resolve it without BankAccountType
-
If you refer to Bank Account 2, BankAccountType becomes mandatory
❗ If the existing ExternalBankAccount has a value for BankAccountType, it must be provided in PersonalPaymentMethod.dat.
Cause 2: Invalid Bank Account Attribute Combination
The system is unable to identify a valid BankAccountId because the values provided for:
-
BankName
-
BankCountryCode
-
BankAccountNumber
-
BankAccountType
-
BankBranchName
-
BankBranchNumber
do not match any existing External Bank Account in Oracle Fusion.
Solution 1: Provide BankAccountType When Required
If the External Bank Account already has a BankAccountType, then it must be passed in PersonalPaymentMethod.dat.
Best Practice
✔ Always provide BankAccountType when multiple bank accounts exist
✔ Ensure the value exactly matches what exists in Fusion
This ensures unique resolution of ExternalBankAccount.
Solution 2: Validate Bank Account Details in Fusion
Ensure that the following attributes in PersonalPaymentMethod.dat match an existing bank account:
-
Bank Name
-
Bank Country Code
-
Bank Account Number
-
Bank Account Type
-
Bank Branch Name
-
Bank Branch Number
If any of these values are incorrect, Fusion will fail to resolve the BankAccountId.
Query to Validate Bank Account Data
Use the below SQL query to verify whether the bank account exists and matches the provided details:
🔎 Replace data with values from your PersonalPaymentMethod.dat file.
Final Root Causes Summary
Cause 1
-
BankAccountType not provided even though it exists in the system
Cause 2
-
No matching BankAccountId exists for the provided bank details
Conclusion
The error occurs when Oracle Fusion HCM cannot uniquely identify the External Bank Account for a Personal Payment Method. By ensuring accurate bank details and providing BankAccountType when required, this issue can be resolved effectively.
This approach is widely used in payroll implementations and data migration projects.
