The short answer
Establish report comparability by documenting each report’s population, cutoff, date basis, field definitions, status rules, grouping, currency/rounding, and later corrections. Reproduce both from retained evidence and build a difference bridge; equal totals can hide different populations, while unequal totals can be explainable.
Key takeaways
- Compare definitions before comparing totals.
- Preserve source reports and parameters as historical evidence.
- Use a bridge that distinguishes mapping, timing, correction, and scope effects.
Write a report-definition contract
For the source and target version, record report name/version, entity and property scope, period and time zone, transaction or effective-date basis, included statuses, account mapping, treatment of reversals and voids, grouping, rounding, and report-generation time. Save the rendered source output and parameters.
A target label such as “collected rent” may include different states than the source. Do not use the familiar label as evidence of semantic equivalence.
Bridge differences by reason
Start with a frozen source total or count and apply supported difference classes until the target result is reproduced. Retain row-level examples for material categories.
| Difference class | Example | Evidence |
|---|---|---|
| Scope | Archived property included only in source | Property population lists |
| Definition/mapping | Credit classified in a different account group | Field and account mapping |
| Timing | Posted date versus effective date | Transaction dates and report rule |
| Correction | Target includes approved post-export correction | Correction chain and version |
| Presentation | Rounding or net/gross display | Calculation rule |
| Unresolved | Difference lacks support | Named owner; report not declared comparable |
State the permitted use of each historical output
Decide whether the source PDF remains the authoritative historical presentation, the target report is suitable for current operations only, or a reconciled restatement is approved. Do not silently replace owner-facing or audit-supporting historical files.
Add a comparability note to downstream dashboards or trend analyses when the definition changes. A single reconciled month may not prove earlier periods follow the same mapping.
Operational checklist
Mark your progress, then save a working copy. Selections reset when you leave this page. A checked box is not an approval or evidence of completion.
☐
Source and target report versions retained
☐
Population and cutoff definitions documented
☐
Date/status/account rules compared
☐
Difference bridge reconciled
☐
Material row samples traced
☐
Unresolved differences owned
☐
Approved historical-use statement recorded
0 of 7 marked
Edge cases
- Source system cannot rerun the exact historical version: preserve the exported file and note the reproducibility limit.
- Target recalculates historical aging using current status: do not present it as the old as-of report.
- A corrected source report was issued after extraction: include its version in delta capture.
Sources and references
Follow each source to check the underlying claim. Access checks and professional review are different steps.
Continue the workflow
PMS migration acceptance criteriaPMS migration delta capture after the source freezeVerify documents and attachments after a PMS migrationRevision history
2026-09-18
Initial Phase 3 operational article with a distinct decision artifact, failure states, source-scope notes, and AI-assisted technical review.