The FCCS close process is the structured sequence of technical operations within Oracle Financial Consolidation and Close Cloud Service that transforms individual entity financial submissions into the group’s consolidated financial statements for a reporting period. The process is not a single operation — it is a multi-step sequence where each step must complete correctly before the next can produce valid results. Running the consolidation before all entity data has been loaded, or translating currency before the exchange rate table has been updated, produces consolidated outputs that are numerically wrong but appear technically complete. Understanding the dependency sequence of the FCCS close process — and building this sequence into the close calendar governance — is the operational knowledge that distinguishes a reliable, audit-ready group close from one that generates discrepancies discovered after distribution to the board.
FCCS Close Process Sequence
| Step | Operation | Dependency / Prerequisite | Failure If Skipped |
|---|---|---|---|
| 1 | Exchange rate table update | Closing, average, and historical rates for all currency pairs and current period entered or loaded | Currency translation uses prior period rates; translated balances incorrect |
| 2 | Entity data collection | ERP period closed; Data Management data load run for all entities; entity submissions reviewed and approved | Consolidation runs on incomplete or prior-period actuals |
| 3 | Entity-level calculation | Data collection complete | Derived accounts (ratios, subtotals) not calculated; consolidation includes incorrect entity input values |
| 4 | Currency translation | Exchange rate table complete; entity data complete; entity calculation complete | Consolidated reporting currency values incorrect; translation difference not computed |
| 5 | Consolidation journals | Translation complete; journal approvals obtained | IFRS reclassifications absent from consolidated output |
| 6 | Consolidation run | All prior steps complete for all entities in scope | Intercompany eliminations apply to incomplete data; NCI calculated incorrectly |
| 7 | Post-consolidation review | Consolidation complete | Errors not detected before distribution |
| 8 | Period lock | Reviewed and approved consolidated output | Post-lock: prevents further data modifications — must not lock before sign-off |
FCCS Close and Task Manager Integration
Oracle FCCS integrates with Oracle Task Manager — the close task orchestration application within the EPM Cloud suite. When FCCS is deployed alongside Task Manager, each step in the FCCS close sequence can be represented as a Task Manager task — with a defined owner, a due date, a dependency on the prior task’s completion, and a status visible to the entire close team in real time. System tasks (the consolidation run itself, the data load completion) can be monitored by Task Manager and automatically advance to the next task when the system task completes successfully. For GCC enterprise close teams coordinating across Saudi Arabia, UAE, and Egypt, this integration replaces the email-based close status updates with a live, governed close calendar visible to all participants simultaneously.
What Goes Wrong in Practice
The most consequential FCCS close process failure — resulting in a consolidated output that must be rerun after partial distribution — is a consolidation that executes before all entity data submissions are complete. When the consolidation is run to meet a tight close deadline while two entities are still in the process of uploading their adjusted submissions, the consolidation output reflects the two entities’ prior-period or incomplete data. If the consolidated P&L is distributed to the board before the complete consolidation is run, a corrected version must be issued — a process that creates board-level credibility damage independent of the magnitude of the data difference.
How Loop Wise Solutions Designs the FCCS Close Process
We design the FCCS close process as a formal sequence document — not a set of instructions, but a dependency-mapped process specification that defines each step, its prerequisite conditions, its responsible owner, its completion evidence, and the governance that prevents the next step from starting before the prerequisite is met. This document is the basis for the Task Manager close calendar configuration and the basis for the annual close process review that identifies where bottlenecks occurred and where the sequence can be optimised.
Answers before you ask.
A structured series of operations — data collection from entities, currency translation, consolidation (including eliminations and minority interest), journal posting, and locking the period. Each step feeds the next, ending in the consolidated group financial statements. Understanding this order is essential because a step run out of sequence produces an incorrect or incomplete result.
Because later steps rely on earlier ones completing correctly. Consolidation cannot be trusted before translation and data collection are done; posting adjustments before consolidating, or locking before adjustments are final, misstates the output. Managing these dependencies is central to running the close calendar so the consolidated result is numerically correct and audit-ready.
It prevents further changes to data once the close is complete, fixing the consolidated result so it cannot be altered after sign-off. Locking protects the integrity of the reported numbers and the audit trail. Locking too early blocks needed adjustments; locking too late risks post-close changes — so its timing is a controlled step in the process.
The close calendar schedules and tracks the tasks; the FCCS close process is the sequence of system operations those tasks drive. The calendar assigns owners and deadlines to steps like collection, translation, and consolidation, while the process defines their technical order and dependencies. Together they turn the close into a governed, repeatable cycle.