Reconciliation request recovery uses saved browser data tied to the original company, account or period, and user. If that storage is unavailable or reports an error, the workflow can prevent a new submission until the recovery state is understood.
- Read the displayed recovery or storage message.
- Keep the original browser session and saved data intact while checking the request.
- Retry through the offered recovery control or ask support to investigate the specific account-period request if the issue persists.
Avoid clearing data during an uncertain save
Deleting browser data can remove the local information used to identify a retained request. Do not treat that as a way to prove the server action failed or to make a replacement submission safe.
A confirmed saved period or action may still be inspectable after refreshing Reconciliation, but establish that outcome before submitting another request. Note the company, account, statement dates, intended action, and exact visible message for a support handoff. Keep credentials and reusable authentication details out of the report. Once recovery is resolved, continue from the current saved evidence. Browser storage supports request continuity; it is not the authoritative evidence that a statement was reconciled, so verify the actual period result as well.
Was this article helpful?
Tell us whether this answered the question you came with.