Surprise Cash Count Unannounced Rotation Checker
Check supplied surprise-cash-count facts for announcement, scheduling, auditor-selected location, team independence, and observation count.
Description
A surprise cash-count screen checks whether a count was announced or routine and whether location and team choices support independence.
A surprise cash-count screen checks whether a count was announced or routine and whether location and team choices support independence. These are entered facts.1
The returned values include Observation count valid, Valid surprise count, Violations, Violation labels. The How section below explains the calculation, input rules and interpretation.
When to use Surprise Cash Count Unannounced Rotation Checker
Use Surprise Cash Count Unannounced Rotation Checker when you need to evaluate the supplied records under the calculation and evidence rules below. No cash is counted, location rotation inferred or completeness of surprise-count controls 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 Surprise Cash Count Unannounced Rotation Checker 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 countObservations, countTeamIndependent, locationSelectedByAuditor, performedOnScheduledDate, wasAnnounced using the field table and calculation rules, then run the tool.
- Read observationCountValid, validSurpriseCount, violationCount, violations. 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 |
|---|---|---|---|
| countObservations | Number of cash observations documented by the count team. | integer; minimum: 1 | Required |
| countTeamIndependent | Count team independent | boolean | Required |
| locationSelectedByAuditor | Location selected by auditor | boolean | Required |
| performedOnScheduledDate | Performed on scheduled date | boolean | Required |
| wasAnnounced | Count announced | boolean | Required |
Require four booleans and positive safe-integer observation count. Collect violations in announced/scheduled/location/team order; return count, violation list and valid flag. observationCountValid is always true for accepted input.
valid=not announced AND not scheduled AND auditor-selected location AND independent team Units, indexing, boundary conditions and exceptional cases are defined in the calculation rules above.
| Output field | Meaning | Value type |
|---|---|---|
| observationCountValid | Observation count valid | boolean |
| validSurpriseCount | Valid surprise count | boolean |
| violationCount | Violations | integer; minimum: 0 |
| violations | Violation labels | list of string |
{
"input": {
"countObservations": 2,
"countTeamIndependent": true,
"locationSelectedByAuditor": true,
"performedOnScheduledDate": true,
"wasAnnounced": false
},
"output": {
"observationCountValid": true,
"validSurpriseCount": false,
"violationCount": 1,
"violations": [
"count_used_scheduled_date"
]
}
}Limitations and assumptions
No cash is counted, location rotation inferred or completeness of surprise-count controls 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 External Confirmation Process Control Checklist: External confirmation depends on control of requests and responses. Independence, verified addresses, authorization, response tracking and resolved exceptions support the declared process. For a complementary task, use Inventory Observation Count Tag Two-Team Controls Lookup: Two inventory counts and control tags provide different evidence. Count agreement alone does not satisfy the tag check.
References
Similar or alternative tools
- External Confirmation Process Control Checklist
External confirmation depends on control of requests and responses. Independence, verified addresses, authorization, response tracking and resolved exceptions support the declared process.
- Inventory Observation Count Tag Two-Team Controls Lookup
Two inventory counts and control tags provide different evidence. Count agreement alone does not satisfy the tag check.