If a transaction description on your Republic Bank 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 is long, a statement document sometimes wraps the text across two or more printed lines. Convert·Into reads each row as part of its table: the engine detects when a line belongs to the same transaction and merges it before extraction, so a single credit-card purchase split into three printed lines lands as one row in the export. The running-balance check still applies to the merged row, keeping the ledger consistent regardless of how the original statement wrapped its text.
When your Republic Bank 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. Statement documents that arrive as a scan or a photograph add a layer of uncertainty: a stray mark or uneven lighting can shift a digit. Convert·Into reads scanned pages with OCR, then runs the same line-by-line verification it applies to any other statement. If the extracted running balance deviates from the printed closing figure, the engine flags the specific row where the gap appeared. You review that row and correct it; the rest of the file exports normally.