Debt Covenant Compliance Independent Recompute Step
Independently recompute a debt-covenant ratio from source values, compare it with the reported ratio, and test both against the supplied limit and tolerance.
Description
A debt-covenant recomputation compares ratios derived from reported and source amounts.
A debt-covenant recomputation compares ratios derived from reported and source amounts. Covenant compliance and agreement between ratios are separate ideas.1
The returned values include Covenant compliant, Recomputed ratio, Reported ratio, Recomputed minus reported. The How section below explains the calculation, input rules and interpretation.
When to use Debt Covenant Compliance Independent Recompute Step
Use Debt Covenant Compliance Independent Recompute Step when you need to evaluate the supplied records under the calculation and evidence rules below. Only an upper-bound covenant is modeled. No ratio agreement test, legal covenant terms, adjustments or source authenticity is established.
Prepare source-backed observations and the applicable engagement policy before entering facts. Use consistent monetary units and periods. Supply all boolean evidence flags explicitly, and treat a successful screen as a reason to continue professional review.
How to use Debt Covenant Compliance Independent Recompute Step and understand its results
- Prepare source-backed observations and the applicable engagement policy before entering facts. Use consistent monetary units and periods. Supply all boolean evidence flags explicitly, and treat a successful screen as a reason to continue professional review.
- Enter covenantLimit, reportedDenominator, reportedNumerator, sourceDenominator, sourceNumerator, tolerance using the field table and calculation rules, then run the tool.
- Read compliant, recomputedRatio, reportedRatio, ratioDifference. 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 |
|---|---|---|---|
| covenantLimit | Covenant limit | number | Required |
| reportedDenominator | Reported denominator | number | Required |
| reportedNumerator | Reported numerator | number | Required |
| sourceDenominator | Source denominator | number | Required |
| sourceNumerator | Source numerator | number | Required |
| tolerance | Tolerance | number; minimum: 0 | Required |
Require finite signed values, nonzero denominators and nonnegative finite tolerance. Return finite ratios and source−reported difference. compliant means both ratios≤limit+tolerance; it does not require their difference within tolerance.
reported=reportedNum/reportedDen; recomputed=sourceNum/sourceDen Units, indexing, boundary conditions and exceptional cases are defined in the calculation rules above.
| Output field | Meaning | Value type |
|---|---|---|
| compliant | Covenant compliant | boolean |
| recomputedRatio | Recomputed ratio | number |
| reportedRatio | Reported ratio | number |
| ratioDifference | Recomputed minus reported | number |
{
"input": {
"covenantLimit": 3.5,
"reportedDenominator": 100,
"reportedNumerator": 320,
"sourceDenominator": 200,
"sourceNumerator": 650,
"tolerance": 0.01
},
"output": {
"compliant": true,
"recomputedRatio": 3.25,
"reportedRatio": 3.2,
"ratioDifference": 0.04999999999999982
}
}Limitations and assumptions
Only an upper-bound covenant is modeled. No ratio agreement test, legal covenant terms, adjustments or source authenticity is established.
Numeric inputs, where present, must be finite. Follow the calculation-specific rules for overflow, underflow and exceptional cases. Missing fields without a declared default, 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 Lead Schedule Supporting Detail Tie-Out Method Lookup: A lead schedule and supporting total should reconcile on matching units and scope. The residual should remain visible rather than be plugged. For a complementary task, use Group Audit Component Materiality Division Instruction Letter: A group/component materiality allocation should reconcile with the component auditor's amount and instruction allocation. This tool applies supplied percentages.
References
Similar or alternative tools
- Lead Schedule Supporting Detail Tie-Out Method Lookup
A lead schedule and supporting total should reconcile on matching units and scope. The residual should remain visible rather than be plugged.
- Group Audit Component Materiality Division Instruction Letter
A group/component materiality allocation should reconcile with the component auditor's amount and instruction allocation. This tool applies supplied percentages.