Manual flux narratives and broken GL links; Workiva?ERP data with AI?drafted, cited explanations and controller sign?off

Overview

A global technology company’s Finance team relied on manual flux narratives and scattered general ledger (GL) support to explain period-over-period movements. Account owners wrote explanations in documents and email, attached ad hoc evidence, and reviewers spent time reconciling narratives to the ledger instead of probing drivers. Intelligex integrated Workiva with the ERP, built an AI assistant that drafted flux explanations with linked evidence, and enforced controller approval and version control. Reviewers focused on material insights, narratives stayed consistent across entities, and audit packs contained traceable citations—while Workiva, the ERP, and existing close calendars remained unchanged.

Client Profile

• Industry: Global technology (hardware, software, and services)
• Company size (range): Multi-entity, multi-currency operations
• Stage: Mature ERP and consolidation; narratives assembled manually in documents and spreadsheets
• Department owner: Finance & Accounting (Controllership and Regional Accounting)
• Other stakeholders: FP&A, Tax, Internal Audit, External Audit, IT/Integrations, Data/Analytics, Shared Services

The Challenge

Flux analysis required every entity and function to explain material movements against prior periods or plan. Account owners opened spreadsheets, pulled trial balances, annotated drivers, and attached PDF extracts from subledgers. Evidence lived in shared folders with inconsistent naming, and the links frequently broke as files moved. Reviewers re-validated figures manually and asked for updated support, delaying sign-off and leaving little time to discuss trends and risks.

Inconsistencies compounded the problem. Materiality thresholds varied by team, variance bucketing differed across account classes, and explanations mixed drivers (volume, price, foreign exchange, one-time items) with journal mechanics. Different regions used different templates, so consolidation reviewers stitched together uneven stories. Internal and external auditors requested clear ties from narrative to ledger, but the trail spanned emails, screenshots, and worksheets. This created avoidable rework late in the close.

Why It Was Happening

Root causes were fragmented support and ungoverned narrative standards. The ERP and subledgers held the facts, but there was no single layer that pulled balances, detected material variances, drafted explanations, and linked support consistently. Analysts relied on manual exports and judgment to classify changes, so similar movements were explained differently across entities. Version control lived in file names rather than in a system, and approvals happened via email without a durable connection to the final narrative.

Ownership was diffuse. Regional accounting wrote explanations, Corporate reviewed, FP&A added context, and Audit assessed sufficiency after the fact. Without an integrated workspace and rules, the team invested energy in assembling and reconciling narratives instead of in analyzing the business.

The Solution

Intelligex delivered a connected flux workflow. Workiva became the narrative workspace; the ERP remained the system of record. A data service pulled trial balances and subledger summaries into a canonical schema, applied materiality and bucketing rules, and invoked an AI assistant to draft explanations. Each draft cited linked evidence—GL detail, journal IDs, subledger extracts, and policy references—and flowed into Workiva sections with pre-approved templates. Controllers reviewed and edited drafts in a maker-checker process with version control. Approvals, changes, and links were captured immutably for audit. The approach aligned with connected reporting practices supported by Workiva and standard ERP integration patterns (for example, Oracle Financials Cloud).

• Integrations: Workiva narratives and templates; ERP trial balance and subledger summaries; identity crosswalks for entities, accounts, and business units; optional data warehouse for historical trend context.
• Canonical flux schema: Standard fields for entity, period, account, movement type (volume/price/FX/one-time/policy), materiality band, linked journals, subledger references, and owner.
• Materiality and bucketing rules: Finance-owned thresholds by account class and region; bucketing logic to classify drivers; effective dating for rule changes.
• AI draft assistant: Drafted narrative text using detected drivers, prior narrative language, and contextual metrics; embedded citations and deep links to support; flagged low-confidence cases for human attention.
• Evidence binder: Automated attachment and linking of supporting documents (GL detail, journal summaries, subledger extracts) with consistent naming and page-anchored references.
• Review gates: Maker-checker workflow for narratives; controller approval and version control inside Workiva; required rationale for overrides or policy exceptions.
• Dashboards: Posture by entity and account class; open reviews, low-confidence flags, and items missing support; policy changes and their impact on narratives.
• Audit trail: Immutable logs of data pulls, draft generation, edits, approvals, and evidence versions; exportable audit packs with cited support.

Implementation

