Account Reconciliation, mapped
ARCS certifies that the numbers in the ledger are real. This module documents the objects, the reports finance actually needs out of it, the compliant export routes, and the owned model that keeps reconciliation history queryable after the period locks.
Note: Oracle EPM is the cloud suite finance teams run planning, consolidation, and close on. Account Reconciliation, ARCS, is the module that proves the balance sheet: every account in scope gets a reconciliation each period, a preparer works it, a reviewer approves it, and the evidence is kept for audit.
ARCS is the one EPM module built on documented relational tables rather than cubes, which changes what is possible; that story starts on Tables & views. The consolidation this module certifies lives one door over, on the FCCS pages, and the two share one sample world: a sixty-entity group, one June close. The same reconciliation discipline on the ERP side lives on our Fusion payables-to-ledger pages.
◆ Dictionary, the objects: profiles and formats, periods, and the tables underneath.
| Page | What it answers |
|---|---|
| Profiles & formats | The four objects that run the module, the three format methods, the four resting statuses, and which fields freeze at each status. |
| Periods | Pending, Open, Closed, Locked, what opening a period actually runs, and the three levers including the 25.08 Pipeline. |
| Tables & views | The relational exception: the FCM_, ARM_, and TM_ table families Oracle documents column by column, custom SQL report queries, and the derived-column trap. |
◆ Reports, the four answers close managers and auditors ask for by name.
| Page | What it answers |
|---|---|
| Reconciliation status | Who holds what, on time against late, and where the on-time number actually lives. |
| Unmatched aging | The unmatched-over-90-days report auditors call a key control, which the application will not produce out of the box. |
| Auto-match rate | Match rate by rule and match type, and the rule-naming habit that makes the number diagnosable. |
| Compliance dashboard | On time, late, rejected, and risk violations by user, and how to get the same numbers outside the dashboard. |
◆ Exports, the compliant routes out, verified against the current REST and EPM Automate surface.
| Page | What it answers |
|---|---|
| Status export | The custom query, the Generate Report REST call, submit, poll, collect, and a nightly CSV of every reconciliation and its status. |
| Transaction matching export | Match Type views, the dynamic tables, and pulling matched, suggested, and unmatched with their audit trail. |
◆ Guidance, the sharpest operational edge in the module.
| Page | What it answers |
|---|---|
| Balance loads | Snapshot mode replaces, a changed balance reopens finished reconciliations, and the two documented incidents, rounding and zero-amount lines, that reopened hundreds at once. |
◆ The owned model, the star beside the application, and the cross-catalog tie.
| Page | What it answers |
|---|---|
| The ARCS data model | The owned star beside the application: reconciliations, statuses over time, balances, matches, and the tie to the FCCS close pages. |
The problem: The reconciliation evidence lives only inside the application, and history dies at the period lock.
What we build: Nightly status and matching exports land in a warehouse you own on GCP, AWS, or Azure, gated before anyone reads them.
What you get: Close-week status and the full audit history, answerable by query, forever.
- ARCS
- Account Reconciliation Cloud Service, the reconciliation module of Oracle EPM Cloud.
- Reconciliation Compliance
- The certification workflow: prepare, review, close, per account per period.
- Transaction Matching
- The high-volume engine that pairs transactions across sources by rule.
- the owned model
- The star schema on your cloud that keeps every period queryable forever.