Once your Brown Brothers Harriman & Co. statement is uploaded, what you get back depends on which export format you actually need next. The export step maps the extracted transaction table into a layout your ledger or tax software can read without rekeying. Columns are categorised during extraction: dates, descriptions, debits, credits and the running balance each go into their own field, so they stay aligned in the output. Choose Excel if you need a full table with the running-balance column preserved, CSV for a lightweight import into accounting platforms, or QBO for a direct QuickBooks Online transfer. A mismatch in the column mapping would push digits into the wrong field and break reconciliation, so the converter keeps each data type in the correct lane; the closing balance you verify on screen is the same figure that lands in the exported file.
When a Brown Brothers Harriman & Co. statement you need to convert spans more than one page, Convert·Into merges every page into a single transaction table rather than treating each page as its own file. When a statement runs several pages, the printed running balance at the foot of page one becomes the opening figure at the top of page two. A manual copy-and-paste across pages often breaks that chain, leaving a gap that is hard to spot until the reconciliation fails. The engine stitches multi-page documents into a single continuous table, carrying the balance forward exactly as the statement prints it, then verifies the final closing figure against the one printed on the last page. If the carried-forward amount does not match the following page's opening line, the row is flagged so you can inspect it before the file goes into your books.
When your Brown Brothers Harriman & Co. statement arrives as a scan or a photo of the page rather than a clean export, the numbers on it are just pixels until they are extracted. Scanned or photographed statements arrive as images, not as text, so the converter applies OCR to pull the transaction rows off the page. A faint print, a skewed camera angle or a smudged digit can cause a misread, which is why every statement is run through the same running-balance check. The engine tallies the extracted figures line by line; if a 3 was read as an 8 and the arithmetic no longer reconciles, that row is highlighted for review. You correct the one problematic line and the rest of the file proceeds, without repeating the entire upload or losing the rows that extracted cleanly.