When a CTBC Bank 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. If the activity covers several pages, the engine reads them as one continuous record. Upload a single multi-page file rather than splitting it into parts; the extraction runs across page breaks without interruption, so the transaction table collects every row before any export step begins. No manual collation or stitching is required on your side.
If the running balance on your CTBC Bank 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 checked line by line against the closing figure printed on the statement itself. When a row does not add up, that row is flagged for review while the rest of the file remains intact: there is no wholesale rejection of the statement, just a specific marker on the entry that needs attention. You can proceed with the export while the flag stands, or pause and correct the discrepancy first.
Whether you need your CTBC Bank statement in Excel, CSV or QBO, the underlying extracted table stays the same; only the export step differs. Export targets the format your next workflow expects. Choose Excel when you need a spreadsheet-ready table with columns mapped the same way every time; choose CSV for a plain import into other tools; choose QBO for a direct upload into QuickBooks. The column mapping is consistent across exports, so the data layout does not shift when you switch formats.