What to do now
A rejected-record register captures every source record not accepted as expected: stable source identity, domain, rejection stage and reason, raw evidence reference, attempted transformation, destination impact, owner, next action, and approved disposition. Reconcile the register to import totals so skipped records cannot disappear between logs and manual fixes.
Key takeaways
- A successful job can still contain rejected records.
- Preserve source identity through every remediation attempt.
- Manual correction needs the same disposition and acceptance evidence as automated import.
Reconcile the import population
For each domain, prove source count equals accepted plus rejected plus intentionally excluded under an approved rule, with duplicates and merges explained. Counts alone are not enough when records split or combine; retain the mapping.
Do not overwrite raw rejected input while cleaning it. Keep a restricted evidence reference and create a new transformation or correction version.
Use a disposition register, not a log dump
Technical logs may contain the error; the operational register explains the decision and impact.
| Field | Required content | Why it matters |
|---|---|---|
| Lineage | Source system, domain, stable ID, source snapshot | Find the original record |
| Failure | Stage, reason code, readable explanation | Group without losing specificity |
| Impact | Related balances, documents, workflows, or parties | Prioritize the consequence |
| Remediation | Transformation or manual action version | Avoid repeating failed attempts |
| Disposition | Reimported, merged, excluded, deferred, or unresolved | Prevent silent deletion |
| Acceptance | Destination ID, verifier, evidence, date | Close the lineage loop |
Separate data defects from mapping decisions
Examples include missing required source value, invalid format, unresolved relationship, destination constraint, duplicate candidate, unsupported legacy field, and technical transport failure. “Bad data” hides whether the source is wrong or the migration rule is incomplete.
When a record is intentionally excluded, name the approved exclusion rule and retrieval path. Excluded is a disposition that requires evidence, not a synonym for unimportant.
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 snapshot and domain populations frozen
☐
Accepted, rejected, and excluded populations reconcile
☐
Stable source identity retained
☐
Readable reason and impact recorded
☐
Remediation versions preserved
☐
Exclusions explicitly approved
☐
Destination outcome and verifier close each item
0 of 7 marked
Edge cases
- One source record becomes several destination records: retain a one-to-many mapping.
- Several source duplicates merge: preserve all source IDs and the merge authority.
- A rejected record contains sensitive data: restrict evidence while keeping a non-sensitive operational reference.
Sources and references
Follow each source to check the underlying claim. Access checks and professional review are different steps.
Continue the workflow
pms migration reconciliationA tenant questions an opening balance: prepare the evidenceChoose the source of truth for property operationsRevision history
2026-09-18
Initial Phase 2 operational article with an original decision artifact, explicit failure states, primary-source scope notes, and AI-assisted technical review.