Oracle Fusion HCM 25B Payroll: Smart Enhancements You Shouldn’t Miss

Fusion Practices

}

Apr 16, 2025

Oracle’s 25B update to Fusion HCM Payroll is more than a routine refresh — it’s a toolkit of practical improvements aimed at giving payroll professionals more control, precision, and efficiency. Whether you’re troubleshooting processes, refining costing logic, or managing complex reporting flows, these updates introduce meaningful changes that can streamline day-to-day operations.

Let’s explore what’s new and how you can make the most of it.

1. Smarter Logging: Say Goodbye to Unintended Performance Drains

Logging can be an incredibly useful tool when diagnosing tricky payroll processing issues — but if left on by accident, it can seriously bog down your system. Oracle’s 25B update introduces a safeguard: logging can no longer be enabled directly on the default process configuration group.

To use logging safely and effectively, you’ll now need to create a custom (user-defined) configuration group that mirrors your default setup, with logging parameters layered in. This helps prevent accidental logging on large-scale processes like the main payroll run, preserving performance while still allowing diagnostic flexibility when needed.

From 25B onwards, if you try to add logging to the default group, you’ll receive an error message. It’s a smart way to keep your system fast and clean, while still enabling targeted troubleshooting when required.

To know more about Fusion Practices' Oracle HCM Cloud Implementation Services

2. Personalised Costing Rules: Define Offset Accounts Using Employee Assignment Info

One of the more powerful updates in 25B allows payroll teams to assign offset accounts based on employee-specific details — think Department, Job, or Position. This means you can now tailor your costing eligibility rules more granularly at the payroll relationship level.

For example, you can route payroll charges like Federal Income Tax to different natural accounts based on which department an employee belongs to. This new logic sits higher in the costing hierarchy and makes your financial tracking significantly more accurate and aligned with organisational structure.

A key point: this feature only applies to payroll relationship-level elements. You can also control when the new logic activates using the configuration parameter Date used to

enable element eligibility hierarchy changes. It defaults to 1 June 2025, but you can delay it if your systems need more preparation time.

3. A Better View into Process Iterations: New Look, New Insights

If you’ve ever used “Submit Another Task” to automate multiple task submissions within a flow, you’ll appreciate the updated Process Results Detail page. It’s been redesigned using Oracle’s Redwood experience to provide a clearer view of each iteration.

Now, every individual task within the flow is displayed as a separate row. This makes it far easier to track outcomes, monitor issues, and drill down into results — especially useful when handling large multi-TRU reporting flows or other repeating tasks. For example, you can define a rule to automatically submit a year-end report for each TRU within your organisation

Oracle Fusion HCM 25B Payroll - Submitting a payroll flow

Customising Iterative Flows: Build It Your Way

While Oracle doesn’t ship ready-made flows that support task iteration, you now have the tools to build your own with total control. You can embed the ‘Submit Another Task’ component within a custom flow and then define rules to control how and when tasks repeat.

Once your flow is up and running, you can head to the Checklist to view all activity, outcomes, and process statuses in one place — making management and adjustments a lot easier.

Oracle Fusion HCM 25B Payroll - Payroll checklist

Submit Another Task Flow Checklist

  • Use the Roll Back All action to roll back all the results, including that of the multiple task iterations, for the process.
  • Use the Refresh option to refresh and reload the page.
  • The Parameters section displays the parameters of the Submit Another Task flow.
  • Click Submit Another Task to view the details of each submitted iteration.
Oracle Fusion HCM 25B Payroll - Submitting another task

New Flow Page Functionality: Drill Deeper into Every Task Iteration

The revamped Submit Another Task Flow page is now packed with useful features for monitoring and reviewing iterative flows. Here’s what you can do:

  • See each task iteration separately in an easy-to-scan table.
  • Use the Attachments tab to find reports and other submitted files.
  • Dive into the Logs tab for detailed information on processing — perfect for diagnosing issues.
  • Explore Parameters & Process History to understand exactly how and when processes were submitted.
  • Check the Messages tab for alerts or system feedback.
  • Click on any iteration to explore its details — right down to the results for each individual employee.

It’s a major usability upgrade, especially for teams managing complex or repetitive payroll flows.

4. Auto-Naming Your Payroll Flows: Let Business Rules Handle It

Naming your flow instances manually each time? That’s now a thing of the past. With the 25B update, you can automatically generate flow instance names using business rules set up through Oracle Visual Builder Studio (VB Studio).

This feature lets you define naming conventions based on input parameters like the Legislative Data Group and Flow Name. It brings consistency to your naming scheme and saves time during flow submissions — especially handy when handling high volumes of flows.

To get started, head to the Redwood Flow Submission page, go to Settings > Edit Page in Visual Builder Studio, and use the Configure Fields and Regions tool to define your rule logic.

5. Improved Pension Reporting Accuracy: Mid-Period Changes Handled Right

For UK organisations reporting to the Teachers’ Pension Scheme (TPS), there’s now a more precise approach to handling notional pensionable pay (NPP) during mid-period changes.

If a member experiences a change in their full-time equivalent (FTE) status or annual salary mid-period — especially in cases involving unpaid absences — the system now accurately calculates the prorated notional pay. This ensures the reported values reflect what the member would have earned if they’d remained on full pay for that service period.

This update applies to both A and U line types and enhances the handling of MCR (Monthly Contributions Reconciliation) split scenarios. It complements the existing method used when pay reduces due to long-term absence or leave, offering better accuracy and compliance for pension submissions.

Final Thoughts: Precision, Control, and Smarter Payroll Management

The Oracle Fusion HCM 25B update brings a host of practical changes that help payroll professionals operate more efficiently — from refined costing to enhanced reporting, better logging control, and smarter automation.

Whether you’re managing thousands of employees or fine-tuning your configuration, these updates give you the tools to get more done with less friction.

Oracle HCM Cloud Implementation button - Fusion Practices

Author: Sourav Malla

Get in touch with us

Read More

Related Posts