Oracle’s third quarterly release of 2026 — Oracle Fusion Cloud 26C — is landing in production today for Cohort B customers. The update represents the most expansive AI-enabled quarterly release Oracle has shipped to date, arriving with 811 total features, 139 AI capabilities, and 473 Redwood UI redesigns that are fundamentally reshaping how enterprise finance, supply chain, and HR teams interact with the platform. For the roughly half of Oracle Fusion customers in Cohort B, today marks the moment the months of preparation either pay off or expose gaps.
What Is Oracle Fusion 26C?
Oracle Fusion Cloud operates on a mandatory quarterly update model. Customers are assigned to cohorts — A, B, or C — with each cohort receiving the same update on a staggered schedule. For 26C, Cohort A production environments updated on August 21. Cohort B, representing a large segment of Oracle’s enterprise customer base, is receiving its production update today, September 18. Cohort C production follows on October 16.
Unlike traditional enterprise software upgrades that organizations could defer for months or years, Oracle’s SaaS delivery model means updates cannot be skipped. Customers can influence when they receive updates through cohort selection and can control whether certain opt-in features are enabled, but the underlying quarterly release arrives on Oracle’s schedule.
This architecture keeps customers current with security patches, compliance changes, and platform evolution. It also means that a quarter like 26C — with 811 features spanning financials, supply chain, HCM, customer experience, EPM, projects, risk, and platform — demands a structured approach to readiness rather than a last-minute testing sprint.
137 Changes in Finance Alone
For Oracle Cloud Financials teams, 26C is the heaviest action-load quarterly release in recent memory. Analysis from Opkey identified 137 changes across 12 Financials modules in this release, covering Payables, Receivables, Project Financial Management, Tax, Fixed Assets, Cash Management, Risk Management, and cross-functional workflows.
The raw number understates the operational challenge. Of those 137 changes, 109 require active intervention from customer teams — meaning finance, tax, IT, and controls groups must review, test, configure, or validate before the update is safe to trust in production. Only 28 changes are auto-enabled in the background, though auto-enabled changes carry their own risk: they alter environment state without a deliberate opt-in decision, which is exactly the kind of silent change that creates audit complications.
Three of the auto-enabled changes are compliance-critical. Oracle 26C includes mandatory updates for Poland’s JPK audit file reporting structure, Polish VAT declaration alignment, and Brazil’s electronic fiscal document workflow. For multinational finance teams operating in those jurisdictions, these are not optional enhancements — they are regulatory requirements that must be configured and validated before production or the organization risks non-compliance in fiscal reporting.
AI Agents Move from Preview to Core
The most strategically significant changes in 26C are on the AI side. Oracle continues to accelerate its Fusion Agentic Applications roadmap, with 26C adding 109 agent features and 18 agentic apps on top of the wave introduced in 26B. The coverage now extends across Finance, Supply Chain, HCM, and customer-facing workflows.
Specific AI agent capabilities in the Finance domain include enhanced versions of the Payables Agent and Ledger Agent introduced in 26B, along with new agent touchpoints in Fixed Assets, Project Financial Management, and cross-functional approval workflows. These agents can recommend actions, route work, automate approvals, and surface anomalies — all without explicit user initiation.
A notable infrastructure change in 26C is the retirement of the standalone AI Configurator. Oracle is replacing it with AI Agent Studio, a unified environment for managing prompts and agents together. Critically, existing prompt configurations do not migrate automatically — they must be manually copied into AI Agent Studio and revalidated. Any organization that has been using Oracle’s AI configuration tools without documentation of their prompt setup is discovering that gap during today’s production update window.
The governance implications of AI agents in finance are being felt across the enterprise software industry. ERP vendors are embedding AI-driven automation into workflows that have traditionally required human authorization. For CFOs, controllers, and audit teams, the question is not only whether the AI agent works correctly in testing, but whether the organization has defined appropriate guardrails, approval chains, and monitoring before users begin relying on agent-recommended actions in live financial processes.
Redwood UI: The Clock Is Running
Of the 811 features in 26C, 473 carry Oracle’s Redwood flag — nearly 60% of the release. The Redwood migration is Oracle’s long-term modernization of its entire Fusion user interface, moving from the legacy Oracle ADF framework to a contemporary UI architecture that the company argues will simplify user experience and enable more consistent AI integration across modules.
In 26C, the Redwood transition becomes mandatory for Oracle Supply Chain Management. Oracle has signaled that SCM’s full Redwood adoption will be required by 26D, the next quarterly release arriving in Q4 2026. Organizations that have been treating Redwood adoption as optional should take note: the opt-in window on SCM is closing.
For configuration management, Redwood conversions are not cosmetic changes. The UI redesign alters the underlying page structure, which means functional configurations, customizations built on Oracle Page Composer, and any workflow automations tied to legacy page behavior may behave differently or fail to carry forward in the new interface. Finance and IT teams need to validate the functional configuration of converting modules against the new UI rather than assuming that a successful pre-Redwood configuration will simply continue to work.
What Oracle 26C Means for ERP Governance
Oracle’s quarterly update model has matured from a delivery mechanism into a governance framework. Each quarterly release now contains compliance changes, AI capability expansions, UI overhauls, and integration updates — all arriving simultaneously on a non-negotiable schedule. Managing this cadence requires organizations to treat quarterly release readiness as an ongoing operational discipline rather than a periodic project.
The immediate practical implications for organizations receiving 26C today are several. Finance and controls teams that have not yet reviewed the 109 action-required changes in the Financials module are entering production with an incomplete validation record. Organizations with Poland or Brazil operations that have not configured the mandatory compliance features are at regulatory risk. Teams that have not copied AI prompt configurations into AI Agent Studio will find their previous customizations inactive.
For ERP program owners, CIOs, and CFOs watching today’s Cohort B update, the broader lesson from Oracle Fusion 26C is that the quarterly release cycle is increasingly a compliance deadline, an AI governance checkpoint, and a technical integration test — all at once.
Looking Ahead to 26D
Cohort B customers who successfully navigate today’s 26C production update have roughly six weeks before Cohort A customers receive their 26D test environments in early November. Oracle has signaled that 26D will include further AI capability expansion, the completion of mandatory Redwood migrations across additional modules, and the expiration of opt-in windows for several SCM and HCM features that have been deferred from previous quarters.
The pattern is clear: Oracle is using its quarterly release cadence to steadily reduce the space between what customers can defer and what they must adopt. For enterprise teams managing Oracle Fusion Cloud, the organizations that will navigate this environment successfully are the ones building the infrastructure — configuration baselines, regression testing pipelines, structured release operations — to handle four major updates per year without treating each one as a crisis.
Today’s 26C production landing for Cohort B is both an arrival and a starting gun.
Sources: Oracle Fusion Cloud Financials 26C What’s New, ERP Today — Oracle Cloud ERP 26C Puts Finance Release Readiness Under Pressure, Flexagon — Oracle Fusion 26C Quarterly Update
