Whichever order your National Bank of Greece statement prints its columns in, each one still has to land in the right place once it reaches a spreadsheet. Before you export, you choose where each column of the extracted table should land. The engine maps the statement's own columns to standard fields automatically. Transaction date, description, debit, credit and balance are matched to the output headers your system expects. You can reorder or rename any column in a single pass before the file is written. The mapping stays consistent across every statement from the same layout, so you set it once and it applies to the next upload without any extra step.
If the running balance on your National Bank of Greece 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. Every converted file is checked against the statement's own printed closing figure. The engine reads the closing balance as it appears on the document and then verifies the running balance line by line. Each row must add up to the next; any discrepancy stops the process and flags the row that broke the chain. A mismatch does not mean the whole file is rejected. You review one flagged row, correct the misread digit or shifted column, and the rest of the transaction set remains intact.
If a transaction description on your National Bank of Greece statement is long enough to wrap across two or three lines, it still needs to land in a single row once converted. Some statement documents print transaction descriptions that are long enough to wrap onto a second or third line. The engine reads these multi-line descriptions as a single record instead of splitting them into phantom transactions. It recognises the pattern of a continued memo field and stitches the lines together before the balance column is parsed. The verification step still checks every row, so a wrapped description cannot hide a missing amount or a transposed figure in the same transaction.