If the running balance on your China Merchants 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. Upload a statement document; the engine identifies the layout automatically so there is no template to set up. The running balance printed on the statement is the source of truth, and the engine checks every row against it. If a figure floats, you see a flag on that line rather than a silent error carried into the export. The closing balance comes straight from the statement’s own printed total: it is not recalculated from the extracted rows alone. That means a mismatch on any intervening line stops before it reaches the general ledger.
If a transaction description on your China Merchants Bank statement is long enough to wrap across two or three lines, it still needs to land in a single row once converted. Statements where transaction descriptions run long and wrap across multiple lines are handled without losing the detail or mangling the columns. The engine groups each transaction’s text together, even when it spans two or three physical rows on the page, so a full narrative stays in one cell rather than scattering into adjacent entries. The extracted table stays clean, with amounts kept in their correct columns alongside the complete description.
Once your China Merchants Bank statement is uploaded, what you get back depends on which export format you actually need next. Choose Excel, CSV or QBO on export and the engine maps the columns into the format you requested. Dates, amounts and transaction text are placed in the standard order with consistent delimiters, so the file drops into a spreadsheet or accounting package without reformatting. If the workflow calls for a different structure next month, pick a different target on the way out; the conversion logic adjusts without reprocessing the statement itself.