If the running balance on your BDL 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 engine compares the running balance on the converted statement line by line with the closing figure printed on the original document. A single digit misread during extraction is enough to cause a mismatch, and that mismatch is caught immediately: rows that do not add up are flagged for review. The rest of the file stays intact rather than being rejected wholesale, so you can correct one anomaly and move on, while every verified row is already safe to export.
When a BDL 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. Longer statements that span multiple pages are handled as a single continuous document rather than a batch of disconnected images. The engine follows the statement’s own pagination, carrying the running balance forward from one page to the next and verifying it at each break. This means a quarterly or annual statement that runs to several pages comes out as one contiguous table, with no duplicate headers, no dropped rows and no manual stitching required later.
Once your BDL statement is uploaded, what you get back depends on which export format you actually need next. After the converted table is verified, map the columns into the layout your downstream system expects and export to Excel, CSV or QBO. The mapping step adjusts column order and selects the fields you need; stripping columns you do not want during export is cleaner than deleting them later. The result is a file shaped to your reconciliation routine rather than a generic dump, ready to import without additional reformatting.