Oracle HCM Extract Best Practice: Draft vs Final Vendor Delivery Using Report Category

Introduction

One of the most common operational requirements in Oracle Cloud HCM and Payroll integrations is not just generating outbound vendor files—but controlling when those files are transmitted.

Typical outbound integrations include files sent to:

• Benefits providers
• Retirement vendors
• Garnishment agencies
• Payroll banking partners
• Insurance carriers
• Tax agencies
• External payroll processors

A very common business requirement looks like this:

Run the HCM Extract → Validate the output → If the results look correct, send the file to the vendor via SFTP

At first glance, teams often assume this requires:

• Custom orchestration
• Middleware intervention
• Manual file download/upload
• Duplicate extract definitions
• Custom ESS job chains

However, Oracle HCM Extract provides a standard capability that is often underutilized:

Report Category

This standard parameter allows implementation teams to control extract delivery behavior by associating different delivery configurations with different report categories.

With the right design, this provides a clean way to separate file generation from vendor transmission, without unnecessary customization.

---

The Common Business Problem

In many payroll and HCM outbound integrations, sending the file immediately after extract generation is not always desirable.

Examples include:

Payroll Vendor Files

A payroll deduction remittance file may require payroll or finance validation before transmission.

Benefits Enrollment Files

Benefit carrier enrollment files may need operational verification before delivery.

Garnishment Files

Incorrect transmission may create compliance or payment issues.

Tax Reporting Files

Organizations may require internal review before sending statutory reporting files externally.

In all these scenarios, the desired operational process becomes:

1. Generate file
2. Review output
3. Approve for release
4. Deliver to vendor

The challenge is enabling this process without introducing unnecessary architectural complexity.

---

Common, But Often Overengineered, Approaches

To solve this requirement, teams often consider:

• Creating separate draft and production extracts
• Middleware orchestration logic
• Manual download and upload processes
• Custom ESS scheduling chains
• External SFTP automation scripts

While these approaches can work, they often add complexity that may not be necessary.

---

The Standard Oracle Solution: Report Category

Oracle HCM Extract includes a standard parameter called:

Report Category

This parameter can be used to group and control extract delivery behavior.

Instead of treating delivery as a fixed part of extract execution, you can design multiple operational modes using report categories.

This becomes especially useful when outbound vendor files require business validation before release.

---

Practical Design Pattern: Draft vs Final

In this implementation approach, the same HCM Extract is configured with two report categories:

• Draft
• Final

Each category supports a different operational outcome. You can create any number of report categories and name them as per your needs.

---

Option 1: Draft

The Draft report category generates the file but keeps it internally accessible within Oracle/UCM without transmitting it externally.

Flow:

Run Extract (Draft)
→ File Generated
→ Payroll / HR Reviews Output
→ Business Approval

In this example, the Draft report category has one delivery option configured under it.

---

Option 2: Final

Once the draft output is validated, the same extract is rerun using the Final report category.

In this mode, the configured delivery options, such as SFTP, are executed.

Flow:

Run Extract (Final)
→ File Generated
→ Automatically Delivered via SFTP

This provides a clean operational promotion model from review to release.

---

Important Design Consideration

Since the extract is rerun in Final mode, organizations should ensure the underlying source data remains unchanged between Draft validation and Final transmission.

For payroll integrations, this typically means ensuring:

• Payroll results are finalized
• No retro changes occur between validation and transmission
• No operational changes impact extract data between runs

This avoids validating one dataset and transmitting another.

---

Real-World Payroll Example

Consider a 401(k)-deduction remittance file.

Business requirement:

• Generate deduction file after payroll
• Payroll team validates totals
• Confirm deduction balances match payroll register
• Only then transmit to Fidelity (vendor)

Without delivery control:

• File may be transmitted immediately
• Errors become vendor-facing operational incidents
• Corrections require rework and vendor coordination

With the Draft/Final report category approach:

Draft

• File generated
• Payroll validates totals
• Internal signoff obtained

Final

• Same extract reruns
• Approved file transmitted via SFTP

This creates a much cleaner operational model.

---

Why This Matters

This is not just a technical extract parameter.

This approach improves:

Operational Control

Prevents premature vendor transmission.

Error Prevention

Catches extract issues before they become external incidents.

Compliance Support

Useful for regulated outbound integrations.

Simplified Design

Avoids unnecessary middleware or duplicate solutions.

Supportability

Gives operations teams a predictable and manageable process.

