Recurring assumptions and recovery

A recurring pattern is a candidate assumption. Repetition in bank activity is not proof that the next payment will happen or that its accounting treatment is correct.

Review a schedule

In /reconciliation, inspect the driver or historical candidate, supporting journals, amount, expected day and accounting template. Confirm that the obligation does not duplicate another forecast, then approve a bounded capture window.

A qualifying three-month historical pattern can become a reviewed monthly driver. Its approval retains the median amount, payment-day assumption, source line identities, source and document-approval fingerprints, and rule version.

The approval window is bounded to 24 months. A schedule does not grant indefinite authority to reinterpret future activity. Pause it when future capture should stop.

Preserve existing obligations

Approval does not rewrite captured expectations. If the current historical occurrence is already preserved, the history-based schedule begins in the next month. Repeated approval cannot create another driver for the same pattern.

Changing a driver does not change the identity or reviewed terms of obligations already captured from it. Review those separately if necessary.

Recognize stale support

Changes to the driver, accounting template, historical journals or supporting document approvals can make a recurring approval stale. Reversing a supporting journal is one example.

Stale support is an exception that needs a new decision, not a reason to silently continue an old inference.

Approve a replacement

The recovery review shows the original schedule, current source lines and the obligations that must remain intact.

1. Inspect why the schedule is stale.
2. Enter the replacement monthly amount, payment day and end month.
3. Review the before/after cash preview and preserved obligations.
4. Acknowledge preservation and give the replacement a reason.
5. Approve the current preview.

This creates an explicitly reviewed manual assumption. It does not recertify changed history as an unchanged recurring pattern. The original future schedule is ended and its capture policy paused; the replacement starts after already captured original months. Existing allocations stay intact.

Payment days clamp to the end of shorter months: a day-31 assumption becomes February 28 in a non-leap year. These dates remain assumptions unless reviewed as obligation dates.

If inputs change before approval, the recovery hash becomes stale and the preview must be refreshed.

Learn without automatic overfitting

Use Forecast accuracy to inspect completed obligations against preserved forecasts. Repeated lateness or amount differences can inform a new assumption. The product does not automatically recalibrate a driver from a small or incomplete sample.