If a transaction description on your Huntington Bancshares statement is long enough to wrap across two or three lines, it still needs to land in a single row once converted. When a transaction description runs long and wraps across multiple lines on a statement document, the conversion engine reads the block as one coherent entry. It recognises that line breaks inside a description are a formatting convenience, not a row boundary. The engine groups the split text back into a single description field so that a four-line memo about a wire transfer or a merchant hold does not fragment into four false transactions. The extracted table keeps each record whole, matching the original statement's intent without manual splicing.
If the running balance on your Huntington Bancshares statement does not add up row by row, that is exactly the kind of mismatch Convert·Into is built to catch rather than pass through silently. The running balance is verified line by line against the statement's own printed closing figure. The engine reads the ending balance on the final page of the statement document, then works backward through the debit and credit columns to confirm every row's arithmetic. A mismatch on any individual line is flagged for review rather than silently carried forward, so a single misread digit does not corrupt the entire ledger. The check completes before export so that the converted file's closing balance precisely mirrors the source document.