Multi-Currency Transaction Matching is Finally Off My Wishlist!
Nadia Lodroman | Oracle EPM Consultant | Integrity in Every Insight.
Listen to Tresora and Ledgeron's chatting about this blog post:
Oracle EPM 26.06 Update
If you caught my thoughts on the Oracle EPM 26.05 release last month, you already know how thrilled I was to see the Tax Rate by Multi-GAAP feature land in Oracle Tax Reporting. It was a massive step forward for global tax provisioning, and it genuinely felt like Oracle was reading my mind. Well, it seems the product management team is still actively working through my personal wishlist, because the upcoming June 2026 (26.06) update brings an absolute game-changer to Oracle Account Reconciliation (ARCS): Support for Multiple Currencies in Transaction Matching.
For anyone who has had to manage complex, multinational transaction matching processes, this feature is the breakthrough we’ve been waiting for. It fundamentally changes how we design and execute global reconciliations, saving finance teams an incredible amount of time and effort.
The Reality of the Old Workaround
Historically, handling different currencies within a single Transaction Matching process required some pretty creative - and frankly, tedious - workarounds. Because a data source couldn't inherently distinguish between currencies on its own, administrators typically had to split source files by currency code before loading them. From there, you had to build out separate match types for each distinct currency or maintain entirely parallel reconciliations just to keep the data clean.
This meant high operational overhead, an increased risk of manual file-handling errors, and a fragmented view during the intense pressure of the period-end close. We weren't just matching transactions; we were managing a complex web of data preparation just to get the system to talk to itself correctly.
How 26.06 Changes the Narrative
Starting with the 26.06 release, Oracle elegantly dissolves this friction. Service Administrators can now enable multiple currencies directly within a single data source by configuring Currency as a standard text attribute.
When you load data, the system associates a specific currency code - whether it’s USD, EUR, INR, or JPY - with each individual transaction. From there, the intelligent matching rules take over. When ARCS runs its matching algorithms, it automatically evaluates both the
currency code and the
amount simultaneously. A match will only succeed if both elements align perfectly, and the system is smart enough to respect the specific precision of each individual currency throughout the process.
The Operational Ripple Effect
The practical benefits of this update ripple across the entire closing cycle. First and foremost, you can completely retire the scripts and manual processes previously used to shard your source files by currency code. You can now feed a single, unified file into the system.
Architecturally, this means instead of building and maintaining dozens of redundant match types for every global entity, you can manage one streamlined structure. This flows into a single period-end reconciliation for multiple currencies in the lowest configured currency bucket. Best of all, you don't lose an ounce of visibility. The currency code is preserved and fully visible exactly where you need to see it—on the Transaction tab, within drill-through links, in transaction exports, and throughout your balance reports.
A Few Other Honorable Mentions
While multi-currency matching is the undisputed star of the show for me, the June 2026 release packs a few other excellent enhancements for Account Reconciliation that are well worth keeping on your radar.
Oracle is continuing to expand its
embedded AI Assistants within ARCS to further streamline user workflows and decision-making during the reconciliation process. For the automation enthusiasts, new
EPM Automate Commands like
runProfileRules and
runReconciliationRules provide much greater programmatic flexibility for scheduling and driving the close from external orchestrators. We are also getting the ability to select unmatched transactions from
both sides to create a single Support ID, giving teams much better flexibility when resolving complex variances, alongside simple but highly requested quality-of-life updates like direct currency code sorting within the Reconciliation List view.
Final Thoughts
Between the 26.05 Multi-GAAP Tax Reporting updates and now the 26.06 Multi-Currency Transaction Matching in ARCS, Oracle is proving that they are laser-focused on solving real-world, complex global finance challenges. This release effectively wipes out hours of manual file preparation and complex workaround maintenance for EPM administrators.
Ready to Transform Your Close Process?
New features are only as good as their implementation. If you are tired of managing tedious currency workarounds, manual file splitting, or disjointed tax provisioning, let’s turn these software updates into tangible time savings for your team.
At www.lodroman.com, we specialize in tailoring Oracle EPM ecosystems to fit the precise rhythm of your business. Whether you want to configure the new 26.06 multi-currency matching rules or optimize your 26.05 Multi-GAAP reporting architecture, we are here to help. Let's get these features working for you.
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?
All things Oracle EPM
