Record Count Reconciliation
Reconcile source and target record counts within a caller-supplied tolerance.
Description
Record-count reconciliation compares migration or processing totals under a supplied tolerance.
Record-count reconciliation compares migration or processing totals under a supplied tolerance.1
Reconcile source and target record counts within a caller-supplied tolerance.
When to use Record Count Reconciliation
Use this tool to reconcile source and target record counts within a caller-supplied tolerance.
Prepare the documented facts, aligned totals or expected/observed evidence labels requested. Choose applicable requirements and thresholds separately before interpreting a planning screen.
How to use Record Count Reconciliation and understand its results
- Prepare the documented facts, aligned totals or expected/observed evidence labels requested. Choose applicable requirements and thresholds separately before interpreting a planning screen.
- Enter sourceRecordCount, targetRecordCount, allowedDifference using the field table and calculation rules, then run the tool.
- Read countDifference, absoluteDifference, reconciles. The explanation below defines the units, signs, ordering and any flags or placeholder values.
- If the tool reports an input issue, correct the values and run it again. Apply the stated assumptions when interpreting a successfully returned result.
| Input field | Meaning | Value type; see rules below | Requirement |
|---|---|---|---|
| sourceRecordCount | Source record count | integer; minimum: 0 | Required |
| targetRecordCount | Target record count | integer; minimum: 0 | Required |
| allowedDifference | Allowed difference | integer; minimum: 0 | Required |
Enter nonnegative integer counts/tolerance; return signed/absolute difference and inclusive gate.
difference=target−source; pass=abs(difference)≤allowed Units, indexing, boundary conditions and exceptional cases are defined in the calculation rules above.
| Output field | Meaning | Value type |
|---|---|---|
| countDifference | Target minus source | integer |
| absoluteDifference | Absolute difference | integer; minimum: 0 |
| reconciles | Reconciles | boolean |
{
"input": {
"sourceRecordCount": 1000,
"targetRecordCount": 998,
"allowedDifference": 2
},
"output": {
"countDifference": -2,
"absoluteDifference": 2,
"reconciles": true
}
}Limitations and assumptions
Equal counts do not establish matching record content or completeness.
Numeric inputs, where present, must be finite. Follow the calculation-specific rules for overflow, underflow and exceptional cases. Missing required fields, extra fields, wrong value types and violations of the calculation rules are input errors. A successfully returned false flag is an evaluated outcome; its meaning is explained above.
Alternative or Complementary methods
Use Forensic Hash Chain: Compare stored and recomputed forensic evidence hashes. For a complementary task, use Final Analytics Reconciliation: Recheck final analytical consistency after recorded corrections.
References
-
Record Count Reconciliation — tool.io
Similar or alternative tools
- Forensic Hash Chain
Compare stored and recomputed forensic evidence hashes.
- Final Analytics Reconciliation
Recheck final analytical consistency after recorded corrections.