Closing or navigating away from a bank transaction with an unsaved clarification reply can prompt you to discard the draft. The prompt helps prevent losing context you have typed but not submitted.
- Decide whether the draft should become part of the transaction’s saved context.
- Stay in the detail and save it if the answer is accurate and replies are available.
- Discard the unsaved reply only when you intend to leave without submitting those changes.
Wait for active saves to finish
The detail also protects active clarification and future-rule operations. A busy save is not the right time to assume that leaving will either cancel or complete the request.
If the outcome is uncertain, use the relevant saved-answer or same-request recovery controls before navigating. A draft shown in the input field is not proof that it has been stored. Likewise, dismissing a discard prompt without leaving does not save the reply. Check the explicit success message and stored response. Once the intended action is confirmed, continue with the category or accounting workflow. Keeping the draft decision separate from the accounting decision helps avoid a transaction being treated as explained when the context was never submitted.
Was this article helpful?
Tell us whether this answered the question you came with.