When a Fidelity Bank Nigeria 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 document runs several pages long, the converter reads every page in sequence without asking you to split the file or mark sections. A multi-page statement creates the same single transaction table as a one-page statement would, with rows that continue naturally from the bottom of one sheet to the top of the next. Headers that repeat on each page are recognised and suppressed automatically, so the exported table contains each transaction once instead of inserting a repeated title row every twenty or thirty entries. The running-balance column, if the statement prints one, is carried forward across the page break and checked for continuity; a gap or a misread that appears where the pages meet is flagged before you export anything.
If the running balance on your Fidelity Bank Nigeria 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. As soon as the file finishes processing, the converter compares the final row it extracted with the closing balance printed on the statement, then checks every intermediate row for arithmetic consistency. A single discrepancy in the middle of the sheet does not halt processing or reject the whole file: that row is flagged for review, while the rest of the table remains intact and ready to export. You see the flag alongside the transaction it belongs to, so you can correct one OCR misread or one shifted column without redoing the entire conversion.
If a transaction description on your Fidelity Bank Nigeria statement is long enough to wrap across two or three lines, it still needs to land in a single row once converted. Long transaction descriptions that wrap across multiple lines are kept together as a single entry. The converter distinguishes a wrapped narrative line from a new transaction row by reading the date column, amount column and running balance, so a three-line description that fills the space below a transaction does not fragment into three separate rows. When the statement's own layout places the narrative on one line and carries an overflow word or two onto the next, the complete description appears in one cell in the export with its line breaks preserved, exactly as it was printed.