If a transaction description on your Iranian-European Bank statement is long enough to wrap across two or three lines, it still needs to land in a single row once converted. Transaction descriptions sometimes run long on a single line, but they can also wrap across two, three or more rows inside the statement. When that happens, a simple line-by-line extraction routine often treats each wrapped line as a separate, new transaction, splitting one real entry into several phantom ones. The engine identifies the boundaries of each transaction row group, not just each printed line, so a multi-line description stays with its date, amount and reference. The result is one row per transaction in the output, matching what the statement originally recorded.
Once your Iranian-European Bank statement is uploaded, what you get back depends on which export format you actually need next. The file lands in the exact format the next step needs. Choose Excel, CSV or QBO from the export menu; the engine writes the columns with the correct headers and data types for that format. There is no intermediate cleaning pass to perform by hand. A CSV export opens cleanly in any spreadsheet application, with amounts in a single, sortable column rather than split across currency symbols or trailing codes. The QBO export maps directly into the QuickBooks fields a bookkeeper would fill if entering the statement manually, saving the time of retyping every line.
Whichever order your Iranian-European Bank statement prints its columns in, each one still has to land in the right place once it reaches a spreadsheet. Every column in the extracted table lands where it belongs in the chosen export. The mapping step assigns the statement's original columns, date, description, debit, credit and balance, to the corresponding export fields. If the statement includes a column you do not need, leave it unmapped; it is stripped from the final file. The running balance column, verified line by line earlier in the process, can go straight into the export as the native balance field or be omitted if the downstream system calculates its own. Review the mapping once, confirm it, and the export is ready.