The example follows a May management report for Lockfield Foods: three cost centers, revenue and operating expense rows, and an operating-result bridge. The downloadable workbook is designed to be edited and recalculated.
One workbook is doing four jobs
In the current state, a monthly ERP export is pasted next to a hand-maintained account map. Formulas produce a department summary, and that same sheet is formatted for the management pack. A reviewer can see the final number, but it takes effort to tell whether a change came from the export, a mapping decision, or a report formula.
Separate the model before choosing the build approach
Current Excel arrangement
- Paste export + adjustments
- Map accounts in-place
- Calculate totals in the presentation sheet
- Format and review the same sheet
Proposed reporting structure
- Inputs: imported rows and owned adjustments
- Calculations: mapping, sign and reconciliation checks
- Reporting: management lines, variance and commentary
- Review: test the cycle and exception paths separately
adjustments
reconciliation
variance
The figures reconcile through one clear calculation path
The example’s source rows total $2,435,000 revenue and ($1,620,000) operating expenses, producing $815,000 operating result. Budget operating result is $805,000; the $10,000 favorable variance is the difference. The workbook shows the numeric source rows, account mapping, calculated signed values and report totals on separate sheets.
Start from the existing workbook, then agree the reporting decisions
What can travel with the file
An existing .xlsx can provide data, formulas and formatting as a starting point. Here, that includes source rows, account codes, calculation formulas and a basic report layout.
Work through with the implementation team
Agree who owns the inputs and account map, how report lines and checks should work, who reviews the output, and which results should be reused.
Reconnect for the target workspace
The team should establish the approved source path, permissions, refresh responsibility and any linked destinations. Importing a workbook does not create those live connections.
Test the agreed flow
Rehearse a prior period, a corrected source row, a missing input, a changed mapping and the review path. Confirm report totals and any downstream linked destinations separately.
Agree the smallest structure that makes review repeatable
Keep formulas in the first imported workbook
Fastest for a familiar report, but formula ownership and exceptions can remain hard to see.
Rebuild the calculation layer around a defined map
More setup work, but a clearer place to test mapping, signs and reconciliation as the report evolves.
Begin with a controlled file refresh
Useful when source access is still changing; it postpones automated connection design rather than pretending it is settled.
Questions to settle together before configuration
- Which export is the reporting source of record, and when is it final enough to refresh?
- Who owns account mapping changes and signs off on a new account code?
- Which adjustment rows are expected, and who can prepare versus approve them?
- Which totals need to appear in one management report, and which must also feed another destination?
- What should a reviewer do when an input is late, a mapping is missing or a refresh fails?
Inspect the formula path yourself
The editable workbook contains an overview, numeric source rows, a mapping table, calculation formulas and the reconciled report. It has no macros or external links. Numeric report cells use numeric formulas, not presentation TEXT() formulas.
Download the editable .xlsx example
Open, edit a source amount or mapping, and recalculate in a spreadsheet application. An import can bring data, formulas and formatting; connections, permissions and review controls need to be agreed for the target workspace.
Useful Workiva documentation
Workiva features and permissions vary by workspace. Your administrator can confirm the setup that applies.