Oracle Cloud HCM 26A Release: Every New Feature, Redwood Upgrade, and Mandatory Payroll Change Explained

Oracle released 26A in the first quarter of 2026. I have reviewed the official readiness documentation from June 2026. You may notice that most blogs treat this as a routine quarterly patch. That approach misses the strategic shift.

This release completes major Redwood UI migrations. It introduces strategic AI agents that can take action, not just suggest answers. It also forces mandatory US payroll changes. The Vertex tax engine replacement is not optional for US customers.

I’ve written this guide after analyzing official Oracle docs, Arclight Consulting release notes, and HighStreetIT payroll analysis. You’ll find page-level Redwood updates, a full agent inventory, mandatory compliance checklists, and a verdict at the end. I’ve organized everything for quick scanning.

If you manage HRIS, payroll, or consulting for global enterprises with 1,000 or more employees, this release affects your daily work. Let me show you exactly how.

Key Insights

These are the verified facts from official sources. I confirmed each point against Oracle documentation, Gartner reports, and analyst data.

Key Finding	Why You Should Care
26A completes major Redwood migrations for core data, compensation, and HR pages.	Your customized pages may redirect or change. You’ll want to test configurations in sandbox first.
600 plus AI agents are embedded across Fusion Cloud at zero extra licensing cost.	You may have already paid for AI features in other platforms. Here they are included by default.
Mandatory US payroll shift: Vertex is replaced by USOPTE in 26A.	Your tax calculations, address verification, and jurisdiction mapping will fail if you do not prepare.
UK legislative updates include P60 template changes and FPS address reporting options.	Non-compliance affects year-end reporting and statutory payment accuracy for UK employees.
New strategic AI agents include Jobs Assistant and Workforce Structures Insight Analyst.	These are not operational chatbots. They support strategic workforce planning and job profile generation.

What Makes 26A Different From Previous Updates?

Most quarterly releases just add small features, but 26A isn’t like that. Actually, I see three strategic phases converging in this single update, and that’s pretty unusual.

First, Redwood standardization reaches a new milestone. Anyway, previous releases introduced Redwood pages slowly. So now, core data, compensation, and HR processes use Redwood as the standard interface.

Second, agentic AI moves from advisory to action-taking. So you may use agents that generate jobs, analyze workforce structures, assist data loading, and refine compensation instructions. Anyway, these agents operate within policy guardrails.

Third, mandatory compliance modernization removes third-party dependencies. Well, Oracle is replacing Vertex with its own US tax engine. Plus, UK statutory updates are enforced by release date, not optional.

You can treat 26A as a strategic inflection point rather than a routine patch.

Also read: Cloud Storage Alternatives

Redwood UI Upgrades in 26A

Well, I’ve reviewed the Redwood migration list from Arclight Consulting. Anyway, several pages moved from partial or legacy interfaces to full Redwood in 26A. So, you’ve got the option to customize these pages using Visual Builder Studio.

Human Resources Redwood Updates

The View Business Objects page in the Data Exchange work area is now fully available in Redwood. You can search, review, and manage business objects supported by the HCM Data Loader and Spreadsheet Data Loader. I’d recommend testing your custom data loader configurations against this new interface.

Role Mappings pages also received full Redwood upgrades. You may see expanded business rule support and new configurable fields. Check your existing role mappings before activation.

The HCM Extracts work area now includes a new User Entity Details page. You can search and review entity details without navigating legacy extract interfaces. That cuts the time needed for data audits.

Compensation Redwood Updates

The Salary and Administrative Individual Compensation pages now display prior compensation history directly in Redwood. You do not need to open separate historical records. The Additional Compensation section on the Redwood Employment Info page is also visible when enabled through Visual Builder Studio.

Workforce Compensation Approval received a full Redwood worksheet. Line managers can access it from the Approve tab on the Landing Page. The overflow menu now allows managers to change access and due dates for all managers at once. You may want to retrain managers on this new flow.

Here’s a quick reference table I built from the official release notes.

Redwood Page or Area	Status Before 26A	26A Update	What You Should Check
View Business Objects (Data Exchange)	Partial or legacy interface	Full Redwood with configurable properties	Custom data loader configurations
Role Mappings	Partial or legacy interface	Full Redwood with expanded rules	All role mapping assignments
HCM Extracts User Entity Details	Legacy review process	New Redwood search and review page	User training materials
Salary and Individual Compensation	Basic Redwood display	Prior history visible directly	Historical data accuracy
Additional Compensation Section	Hidden by default	Visible when enabled in VBS	Visual Builder Studio settings
Workforce Compensation Approval	Legacy or basic interface	Full Redwood worksheet with overflow menu	Manager training plans

