Client Provided Schedule Reliability Foot-Tie Sampler
Sum selected client-schedule balances and compare the sum with the stated foot total and ledger total against an explicit tolerance.
Description
Footing tests arithmetic within a schedule and tying tests its relation to a ledger total.
Footing tests arithmetic within a schedule and tying tests its relation to a ledger total.1
This tool calculates both signed differences for supplied balances without selecting a sample or verifying its completeness.
When to use Client Provided Schedule Reliability Foot-Tie Sampler
Use this tool to calculate both signed differences for supplied balances without selecting a sample or verifying its completeness.
How to use Client Provided Schedule Reliability Foot-Tie Sampler and how it works
- Establish the observations, units, reference context and assumptions described below.
- Enter ledgerTotal, sampledBalances, sampledFootTotal, tolerance and run the tool.
- Read footDifference, ledgerDifference, reconciled, sampledBalanceSum using the meanings and sign conventions below.
- Correct any rejected inputs and rerun; independently review the result under the stated scope.
| Input field | Meaning | Value type | Requirement |
|---|---|---|---|
| ledgerTotal | Finite signed ledger total on the same scope and monetary basis. | number | Required; finite; branch conditions below |
| sampledBalances | Nonempty finite signed balances selected independently for the stated footing basis. | array of number | Required; branch conditions below |
| sampledFootTotal | Finite signed total stated on the matching client schedule. | number | Required; finite; branch conditions below |
| tolerance | Tolerance, on the measurement or ledger basis specified below. | number | Required; finite; minimum 0; branch conditions below |
Supply nonempty finite signed sampled balances, finite schedule foot total and ledger total on the same monetary basis, and nonnegative tolerance. Sum balances, calculate footDifference=statedFoot-sum and ledgerDifference=sum-ledger. Return reconciled only if both absolute differences<=tolerance; zero differences are normalized to zero. The tool does not choose a sample or establish that a partial sum should equal a full ledger.
sumBalances=sum(sampledBalances); footDifference=statedFoot-sumBalances; ledgerDifference=sumBalances-ledgerTotal Use the stated ordering, units and branch conditions.
| Output field | Meaning | Value type |
|---|---|---|
| footDifference | Signed schedule-stated foot total minus supplied balance sum. | number |
| ledgerDifference | Signed supplied balance sum minus ledger total. | number |
| reconciled | True when both absolute foot and ledger differences are at most tolerance. | boolean |
| sampledBalanceSum | Sampled Balance Sum, using the scope, ordering and rule explained above. | number |
{
"input": {
"ledgerTotal": 1000000,
"sampledBalances": [
250000,
300000,
450000
],
"sampledFootTotal": 1000000,
"tolerance": 100
},
"output": {
"footDifference": 0,
"ledgerDifference": 0,
"reconciled": true,
"sampledBalanceSum": 1000000
}
}Limitations and assumptions
The result summarizes supplied audit observations under the stated arithmetic or checklist rule. It does not inspect underlying documents, select sufficient audit evidence, make a professional assurance judgment or establish regulatory compliance. Empty or all-true input can describe only the recorded assertions.
Supply explicit values and dense aligned arrays. Unexpected fields, wrong types and nonfinite scalar values are rejected; fixed-token, alignment and other branch conditions are explained above. A successful false flag, empty match list or unknown-evidence list differs from an input error. Extremely large inputs or nonrepresentable results may fail.
Alternative or Complementary methods
Use Application Control Report Parameter Integrity Checker for a related operation: Report parameter completeness depends on which parameter names are supported, required and actually supplied.
Use CAATS Full Population Testing Benefit Lookup for a related operation: Testing a full population still depends on data completeness, query controls, reconciliation and review.
References
Similar or alternative tools
- Application Control Report Parameter Integrity Checker
Report parameter completeness depends on which parameter names are supported, required and actually supplied.
- CAATS Full Population Testing Benefit Lookup
Testing a full population still depends on data completeness, query controls, reconciliation and review.