When a Banca Comercială Română 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 runs several pages long, the engine stitches them into one continuous table automatically. It reads each page in order and aligns the transaction columns from one leaf to the next without dropping the running balance. Headers and repeated bank boilerplate are stripped so the conversion output gives you a single, uninterrupted ledger. If a closing balance is printed only on the final page, the engine picks that figure up and uses it for the full-file verification; an intermediate subtotal or carry-forward figure that appears page by page is not confused with the statement’s own final number.
Should a description on your Banca Comercială Română statement break across multiple lines of the printed page, that line break is not the same thing as a new transaction. Long transaction descriptions that wrap across multiple lines are flattened into a single row in the output. The engine identifies where a description cell breaks and wraps, then joins those fragments together so the narrative stays whole in your exported file. No stray line breaks bleed into the next column, and the amount and date cells stay locked to the same transaction row. Because the engine works from the underlying text positions rather than visual borders, even a two-line or three-line description is rebuilt cleanly into one cell.
Whichever order your Banca Comercială Română statement prints its columns in, each one still has to land in the right place once it reaches a spreadsheet. Mapping each column into the right place in the export is automatic. The engine recognises the standard fields, date, description, debit amount, credit amount, and balance, and places them in the columns an accounting workflow expects. If your ledger template uses a different order, you can reorder the columns once the file is open in your spreadsheet application. The export keeps the same column layout whether you send the output to Excel, CSV or QBO, so the mapping stays consistent across every format you use.