New AI Agents and Generative AI Features

Well, here’s the deal: most sources say “AI is embedded in HCM,” but that’s not really helpful, is it?

So, I’ve counted every verified agent listed in the official Oracle Fusion AI documentation updated June 10, 2026. Anyway, I’ll show you exactly which agents arrived in 26A and what each one does.

Human Resources and Workforce Planning Agents

The Jobs Assistant arrived in 26A. You can give it a job name and job code. It then generates a complete job profile using organizational structure rules, skill requirements, and existing templates. I’m seeing this reduce manual job profile creation significantly.

The Workforce Structures Insight Analyst also arrived in 26A. You can ask it to pull workforce data and apply scenario modeling. For example, you may ask what labor costs look like if you shift 15 percent of full-time staff to part-time in Q3. The agent presents a structured insight report.

HCM Common Agents

The AI Agent for HCM Data Loader is new in 26A. It assists with bulk data import. It validates mappings, suggests corrections based on previous loads, and flags conflicts against security rules. You may find this valuable during acquisitions or large hiring events.

The Employee Self-Service agent received enhanced AI assistance in 26A. It’s using company policy documents to deliver more tailored support. When an employee asks about direct deposit changes, the agent retrieves the current policy and guides the user through the correct form.

The Team Management agent also received 26A enhancements. It’s integrating workforce data to provide recommendations for managers handling team-level HR actions.

Compensation Agents

The Compensation Advisor for my team now includes market composite data in 26B. In 26A, you can see the foundation through enhanced AI assistance for individual compensation plan instructions. Admins can now revise, expand, summarize, or formalize instructions using five AI options.

Before 26A, you could generate instructions. Now you can refine them directly in the workflow.

The Peer-Group Salary Benchmarking feature also arrived in 26A. Managers can compare team salaries using peer-group market composites.

Absence, Benefits, and Dynamic Skills Agents

The Time-off Assistant in 26A uses uploaded company policies to deliver tailored time-off assistance. The Leave and Absence Policy Advisor from 25C continues to support absence rules based on policy documents.

For dynamic skills, the Skill Suggestions for Learning Items feature uses generative AI in 26A. It’s suggesting skills based on learning item descriptions. The Skills Library Description Agent from 25D continues to generate skill descriptions from library templates.

Here’s the agent inventory table I compiled from official readiness documentation.

Module	Agent or Feature Name	Release	Type	What It Does for You
HCM Common	AI Agent for HCM Data Loader	26A	Agent	Validates bulk imports and suggests corrections
HCM Common	Employee Self-Service with AI Assistance	26A	Agent	Policy-aware employee guidance and form help
HCM Common	Team Management with AI Assistance	25D, enhanced 26A	Agent	Manager-level team HR recommendations
Human Resources	Jobs Assistant	26A	Agent	Generates job profiles from name and code
Human Resources	Workforce Structures Insight Analyst	26A	Agent	Workforce scenario analysis and reporting
Compensation	Compensation Plan Instruction Refinement	26A	Generative	Revise, expand, summarize, or formalize instructions
Compensation	Peer-Group Salary Benchmarking	26A	Agent	Peer-group salary comparison for managers
Absence	Time-off Assistant	26A	Agent	Policy-aware time-off assistance
Dynamic Skills	Skill Suggestions for Learning Items	26A	Generative	Suggests skills for learning items

Mandatory Payroll Changes: The Vertex Replacement

Let’s discuss these important changes too.

I’ve reviewed the HighStreetIT analysis from January 20, 2026, and the Arclight Consulting payroll notes from March 21, 2026. So, the change is mandatory due to 26A activation.

Before and After USOPTE

Before 26A, Oracle Cloud Payroll used Vertex, a third-party tax engine, for US local tax jurisdiction detection and tax rate management. After 26A, Oracle’s own US Payroll Tax Engine (USOPTE) replaces Vertex entirely.

Tax rates and rules are now managed inside Oracle Cloud Payroll. You receive monthly tax updates directly from Oracle. This removes your dependency on Vertex release schedules.

The change also introduces auto-detection of local tax jurisdictions. Before, you might’ve relied on manual mapping or Vertex updates. Now it detects jurisdictions based on verified street-level employee addresses.

Technical Requirements You Must Verify

Street-level address verification is now standard. You’ve got the option to enable Address Auto-Complete (Type-Ahead) during data entry. That cuts errors when employees or admins enter work addresses.

The Enhanced Oracle HCM Master Geography database provides a more robust geographic foundation. You’ll want to review all state, county, and city mappings before activation.

A new Tax Calculation Statement gives you built-in transparency. Before, audit traces may have required external Vertex reports. Now it’s native to Oracle Payroll.

