Glossary Oracle EPM & Hyperion services

What Is Account Reconciliation (ARCS Architecture)?

Oracle Account Reconciliation Cloud Service (ARCS) is Oracle's dedicated application for managing the period-end balance sheet reconciliation process — automating the matching of GL balances to supporting sub-ledger data, bank statements, and other source documents, and tracking reconciliation completion status…

Oracle Account Reconciliation Cloud Service (ARCS) — now branded as Oracle Account Reconciliation within the Oracle EPM Cloud suite — is Oracle’s dedicated application for managing the balance sheet account reconciliation process: the period-end verification that every balance sheet account’s GL balance is supported by sub-ledger data, bank statements, asset registers, or other third-party evidence. ARCS automates the workflow through which reconciliation preparers complete and submit their account reconciliations, reviewers approve or return them, and finance leadership has real-time visibility into reconciliation completion status across all accounts and entities. ARCS does not replace the reconciliation work — the preparer must still verify that the GL balance matches the supporting evidence — but it replaces the spreadsheet, email, and SharePoint-based tracking processes that most finance teams use to manage reconciliation status and certification.

ARCS Architecture Components

Component Function
Profile Configuration for each reconcilable account — defines the account, the supporting source, the method (Transaction Matching or Balance Comparison), the preparer, and the reviewer
Reconciliation Instance of a profile for a specific period — the working document where the preparer enters the reconciliation and submits for review
Transaction Matching ARCS module that automatically matches individual transactions between two data sources (GL transactions vs bank statement, sub-ledger transactions vs GL)
Balance Comparison Simpler reconciliation method — compares the account balance from one source to another source at the summary level
Workflow Status-based review process — Open → In Progress → Pending Review → Approved; each status transition governed by role-based access
Dashboard Real-time view of reconciliation completion across all accounts, entities, and preparer assignments

ARCS and the Close Calendar

ARCS integrates with Oracle Task Manager — reconciliation completion milestones (all bank reconciliations approved, all intercompany reconciliations submitted) can be represented as Task Manager tasks with ARCS as the underlying data source for completion status. This integration connects the balance sheet reconciliation governance (managed in ARCS) with the broader close calendar (managed in Task Manager) into a single view of close progress — enabling the finance controller to see both that the “Bank Reconciliation” Task Manager task is pending and that three specific bank accounts in ARCS are still in “Pending Review” status without toggling between two applications.

Transaction Matching in ARCS

ARCS’s Transaction Matching module is the highest-value feature for GCC enterprises with large-volume reconciliation requirements — bank reconciliations with hundreds of daily transactions, intercompany reconciliations with thousands of entries across many entity pairs, or AR/AP sub-ledger-to-GL reconciliations. Transaction Matching uses configurable matching rules (exact amount match, amount plus date match, amount plus reference match) to automatically identify matched transactions between the two data sources and present only the unmatched items to the preparer for manual review. For a bank reconciliation with 500 transactions where 480 automatically match, the preparer reviews 20 exceptions rather than 500 items — reducing reconciliation time from hours to minutes for high-volume accounts.

What Goes Wrong in Practice

The most common ARCS implementation failure is building reconciliation profiles that do not reflect the actual reconciliation methodology — the profile’s “source balance” and “sub-system balance” don’t map to the correct GL accounts or sub-ledger data sources, producing reconciliations where the system-calculated variance does not match what the preparer’s manual calculation shows. ARCS profiles must be built from the existing reconciliation spreadsheet templates — not from a generic ARCS template — to ensure the system-calculated balance matches what the preparer expects to see.

How Loop Wise Solutions Implements ARCS

In ARCS implementations, we begin with a reconciliation inventory — cataloguing every account currently reconciled in the finance team, the data sources used, the matching methodology, and the current time to complete. This inventory becomes the ARCS profile specification and the baseline against which post-implementation time savings are measured.

← Back to glossary

Need help implementing Account Reconciliation (ARCS Architecture)?

Our team works with enterprise organizations across Egypt and the GCC. Tell us about your situation.