Narrative Reporting support questions, answered clearly.

Oracle Narrative Reporting Support is the ongoing service that keeps your report packages, Reports and disclosure documents producing on schedule: report package setup for each cycle, doclet template maintenance, data source and refresh repairs after outline changes, author, reviewer and signer administration, Reports design and maintenance, Disclosure Management taxonomy and iXBRL support where you file electronically, monthly update testing and standby cover while a board pack or annual report is being produced. It is distinct from Oracle’s cloud service support. Namandla provides it as a managed service with a named senior consultant.

Because Narrative Reporting sits at the end of the chain, where the board pack, the integrated report and the annual financial statements come together from many contributors under a fixed deadline. A doclet that will not refresh because an account was renamed in FCCS, a reviewer who cannot see their sections, a Reports grid pointing at last year’s members, or an iXBRL tagging error the day before filing, all become the finance director’s problem. Support exists so templates are maintained between cycles, data sources are tested before authors start, and someone can act while the package is in flight.

A typical Namandla Narrative Reporting support scope covers report package creation and rollover each cycle; doclet and reference doclet template maintenance in Word, PowerPoint and Excel; data source connections to FCCS, Planning Cloud, Essbase and other sources; refresh and variable repairs after metadata changes; author, reviewer and signer setup and phase administration; Reports design, maintenance and bursting; Disclosure Management taxonomy updates and tagging support for statutory filing; Smart View extension support for authors; monthly update regression testing; quarterly health checks; and priority standby during board reporting, interim and year-end cycles.

Usually, and the causes are in design rather than infrastructure. Common findings are doclets carrying far more embedded data points than they present, reference doclets refreshing whole grids for a single number, Reports built with unbounded member selections, report packages with every section assigned to every author, and review phases that duplicate work. A health check measures refresh times per doclet and Reports run times, identifies the drivers and fixes them in order of impact. A package that took an hour to refresh completing in minutes is a normal outcome.

A structured review across three layers. Content: report package structure, doclet templates, embedded content and variables, Reports definitions and data sources. Process: author, review and sign-off phases against the real production calendar, distribution and bursting, and the Disclosure Management taxonomy and tagging status where it is used. Platform: update status, Smart View extension versions on author desktops, permissions and audit. The output is a written findings report with prioritised fixes, each with effort and expected effect, and a package checklist for the next cycle.

Yes, and this is where the service earns its place. Namandla provides standby cover during board reporting, interim and year-end cycles, with a consultant available to resolve refresh failures, permission problems, doclet check-in and check-out issues, Reports errors and tagging questions while authors and reviewers are working. Before a cycle we roll the package forward, test every data source against the current FCCS and Planning outlines, refresh the reference doclets, confirm assignments and, for statutory filing, check the taxonomy version.

Yes. Typical improvements are reference doclets and variables that carry every recurring number so authors never retype figures, package templates rolled forward rather than rebuilt, Reports replacing legacy Financial Reporting output with bursting to entities, review phases matched to who actually reviews, and Disclosure Management mapped once so tagging is a check rather than a project. Every template change is tested against the prior cycle’s numbers. The aim is a package where authors write commentary and the numbers take care of themselves.

Yes. Support covers the data sources that feed report packages and Reports: FCCS, Planning Cloud, Account Reconciliation, Essbase on-premises or on OCI, Oracle Fusion and file-based sources, including the connections, the variables that pull numbers into narrative and the refresh behaviour after outline changes. It also covers the Smart View extension authors use, distribution of finished packages, and Reports embedded in other EPM Cloud services. When a source application changes its structure, support re-tests every doclet that depends on it before authors notice.

Narrative Reporting is updated by Oracle monthly, so the upgrade work is update testing. The migration work is typically moving formatted reporting from on-premises Financial Reporting to Reports, moving the board pack from a Word-and-email process into report packages, or moving statutory disclosure into Disclosure Management for electronic filing. Namandla handles the assessment of existing reports and packs, template design, data source setup, parallel production for one cycle and cutover timed away from year-end.

By keeping every number in the narrative connected to its source: variables and embedded content that refresh from FCCS or Planning rather than being typed, reference doclets tested after every metadata change, Reports grids pointing at current members, and sign-off phases that lock the package once approved. For statutory filing, Disclosure Management tagging validated against the current taxonomy before submission. The most common accuracy failure in narrative reporting is a typed number that was not updated, and a maintained package removes it.

Support that works from the reporting calendar rather than from incident tickets. In practice that means reading the monthly readiness notes and testing the update, rolling packages forward and testing data sources before authors are due to start, checking Smart View extension versions on author desktops, reviewing assignments as people change roles, and tracking taxonomy releases where you file electronically. It also means telling you when a risk exists, such as a doclet only one person can refresh or a reference doclet pointing at a retired member, before it becomes a board-pack incident.

Outsourcing makes sense when the report package is built and maintained by the finance team between their other duties, when the person who set it up has moved on, when statutory filing adds Disclosure Management to the workload, or when board reporting is quarterly and the skills go cold between cycles. It makes less sense if you have a reporting team that owns the templates and tests each update. Namandla’s managed support is designed to work alongside that team, taking the specialist and standby work while your team keeps ownership of the content.

Break-fix support responds after a doclet has failed to refresh or a reviewer is locked out, bills by the incident and learns your package during the call, usually days before the board meeting. Managed support knows your packages, templates, data sources and calendar, tests before updates rather than after, prepares each cycle in advance and carries responsibility for the package being ready. Break-fix suits a simple package with a capable owner. For an organisation whose board and statutory reporting run through Narrative Reporting, managed support is usually cheaper over a year, because the incidents that happen before a deadline are the expensive ones.

By measurable results on the subscription you already pay for: packages that roll forward in hours rather than days, authors who write commentary instead of chasing numbers, reviewers who see the right sections the first time, Reports replacing a legacy reporting tool you may still be paying for, and statutory filing tagged once and validated rather than outsourced each year. The return is highest where the service was bought for the annual report and sits unused the rest of the year; extending it to the monthly board pack is a support programme, not a project.

Namandla is a South African consultancy whose senior team has delivered EPM reporting for about two decades, from Financial Reporting to Reports and Narrative Reporting, and the consultant assigned to your packages is the one who answers before the board meeting. We understand the FCCS and Planning applications the numbers come from as well as the packages themselves, we run the monthly update discipline as a standing task, and where AI can help draft commentary from refreshed data we apply it with a person reviewing every word that reaches the board. Contact info@namandla.com or 087 188 3388.