Here’s the comparison table I created from the official release documentation.

Change Area	Before 26A (Vertex)	After 26A (USOPTE)	Your Action
Tax jurisdiction detection	Manual or Vertex-driven	Auto-detection inside Oracle Payroll	Verify master geography mappings
Address verification	Basic or manual	Street-level verification with type-ahead option	Clean employee addresses; test verification
Tax rate management	Third-party Vertex releases	Monthly Oracle-managed updates	Remove Vertex update calendars
Tax calculation transparency	Limited or external reports	Native Tax Calculation Statement	Train staff on new statement format
Integration dependency	Vertex API connections required	Fully native; no third-party dependency	Update integration documentation

Mandatory US Payroll Checklist Before Go-Live

You may use this checklist to prepare your US payroll team. I’ve designed it based on the technical changes verified in official documentation.

1. Review Master Geography. Confirm that all employee work locations are mapped correctly to state, county, and city levels in the enhanced database.
2. Clean Address Data. Run street-level verification on a sample of 100 or more records. Fix discrepancies before full activation.
3. Enable Auto-Complete. Configure type-ahead settings for new hires and address change forms.
4. Validate Jurisdiction Auto-Detection. For multi-state employers, test that remote employees are mapped to correct local jurisdictions based on verified addresses.
5. Confirm Tax Rule Migration. Verify that existing Vertex rules map correctly to Oracle’s internal rules. Run test calculations for all active jurisdictions.
6. Generate Tax Calculation Statements. Produce statements for test payroll runs. Confirm transparency meets your audit requirements.
7. Remove Vertex Dependencies. Update any custom integrations, reports, or third-party feeds that reference Vertex endpoints.
8. Train Payroll Staff. Schedule sessions on jurisdiction mapping reports, address verification workflows, and the new Tax Calculation Statement.
9. Plan Activation Timing. Schedule 26A activation outside of active payroll processing windows. Maintain a rollback plan in case mapping corrections are needed.
10. Document Changes. Update your internal payroll procedure guides to reference USOPTE instead of Vertex.

Image placement suggestion. SEO alt text: “Printable checklist for US payroll administrators preparing for Oracle Cloud HCM 26A USOPTE mandatory transition.”

UK Legislative Updates in 26A

I’ve checked the UK legislative notes from K8Mead published December 6, 2025, and the Arclight payroll updates from March 21, 2026. Several UK requirements became mandatory with 26A.

P60 Template Updates for 2025/26

The P60 template now includes a Statutory Neonatal Payment field in the Statutory Payments section. There’s a corresponding balance in the UK Balances for the End-of-Year Archive group. The updated template types are LE(P) and eP60 for both online and plain paper formats.

You’ll want to update your P60 generation processes before year-end. You might also want to verify that the Neonatal Payment balance is included in archive groups.

FPS Address Reporting Options

You can now choose whether employee addresses appear in the Full Payment Submission (FPS) for all employees or only new starters. This applies to tax years ending April 2025 and April 2026. The default setting is All Employees.

To change this, you may use the new field called Employee Address on FPS from Tax Year 2024-25 on the organization-level Statutory Deductions calculation card. Confirm your organization’s reporting preference before submitting FPS files.

Also read: What Is Centricity ShiftSelect?

New Absence Attributes for Family Leave

New payroll attributes help you set up absence types for adoption, maternity, and paternity. These include entitlement formulas, benefit payments, and offset calculations.

You may create or update absence plans using delivered templates. I’d recommend testing absence calculations for affected employees before relying on the new formulas in production.

Legislative Area	Before 26A	After 26A	Your Action
P60 Template	No Neonatal Payment field	Statutory Neonatal Payment added; updated archive balance	Update templates; test year-end archive
P60 Template Types	Previous year versions	Updated LE(P) and eP60 for 2025/26	Confirm correct template selection
FPS Address Reporting	Fixed rules	Configurable: All Employees or New Starters Only	Set calculation card preference
Family Leave Absence Setup	Manual or basic tracking	New entitlement formula attributes for adoption, maternity, paternity	Update absence plans; test calculations

Employment Process Controls and Security

This section covers updates that improve data integrity. Most articles skip these details. I’ve included them because they directly affect how you manage high-volume employment changes.

Read-Only Payroll Fields for Employment Processes

In 26A, you may mark payroll fields as read-only for specific employment processes. The affected processes include Add Assignment, Change Assignment, Promote, and Transfer.

You can configure this through Visual Builder Studio. Select Configure Fields and Regions under Business Rules for each process. This prevents accidental changes to critical payroll data during routine HR transactions.

You’ve got the option to apply different read-only rules to each process. For example, you may allow salary updates during a promotion but block them during a standard assignment change.

