Oracle Narrative Reporting Consulting and Support
Oracle Narrative Reporting consulting for report packages, doclets, collaborative authoring, data integration, support and Financial Reporting transition.
Start with the reporting burden you actually carry.
Oracle Narrative Reporting consulting helps finance teams control the production of board, management and statutory reporting packs. Namandla designs report packages, doclet ownership, review cycles, data integration and publication around the way contributors and approvers work.
The objective is to create a reporting process with clear responsibilities, consistent data and an audit trail from source numbers to the approved narrative.
Financial reporting automation with control
Financial reporting automation should reduce manual assembly without weakening review. Narrative Reporting can combine structured EPM data with commentary, tables and presentation content while preserving ownership and approval stages. Namandla identifies which elements can be automated, which need professional judgement and how changes should be governed across the reporting cycle.
Where restatements actually come from
The month-end board pack is usually assembled in Word and PowerPoint from numbers copied out of the consolidation system. Several people contribute sections. Someone merges them. Then the numbers change, and every figure has to be found and updated by hand under deadline.
That process is where restatements are born. Not in the consolidation, which is controlled and auditable, but in the manual assembly afterwards, which is neither.
Connected expertise for the wider environment.
Assess
Establish the architecture, symptoms, evidence and business impact.
Resolve
Select the safest corrective action and validate the outcome.
Strengthen
Document the change, reduce recurrence and transfer knowledge.
Report packages, doclets and reference doclets
Oracle Narrative Reporting, formerly EPRCS, addresses this by holding the report as a structured package rather than a document.
- Report packages define the structure, the contributors, the reviewers and the deadlines
- Doclets are the individual sections, each owned by a named author, worked on in parallel
- Reference doclets hold the numbers, sourced live from the EPM application, so a change flows everywhere it appears
- Workflow manages author, review and sign-off with a recorded audit trail
- Management Reporting produces the formatted output
The gain is not speed of authoring. It is that the numbers in the narrative are the numbers in the system, provably, at the moment of publication.
Narrative Reporting work we take on
Assessment. Establish whether Narrative Reporting is proportionate to the reporting burden, contributor model, review cycle and control requirements.
Package design. Structure, doclet breakdown, contributor and reviewer model, deadlines and workflow.
Data integration. Reference doclets sourced from FCCS, Planning, Essbase or on-premises applications, so figures refresh rather than being retyped.
Migration. From Financial Reporting, Disclosure Management or a manual Word and Excel process.
Ongoing support. Cycle support, package change and reporting period rollover.
When Narrative Reporting fits the reporting process
Narrative Reporting earns its place when several people contribute to a recurring package, when the review cycle is structured and when the figures in the narrative need to be traceable to the system. Where those conditions do not apply, a lighter process or targeted data-refresh improvement may be more proportionate.
Two people and a short pack. If your board pack is assembled by two people who sit near each other and the review is a conversation rather than a workflow, the overhead of package structure, doclet ownership and approval routing exceeds the benefit. Fix the data refresh instead.
One author, one document. Where a single person owns the whole narrative, the collaboration model that makes Narrative Reporting valuable has nothing to work on.
The problem is actually the close. If the pack is late because the consolidation is late, a reporting tool moves the bottleneck rather than removing it. That is a consolidation conversation, not a Narrative Reporting one.
Where it does earn its place, the return is not authoring speed. It is that a restatement caused by somebody pasting last month’s figure into this month’s commentary stops being possible.
The AI position, and whether it applies to you
Narrative Reporting is one of the Cloud EPM business processes for which Oracle publishes generative AI capability. Two prerequisites gate it, and both are hard.
Release. From July 2026, Oracle publishes that generative AI functionality is available only for environments running Cloud EPM 26.04 or later. Oracle names Narrative Reporting explicitly alongside Account Reconciliation, Enterprise Data Management, Enterprise Profitability and Cost Management, Financial Consolidation and Close, FreeForm, Planning, Profitability and Cost Management and Tax Reporting. Environments not upgraded by the end of July 2026 lose access.
Realm. Oracle publishes that generative AI is available in all regions in the following realms only: OC1, OC4, OC19, OC29 and OC42. Oracle lists South Africa Central (Johannesburg) in OC1, so for a Johannesburg tenancy the region is not the obstacle : the release level might be.
A word of caution specific to this product. Narrative commentary is exactly the kind of writing generative AI produces fluently and confidently, which makes review discipline more important here than anywhere else in the EPM stack, not less. The value is in drafting from figures that are already governed. The risk is in publishing text nobody checked against them.
Questions answered
How does Namandla engage on Narrative Reporting?
Assessment first, and it is a short piece of work. We establish how the pack is assembled today, who contributes, where the figures come from and where the time actually goes : and whether Narrative Reporting is proportionate to that burden. Where the pack is short and the contributors few, the honest answer is often that it is not, and you will hear that from us before any scoping.
Where it is proportionate, the work is package design, doclet and contributor model, data integration so figures refresh rather than being retyped, migration from Financial Reporting or a manual Word and Excel process, and ongoing cycle support. Delivered remotely by default, subject to agreed access, security, scope and support hours.
What is a doclet?
A doclet is an individual section of a report package : a commentary, a set of tables, an appendix : owned by a named author and checked in and out under version control. The package defines the structure, the contributors, the reviewers and the deadlines; the doclets are the parts people actually write.
A reference doclet is the important variant. It holds the figures, sourced from the reporting application, so a number appearing in three places in the pack comes from one place and refreshes everywhere at once.
Can Narrative Reporting replace Oracle Financial Reporting?
It can replace parts of a Financial Reporting and document-production process, but the fit depends on the reports, data sources, formatting requirements and review workflow. Namandla assesses the existing outputs before recommending a transition.
Oracle Financial Reporting may remain appropriate for formatted statements and grids. Narrative Reporting adds package structure, collaborative authoring, narrative workflow and an audit trail around the reporting process.
Can Narrative Reporting connect to on-premises Hyperion?
Yes, and this is the question we are asked most often by groups not planning to migrate. Data can be brought into a report package from on-premises applications as well as from Cloud EPM, so a group running Financial Management or Essbase on-premises can still hold the pack as a governed package rather than a Word document.
The design question is how figures are refreshed and how often, and it is worth answering before the package structure is built rather than after.
Do we actually need it?
Often no, and we would rather establish that in a short assessment than during an implementation. It earns its place when several people contribute to a recurring package, the review cycle is real, and the numbers in the narrative need to be provably the numbers in the system.
It does not earn its place when the pack is short and assembled by two people, when a single author owns the whole narrative, or when the pack is late because the close is late. That last one is a consolidation problem and a reporting tool will move it rather than fix it.
Can we migrate from Financial Reporting or Disclosure Management?
Yes, and both are common starting points. The migration is a redesign rather than a conversion: the structure of a report package is different from a book or a Disclosure Management setup, and rebuilding the pack is an opportunity to remove sections nobody reads.
Expect the contributor and review model to take longer to agree than the technical build. It is a process decision about how your group actually reviews, not a configuration step.
Does Narrative Reporting have AI capability?
Yes. Oracle publishes generative AI across Cloud EPM business processes and names Narrative Reporting explicitly among them. From July 2026 the functionality requires Cloud EPM 26.04 or later, and Oracle publishes availability in the OC1, OC4, OC19, OC29 and OC42 realms only. Oracle lists South Africa Central (Johannesburg) in OC1.
We would add one caution for this product specifically. Narrative commentary is exactly what generative AI writes fluently and confidently, so the review discipline matters more here than elsewhere. Drafting from governed figures is valuable; publishing text nobody reconciled against them is not.
How long does an implementation take?
Less than most EPM projects, because the scope is a reporting package rather than an application. What moves the number is the number of doclets, how many source systems the reference doclets draw from, and how quickly the contributor and review model can be agreed.
The part most often underestimated is the first live cycle. Running the pack for real, with the actual contributors under the actual deadline, is where the design gets tested and it should be planned for rather than treated as go-live.
Where do we start?
With an assessment of how the pack is produced today: who contributes, how many figures are retyped, where the review actually happens and how long the assembly takes after the close is done.
That produces a proportionate answer, and sometimes the answer is that a better data refresh and a tighter process solves the problem without new software. We will tell you when that is the case.