Skip to content
Enjoy complimentary data migration when switching from your existing bookkeeper or CPA to Institution.
Bank activity and transaction review

Reload a bank category after source or access changes

Use current saved evidence when an inline edit becomes stale.

Updated 2026-11-11

The inline category editor can stop a save when the transaction or your access changed. It asks you to reload the saved category before editing so the next decision uses current evidence and permissions.

  1. Choose Check saved category from the editor.
  2. Read the current saved choice and any source hold or access message.
  3. Make a new supported selection only when the record is editable in its current state.

A valid earlier edit can become outdated

Another reviewer may have saved a category, the bank may have changed the source, or your permissions may have changed. The previous account selection should not automatically overwrite those newer conditions.

If the source is held for correction, resolve that review in Integrations. If access is no longer sufficient, use the company’s normal permissions or reviewer handoff process. Do not repeat the stale save in another tab to try to bypass the check. A fresh read lets you distinguish a real account disagreement from an outdated screen. After a successful new save, verify the row’s current category and keep any ledger posting or correction action separate. The editor’s source check protects the decision against changes made after you opened it.

Was this article helpful?

Tell us whether this answered the question you came with.

Related articles

Still stuck?

Tell us what you were trying to do and where it went wrong. If you are already a client, you can also open a support case from Help and support in your workspace.

We confirm who you are before we change anything on an account.