Once your Tejarat Bank statement is uploaded, what you get back depends on which export format you actually need next. The converted data can be written straight into the format your ledger or tax software expects. Excel (XLSX) and CSV exports preserve every transaction row and column exactly as they were read from the statement, so you can open the file and begin working immediately. QuickBooks (QBO) export maps the statement’s structure into the standard fields a reconciliation workflow needs: date, description, debit, credit and the running balance. No intermediate spreadsheet manipulation is required; the file lands ready for import.
Whichever order your Tejarat Bank statement prints its columns in, each one still has to land in the right place once it reaches a spreadsheet. Every column the engine identifies can be mapped to the corresponding field in your chosen export. If the statement prints a transaction reference code alongside the amount, that code stays with its row and lands in the correct QBO memo or reference field rather than being dropped or merged into the description. The mapping logic respects the source layout, so the export preserves the relationship between the raw statement data and the final ledger-ready columns.
If the running balance on your Tejarat 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. The running balance printed on the statement is never taken on trust. Each transaction row is checked arithmetically against the previous row’s balance, and the final computed figure is compared with the closing balance the bank itself published. A row whose balance does not add up is flagged for review rather than causing the whole file to be rejected, so a single misread does not block the rest of the statement from being usable.