A Welcome Integration: How EPM's 25.11 Update Streamlines Match Type Changes
Nadia Lodroman • 2 November 2025
Listen to Tresora and Ledgeron's chatting about this blog post:
Learn how the November 25.11 release for Account Reconciliation removes manual data sync work and saves EPM admins valuable time.
For EPM Service Administrators, here's a scenario that might feel all too familiar.
You're in Account Reconciliation, performing routine maintenance on a Match Type. Perhaps you need to update the ID of a data source, change a source attribute, or rename a journal column. It's a simple, necessary change.
Your work should
be done, right?
Not quite.
Until now, that simple tweak often triggered a cascade of manual rework. You had to go back, identify every single Data Integration
application
using that match type, and manually update each one.
It was a significant time-sink and a source of understandable frustration. More importantly, it was a prime opportunity for human error to cause integration failures, creating real headaches during the close process.
Well, we have some great news: Oracle's EPM 25.11 update is designed to take that entire task off your plate.
What's New? True, Seamless Integration!
Included in the November 25.11 update for Account Reconciliation is this key feature: "Updates to Match Types Reflected in the Associated Data Integration Applications."
It may not have a flashy name, but its impact is significant. Here’s the simple, powerful improvement this update delivers:
When you update any of the following properties in a Match Type...
- ID of a match type
- ID of a data source (a key field, which we know is often used for creating Transaction Matching reports)
- ID of a data source attribute
- Name of a journal column
...Oracle EPM now automatically reflects those changes in all associated Data Integration applications.
That's right—no more manual intervention is required. No more manual updates, no more cross-checking, and no more worrying if you missed one. The sync just works.
Why This Is More Than Just a 'Nice-to-Have' Feature
Oracle's release notes call this a "seamless integration," and it's an accurate description. This is a massive quality-of-life improvement for admins that translates directly into business value.
- For Service Admins: You get your time back. Every minute not spent on tedious, manual data-syncing is a minute that can be reinvested in high-value tasks like optimizing rules, building better reports, or training your users.
- For Data Governance: This update makes your data connections more robust. By automating the sync, you eliminate the risk of human error. Your data integrations will always be aligned with your reconciliation definitions, which means more reliable data.
- For the Business: It's all about agility. This update removes a key point of friction in your EPM ecosystem. It makes the entire platform more resilient, easier to maintain, and faster to adapt—which is exactly what you need for a faster, more accurate close.
One More Suggestion for the Wishlist
And while we're on the subject, this update is a perfect opportunity to share related feedback. Since we know that Data Source ID is so critical for Transaction Matching reports, a future update to Account Reconciliation (ARCS)
that helps automatically sync those report definitions
when an ID changes would be the next logical step in this streamlined integration. Just a thought for the Oracle team!
Also Noteworthy in 25.11 for Account Reconciliation
This Match Type update isn't the only change for ARCS this month. The 25.11 release also includes several other logic enhancements worth reviewing:
- Evaluation of User Roles: A change in how user roles are evaluated when determining the validity of profiles.
- Auto Submit Reconciliation Rules: A change in the eligibility criteria for auto-submit rules.
- Evaluation of Invalid Mappings: A change in how invalid mappings are evaluated.
These all point to Oracle tightening up the logic to ensure more accurate and robust reconciliations.
Our Take: A Welcome and Practical Improvement
This is the kind of update we're always happy to see. It's not a giant new module, but it's a smart, practical fix that solves a real-world problem. It shows Oracle is listening to users and smoothing out the rough edges of the platform.
So, as you're planning your 25.11 update, this is definitely one to look forward to. It's a significant win for automation and a big step forward for a smoother, more efficient EPM experience.
Get Expert Insight on Your EPM Strategy
This update is just one small part of the ever-evolving EPM landscape. If you have questions about how the 25.11 updates will impact your environment, or if you want to strategize on how to get the most value from your Oracle EPM Cloud, we're here to help.
Contact Nadia Lodroman
at nadia@lodroman.com
to start the conversation.



