Whichever order your SouthState Bank statement prints its columns in, each one still has to land in the right place once it reaches a spreadsheet. Mapping each column into the right place in the export is handled field by field. The engine identifies which column holds the date, which holds the transaction description, which carries the debit, credit and running balance. It then places each into the corresponding column of the chosen export format. If the source layout puts the credit amount in a column that another bank uses for debits, the mapping follows the actual data, not a rigid template. The result is an export where a debit lands in the debit column, a credit in the credit column, and the running balance continues in sequence, ready for import without re-sorting.
Should a description on your SouthState Bank statement break across multiple lines of the printed page, that line break is not the same thing as a new transaction. Some statement documents show transaction descriptions that run long and wrap across multiple lines. The engine does not treat each wrapped line as a separate row. It recognises the continuation and groups the lines back into a single transaction record. The export preserves the full description in one cell, so a note that stretched over three lines on the statement page stays whole in the spreadsheet. A second transaction beginning on the next clean line starts a new row without pulling in the preceding wrap.