Totals should survive the handoff.
Platform export$12,480.00
Report total$12,180.00
Unexplained difference−$300.00
Trace the missing row before interpreting cost per result. A correct formula cannot rescue an incomplete input range.
MONTH-END CLIENT REPORTING QA
Find the mismatch
before the client does.
A recurring report can look polished while its dates, definitions, source totals, and exported output disagree. Use these checks before delivery—or have ReportPatch review one report end to end.
The examples below are synthetic illustrations, not client work or performance results.
THREE RECONCILIATIONS
Small checks that catch expensive confusion.
Similar names are not the same metric.
Dashboard label Leads
Source definition Platform-reported form submissions
QA decision Rename the metric or document the inclusion rule.
Do not present platform events as unique CRM leads unless the deduplication and attribution logic support that claim.
The visible dates must match the filtered dates.
Report heading September 1–30
Source filter September 1–29
QA decision Refresh the full period, then re-export every format.
Check time zones, partial final days, comparison periods, and whether PDF, slide, and spreadsheet outputs show the same cutoff.
BEFORE DELIVERY
A compact acceptance pass.
For one representative client report, capture the evidence for each check—not just a green status.
- Source completeness. Expected files, tabs, channels, and reporting days are present.
- Metric agreement. Every headline label has an approved definition and owner.
- Date consistency. Current and comparison periods use the intended calendar and time zone.
- Recalculation. Totals and ratios recompute from the accepted inputs.
- Output parity. Dashboard, PDF, slide, and spreadsheet exports agree.
- Known limits. Attribution, duplication, missing data, and manual adjustments are visible.
BROWSER-LOCAL SELF-CHECK
Where could this report break?
Answer five workflow questions. Nothing is uploaded; the result stays only in this browser session and can prefill the enquiry context.
Complete all five checks to see the first QA priority.
FIXED-SCOPE REVIEW
One recurring report.
Three business days.
ReportPatch reviews one existing recurring report after written scope, payment, an approved transfer method, and complete agreed redacted inputs.
- Source-to-output map and source reconciliation.
- Metric-definition and reporting-date checks.
- Severity-ranked QA risks.
- Prioritized patch and acceptance plan.
- Refresh and export acceptance checklist.
- Go/no-go recommendation for implementation.
No passwords, card data, unrestricted account access, or unnecessary personal data. No performance, revenue, or time-savings guarantee.
SEE THE METHOD
Try the labeled synthetic sample.
Inspect monthly aggregates, validation rules, comparisons, and the reporting caveats before deciding whether the review fits.
Open the working sample ↗