Event take · Oracle

Oracle 26D readiness: what I would do with it

By John Rae · Oracle · Released September 4, 2026 · Posted November 7, 2026

Modules: quarterly update · payables · procurement · ai agents

Four times a year Oracle updates Fusion Cloud for every customer, and it publishes guides ahead of time describing what is changing. The 26D guides are out, and they are still moving: the Financials guide was first posted on September 4 and revised as recently as November 2. Most of the attention in this round goes to AI agents. For the people running Finance and Procurement, though, the useful question is smaller: which changes arrive without anyone asking, and which ones wait until someone decides to turn them on.

What was announced

Payables Agent. Software that reads incoming invoices, checks them against your policies and flags exceptions for a person. You have to opt in.
Payables Period Close Workspace. One screen showing what is holding up the Payables close for a ledger and period, with actions shaped by a written procedure you supply. Oracle rates its effect on existing processes as larger scale.
Supplier Portal. New pages for suppliers to enter invoices and check payments. They replace the classic pages once enabled, and setup is required.
Form 1099 electronic filing. Support for filing through the IRS Information Returns Intake System.
Purchase agreement date changes. When agreements are imported from external purchase prices, a start or end date change on a contract line now updates the existing agreement line. Before, the old line was closed and a new one created.
Sourcing and spend. A tool that simulates award scenarios against your sourcing policy, and a Procurement Spend Command Center that shows purchases made outside your agreements. Both run on Fusion Claw, Oracle's name for agents that plan and carry out a defined goal.
AI budgets. Administrators can set budgets for AI units, the measure Oracle uses for agent consumption, watch usage by user and stop new runs when a budget runs out.

What it changes for you

Finance. The close workspace depends on the procedure you give it, so a vague procedure produces vague guidance. If your Payables close lives in one person's head, write it down first.

Procurement. If you use that import, the date change is the one to test. Any report or interface that treats a new agreement line as the sign of a date change will stop seeing that sign. The Spend Command Center is worth a look only if you trust how your purchases map to agreements.

The ERP owner. You now own a budget for AI consumption as well as a list of features. Multifactor sign-in also deserves a read: Oracle says new environment families require it, while people signing in through corporate single sign-on are not prompted, and the identity upgrade for existing environments is scheduled separately from any quarterly update. Find out which case you are in.

What I would do

Download the feature summary tables for Financials, Procurement and Common Technologies, and sort every row into forced, adopt or defer. The two columns that matter are impact and action to enable.
If you import agreements from external prices, build a regression test around date changes before the update reaches your test environment.
Decide who owns the AI unit budget and set a warning threshold before anyone turns on an agent.
Pick one agent to pilot, not five. Payables is a reasonable start because the outcome is easy to measure: invoices that needed a person, before and after.

What to ignore

Ignore the language about Payables becoming a value-generating engine. That is Oracle's description of a goal, and nothing in the guide measures it for you. Do not plan around "near-touchless" either until your own invoices have been through it. Also remember that a feature in the guide is not a feature in your environment: many of the agent items here are marked opt in or setup required, and some need access or licensing checks that the summary table will not settle. Ask Oracle through a service request if the guide leaves that unclear. Finally, the guides keep changing, so check the revision history before you rely on what you read in September.

One complete ERP

Agents that read invoices, supplier terms and policy on the same platform are one more reason to keep those functions on one ERP, because an agent can only reason over the data it is able to reach.

Sources

The event: Oracle Fusion Cloud 26D quarterly update readiness material, first posted September 4, 2026: https://docs.oracle.com/en/cloud/saas/readiness/news.html

Next reads

The full release read in Decoded

← Four ERPs, one update calendar · All Field Notes and Decoded