Oracle HCM Data Loader (HDL) Example: Loading Payroll Costing Using CostAllocationV3
Introduction
Oracle Fusion HCM Payroll Costing enables organizations to allocate payroll expenses to General Ledger (GL) accounts for accurate financial reporting and accounting. Using HCM Data Loader (HDL), payroll costing can be loaded in bulk, making implementation and data migration activities significantly easier.
In this article, we'll walk through a complete HDL example for loading Payroll Costing, including:
What is Payroll Costing in Oracle HCM?
Payroll Costing determines how payroll expenses are distributed to accounting segments and eventually transferred to the General Ledger.
Costing can be configured at various levels:
Payroll Level
Department Level
Position Level
Element Eligibility Level
Person Level
The Payroll Level is generally used for segments that rarely change across employees such as:
Company
Business Unit
Fund
Line of Business
Why Configure Costing at Payroll Level?
Organizations often maintain multiple payrolls such as:
Weekly Payroll
Biweekly Payroll
Monthly Payroll
Instead of assigning identical costing information to every employee, Payroll Level Costing allows common accounting segments to be configured once and inherited by all workers within that payroll.
Benefits
✔ Simplifies costing setup
✔ Reduces maintenance effort
✔ Supports General Ledger integration
✔ Improves payroll accounting accuracy
✔ Supports suspense and default accounts
Business Scenario
A fictional organization, GlobalTech Solutions, maintains a monthly payroll named:
GlobalTech Monthly Payroll
The Payroll team wants to:
Cost all payroll expenses to a predefined cost account.
Configure Default Account.
Configure Suspense Account.
Transfer payroll costing to General Ledger.
Payroll Costing Structure
Cost Account
| Segment | Description | Value |
| Segment1 | Company | 2001 |
| Segment2 | Cost Center | 3001 |
| Segment3 | Fund | 4001 |
| Segment4 | Department | 5001 |
| Segment5 | Business Unit | 6001 |
| Segment6 | Program | 7001 |
| Segment7 | Natural Account | 8001 |
| Segment8 | Project | 9001 |
Suspense Account
All segments:
0000.0000.0000.0000.0000.0000.0000.0000
Default Account
All segments:
0000.0000.0000.0000.0000.0000.0000.0000
Step 1: Create Cost Allocation Record
CostAllocationV3.dat
METADATA|CostAllocationV3|EffectiveEndDate|EffectiveStartDate|SourceType
|PayrollCode|LegislativeDataGroupName
MERGE|CostAllocationV3|4712/12/31|2025/01/01|PAY|GlobalTech Monthly Payroll
|GlobalTech US LDG
Explanation
| Field | Description |
| SourceType | PAY = Payroll Level Costing |
| PayrollCode | Payroll Name |
| LDG | Legislative Data Group |
| EffectiveStartDate | Costing Effective Date |
Step 2: Load Payroll Costing Accounts
CostAllocationAccountV3.dat
METADATA|CostAllocationAccountV3|SourceType|PayrollCode|LegislativeDataGroupName
|EffectiveDate|SourceSubType|Proportion|SubTypeSequence|ConcatenatedSegment
|Segment1|Segment2|Segment3|Segment4|Segment5|Segment6|Segment7|Segment8
MERGE|CostAllocationAccountV3|PAY|GlobalTech Monthly Payroll|GlobalTech US LDG
|2025/01/01|COST|1|1||2001|3001|4001|5001|6001|7001|8001|9001
MERGE|CostAllocationAccountV3|PAY|GlobalTech Monthly Payroll|GlobalTech US LDG
|2025/01/01|SUSP|1|1|0000.0000.0000.0000.0000.0000.0000.0000||||||||
MERGE|CostAllocationAccountV3|PAY|GlobalTech Monthly Payroll|GlobalTech US LDG
|2025/01/01|DFLT|1|1|0000.0000.0000.0000.0000.0000.0000.0000||||||||
Understanding Source Sub Types
COST
Primary payroll expense account.
Used to charge payroll expenses.
Example:
2001.3001.4001.5001.6001.7001.8001.9001
SUSP (Suspense Account)
Used when payroll costing cannot determine a valid account combination.
Example:
0000.0000.0000.0000.0000.0000.0000.0000
DFLT (Default Account)
Used when account information is missing during payroll costing.
Example:
0000.0000.0000.0000.0000.0000.0000.0000
Payroll Costing Flow
 |
| Payroll costing process flow diagram |
HDL Upload Steps
Step 1
Create CostAllocationV3.dat
Step 2
Create CostAllocationAccountV3.dat
Step 3
Zip HDL files
Payroll_Costing.zip
Step 4
Navigate to:
My Client Groups
→ Data Exchange
→ Import and Load Data
Step 5
Upload ZIP file.
Step 6
Submit HDL Process.
Step 7
Verify Status:
Completed Successfully
Validation Checklist
Before Upload
After Upload
Common HDL Errors
Error: Payroll Not Found
Cause:
Incorrect Payroll Code.
Solution:
Verify Payroll Name exactly matches Oracle Payroll.
Error: LDG Not Found
Cause:
Invalid Legislative Data Group.
Solution:
Validate LDG configuration.
Error: Invalid Segment Combination
Cause:
GL account combination not valid.
Solution:
Validate accounting flexfield combinations.
Error: Cost Allocation Already Exists
Cause:
Duplicate costing record.
Solution:
Use MERGE instead of CREATE.
Best Practices
Always configure Suspense Account.
Always configure Default Account.
Validate account combinations before migration.
Test in lower environments first.
Reconcile payroll costing with Finance team.
Maintain version-controlled HDL templates.
Document all segment mappings.
Frequently Asked Questions (FAQ)
Can Payroll Costing be loaded using HDL?
Yes. Oracle supports payroll costing using CostAllocationV3 and CostAllocationAccountV3 business objects.
Why should I configure Suspense Accounts?
Suspense Accounts prevent payroll costing failures when valid costing information is unavailable.
Can multiple payrolls have different costing accounts?
Yes. Each payroll can have its own costing configuration.
What is SourceType PAY?
PAY indicates Payroll Level Costing.
What is the difference between COST, DFLT, and SUSP?
Can payroll costing be updated later?
Yes. Use HDL MERGE statements to update costing records.
