Skip to main content

Excel and Power Query

Use Excel and Power Query without hiding the monthly routine.

For finance, operations and reporting teams whose recurring work begins with folders of files and ends in a workbook, review pack or action log.

Quanta Meridian separates file intake, query logic, approved adjustments, checks and reviewed outputs so the workbook can be refreshed and handed over.

The working question

Which files entered the refresh, what changed them, which adjustments were approved and do the workbook totals still reconcile?

Inspect the project evidence

In the monthly sales workbook, eight regional files replace manual copying. In the supplier-quality build, six plants provide defect and downtime files. Power Query combines the expected files and checks their structure; Excel keeps the visible issue decision, approved adjustments and report tie-out. A missing file is treated as a reporting problem, not silently ignored.

Monthly files into a checked workbook
01

Check the expected files

The refresh confirms the period, sender, filename and required columns before combining data.

02

Run staged queries

Reusable functions, filters, types and reference joins remain visible in Power Query.

03

Separate adjustments

Manual corrections have an owner, reason and approval instead of being typed over source values.

04

Reconcile the workbook

Row counts, sales, margin, defects or downtime tie to the refreshed inputs.

05

Record the issue decision

The owner releases, limits or holds the output and leaves instructions for the next run.

01

The workbook remains a working tool

A controlled workbook can still support familiar review and commentary. The change is that source files are loaded through named queries, transformations are inspectable and manual decisions sit in dedicated tables rather than being mixed into formulas.

Parameters and reusable functions reduce repeated steps. Data types are assigned early, rows are filtered before expensive operations and query names explain their purpose to the next analyst.

02

Refresh failure protects the report

If one plant file is missing, the combined defect total will be incomplete even though the remaining files are valid. The refresh therefore records the missing input and blocks or limits the report according to the agreed release rule.

The retained projects include genuine XLSX files, embedded Power Query where claimed, source data, checks, outputs and handover notes. Screenshots are used to show the native workbook, not replace it.

Readable project evidence

Folder query and staged Power Query

From Monthly Sales and Margin Workbook Rebuild. The XLSX retains a real folder function, staged M code, named checks and a separate failed row result.

Native workbook evidence showing the regional folder query, typed staging, customer and product joins, failed row output and selected Power Query M code

Evidence type: native workbook evidence

Used in public projects

How workbooks prepare, reconcile and hand over monthly work

These links cover the complete set of current projects that use this capability. Each project states its data, native build, validation and limitation.

01

Monthly Sales and Margin Workbook Rebuild

Eight regions send monthly sales files and manual copying can hide a missing file or changed column.

How Excel and Power Query is used

Power Query imports, types and joins the files while Excel keeps approved adjustments and the issue decision.

Retained proof

The native workbook retains the folder function, M code, failed rows, reconciled sales and margin and June release review.

02

Order-to-Delivery Metric Dictionary

Finance and Operations need the same on-time-delivery formula in SQL, Excel and Power BI.

How Excel and Power Query is used

The catalogue gives the workbook a named formula reference, version and approved treatment of split orders.

Retained proof

Known cases and one two-line order confirm implementation equivalence.

03

On-time Delivery Metric Reconciliation

The management pack and analytical reports publish different delivery percentages.

How Excel and Power Query is used

A real reconciliation workbook independently calculates each numerator and denominator and records the fix.

Retained proof

The exact bridge from each report result to the approved figure is retained.

04

Reporting Data Issue and Retest Register

A missing product mapping removes a supplier category from the monthly report.

How Excel and Power Query is used

The native register preserves impact, containment, correction, independent retest and release history.

Retained proof

The workbook contains realistic multi-period issues and one incident documented in full.

05

Monthly Operating Review Pack

A long monthly status pack contains many charts but does not make the leadership meeting easier.

How Excel and Power Query is used

A source workbook feeds a concise six-page operating review with four material exceptions, three decisions and named actions.

Retained proof

The PPTX, PDF, source tie-outs, decision log and action carry-forward are retained.

06

Monthly Performance Commentary and Decision Log

Metric owners must explain material movements before the monthly pack is issued.

How Excel and Power Query is used

The workbook applies thresholds, records responses and reviewer challenges, and carries deferred decisions once into the next cycle.

Retained proof

Aged backlog rising from 420 to 515 cases is traced through explanation, meeting decision and next-month action.

Working boundary

What a workbook cannot control without an agreed routine

A workbook is appropriate when its scale, users and controls fit the routine. It should not conceal unstable source structures, uncontrolled access or transformations that need a managed data platform.

Bring one recurring workbook, a sample of the monthly files and the checks used before issue. The first review can identify what should remain visible to the analyst and what should become repeatable.

Discuss this capabilityReturn to all capabilities