An FP&A reporting workflow with a trail to the model

For: FP&A team producing a monthly reporting pack

An FP&A reporting workflow repeats every month: refresh the model, update the pack, explain the movements. The expensive part is the explanation — finding why a number moved, and proving it did not move because a formula broke during the refresh.

The situation

The pack is rebuilt from the same model every month. Between two cycles the model is edited by several people, a couple of rows get inserted, and one tab is rolled forward. The numbers in the pack change, and the commentary has to say why.

What the work looks like today

Comparing two versions of the workbook is the native way to see what moved: Inquire, then Compare Files, which shows differences cell by cell and colour-codes them by kind (Microsoft Support).

The output is a diff, not an explanation. Turning a few hundred changed cells into three sentences of commentary is still manual, and deciding which changes are real rather than a shifted row takes judgement.

Where CalcoraSuite fits (planned)

Two parts are planned to help: a comparison that aligns versions before reporting differences, and a link report so the pack’s tables can be checked against the model before circulation.

Neither is released. The compare workbooks and Excel to PowerPoint link pages carry the current status of each.

Get early access

Test each add-in on a real model before it is released.