A Welcome Integration: How EPM's 25.11 Update Streamlines Match Type Changes

Nadia Lodroman | Oracle EPM Consultant | Integrity in Every Insight.

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.

Turning financial complexity into operational clarity. Because in Finance, Integrity is Permanent.

General EPM Strategy FAQs

  • Why should a company use EPM Automate instead of custom scripting

    EPM Automate allows for robust, bi-directional data orchestration between Oracle EPM and source ERPs (like NetSuite or Fusion) using native capabilities. It is highly scalable, easier to maintain during Oracle's monthly updates, and avoids the fragility of heavy custom coding.

  • Can Oracle Cloud EPM integrate with multiple different ERPs simultaneously?

    Yes. Through strategic data pipeline architecture, Oracle EPM can ingest, consolidate, and even write-back finalized data to multiple disparate ERPs concurrently, acting as the single source of truth for the enterprise.

  • How does Oracle FCCS handle Minority Interest (NCI) and CTA?

    While standard FCCS provides out-of-the-box functionality, complex global enterprises often require advanced configuration to isolate and calculate Minority Interest (NCI) and Cumulative Translation Adjustments (CTA) accurately at the top consolidated hierarchy without relying on manual journals.

  • Can you bypass the out-of-the-box Goodwill calculation in Oracle FCCS?

    Yes. By utilizing advanced native configuration and custom consolidation rules, you can bypass standard Goodwill Input/Offset functionality to meet highly specific, non-standard acquisition accounting requirements.

  • How many daily transactions can Oracle ARCS process?

    Oracle ARCS is built for enterprise scale. With proper architecture in the Transaction Matching engine, ARCS can easily process and auto-match hundreds of thousands of daily banking transactions, representing billions of dollars in value.

  • What is the difference between Transaction Matching and Reconciliation Compliance in ARCS?

    Transaction Matching automates the high-volume, line-by-line matching of data (like daily bank feeds or ACH). Reconciliation Compliance is used to govern the period-end justification of broader balance sheet account balances.

  • Does Oracle TRC handle Country-by-Country Reporting (CbCR)?

    Yes. Oracle Tax Reporting Cloud (TRC) provides built-in frameworks to automate Country-by-Country Reporting, ensuring multinational organizations remain compliant with global BEPS (Base Erosion and Profit Shifting) regulations.

  • How does Oracle TRC integrate with FCCS?

    TRC and FCCS share the same platform architecture, allowing for seamless data flow. Finalized pre-tax consolidated data from FCCS feeds directly into TRC for tax provisioning, ensuring perfect alignment between the finance and tax departments.

Still have a question?

Contact me

All things Oracle EPM

A screenshot of the Oracle EPM Data Integration interface highlighting the use of Split expressions
by Nadia Lodroman 7 March 2026
Discover how to overcome faulty source designs in ARCS Transaction Matching using Source and Target Expressions in the new Data Integration interface. Improve performance and reduce administrative tasks.
Pillar Two Strategy, using CbCR for GloBE compliance. Shield, globe, and gears on a block.
by Nadia Lodroman 5 March 2026
Is your CbCR data robust enough to trigger the Pillar Two Safe Harbour? We analyse why CbCR is the only foundation for GloBE compliance, saving you hundreds of data hours.
Architecture diagram showing how an Oracle FCCS custom consolidation rule
by Nadia Lodroman 3 March 2026
Learn how to use Configurable Consolidation Rules in Oracle FCCS to bypass the default Goodwill offset and route intercompany investments to Paid-in Capital.
Show More