Conditional Page Properties Based on Security Access

You may now define which page properties apply conditionally based on the logged-in user’s security access. This works for all employment processes. You can use the Configure Page Properties feature with list of values for Guided Journey codes and Info to Include properties.

This means different user roles see different configurations automatically. HR admins see full options. Managers see simplified views.

Employees see only relevant fields. You can document these configurations for your user training program.

Implementation and Migration Strategy

Anyway, I’d recommend a phased approach rather than activating everything at once. That cuts the risk, and it gives you time to fix Redwood configurations or payroll mappings.

Phase One: Sandbox Testing (Four to Six Weeks Before Production)

Apply the 26A update to your non-production environment. Test Redwood page configurations for all customized areas. Validate the new AI agents with sample data from your organization. Run payroll test cycles for both US and UK scenarios.

You’ll want to verify USOPTE jurisdiction mapping and UK P60 output during this phase. If you find errors, you have time to clean master data before production activation.

Phase Two: User Acceptance Testing (Two to Three Weeks Before Production)

Invite HR admins, payroll staff, managers, and employees for role-based testing. Confirm that read-only field controls work correctly. Verify that conditional page properties display correctly for each user role. Test the HCM Data Loader agent with high-volume import scenarios.

Test the Workforce Compensation Approval worksheet with actual managers. Confirm that the Redwood interface functions smoothly for approval actions.

Phase Three: Production Activation and Monitoring

Schedule activation outside of active payroll processing windows. Monitor jurisdiction detection accuracy for the first US payroll run.

Monitor UK FPS submissions for address reporting accuracy. Collect user feedback on Redwood navigation. Adjust Visual Builder Studio configurations based on real user behavior.

Data Migration Priorities

Before activation, you’ll want to clean US employee addresses to match the enhanced Master Geography database. Review UK absence records for adoption, maternity, and paternity. Confirm compensation history is complete because Redwood pages now display prior history directly.

Review all role mappings. Redwood role pages may expose outdated configurations. Update your documentation before users access the new interfaces.

Competitive Context: How 26A Compares

To get more details, I’ve compared Oracle’s 26A strategy against Workday and SAP SuccessFactors using verified market data from 6sense and Softabase.

Oracle holds approximately 6.99 percent of the HCM market according to 6sense 2026 data. Workday leads with 23.15 percent. SAP SuccessFactors holds 10.76 percent.

However, Oracle has been named a Gartner Magic Quadrant Leader for Cloud HCM Suites for 10 consecutive years. It has held the furthest Completeness of Vision position for eight consecutive years.

Oracle includes over 600 embedded AI agents at zero additional licensing cost. Workday and SAP generally charge extra for AI capabilities. Oracle’s deployment speed is faster than SAP’s due to built-in best practices.

26A reveals Oracle’s strategic focus. The Jobs Assistant and Workforce Structures Insight Analyst are strategic planning agents embedded directly in the HR platform.

You might not see equivalent strategic agents in Workday or SAP without additional licensing or custom development.

Here’s a brief comparison for strategic decision-making.

Dimension	Oracle 26A	Workday	SAP SuccessFactors
AI agent licensing	600 plus agents included at no extra cost	Typically requires additional fees or consumption pricing	Typically requires additional modules or fees
Redwood UI standardization	Completed for core HR, compensation, and data pages in 26A	Strong native user experience design	Mixed; customization often required
US payroll tax engine	Native USOPTE with monthly updates; Vertex replaced in 26A	Uses third-party or partner integrations	Uses partner or native solutions depending on region
Global payroll depth	116 plus countries per Oracle analyst events	Strong multi-country support	50 country native coverage, often considered deepest
Implementation speed	Faster than SAP; best-practice configurations built in	Comparable for core modules	Slower due to heavy customization requirements
Strategic planning agents	Jobs Assistant, Workforce Structures Insight Analyst (26A)	Not available as native embedded agents	Not available as native embedded agents

Frequently Asked Questions

Final Thoughts and Verdict

I have reviewed official Oracle documentation, analyst release notes, and technical payroll guides for this article. 26A is not routine.

You may view it as three strategic shifts combined into one update. Redwood standardization completes major interface migrations. Agentic AI introduces strategic planning tools, not just operational chatbots. Mandatory compliance removes third-party dependencies for US and UK payroll.

Organizations that treat it as an optional patch risk compliance failures and miss strategic capabilities. Organizations that test Redwood configurations, validate payroll mappings, and train users by role will gain efficiency and accuracy.

If you manage a global workforce with 500 or more employees, you should start sandbox testing now. You can use the checklists and tables in this guide to organize your team. The agents included at no extra cost provide capabilities that competitors charge for separately.