Oracle ships an EPM Cloud update every month. Each one gets a review here: what changed, why it matters, and what to do, sorted by how urgent it is, with the deadline calendar and a checklist your admin can work through.
The Integration Agent gets stronger credential encryption, Balance Loads replace Data Loads in Account Reconciliation, every application gets the Redwood home page, two FCC assistants arrive for AI Agent Studio, and Generative AI gets a floor: 26.08 by the end of January 2027.
Read the review →The EPM Automate password file switch that is now live, the predefined dashboards upgraded to 2.0 on their own, the six month limit on one off patches, three new AI assistants for the close, and the deadline calendar through 26.12.
Read the review →The Financial Analysis Hub for consolidation teams, the enhanced PCM agent, Task Manager for FreeForm, the Strategic Modeling redesign, and the EPM Automate password file deadline that belongs in every admin calendar.
Read the review →Three releases in one page: the Reporting Agent and the AI assistant fleet, the stricter Groovy engine, removed IP allowlists, the OAuth 2 action, and the full deadline calendar.
Read the review →Essbase 21c, the agentic AI REST APIs, the Groovy Script Validator, Smart View changes, and the security updates, in two videos with an action checklist.
Read the review →Oracle's release notes list every feature with the same weight. These reviews do not. Each item lands in one of three buckets, and every item carries the same three lines: what changed, why it matters, what to do.
Action required. The change can break something, or already did: a rule engine change, a removed command, a security setting, a hard deadline. An administrator should do something before the next cycle.
Review for your environment. New capability that is useful if you run the module, from AI assistants in reports to a new backup command. Try it in test, then decide.
No action. Screens that moved to a new design, renamed menus, retired features you probably were not using. Read once so nothing surprises you or your users.
Every review closes with the deadline calendar, a checklist that saves your progress in the browser, and links to the Oracle documents the review was written from. Nothing is added that Oracle did not publish.
Oracle publishes the What's New document for the coming release on its Cloud Readiness site, ahead of the test update.
Test environments are updated on the first Friday of the month. This is the window to try what applies to you.
Production environments follow on the third Friday. Updates apply automatically; a skip is possible for up to three updates, and six months off the main line is the ceiling from 26.09.
The review lands here and on YouTube after the production update, with the deadline calendar updated for the months ahead.
Reading every release against client environments is part of my Oracle EPM managed services work. If an update broke something in your environment, support and rescue is a separate page.
One review a month. The 30 second brief for the CFO, what changes on the screens for the FP&A team, the checklist with due dates for the admin. Pick the inbox you already read.
Same review as an edition. LinkedIn emails it to you and shows it in your feed. Best if LinkedIn is where you read.
Subscribe on LinkedInNeeds a LinkedIn account. Comments and questions happen there.Subscribe once. New dates arrive on their own each month, with a reminder two weeks before and a link to the card.
Outlook and Google open with the address filled in. Any other calendar: copy the address and paste it under Subscribe from web. No email involved./feed subscribe fmepm.com/feed.xml. Teams: a Workflow that posts new feed items to a channel. Two minute setup.oracle-epm-updates.json. The same file the pages are built from, updated with each review. Ask your assistant "what do we need to do before 26.12".The video is on YouTube the same morning.