A retained reconciliation request belongs to the user who prepared it. If the signed-in account changes, the workflow can ask you to sign in to the original account before resuming that request.
- Read the recovery message and confirm which account originally submitted the action.
- Return to that authorized account using the normal sign-in process.
- Open the same company and statement context, then retry the retained request to check its outcome.
Do not transfer a pending action through shared credentials
Another reviewer’s session should not be used to impersonate the original submitter. If responsibility changes, first establish the existing request’s outcome through the supported access and review process.
The current company permissions are still checked, so signing in as the original user does not guarantee that an outdated action remains permitted. If access has changed, read the resulting rejection and follow the appropriate recovery path. An uncertain request needs outcome recovery; a definitively rejected request can be discarded and replaced after refresh. Keep the original evidence and action scope clear during the handoff. The goal is a traceable saved result attributed to the authorized user who made the decision, followed by any separate current correction that is actually needed.
Was this article helpful?
Tell us whether this answered the question you came with.