Finance and accounting teams have spent decades building board books, management reports, and regulatory filings inside Microsoft Word, PowerPoint, and Excel. Oracle built Narrative Reporting, a business process within Oracle Fusion Cloud EPM (Enterprise Performance Management), around that reality rather than against it. Instead of asking report authors to abandon the Office tools they already know, Narrative Reporting layers a governed, collaborative process on top of Word, PowerPoint, and Excel through Oracle Smart View for Office. This post looks at what Narrative Reporting is, how the Microsoft Office connection actually works, and what is current enough in 2026 to matter for anyone planning a rollout or an upgrade.
What Narrative Reporting Does
Narrative Reporting is Oracle's cloud solution for combining financial data with written commentary into a single, managed reporting process. Oracle originally brought this capability to market as Enterprise Performance Reporting Cloud Service, or EPRCS, a name that still turns up in documentation URLs and in the habits of longtime consultants, before folding it into the Narrative Reporting name inside Oracle Fusion Cloud EPM. Its purpose has stayed the same throughout: let finance teams pull information from Oracle and non Oracle sources, including spreadsheets, EPM applications, Oracle Cloud Financials, and other databases, and then wrap that data in the qualitative explanation that boards, regulators, and executives actually read. The building blocks are report packages, which group individual doclets into a finished deliverable, and Books, which can bundle Reports, other Books, and uploaded Word or PDF documents into a single publication. Because the process is meant to replace scattered email attachments and manually assembled decks, Narrative Reporting also supports secure distribution through report bursting and can produce regulatory output formats such as XBRL and SEC EDGAR HTML through its Disclosure Management capability, covered in more detail further down.
Rather than forcing every report into a brand new format, Narrative Reporting can import existing Word, PowerPoint, and PDF reports as a starting point, so teams are not rebuilding years of report design from scratch.
The Bridge to Word, PowerPoint, and Excel
The mechanism that connects Narrative Reporting to Microsoft Office is a specific add on called the Narrative Reporting extension, which installs inside Oracle Smart View for Office. Smart View itself is Oracle's long standing Office add in for EPM data, shared across every business process in Oracle Fusion Cloud EPM, including Planning, Financial Consolidation and Close, Tax Reporting, Account Reconciliation, and Profitability and Cost Management, with Narrative Reporting as just one of the connections it supports. That shared foundation is part of why an organization already running one of those other processes tends to find the Narrative Reporting extension a short extra step rather than a new platform to learn. To install the extension, a user opens the Smart View ribbon in Word, PowerPoint, or Excel, goes to Options, then Extensions, and selects "Check for Updates, New Installs, and Uninstalls." After choosing the relevant Narrative Reporting connection and selecting Get Updates, the extension appears in the list and can be installed with a single click, followed by closing and restarting Office to complete setup.
Once installed, the extension turns Word and PowerPoint into authoring surfaces for doclets, the individual sections that make up a report package, while Excel becomes the environment for building reusable reference content that other doclets can pull from. A report package can start from a single Word or PDF document with additional doclets layered in later, or it can be assembled from a whole set of Word, PowerPoint, Excel, and PDF files at once.
Doclets Are the Real Unit of Work
Doclets come in several forms, and the differences matter for anyone planning a report structure. Regular doclets are Word, PowerPoint, or PDF based content owned by a single author. Linked regular doclets point to Office documents that already live in the Narrative Reporting library. Excel based reference doclets hold reusable, embeddable content such as named ranges, charts, and grids that other doclet authors can pull from without recreating the underlying numbers. Supplemental doclets round things out by letting Word, PowerPoint, Excel, PDF, HTML, or plain text files travel alongside the main package, and Word based tables of contents keep long packages navigable.
There is also a distinction between reference doclets and reference files. A reference doclet is created by the report package owner and shared with authors who need to draw from it, and it can contain content from both Excel and Oracle Reports. A reference file, by contrast, is created individually by each author and can only pull from Excel, since Reports content requires the fuller reference doclet.
Keeping the Numbers Alive
The feature that separates this from simply pasting a screenshot into a Word document is refreshable, connected content. Authors copy data, whether a single number, a formatted grid, or a chart, from a connected EPM source such as Essbase, Planning, Financial Consolidation and Close, or Tax Reporting, and paste it into a doclet as an embedded object rather than static text. That embedded object keeps its connection back to the source, so a single doclet can legitimately combine, for example, a profit and loss statement pulled from Essbase with an income statement pulled from Planning, and both can be refreshed on demand instead of retyped every reporting cycle.
Narrative Reporting also lets authors define variables, so a figure only has to be correct once. A static variable holds a value, such as a date label or a headline number, that an author sets directly and can update centrally so every doclet using it reflects the change. A reference variable instead pulls its value live from a specific cell or paragraph elsewhere in the package, such as a number in an Excel sheet or a phrase in a Word doclet. A shared variable, available since the Narrative Reporting 25.03 update, lets designated power users define common values in the web interface that multiple report packages in the same reporting period can all draw from. Authors insert any of these into a heading, table, cell, or paragraph from inside Smart View, and when the underlying value changes, every inserted instance updates automatically, which is what keeps one stale figure from surviving a hundred pages of proofreading.
This convenience comes with practical limits worth planning around. Oracle recommends keeping embedded content to thirty or fewer items per reference doclet or reference file, and keeping file sizes under five megabytes, since going past those limits can slow processing and cause check in failures. There are also formatting quirks specific to each application. In Word, embedded content is table based and left justified, so it cannot be centered directly, and Oracle recommends placing it inside text boxes when flexible positioning is needed, particularly for floating chart objects. In PowerPoint, embedded content is inserted as an image rather than live, searchable text, though it keeps its aspect ratio when refreshed and carries the original variable or content name as alt text. In both applications, the embedded content itself cannot be edited from inside the doclet. Any correction has to happen back at the source, in the originating Excel file or Reports object, which is what keeps the numbers trustworthy across dozens of contributors.
Running the Actual Reporting Process
None of this would scale without a workflow layer, and that is where Narrative Reporting earns its place as a governed process rather than a shared drive full of Word files. Report package owners assign authoring, review, and approval responsibilities to specific people with defined due dates. Contributors check out a doclet, work on it either in the web interface or directly in Smart View inside Office, then upload and check it back in. Each review cycle runs on a single shared review instance, so while individual reviewers see only the sections assigned to them, their comments post to that same shared instance and stay visible to other reviewers, and the system keeps a full audit trail of who changed what and when. Once every section clears review, the package moves to electronic sign off, with the ability to reject and resend sections that are not ready, before the finished package is finalized in the web interface.
Because doclets can also be downloaded and worked on offline, contributors are not required to stay connected to Narrative Reporting the entire time they are writing. They can take a Word or PowerPoint doclet offline, write against it locally, and reconnect later to check it back in and pick up any refreshed data.
All of this, the report packages, the Reports and Books, and the supporting files, lives in the Library, Narrative Reporting's role based artifact repository. Access is granted folder by folder rather than all or nothing, so a contributor typically sees only the folders their role requires, while a service administrator retains the ability to reach every artifact when something needs sorting out.
What Is Actually Current in 2026
Three things are worth knowing if you are planning a rollout or an upgrade right now. First, Oracle Smart View for Office release 26.100, published June 3, 2026 and the most recent version as of this writing, supports Microsoft Office 2021, Office 2024, and Microsoft 365 on Windows 11, along with Microsoft 365 on Mac and in the browser. Support for Office 2016, Office 2019, and Windows 10 has been gone since release 25.200, because Microsoft itself ended support for those versions on October 14, 2025. Smart View 25.100 was the last release to support the older Office versions, so any organization still running Office 2016 or 2019 needs to plan an upgrade path before moving Smart View forward.
Second, Oracle has been layering generative AI into the reporting side of the platform, though it is worth being precise about where that AI actually lives. The generative AI capability inside Reports and Narrative Reporting works through a conditional text framework: it can automatically describe cells that trip a variance threshold, explain the top contributors behind an exception, run comparative analysis against a prior period, and summarize free text notes on request. This runs inside the report design and grid environment itself, using prompt template files, and it is currently limited to Enterprise level Narrative Reporting deployments, English language output, and the specific OCI regions where the required identity and generative AI services are available together. Oracle positions it explicitly as a decision support feature that a person should review before anything goes out the door, and it is a separate capability from the Word and PowerPoint doclet authoring described above rather than a replacement for it.
Third, if part of why you are evaluating Narrative Reporting is regulatory filing, it is worth knowing where that capability actually stands right now. Disclosure Management, the Word and Excel based tool for tagging XBRL submissions such as SEC 10-K and 10-Q filings, is no longer sold to new customers. Oracle's own documentation describes it as available only to existing subscribers for the remainder of their current term, and support for ESMA and ESEF inline XBRL submissions inside Disclosure Management has already been discontinued. Anyone evaluating Narrative Reporting today specifically for European inline XBRL filing should confirm the current state of that capability directly with Oracle or an implementation partner rather than assuming it is included.
Why This Combination Still Matters
The appeal of Narrative Reporting's Office integration is not that it replaces Word, PowerPoint, or Excel. It is that it wraps a controlled, auditable process around documents that finance teams were always going to write in those tools anyway. Numbers stay connected to their source instead of being retyped, review and approval happen on a tracked timeline instead of an email chain, and the final package still gets published as a familiar Word document, PowerPoint deck, or PDF. For finance organizations that live in Microsoft Office and are not about to leave it, that is the real value: governance and connected data layered on top of software people already know how to use.
For a broader walkthrough of the Narrative Reporting process itself, including report packages, the review workflow, and where it fits in the wider EPM platform, see our companion post on Narrative Reporting in Oracle Cloud EPM.