Power BI Row Count and Totals Reconciliation Pack for Every Refresh
Build checks into the report.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.
Design a reconciliation page for a Power BI report. Source systems and tables: [SOURCES]. Key totals and counts that must agree: [KEY_TOTALS]. Tolerance: [TOLERANCE]. Write the measures in plain words and as DAX outlines, marked [VERIFY] since syntax and settings depend on version; test them on a small sample first. Page design with a table of checks: for each source table, source rows, loaded rows, difference and status; for each key measure, source total, report total, difference, tolerance and status; plus the latest refresh timestamp, the maximum date in the data and a count of rows with missing keys. Use green and amber states that also use text. Example: source 12,480 rows, loaded 12,432, difference 48 or 0.38 percent. Example table (invented): Sales rows 1,248,330 in both; Customers 18,402 in both; Revenue total 9,481,220.55 in both; Refund total 214,880.10 in both; Latest date 2026-03-14 in both. Produce the source figures with an agreed query or report run by the data owner at refresh time, stored in a table the report reads [VERIFY]. Failed checks must be visible to report owners: show a warning banner, notify the owner, and do not promote the report until fixed, with a log (date, result, action), an escalation path for red status, and data owner sign-off after each month-end refresh. Explain differences: timing, filters, currency conversion rounding, and the tolerance rule.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.