Once your ING Türkiye statement is uploaded, what you get back depends on which export format you actually need next. When the statement table is extracted, you choose the exact format the next step requires. Select Excel for a single‑sheet workbook with every column mapped to its own field, or CSV when you need a lightweight file that any ledger or data tool can read. QuickBooks Online is supported directly: the export maps dates, descriptions, amounts and running‑balance data into the fields QBO expects, so the journal imports without hand‑editing column headers or reordering rows. The mapping is automatic, but you can review and re‑map a column before export if your firm’s chart of accounts uses a different label. No row is dropped, no decimal place is rounded because of a format mismatch, and the same extracted data can be exported in multiple formats from a single conversion session, so you can keep a CSV archive alongside the Excel working file or send QBO the ledger data it needs while leaving the full transaction detail in a spreadsheet.
Whatever the running balance looks like on your ING Türkiye statement, Convert·Into checks it against the statement's own printed closing figure before you export anything. Every statement processed by Convert·Into passes through a running‑balance verification. The software reads the printed closing figure that appears on the last page of the statement document, then steps through every recorded transaction line, adding credits and subtracting debits in chronological order. If the running total at any line does not match the value printed beside it on the statement, that row is flagged. The file is not rejected: every other transaction that adds up remains usable, and you get a clear marker on the specific row where the figures diverge. The check catches scanner misreads, OCR errors that turn a 3 into an 8, and statement‑generation quirks that pad or truncate a cent value.
Should a description on your ING Türkiye statement break across multiple lines of the printed page, that line break is not the same thing as a new transaction. Transaction descriptions that run long and wrap across two or three printed lines are a common cause of extraction errors in manual copy‑and‑paste workflows. Convert·Into reads the full statement layout and groups wrapped lines back into a single description field, so a merchant name, reference number and terminal location that span multiple printed rows stay together as one complete record. The grouping relies on the column structure rather than guesswork, so a blank‑line separator or a carried‑forward balance row does not get merged into the description by mistake.