Workbook & Spreadsheet Rebuilds

Power Query Consolidation Pack

A Power Query routine that checks the expected exports, identifies file changes and combines the received months into one reporting table.

Power Query consolidation viewOpen image

Power Query consolidation

Repeated exports combined into one checked reporting table.

The reporting owner can see what arrived, what changed, what is absent and why the final refresh remains held before the combined table is used.

Useful forReporting analystsFinance teamsOperations teamsProcess owners
What is difficult now

Recurring workbook updates become unreliable when monthly exports sit in a folder with inconsistent columns, missing files and unclear refresh notes. The team may not know whether the combined table is complete before the report is used.

What needs to be decided

Which exports loaded, which file is missing, where column drift needs review and whether the combined reporting table is safe to use?

What this page shows

A folder register, repeated exports, a column change warning, a missing file check, Power Query append logic, a consolidated reporting table and a handover note.

How the work fits together

Repeated exports feed one checked Power Query routine.

The files are checked for missing months and changed columns before they are appended into the reporting table.

01Source

What the work starts with

  • Three received monthly exports and one missing expected file
  • Four-row team reference
  • Seven-row manual adjustment register
02Prepare

How it is prepared

  • Folder.Files source routine
  • Monthly-file filter and period extraction
  • Transform-each-file and Table.Combine route retained in M
03Check

Checks applied

  • One missing file
  • One column change to review
  • Duplicate period, reference join and total reconciliation checks passed
04Output

What the review receives

  • One hundred and thirty-three combined rows
  • Period-level refresh summary
  • File state, check result and owner action retained beside output
05Handover

Notes for the next update

  • File pattern and expected fields documented
  • April absence holds the final refresh
  • Source owner to decide whether the February channel field is retained
Tools used
  • Excel
  • Power Query
  • Folder refresh
  • Validation checks
Skills shown
  • Data consolidation
  • Controlled refresh
  • Column drift checking
  • Handover
Why this matters

The reporting owner can see what arrived, what changed, what is absent and why the final refresh remains held before the combined table is used.

Built from a non-client example dataset. No protected data is used.

Before the refresh

The folder is checked before its files are combined.

Confirm the folder pattern, expected files, column rules, refresh sequence and combined table needed for reporting.

  1. 01

    Three monthly exports are loaded from one folder rather than copied into the workbook separately.

  2. 02

    One missing file and one changed column set are surfaced before the 133-row combined table is cleared for use.

  3. 03

    The file pattern, owner decisions and reason for the refresh hold are recorded for the next update.

Refresh checks

Whether the expected files arrived and whether their columns still match.

Source folder6 files

Registers expected monthly exports, reference files and manual adjustment files before refresh.

Column drift1 file

Shows where one export needs review by its source owner before consolidation is trusted.

Combined output133 rows

Combines three received monthly exports while retaining period and source-file context.

Refresh hold1 missing

Keeps the absent April file visible as an owner action before the final refresh.

Folder rules

The file pattern, Power Query steps and limits used here.

What is included

  • Source folder
  • Repeated exports
  • Column change check
  • Combine and append steps
  • Missing file check
  • Combined reporting table

What it can start from

  • Monthly export folder
  • Source register
  • Power Query consolidation steps
  • Validation checks
  • Handover note

What this example does not claim

  • The M route is retained as preparation evidence; the workbook records verified output rather than running a live folder connector.
  • The evidence covers three received monthly files and 133 rows rather than production volume.
  • File patterns, field standards and the refresh owner would be agreed for implementation.

Related work

More in Workbook Rebuilds.

Workbook recovery overview showing source imports, Power Query steps, checks, controlled output and handover notes

Workbook recovery overview

Excel / Power Query Reporting Rebuild

What is difficult now
Recurring Excel reports become fragile when sources, formulas, copied tabs, manual adjustments and outputs are mixed into one workbook.
What the work helps decide
How can a recurring workbook be made safer and easier to update without first rebuilding the wider data platform?
  • Excel
  • Power Query
  • Controlled refresh
View this example

Next step

Consolidate recurring exports with visible checks.

Start with the recurring workbook, its source files and the steps that make each update difficult to run or explain.