---

Where This Pattern Works Well

This approach works especially well for:

• Payroll deduction remittance files
• Retirement contribution vendor files
• Benefit carrier interfaces
• Garnishment remittance files
• Tax reporting interfaces
• Banking/payment outbound files
• Third-party payroll vendor integrations

---

Practical Recommendation

For outbound vendor integrations, ask a simple question:

Should this file be transmitted immediately, or should the business validate first?

If validation is required, consider using Report Category strategically before introducing custom orchestration.

---

When This May Not Be Enough

While this pattern works well for many use cases, more complex scenarios may still require additional design considerations.

Examples include:

• Conditional routing to different vendors
• Multiple simultaneous delivery destinations
• Dynamic file naming rules
• Complex orchestration dependencies
• Approval workflows requiring system-enforced gating

In these cases, middleware or additional automation may still be appropriate.

---

Final Thoughts

Oracle often provides standard capabilities that solve practical implementation problems without customization.

Report Category in HCM Extract is one of those underused features.

If your operational requirement is:

Generate → Validate → Then Send

Do not immediately assume middleware or custom orchestration is required.

A simple Draft vs Final Report Category design may provide exactly the operational control your business needs—with far less complexity.

Oracle Payroll Integration with UKG: Calculation Card vs Element Entry — Understanding the Correct HDL Object

Introduction

When integrating UKG, or any external time system, with Oracle Cloud HCM Payroll, a common design question is:

Should time be loaded as Element Entries, or should we use PayrollTimeCard / PayrollAbsenceRecord HDL objects?

This blog clarifies the relationship between PayrollTimeCard.dat, PayrollAbsenceRecord.dat, ElementEntry.dat, and Calculation Cards, and explains the recommended design approach for Oracle Payroll integrations.

---

The Core Design Decision

There are two primary integration patterns for third-party time and absence data:

1. PayrollTimeCard.dat / PayrollAbsenceRecord.dat — time/absence-driven model
2. ElementEntry.dat — payroll-result-driven model

Calculation Cards should not be treated as a separate third option. They are the payroll representation layer where time and absence data may appear after being loaded through the correct business objects.

---

Key Clarification: Calculation Cards Are the Target Representation

The most important clarification is:

PayrollTimeCard.dat and PayrollAbsenceRecord.dat both populate Calculation Cards, but you should not use CalculationCard.dat directly to load time or absence data.

In other words, Oracle may create or update Calculation Cards as part of the payroll time or absence load process, but the integration should use the purpose-built HDL objects.

What This Means in Practice

• PayrollTimeCard.dat creates or updates Calculation Cards with time entries.
• PayrollAbsenceRecord.dat creates or updates Calculation Entries for absences.
• CalculationCard.dat should not be used for time or absence integration.

---

How Oracle Designed This

Oracle separates the object you load from where the data appears in payroll.

HDL Object	Purpose	Where Data Appears
PayrollTimeCard.dat	Time-card data	Calculation Cards / Calculation Entries
PayrollAbsenceRecord.dat	Absence data	Calculation Entries
ElementEntry.dat	Payroll-ready inputs	Element Entries
CalculationCard.dat	Generic calculation card object	Not recommended for time/absence loading

---

Pattern 1: PayrollTimeCard.dat — Recommended for Time

When to Use

Use PayrollTimeCard.dat when UKG is the system of record for approved time, but Oracle Payroll still needs to process the time data.

This approach is useful when Oracle Payroll needs to:

• Calculate overtime
• Apply premiums
• Handle costing
• Apply jurisdiction-specific payroll logic
• Preserve work-date level detail

What Happens

1. UKG sends approved time-card data.
2. PayrollTimeCard.dat is loaded.
3. Oracle validates the time-card elements.
4. Oracle creates or updates Calculation Cards.
5. Payroll processes the time entries.

---

Pattern 2: PayrollAbsenceRecord.dat — Recommended for Absences

When to Use

Use AbsenceEntry.dat when UKG or another external system sends approved absence data and you want Oracle Payroll to process absence-related payroll logic.

What Happens

• Absence records are loaded using PayrollAbsenceRecord.dat.
• Oracle creates the related calculation entries.
• Payroll processes the absence-related elements.

---

Pattern 3: ElementEntry.dat — Payroll-Ready Inputs

When to Use

Use ElementEntry.dat when UKG has already calculated the payroll values and Oracle Payroll only needs to consume the final results.

