QBO File Editor

Why edit a QBO file at all?

A Web Connect file is supposed to be a one-way trip: bank to QuickBooks, untouched. Real files break that ideal in ordinary ways. The statement you downloaded covers three extra days and includes two transactions that belong to another period. The bank truncates payee names to a code nobody recognises. One amount was exported with the wrong sign. Until now the choices were to import the flaws and repair them inside QuickBooks one transaction at a time, or to open the QBO in a text editor and risk breaking its OFX structure with a stray keystroke.

This editor is the middle path. It reads the file's transactions into a table where each value is a field — not markup — so a fix is a typed correction, not surgery on tags. When you download, the file is rebuilt from scratch as clean OFX 1.02 with the same structure the OFX to QBO fixer produces: valid whether or not the file you started with was.

What you can change — and what you deliberately cannot

Find & replace: the payee-name cleanup

The highest-value edit is usually the least dramatic one. Bank exports shorten names to fit legacy fields, so a year of card spending arrives as fragments: “AMZN MKTP US*”, “SQ *COFFEE”, “DD *DOORDASH”. Inside QuickBooks those fragments become vendor names, and every report inherits the mess. Find & replace fixes a whole class of transactions in one pass: search for the bank's fragment, replace it with the name your chart of accounts expects, and the tool reports exactly how many transaction names contained the text before anything changes.

Two cautions keep the feature honest. Matching is exact and case-sensitive — the tool will never rename something that merely resembles your search text. And replacement applies to the name field only: amounts, dates, and IDs are untouched, so a cleanup pass cannot move a single cent.

The reconciliation caution, stated plainly

Editing a statement file is safest before its first import. QuickBooks matches imported transactions against what it already holds, using the FITID and the transaction details. If a file was already imported and you edit an amount or a date and import it again, QuickBooks sees a transaction it cannot match to its earlier copy — and reconciliation inherits the difference. The totals bar in the editor exists for exactly this reason: money in, money out, and net update with every edit, so you can prove your edited file still adds up to the statement before it goes anywhere near QuickBooks.

When to use a different tool instead

If the file is structurally broken — unclosed tags, a wrong OFX version, repeated FITIDs — the OFX to QBO fixer repairs it automatically rather than asking you to edit around the damage. If you only need part of the file, the QBO splitter trims it to a date range and recomputes the closing balance for the kept period. And if you are not sure the file is sound, run it through the QBO File Checker first — it diagnoses without changing a byte.

How the rebuild works

Downloading does not patch your file — it builds a new one. The rows in the table, in the order shown, become the transaction list of a fresh OFX 1.02 document with full 14-digit timestamps, your file's account number, and its closing (ledger) balance carried over untouched. FITIDs ride along unchanged where they exist; a row whose original file carried no ID gets a deterministic one generated from its own contents, so re-importing the same edited file twice cannot create duplicates. If you would rather work in a spreadsheet, the CSV download contains the same edited rows in the same columns as the QBO to CSV converter.