Final Analytics Reconciliation
Recheck final analytical consistency after recorded corrections.
Description
Final analytics compare a corrected metric with its expected value.
Final analytics compare a corrected metric with its expected value. Corrections and remaining discrepancy have different signs.1
Recheck final analytical consistency after recorded corrections.
When to use Final Analytics Reconciliation
Use this tool to recheck final analytical consistency after recorded corrections.
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 Final Analytics 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 preCorrectionMetric, postCorrectionMetric, expectedMetric, tolerance using the field table and calculation rules, then run the tool.
- Read correctionChange, remainingDifference, consistent. 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 |
|---|---|---|---|
| preCorrectionMetric | Pre-correction analytic metric | number | Required |
| postCorrectionMetric | Post-correction analytic metric | number | Required |
| expectedMetric | Expected analytic metric | number | Required |
| tolerance | Allowed absolute difference | number; minimum: 0 | Required |
Enter finite signed metrics/nonnegative tolerance; return differences and inclusive absolute remaining gate.
change=post−pre; remaining=post−expected Units, indexing, boundary conditions and exceptional cases are defined in the calculation rules above.
| Output field | Meaning | Value type |
|---|---|---|
| correctionChange | Metric change from corrections | number |
| remainingDifference | Post-correction difference from expected | number |
| consistent | Post-correction metric is within tolerance | boolean |
{
"input": {
"preCorrectionMetric": 120,
"postCorrectionMetric": 101,
"expectedMetric": 100,
"tolerance": 2
},
"output": {
"correctionChange": -19,
"remainingDifference": 1,
"consistent": true
}
}Limitations and assumptions
No expected-value model, correction validity or audit sufficiency is established.
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 Variance Explanation Check: Compare caller-supplied expected and observed records for variance explanation check. For a complementary task, use Ratio Narrative Check: Compare caller-supplied expected and observed records for ratio narrative check.
References
-
Final Analytics Reconciliation — tool.io
Similar or alternative tools
- Variance Explanation Check
Compare caller-supplied expected and observed records for variance explanation check.
- Ratio Narrative Check
Compare caller-supplied expected and observed records for ratio narrative check.