This may include:

• Regular pay
• Overtime
• Premiums
• Adjustments
• Payroll-ready hours or amounts

This pattern can be simpler, but it places more responsibility on the integration for validation, correction handling, duplicate prevention, and reconciliation.

---

Why Not Use CalculationCard.dat?

Although PayrollTimeCard.dat and PayrollAbsenceRecord.dat populate Calculation Cards, you should not use CalculationCard.dat directly for time or absence loads.

Using CalculationCard.dat for time or absence can create issues because:

• It bypasses purpose-built validation logic.
• It does not align with Oracle’s recommended payroll data model.
• It can make reconciliation and maintenance more difficult.

---

The Real Relationship

The correct way to think about this is:

PayrollTimeCard.dat and PayrollAbsenceRecord.dat are calculation-card-based integrations, but they are implemented through specialized business objects, not through CalculationCard.dat.

---

Benefits of PayrollTimeCard.dat and PayrollAbsenceRecord.dat

1. Data Model Alignment

• Matches Oracle Payroll architecture
• Preserves time and absence granularity

2. Built-In Validation

• Supports element eligibility validation
• Provides structured error handling

3. Better Reconciliation

• Aligns source system data with payroll processing
• Supports audit at a detailed level

---

Challenges to Plan For

1. Source Key Strategy

A strong source key strategy is required for updates, corrections, and reconciliation.

2. Correction Model

Corrections should generally be made in the source system and re-imported, rather than manually adjusted in payroll.

3. Visibility

• Data appears in Calculation Cards.
• It does not appear in Oracle Time and Labor time cards.

4. Setup Requirements

The design requires proper configuration of:

• Payroll elements
• Element eligibility
• Related generated elements where applicable

---

Practical Recommendation

Use PayrollTimeCard.dat when:

• You want time-driven payroll processing.
• You need detailed audit and reconciliation.
• You want Oracle Payroll to process time-card-style data.

Use PayrollAbsenceRecord.dat when:

• You are integrating approved absence data.
• You want Oracle Payroll to process absence-related payroll logic.

Use ElementEntry.dat when:

• You receive payroll-ready values from UKG.
• UKG has already calculated the final payable hours or amounts.

Avoid:

• Using CalculationCard.dat directly for time or absence data.

---

Conclusion

The confusion around Calculation Cards usually comes from treating them as an integration option rather than understanding what they represent.

Calculation Cards are the internal payroll representation of time and absence data, but the correct load mechanism is through the appropriate HDL business object.

Final Takeaway

• PayrollTimeCard.dat and PayrollAbsenceRecord.dat do populate Calculation Cards.
• You should not use CalculationCard.dat directly for time or absence loads.
• ElementEntry.dat remains valid for payroll-ready inputs.

Using the correct HDL object ensures that the integration is aligned with Oracle’s payroll architecture, easier to reconcile, and more scalable for long-term maintenance.

Oracle Cloud 25B: Enabling Approvals for Employee External Bank Account Creation and Modification

Introduction

A long-standing control gap in Oracle HCM and Payroll has been the lack of approval workflows for employee bank account changes. Organizations have consistently raised concerns about allowing employees to create or modify external bank accounts without validation or oversight.

With Oracle Cloud 25B, Oracle has introduced the ability to enforce approvals specifically for Employee External Bank Account creation and modification, adding a critical governance layer to payroll processing.

Business Context

Employee external bank accounts directly impact salary disbursement. Any incorrect or unauthorized change can lead to:

• Payments being routed to incorrect accounts
• Payroll failures and rework
• Increased risk of fraud
• Compliance and audit challenges

This enhancement introduces a structured approval mechanism to mitigate these risks within the application itself.

What’s Delivered in 25B

The solution is built using three core components:

1. Feature Opt-In for Payments
2. Controlled Lookup Enablement
3. Spreadsheet-Based Approval Rules

This functionality applies specifically to:

• Creation of external bank accounts
• Modification of external bank accounts

Step 1: Enable Feature Opt-In

Navigate to:

Setup and Maintenance > Financials > Payments > Edit Features

Enable:

Employee Bank Account Ownership Verification Workflow

This step activates the underlying approval framework.

Step 2: Enable Controlled Lookup

Navigate to:

Setup and Maintenance > Manage Standard Lookups

Search for:

ORA_ERP_CONTROLLED_CONFIG

Enable the following lookup:

