Still reconciling in Excel after implementing Workiva? What to keep and what to move

Find which recurring Excel steps could move into Workiva and which analysis still belongs in your workbook.

The short answer

Map one reconciliation that still runs in Excel from its source through to the reviewed report line. If the spreadsheet is occasional, controlled analysis, keep it. If it is a recurring bridge the reporting package cannot move without, it is a candidate to rebuild inside Workiva, using spreadsheets, formulas, and Wdata or a supported connection, once the inputs, owners, and acceptance checks are confirmed.

Where the spreadsheet still sits

Workiva is implemented. The statements, management report, or board package are built there. Yet every cycle someone exports data to Excel to reconcile totals, apply recurring adjustments, or build a bridge before the package can move forward.

This is about reporting bridges: tie-outs, recurring adjustments, and mapping steps that feed the Workiva package. Balance-sheet account reconciliations usually belong in your ERP or a reconciliation tool, and are not the subject here.

A controlled, well-understood spreadsheet analysis can be the right tool. The question is whether the spreadsheet is occasional analysis, or a recurring manual bridge that the reporting process depends on every period.

Map one reconciliation

Pick one reconciliation that still runs in Excel and trace it from source to the reviewed report line.

Illustrative figures.

Step What to map for one cycle Evidence and owner Question it answers
Source basis Period, entity, population, and source total Export or file; source owner Is the source and its scope consistent each cycle?
Approved items Adjustments included Approval record; accounting approver Which items are authorized and which are open?
Excel bridge Formulas, mappings, exclusions, manual steps Workbook version; preparer Is this analysis, or a required recurring step?
Workiva report line Where the reconciled result lands Spreadsheet and report output; operator Could Workiva carry this step directly?
Review Checks performed; items carried forward Reviewer sign-off; open-item owner What must be preserved for review?

Keep unexplained differences visible on the map. A balancing line added to make the bridge tie is itself a finding.

Signs the bridge belongs in Workiva

  • The same export, paste, and formula steps happen every cycle.
  • The workbook’s output is typed or pasted into a Workiva spreadsheet rather than linked.
  • Only one person can run it, and the steps are not written down.
  • Reviewers re-perform the reconciliation because they cannot see how it was built.
  • A late adjustment means redoing the bridge by hand.

Signs it should stay in Excel

  • It is exploratory or one-off analysis.
  • Its inputs and logic change materially every cycle.
  • It supports a judgment, and the judgment is what the reviewer needs to see.

What moving it takes

Moving a recurring bridge into Workiva usually means three things: a stable input, logic that lives in formulas instead of hand steps, and a link from the result to the report line.

  • Input. Either a controlled upload each period or a Wdata table fed by a supported connection. Importing the old workbook once does not create a live connection. See what Wdata is and when finance teams need it.
  • Logic. Mappings and exclusions expressed as formulas or queries a reviewer can read, not as a sequence of manual edits.
  • Output. The reconciled figure linked into the reporting spreadsheet or document, so a correction flows through instead of being re-keyed.

Before switching over, run the new version in parallel with the Excel bridge for at least one real cycle and compare results line by line. Replace the spreadsheet only when the two agree and the differences you do find are explained.

  • Overview
  • Excel beside Workiva
  • Map one reconciliation
  • Recurring bridge
  • Analysis that stays
  • Moved into Workiva
  • Parallel cycle

Agree which steps to move

Review the process map with your Controller and reporting team. Identify which steps support accounting judgment and which repeat the same calculations or transfers each period. Keep accounting decisions with the designated approver and plan the repeatable steps with the source, approvals, and review checks intact.

The goal is to make one reconciliation understandable, keep the analysis that belongs in a spreadsheet, and move only the repeatable bridge that can be safely rebuilt and verified. For a fuller example of separating inputs, calculations, and presentation, see moving an Excel management report into Workiva.

Common questions

Is it wrong to use Excel alongside Workiva?

No. Excel is a reasonable tool for one-off or exploratory analysis. The risk is a recurring bridge that the reporting package depends on every cycle, outside the controls and links the rest of the package uses.

Does importing an Excel file into Workiva create a live connection?

No. Importing a workbook brings in its contents at that point in time. Ongoing updates require links inside Workiva, a Wdata table and query, or another supported connection.

What should stay outside Workiva?

Accounting judgment, genuinely ad hoc analysis, and anything whose owner and inputs change every cycle. Move the repeatable mechanics; keep the judgment with the people accountable for it.

Tell us what needs to work better

Describe the report, control process, or data flow that is not working the way it should. Every engagement starts with a fixed-fee Workiva diagnostic.

Start a conversationWorkiva financial reporting consulting