Oracle Cloud Payroll: Loading Payroll-Ready Time Transactions Using PayrollTimeCard HDL
Introduction
Oracle Payroll provides a powerful HDL business object that is often overlooked:
PayrollTimeCard
This object allows organizations to load payroll-ready time transactions directly into Oracle Payroll.
This capability is particularly valuable when an external workforce management system is responsible for collecting, approving, and calculating employee time before it reaches Oracle.
Examples of external workforce management systems include:
- UKG
- Kronos
- Workforce Software
- ADP eTime
- Workday Time Tracking
- Custom Time Collection Applications
Instead of recreating complex time rules in Oracle, organizations can load the approved payroll-ready results.
A Common Misconception
One misconception I frequently encounter is that any time-related transaction must be loaded using:
- Oracle Time and Labor
- AbsenceEntry HDL
- ElementEntry HDL
In reality, Oracle provides a dedicated HDL object specifically designed for payroll time transactions:
PayrollTimeCard
Another common misconception is that PayrollTimeCard is the same as a Payroll Calculation Card.
It is not.
| Object | Purpose |
|---|---|
| CalculationCard.dat | Tax cards, involuntary deductions, benefits, pensions |
| PayrollTimeCard.dat | Payroll-ready time transactions |
| AbsenceEntry.dat | Absence transactions |
| ElementEntry.dat | Payroll element entries |
Understanding this distinction can simplify many integration designs.
Business Scenario
Consider a simple example.
An employee has:
4 Hours of OT Straight
on:
20-May-2026
The time has already been:
- Entered
- Approved
- Calculated
within an external workforce management application.
The business does not want Oracle to:
- Calculate time
- Evaluate time rules
- Recreate time calculation logic
Instead, Oracle Payroll simply needs the final transaction for payroll processing.
This is an ideal use case for PayrollTimeCard HDL.
Sample HDL
The following HDL creates both a payroll time card and a related time entry.
METADATA|PayrollTimeCard|LegislativeDataGroupName|AssignmentNumber|EffectiveStartDate|EffectiveEndDate|TimeCardId MERGE|PayrollTimeCard|US Legislative Data Group|E100|2026/05/20|2026/05/20|10020260520 METADATA|TimeEntry|LegislativeDataGroupName|AssignmentNumber|EffectiveStartDate|EffectiveEndDate|TimeType|Time|UnitOfMeasure|TimeCardId|TimeEntryId|Periodicity|Factor|RateName|RateValue|Segment1 MERGE|TimeEntry|US Legislative Data Group|E100|2026/05/20|2026/05/20|OT Straight|4|H_DECIMAL3|10020260520|1002026052001|HOURLY||||
Understanding the PayrollTimeCard Record
The first section creates the parent payroll time card.
MERGE|PayrollTimeCard|US Legislative Data Group|E100|2026/05/20|2026/05/20|10020260520
Legislative Data Group
US Legislative Data Group
Defines the legislative context.
Assignment Number
E100
Identifies the employee assignment.
Effective Dates
2026/05/20
Represents the date associated with the payroll transaction.
TimeCardId
10020260520
Acts as the parent identifier used to associate TimeEntry records with the time card.
Understanding the TimeEntry Record
The second section creates the actual payroll transaction.
MERGE|TimeEntry|US Legislative Data Group|E100|2026/05/20|2026/05/20|OT Straight|4|H_DECIMAL3|10020260520|1002026052001|HOURLY||||
Time Type
OT Straight
Identifies the type of payroll time being loaded.
Examples include:
- OT Straight
- Overtime
- Double Time
- Shift Differential
Time
4
Represents the quantity.
Unit of Measure
H_DECIMAL3
Indicates hours with three-decimal precision.
Examples:
8.000 4.500 2.250
TimeEntryId
1002026052001
Unique identifier for the individual time transaction.
Periodicity
HOURLY
Defines how Payroll interprets the transaction.
Why Use PayrollTimeCard HDL?
Many organizations already have mature workforce management platforms.
These systems may already calculate:
- Overtime
- Double Time
- Shift Premiums
- Call Back Pay
- On Call Pay
- Hazard Pay
Recreating those same calculations in Oracle often leads to:
- Duplicate rule maintenance
- Increased testing effort
- Additional support overhead
Using PayrollTimeCard HDL allows Oracle Payroll to consume the final approved results.
Additional Attributes and Costing
TimeEntry supports additional attributes that can be used for labor allocation and payroll processing.
Examples include:
Segment1 Segment2 Segment3
These attributes can be leveraged to pass:
- Cost centers
- Departments
- Projects
- Labor allocations
from external systems into Oracle Payroll.
This can be especially useful when integrating with UKG or Kronos labor tracking structures.
Rollback Capability
One of the most useful features of HDL is the ability to roll back a load.
If an incorrect time card is loaded:
- A separate delete HDL file is not required
- Administrators can roll back the HDL load
- Correct the source file
- Reload the transactions
This significantly simplifies:
- Testing
- Data conversion
- Payroll parallel runs
- Production support
Compared to manually creating reversal HDL files, rollback can save considerable effort.
Typical Use Cases
I commonly see PayrollTimeCard HDL used for:
UKG Integrations
Loading approved payroll hours directly into Oracle Payroll.
Kronos Integrations
Loading overtime, premiums, and shift differentials.
Workforce Software Integrations
Passing final payroll-ready transactions.
Legacy Time Systems
Migrating approved time transactions into Oracle.
Payroll Conversion Projects
Loading historical payroll time transactions during implementation.
Testing Recommendations
Before moving to production, validate:
- HDL load success
- PayrollTimeCard creation
- TimeEntry creation
- Payroll calculation results
- Time type mappings
- Labor allocation values
- Payroll balances
- Retro processing behavior
Particular attention should be paid to overtime and premium calculations when external systems are performing the calculations.
Final Thoughts
Many Oracle Payroll implementations spend considerable effort recreating time calculation logic that already exists in external workforce management applications.
The PayrollTimeCard HDL business object provides a simpler alternative.
If your external system is already producing approved payroll-ready time transactions, consider loading the final results directly into Oracle Payroll rather than duplicating complex rules inside Oracle.
Used correctly, PayrollTimeCard HDL can simplify integrations, reduce maintenance effort, and streamline payroll processing while maintaining a clear audit trail between the source time system and Oracle Payroll.
No comments:
Post a Comment