If a transaction description on your Bank Gospodarstwa Krajowego statement is long enough to wrap across two or three lines, it still needs to land in a single row once converted. When a transaction description runs long, it often breaks across several lines in the statement document. A simple line-by-line parser treats each wrapped line as a separate row: the date grabs the narrative text instead of the debit column, and the table fractures. Convert·Into recognises wrapped descriptions and reconstructs the row they belong to, so the transaction stays whole with every field in its right column.
If your Bank Gospodarstwa Krajowego statement runs to several pages, uploading it starts the same layout detection Convert·Into applies to any statement document, page by page. Statements that run for several pages sometimes split the transaction table mid-sequence, repeating headers, carrying forward subtotals, or inserting page-break artefacts that look like data rows. The engine follows the table across page boundaries without mistaking the header reprint for a fresh transaction or bringing the artefacts into the export. Column positions stay aligned from the first page to the last, so the full statement arrives as a single continuous table instead of a stack of disjointed fragments.
Whatever the running balance looks like on your Bank Gospodarstwa Krajowego statement, Convert·Into checks it against the statement's own printed closing figure before you export anything. Every row the engine extracts is tested against the closing balance printed on the statement itself. The running balance is calculated line by line from the opening figure; once the final transaction is accounted for, the computed balance must match the statement's own declared closing figure exactly. When the two figures agree, the file is ready to export. If any row does not add up, whether from a digit misread in a numeric field or a date that landed in the wrong column, that row is flagged for review. The rest of the file stays intact: no blanket rejection, no starting over. Once you have confirmed or corrected the flagged line, the export to Excel, CSV or QBO proceeds with every column mapped into the format your ledger expects.