Resolve unsaved drafts, duplicate warnings and stale data
Understand what a save message proves and recover from uncertainty, duplicate warnings or concurrent changes without double posting.
Distinguish draft, review and saved record
Preparing an entry and opening Review before saving do not post it. Confirm and save sends the reviewed request. Verify the success/readback message and the record after refresh before assuming it is saved.
Resolve an uncertain save using the same request
If the screen offers Resolve by retrying this request, use that existing request. Do not start a fresh entry for the same cash movement until its outcome is known. A repeated identical request is designed to be counted once.
Review a duplicate warning
Check the existing ledger, bank statement and original reference. Only acknowledge a genuinely separate legitimate transaction and enter the requested review reason. Do not change a reference just to avoid a warning.
Reload after a stale-data message
If another session changed the book, reload the saved state, compare your intended entry with the latest balances, and prepare a fresh review. Account/profile conflict controls likewise require reloading current details before retrying.
Correct validation and access issues
An allocation that exceeds cash or balance must be corrected. A pilot or unavailable-feature message requires enabled access; a password reset does not grant financial permissions. If fresh authentication is requested, follow that prompt without bypassing it.
Confirm the final saved outcome
Reopen the borrower, loan, receipt and audit history at the intended date. Retain the saved reference when seeking support. Avoid sharing passwords, authenticator codes, recovery links or unmasked bank details.
Check your result
- The cash movement is present exactly once.
- A failed or cancelled review has not been treated as saved.
- The reviewed result was checked after reload.