Skip to content
Enjoy complimentary data migration when switching from your existing bookkeeper or CPA to Institution.
Statements and transaction imports

Handle an OFX file containing a bank correction

Resolve source corrections before importing ordinary transaction rows.

Updated 2026-11-11

An OFX export containing a bank correction is not accepted as an ordinary transaction import. The parser asks you to resolve the correction first so a replacement or removal is not mistaken for an additional movement.

  1. Read the bank’s original correction information and identify the transaction it changes.
  2. Check whether the original movement already exists in Institution and what review or posting work depends on it.
  3. Use the appropriate source or accounting correction workflow, or ask support to help interpret the source before importing the remaining activity.

Do not delete the correction directive while retaining its transaction as if it were a new independent row. That can preserve both the original and its replacement in the books.

Keep the correction trail

Retain the original export and any bank notice explaining the change. Record the account, date, amount and reference of the affected movement.

A clean replacement export may be useful once the correction is understood, but still compare it with existing records. Posted or reviewed transactions can require a protected accounting correction rather than the limited update available for an untouched imported source.

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.