Irvine Analytics Get in touch
Analytics Catalog/Oracle EPM/Account Reconciliation/Balance Loads
Explore the catalogAccount ReconciliationPeriodsReconciliation statusStatus export
Oracle EPM Cloud · Account Reconciliation · Guidance

Balance loads, the sharpest edge in the module

Every load replaces, and every changed balance sends finished work back to the preparer. That is documented design, and twice in the field it has reopened hundreds of reconciliations nobody meant to touch. This page is the mechanism, the two incidents, and the operating rules.

Note: ARCS, Oracle's account reconciliation module, works by comparing balances loaded in from your ledger and other systems. Loading those balances is routine, and it is also the easiest way to accidentally undo finished work. This page is how to load so that never surprises you.

One question this page answers: why did last month's signed-off reconciliations reopen overnight, and how do I load so that never surprises me? The whole module is mapped on the Account Reconciliation index.

RuleLoad on the close calendar, control decimals and zero rows in the file, expect the reopen when a balance truly changed, and lock periods that are done.
Neverload a file you have not filtered. Zero-amount rows and stray decimals both read as changes, and the system reopens on inequality, not materiality.
◆ The mechanism, drawn, staging, load, and the post-processing step that reopens, doc-verified.

Three doc-verified rules run every load. Mode is Snapshot: per the import doc, a balance for the same reconciliation and period replaces the old one, and incremental loading is not what the system does. Post-processing per the execution doc changes Open with Reviewer or Closed to Open with Preparer if a balance changed, and flags normal-balance violations. And CSV or Smart View imports skip validation on required fields, so a bad file loads before it fails.

INSIDE ORACLE EPM · EVERY BALANCE LOAD the fileCSV · pre-mapped stagingwiped every load loadsummed by profile · bucket post-processing, every loadreopens if a balance changedflags normal-balance violationsruns rules Closed / Open with Reviewer → Open with Preparer left to right · Snapshot mode: same reconciliation, same period, the new balance replaces the old the red step is documented behavior, not a defect · ARCS: Account Reconciliation Cloud Service
◆ Two documented incidents, and the calendar rule, the rounding reopen, the 0.00 reopen, and when loads must stop.
The incidentThe lesson
The rounding reopenClosed reconciliations reopened with no balance change anywhere. Cause, confirmed by Oracle: a patch began rounding to two decimals, so stored and loaded values differed by fractions. Lesson: reopen triggers on inequality, not materiality; control your decimals in the file.
The 0.00 reopenAn adjustment file with zero-amount lines reopened 600 plus reconciliations whose balances did not move. Lesson: filter zero rows before the load, expected 15 reopens, or you will explain the other 585.

The calendar rule follows from the period statuses: Closed periods still accept loads, only Locked stops them, so schedule loads against the close calendar and lock, prior periods first, when a month is truly done.

THE USE CASE, SIMPLIFIED

The problem: A routine load reopened six hundred reconciliations nobody meant to touch.

What we build: Decimal and zero-row gates run in front of every load, scheduled against the close calendar.

What you get: The only reopens left are the real ones.

Loads reopening work nobody meant to touch?
We put the filter and the decimals gate in front of your loads, schedule them against the close calendar, and the only reopens left are the real ones.
Talk to us
Terms on this page
Snapshot mode
Same reconciliation, same period: the new balance replaces the old.
the reopen
Changed balance sends Closed or in-review back to the preparer. Design.
zero-row trap
0.00 lines read as changes. Filter before loading.
Locked
The only period status that stops loads.