Whichever order your Alpha Bank statement prints its columns in, each one still has to land in the right place once it reaches a spreadsheet. The engine maps each column into the right place in the export without a manual template. Transaction date, description, debit amount, credit amount and running balance are recognised by their position and content pattern, not by hard-coded labels that vary from one statement to the next. When a statement uses a single amount column with a separate debit/credit indicator, the engine splits the values into two columns so the export always lands clean for the ledger. Every mapped field is visible in the review screen; drag a column heading to reorder it, or rename a field to match your chart of accounts before you download.
Should a description on your Alpha Bank statement break across multiple lines of the printed page, that line break is not the same thing as a new transaction. Statement documents where transaction descriptions run long and wrap across multiple lines are handled without splitting a single entry into phantom rows. The engine reads the table structure, not raw line breaks, so a description that occupies three printed lines inside one cell stays inside that one transaction. If a wrapped description pushes other cells out of alignment in the source, the balance column acts as a fence: the engine uses the running-balance sequence to confirm which lines belong together, and any row whose balance does not follow cleanly from the previous one is flagged for review rather than silently merged.