Page pattern

Reconciliation / Audit

“Derived from the page purpose; write it explicitly before implementation.”

Validate numbers, expose mismatches and support traceability between sources or calculations.

[ Status summary ] [ Difference KPIs ] [ Mismatch table ] [ Source / record detail ]

Simulation of native Power BI behaviour

Zone 1

Status summary

Zone 2

Difference KPIs

Zone 3

Mismatch table

Zone 4

Source / record detail

Reading order follows the zones above, top-left to bottom-right.

Designer

Components: Cards, Table, Matrix, Conditional formatting

Hierarchy: Context/control → status/primary answer → explanation/breakdown → detail → next step.

Developer

Interaction: Use only interactions that support the page's next analytical step; typical next level: **Record detail**.

Navigation: Record detail

Implementation: Compose from the listed native visuals/controls and the standard interaction patterns in this guide; custom visuals are exceptions.

Common mistakes

Treating the archetype as a rigid screen; adding unrelated analytical tasks; duplicating controls already handled globally.

Related entries