Cloud / Integrations and data / ARTEFACT
Reconciliation reporting
A report that shows where two systems disagree, how far apart they are, and since when.
Reconciliation reporting drawn as a report. Parts: Matching rules, Difference register, Scheduled report and Exception register. Acceptance: Every record in the agreed test exports is paired or classified as unmatched by the approved rules. Every open exception records a named owner and status.
01
Matching rules
02
Difference register
03
Scheduled report
04
Exception register
- Every record in the agreed test exports is paired or classified as unmatched by the approved rules.
- Every open exception records a named owner and status.
WHAT THIS ARTEFACT IS
A named output with defined parts
Reconciliation reporting compares records held by two systems, identifies missing or conflicting values and records the age and ownership of each unresolved difference.
What is inside it
- 01
Matching rules
Stable identifiers and fallback rules state how records from the two systems are paired.
- 02
Difference register
Missing, conflicting and duplicate values are classified with their source, age and current owner.
- 03
Scheduled report
A defined job reads both approved exports, applies the matching rules and writes the dated comparison.
- 04
Exception register
Unresolved differences retain an owner, status and resolution note between report runs.
WHAT IT TAKES
Inputs, time and ownership
FROM YOU
4 inputs
- Exports from both systems
- Record identity rules
- A named data decision maker
- Existing reconciliation notes
WORKING RANGE
CLIENT ROLE
A data decision maker must approve record identity rules and decide which source wins when values conflict.
WHERE IT SITS
The work around this artefact
- ParentIntegrations and data
- Service lineCloud & Modernization