Nonresponse Alternative Procedures Second Request Steps
Select the next confirmation follow-up or require documented alternative procedures when no responses remain outstanding.
Description
Confirmation follow-up depends on outstanding responses and documented alternatives.
Confirmation follow-up depends on outstanding responses and documented alternatives. This tool routes entered status rather than receiving evidence.1
The returned values include Next action, Alternative procedures, Follow-up complete. The How section below explains the calculation, input rules and interpretation.
When to use Nonresponse Alternative Procedures Second Request Steps
Use Nonresponse Alternative Procedures Second Request Steps when you need to evaluate the supplied records under the calculation and evidence rules below. Even response_received with no outstanding items returns complete false. The rule does not represent a general engagement completion test or send requests.
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 Nonresponse Alternative Procedures Second Request Steps 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 alternativeProcedures, confirmationStatus, remainingResponses, secondRequestSent using the field table and calculation rules, then run the tool.
- Read action, alternativeCount, complete. 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 |
|---|---|---|---|
| alternativeProcedures | Alternative procedures available for nonresponding balances. | list of string | Required |
| confirmationStatus | Confirmation status | string; one of "nonresponse", "partial_response", "response_received" | Required |
| remainingResponses | Number of confirmation responses still outstanding. | integer; minimum: 0 | Required |
| secondRequestSent | Second request sent | boolean | Required |
Require exact status, nonnegative safe-integer outstanding count, second-request boolean and nonblank procedure list, possibly empty. If outstanding>0 return complete false and action based only on second request. Otherwise action document_alternatives; complete is status not response_received AND at least one alternative.
outstanding>0→second-request or resolve; else document-alternatives Units, indexing, boundary conditions and exceptional cases are defined in the calculation rules above.
| Output field | Meaning | Value type |
|---|---|---|
| action | Next action | string; one of "document_alternatives", "obtain_response", "resolve_response", "send_second_request" |
| alternativeCount | Alternative procedures | integer; minimum: 0 |
| complete | Follow-up complete | boolean |
{
"input": {
"alternativeProcedures": [],
"confirmationStatus": "nonresponse",
"remainingResponses": 1,
"secondRequestSent": false
},
"output": {
"action": "send_second_request",
"alternativeCount": 0,
"complete": false
}
}Limitations and assumptions
Even response_received with no outstanding items returns complete false. The rule does not represent a general engagement completion test or send requests.
Numeric inputs, where present, must be finite. Follow the calculation-specific rules for overflow, underflow and exceptional cases. Core numeric and string lists are limited to 100,000 entries; text entries are subject to the general large-text limit. Follow any smaller calculation limits above. Extremely large text inputs are rejected. 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 Positive vs Negative Confirmation Type Selector Lookup: Positive and negative confirmations differ in how responses support an audit procedure. This implementation applies a narrow boolean routing rule. For a complementary task, 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.
References
Similar or alternative tools
- Positive vs Negative Confirmation Type Selector Lookup
Positive and negative confirmations differ in how responses support an audit procedure. This implementation applies a narrow boolean routing rule.
- 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.