• Discovery: Mapped close calendar and narrative owners; cataloged ERP chart, consolidation views, and subledger sources; collected prior narratives and audit comments; documented materiality and bucketing practices by region and account class.
• Design: Defined the canonical flux schema and account mappings; authored materiality and bucketing rules with effective dating; designed Workiva templates and section structures; specified evidence linking patterns and naming standards; set review roles and approval tiers.
• Build: Implemented ERP data pulls and normalization; built the rules engine and AI drafting service; integrated narrative publishing to Workiva and evidence binder linking; configured review gates, version control, and approval routing; assembled dashboards and exportable audit packs.
• Testing/QA: Ran in shadow mode: generated draft narratives alongside the existing process; compared drafts to prior periods; tuned thresholds, bucketing, and AI phrasing; validated evidence links and Workiva permissions; piloted maker-checker with selected controllers.
• Rollout: Enabled the workflow for a subset of entities and account classes first; retained manual narratives as a controlled fallback; expanded coverage after stable cycles; made controller approval mandatory in Workiva for all flux sections once reviewers were trained.
• Training/hand-off: Delivered sessions for account owners, controllers, FP&A, and Internal Audit on reading drafts, editing, approving, and exporting packs; updated SOPs for narrative standards and evidence; transferred ownership of rules, templates, and dashboards to Controllership under change control.
• Human-in-the-loop review: Established a periodic review of rule updates, AI phrasing libraries, and exception trends; decisions recorded with rationale and effective dates.

Results

Flux narratives arrived with linked evidence and consistent structure. Account owners started from AI drafts that reflected materiality rules and prior language, then added business insight. Controllers reviewed side-by-side with cited support, so time shifted from reconciling numbers to probing the story behind movements. Consolidation reviews saw uniform narratives across entities, which made comparisons straightforward.

Audit readiness improved. Each flux line carried links to GL detail, journal summaries, and subledger extracts, with version history and approvals in Workiva. When auditors asked “why did this move?”, reviewers opened a single pack that tied the narrative to the ledger and the rule set in effect. The ERP and Workiva stayed in place; the addition was a governed layer that standardized how explanations were drafted, reviewed, and evidenced.

What Changed for the Team

• Before: Narratives were drafted manually from scratch. After: AI-generated drafts in Workiva embedded drivers and citations.
• Before: Evidence lived in folders and emails. After: An evidence binder linked GL and subledger support directly to narrative lines.
• Before: Materiality and bucketing varied by team. After: Finance-owned rules applied consistently with effective dating.
• Before: Approvals happened via email. After: Controller sign-off and version control occurred inside Workiva.
• Before: Reviews focused on reconciling numbers. After: Reviews focused on business drivers and risks.
• Before: Audit packs were assembled ad hoc. After: Exports contained narratives, links, and approvals in one package.

Key Takeaways

• Codify materiality and bucketing first; consistent rules make narratives comparable.
• Treat narratives as data; a canonical schema and evidence links reduce rework.
• Use AI to draft, not decide; humans refine insights while the assistant handles structure and citations.
• Keep approvals in the system of work; controller sign-off and version control prevent drift.
• Integrate, don’t replace; bind Workiva and your ERP with a governed pipeline and templates.

FAQ

What tools did this integrate with? Workiva served as the narrative and approval workspace (Workiva). The pipeline pulled trial balances and subledger summaries from the ERP (for example, Oracle Financials Cloud) and published drafts and links back into Workiva. Optional data warehouse sources provided historical context; the close calendar and consolidation tooling remained unchanged.

How did you handle quality control and governance? Materiality thresholds, bucketing logic, and templates lived under Controllership change control with effective dating. Maker-checker approvals were required in Workiva for all flux sections. Every data pull, draft, edit, and approval was logged with version history and links to GL and subledger evidence. Policy alignment supported internal control expectations consistent with established guidance for financial reporting and controls.

How did you roll this out without disruption? The assistant ran in shadow mode first, generating drafts while teams continued their manual process. Drafts and links were compared to prior narratives, and rules and phrasing were tuned. Rollout began with selected entities and account classes, with manual narratives as a fallback. Controller approvals inside Workiva became mandatory only after several stable cycles and training.

How did the AI generate and validate explanations? The assistant used the canonical flux schema, materiality and bucketing rules, and historical narrative language to draft explanations. It embedded links to GL detail, journal IDs, and subledger extracts and flagged low-confidence cases for human review. Controllers edited and approved text inside Workiva, and version control preserved the final narrative alongside the draft.

How were evidence links maintained and secured? Evidence came from controlled ERP exports and subledger summaries with consistent naming. Links pointed to managed locations with role-based access, and Workiva permissions governed who could view narratives and attachments. The evidence binder updated automatically when support refreshed, preserving prior versions for audit.