Streamlining Transaction Matching in Oracle ARCS: A Deep Dive into Adjustments and Reconciliation Balancing

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

4 April 2025

Listen to Tresora and Ledgeron's chatting about this blog post:

Navigating the Adjustment Paradox in Oracle ARCS Transaction Matching

Oracle Account Reconciliation Cloud Service (ARCS) is a powerful tool for streamlining reconciliation processes. Its Transaction Matching feature is particularly useful for comparing large volumes of data, identifying discrepancies, and ensuring accuracy. However, like any sophisticated system, it presents unique challenges that require careful navigation. One such challenge revolves around the use of adjustments and their impact on reconciliation balance.

The Purpose of Adjustments
In ARCS Transaction Matching, adjustments serve a crucial role: they allow users to reclassify items that shouldn't be part of the core reconciliation. This is particularly useful for items that need to be moved to a different account or require further investigation outside the standard matching process.

The Balancing Act: When Adjustments Throw Things Off
The problem arises when these adjustments are confirmed. While they correctly reclassify the items, they often cause the reconciliation to become out of balance. This is because ARCS treats these adjustments as real transactions, affecting the overall balance.

The Subsequent Correction: A Double Adjustment
To rectify this imbalance, users typically need to import an adjustment journal in the next transaction import cycle. This journal reclassifies the initial adjustment, effectively offsetting its impact on the reconciliation balance. However, this correction adjustment is often purely for ARCS purposes and doesn't require posting in the Enterprise Resource Planning (ERP) system.

Why This Happens and How to Manage It
Understanding why this occurs is essential for effective management:
ARCS Accounting Treatment: ARCS processes adjustments as actual accounting entries within the reconciliation, impacting the balance.
ERP vs. ARCS: The ERP may not require these adjustments, leading to a disconnect between the two systems.

Best Practices and Recommendations
Here are some best practices to manage this situation:
  • Clear Documentation: Maintain detailed documentation of all adjustments, including the reason for the adjustment and whether it requires an offsetting entry in the next cycle.
  • Naming Conventions: Implement clear naming conventions for adjustment journals to distinguish between ERP-required and ARCS-specific adjustments. For Example, using a prefix such as "ARCS_ADJ" for adjustments that only exist for ARCS.
  • Regular Reconciliation Reviews: Conduct regular reviews of reconciliation balances and adjustment activity to identify and correct any imbalances promptly.
  • Process Standardisation: Establish a standardised process for handling adjustments, ensuring consistency across all reconciliations.
  • Leverage Comments and Explanations: Use the comments and explanation fields within ARCS to provide context for each adjustment, making it easier to track and understand.
  • Consider Custom Attributes: Explore using custom attributes in ARCS to flag adjustments that don't need ERP posting, streamlining the identification process.
  • Training: Ensure all users are thoroughly trained on the adjustment process and understand the implications of confirming adjustments.
  • Automation: If possible and if your organization uses EPM automate, create scripts that can automatically create and import these offsetting adjustment journals.

The Importance of Communication
Effective communication between the reconciliation team and the ERP team is vital. Ensuring that both teams understand the nature of these ARCS-specific adjustments can prevent confusion and streamline the reconciliation process.

Conclusion
While the adjustment paradox in Oracle ARCS Transaction Matching can be challenging, understanding the root cause and implementing best practices can help users maintain accurate and balanced reconciliations. By prioritising clear documentation, standardised processes, and effective communication, organisations can leverage the full potential of ARCS while minimising the impact of these unique adjustment scenarios.

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

The Evolution of Data Orchestration

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.

Leveraging CbCR as the Foundation for GloBE Compliance

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

Bypassing the Default Goodwill Reclass with Custom Consolidation Rules in Oracle FCCS

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