In Oracle EPM, a journal adjustment is a manual entry applied within the EPM application — typically FCCS or PBCS — to modify the financial data after it has been loaded from source systems. Unlike a posting in the ERP, a journal in Oracle EPM affects only the EPM data and not the underlying statutory books. EPM journals are used for period-end accruals that need to be reflected in the consolidated view but are not in the ERP, IFRS reclassifications applied at the group level, management reporting adjustments that present performance differently from statutory results, and consolidation corrections for intercompany differences that are resolved at the group level rather than requiring each entity to repost in their own system.
When EPM Journals Are Appropriate — and When They Are Not
EPM journals are appropriate when the adjustment is a group-level reporting decision rather than a statutory accounting requirement. If the group finance team decides to reclassify certain selling costs from operating expenses to cost of sales for management reporting purposes, but the statutory accounts in each entity retain the original classification, an EPM journal applies this reclassification only in the group consolidation. The entity statutory accounts are unaffected; the group management accounts reflect the preferred presentation.
EPM journals are not appropriate as a permanent workaround for incorrect data coming from the ERP. When a journal is used each period to correct a systematic error in the ERP data load — for example, to reclassify transactions that are consistently mapped to the wrong EPM account because the mapping table has not been updated — the journal masks a data quality problem that should be fixed at the source. Over time, the accumulation of journals applied each period to correct systemic issues produces an EPM environment that cannot be audited without a detailed understanding of every standing journal and its justification.
Governance Controls That Prevent Journal Abuse
A well-governed EPM journal process has four elements. An approval workflow: every journal requires review and approval by a designated authoriser before it is posted to the consolidation. A documented justification: each journal has a reference to the underlying business reason, the supporting calculation, and the IFRS basis (if applicable) for the adjustment. A classification: journals are categorised as standing (repeated each period), recurring (expected to recur but not automatic), or one-time (not expected to repeat). And a periodic review: standing journals are reviewed at least annually to confirm they are still appropriate and that the underlying data quality issue they address has not been resolved at the source.
Where Journal Governance Fails
The most common journal governance failure in enterprise EPM environments is the accumulation of standing journals that no one fully understands because they were created by team members who have since left the organisation. Each period, the journals are posted because they have always been posted, but the justification is no longer current and the business reason for the original adjustment may no longer exist. A journal audit — systematically reviewing every standing journal to confirm its continued appropriateness — is a necessary but frequently neglected element of EPM environment maintenance.
How Loop Wise Solutions Approaches This
We include journal governance design in every EPM consolidation implementation — building the approval workflow, the journal categorisation framework, and the periodic review process before the application goes live. We also conduct journal audits as part of EPM health check engagements, frequently finding journals that have been posted for years without review and that are either no longer justified or that mask data quality issues that should have been resolved at the source.
Answers before you ask.
Some entries belong at the group level, not in the statutory books — consolidation adjustments, IFRS reclassifications, and period-end accruals made for reporting. Posting them in EPM corrects the reported figures without disturbing the underlying ERP data, preserving each entity's local records while producing the correct consolidated view. Mixing the two would corrupt the statutory ledgers.
Group-level accruals, intercompany and consolidation adjustments, reclassifications between local GAAP and IFRS, and manual corrections that arise during consolidation. These are adjustments to the reported result rather than operational transactions, which is why they sit in the consolidation environment rather than in the transactional system.
Through review and approval workflow and a full audit trail, so each adjustment has a reason, a preparer, and an approver, and can be traced later. This governance matters because manual adjustments are exactly where errors and, in the worst case, manipulation can enter reported numbers. Controls turn a necessary flexibility into a safe one.
Often, yes. A high volume of recurring manual adjustments usually points to a data or process gap — mappings that should be automated, or source data that arrives wrong. While some group-level judgement always requires journals, leaders should watch the trend: rising manual entries erode auditability and suggest the underlying integration or model needs attention.
An ERP journal posts to the statutory books and affects the entity's legal records; an EPM journal adjusts the consolidated reporting layer without touching those books. One records what the entity actually did; the other reflects group-level presentation and accounting choices. Understanding the distinction keeps statutory and group reporting properly separated.