Will your Cloud EPM Financial Reporting reports still work in 2027?

Who should check?

Organizations using legacy Financial Reporting in Oracle Cloud EPM Enterprise Profitability and Cost Management, Financial Consolidation and Close, FreeForm, Planning, Profitability and Cost Management or Tax Reporting. Organizations already using only the newer Cloud EPM Reports experience, and ordinary NetSuite ERP SuiteAnalytics or financial statements, are not automatically affected.

Published milestones

1. November 2026 readiness guidance — documented requirementOracle identifies affected Cloud EPM products, the new Reports destination and the 27.02 functionality milestone. This is existing vendor guidance first added to Ebenstead on November 7, not a new Oracle November 7 announcement.
2. Before the account's 27.02 update — inventory and verified migrationUse an authorized Service Administrator to convert selected reports and validate finance figures, layout, prompts, schedules and recipients. Confirm the actual upgrade window; the old reports remain in the legacy repository during in-place conversion.
3. February 2027 (27.02) — planned end of legacy functionalityOracle states unmigrated Financial Reporting reports stop working when 27.02 is applied to the affected Cloud EPM environment; there is no separately established universal day of February.

Check your Oracle account notice before scheduling an update.

A practical response

• Ask the Cloud EPM reporting owner to identify any legacy Financial Reporting reports used for close, consolidation, budgets or taxes and confirm the 27.02 update notice for the relevant environment.
• With permitted Service Administrator access, migrate an agreed sample into modern Reports. Reconcile filters, point of view, calculations, financial totals and the output against the approved legacy baseline.
• Assess reports that do not convert cleanly, and separately rebuild books, bursting, scheduled runs or Excel integrations when required. Check snapshot migration against the actual account because Oracle documents conflicting compatibility guidance.
• Obtain finance UAT for the target report and document migration/rollback or recovery decisions before broader rollout; do not delete the legacy repository until the customer authorizes the appropriate retention approach.

What we’ll review

With the finance/reporting owner, inventory legacy Financial Reporting report names, folders, execution frequency, report books, bursting definitions, scheduled distributions, downstream Excel workbooks, dependencies and owners. Confirm the actual environment update schedule, Service Administrator access and a representative close-period sample for comparing the replacement Reports outputs.

Follow this topic via RSS