Subsequent Disbursement Postdated Check Review Window
Classify subsequent cash payments inside or outside a caller-selected post-balance-date review window bounded by explicit dates.
Description
A subsequent-payment review window has both a day-offset allowance and an explicit end date.
A subsequent-payment review window has both a day-offset allowance and an explicit end date. A payment must fit both constraints.1
The returned values include Payments in window, In-window indices, In-window total, Payments outside window. The How section below explains the calculation, input rules and interpretation.
When to use Subsequent Disbursement Postdated Check Review Window
Use Subsequent Disbursement Postdated Check Review Window when you need to evaluate the supplied records under the calculation and evidence rules below. No postdated-check status, cleared-payment evidence or liability recognition is examined.
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 Subsequent Disbursement Postdated Check Review Window 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 balanceDate, payments, searchEndDate, windowDays using the field table and calculation rules, then run the tool.
- Read inWindowCount, inWindowIndices, inWindowTotal, outsideWindowCount. 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 |
|---|---|---|---|
| balanceDate | Balance date | string | Required |
| payments | Rows ordered as whole days after balance date and positive amount. | list of list of number | Required |
| searchEndDate | Search end date | string | Required |
| windowDays | Window days | integer; minimum: 0 | Required |
Require real exact YYYY-MM-DD dates, end≥balance and nonnegative safe-integer window. Supply rows [finite nonnegative dayOffset, positive finite amount], possibly empty; fractional offsets are allowed. Return zero-based qualifying indexes/count, checked amount sum and outside count. Day0 and equality qualify.
inWindow=offset≤windowDays AND balanceTimestamp+offset×86400000≤endTimestamp Units, indexing, boundary conditions and exceptional cases are defined in the calculation rules above.
| Output field | Meaning | Value type |
|---|---|---|
| inWindowCount | Payments in window | integer; minimum: 0 |
| inWindowIndices | In-window indices | list of number |
| inWindowTotal | In-window total | number; minimum: 0 |
| outsideWindowCount | Payments outside window | integer; minimum: 0 |
{
"input": {
"balanceDate": "2026-01-31",
"payments": [
[
1,
5000
],
[
20,
7000
],
[
45,
9000
]
],
"searchEndDate": "2026-03-15",
"windowDays": 30
},
"output": {
"inWindowCount": 2,
"inWindowIndices": [
0,
1
],
"inWindowTotal": 12000,
"outsideWindowCount": 1
}
}Limitations and assumptions
No postdated-check status, cleared-payment evidence or liability recognition is examined.
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. Matrices are limited to 128 rows and 128 entries per row. 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.
Alternative or Complementary methods
Use Unrecorded Liabilities Subsequent Disbursements Search Procedure: A search for unrecorded liabilities needs evidence connecting payment with an earlier obligation. This tool accepts only day-offset and amount rows, so its selection is a very narrow proxy. For a complementary task, use Dual Dating Subsequent Event Footnote Usage Lookup: Subsequent-event treatment involves chronology, recognition and disclosure. This screen applies entered treatment labels rather than deciding their applicability.
References
Similar or alternative tools
- Unrecorded Liabilities Subsequent Disbursements Search Procedure
A search for unrecorded liabilities needs evidence connecting payment with an earlier obligation. This tool accepts only day-offset and amount rows, so its selection is a very narrow proxy.
- Dual Dating Subsequent Event Footnote Usage Lookup
Subsequent-event treatment involves chronology, recognition and disclosure. This screen applies entered treatment labels rather than deciding their applicability.