• Lookup Code: IBY_37070344
• Meaning: Enable Bank Account Approval
• Status: Enabled

This lookup acts as the trigger for approval processing.

Step 3: Configure Approval Rules

Navigate to:

Manage User-Defined Rules for Employee Bank Account Approvals

Download:

ExternalBankAccountApprovalRulesTemplate.xlsm

Important

Ensure the following privilege is assigned:

IBY_MANAGE_BANK_ACCOUNT_APPROVALS_PRIV

Without this privilege, users will not be able to configure approval rules using the task Manage User-Defined Rules for Employee Bank Account Approvals.

Step 4: Define Approval Logic

Approval rules are defined using the Excel template.

In this implementation example, a two-level approval was configured:

1. Account Owner approval using username
2. Approval by users with the role KP_PAYROLL_ADMIN_VIEW_ALL_DATA

If multiple users have this role, any one of them can approve the notification.

After defining the rules in Excel:

1. Click Generate Rule File
2. A ZIP file will be generated
3. Upload the ZIP file back into Manage User-Defined Rules for Employee Bank Account Approvals

End-to-End Flow

1. Employee creates or updates an external bank account
2. System evaluates feature opt-in and lookup configuration
3. Approval rules are applied
4. Request is routed to approver or approvers
5. Upon approval, the bank account is created or updated

Basic Testing of Configuration

After completing the setup, perform a simple validation to confirm the configuration is working.

Test Steps

1. Login as an employee
2. Navigate to Me > Pay > Payment Methods
3. Add a new external bank account or update an existing one
4. Submit the transaction

Expected Result

• The change should not be applied immediately
• An approval request should be triggered
• The request should appear in the approver’s worklist or notifications

Approval Validation

1. Login as the approver
2. Open the approval notification
3. Approve the request

Result: The bank account should be successfully created or updated.

What This Confirms

• Feature opt-in is enabled correctly
• Lookup configuration is active
• Approval rules are functioning
• Workflow routing is working as expected

Key Observations

Scope of Approval

This feature applies only to:

• External bank account creation
• External bank account modification

It does not apply to other payment method configurations such as allocation or percentage splits.

Configuration Model

This feature is not configured like standard HCM approval transactions.

It does not use:

• Transaction Design Studio
• Standard BPM rule configuration

Instead, it relies on:

• Feature opt-in
• Controlled lookup
• Spreadsheet-based rule definition

Implementation Considerations

Payroll Timing

Bank account changes are applied only after approval. Approval timelines must align with payroll processing cutoffs to avoid delays.

Limitations and Considerations

While this feature addresses a critical control gap, there are important limitations to consider.

Limited Rule Authoring Model

Approval rules are defined using a spreadsheet template rather than the standard BPM rule UI.

This results in:

• Static, template-driven rules
• Limited flexibility compared to dynamic BPM configurations
• No support for advanced conditional expressions

No Support for AOR-Based Routing

Unlike other HCM approvals, this feature does not support routing based on Areas of Responsibility (AOR).

This means:

• Approval cannot dynamically route based on HR or payroll responsibility
• Routing must be predefined in the template

Limited Support for Complex Approval Scenarios

Compared to other HCM transactions, the following are not supported:

• Dynamic multi-stage approvals
• Parallel approval flows
• Rule chaining or advanced escalation logic

Approval flows are generally linear.

Dependency on Template Maintenance

Since rules are managed through a spreadsheet:

• Any change requires re-download and re-upload
• Version control must be managed externally
• There is a higher risk of manual errors

Limited Debugging Capability

Troubleshooting approval issues is less intuitive due to:

• Lack of visual rule builder
• Limited runtime diagnostics
• Errors often identified only during upload or execution

Practical Recommendations

• Start with simple approval rules, such as manager-based or payroll-admin-based routing
• Avoid overly complex logic
• Maintain proper documentation of rule logic
• Establish governance for template updates
• Validate the approval flow before enabling in production

Compliance and Audit

This feature strengthens:

• Audit traceability
• Internal controls
• Fraud prevention

User Communication

Employees should be informed that:

• Bank account changes require approval
• Changes are not immediate
• Approval must be completed before the change becomes effective

Conclusion

Oracle Cloud 25B introduces an essential control for managing employee external bank account changes.

By combining feature enablement, controlled configuration, and approval rules, organizations can significantly improve governance over payroll-critical data.

This is a practical enhancement that should be enabled and validated as part of any payroll implementation.