Bank Statement Won't Convert Right? How to Fix Misaligned Columns & Flipped Debits/Credits

You convert a statement and the result is a mess: columns don't line up, debits show as credits, a description spills across three rows, or a transaction is missing entirely. This is the single most common frustration with bank statement conversion — and almost all of it comes down to one root cause.

Why it goes wrong

Every bank designs its own statement layout, and generic PDF-to-Excel tools don't understand statements — they just rebuild a grid from the visual spacing of text on the page. So anything slightly unusual breaks them: an extra reference column, a description that wraps onto a second line, amounts and balances printed close together. The fix is either a converter that reads the structure of a statement, or a quick manual correction. Here are the specific problems and what to do.

Problem: misaligned or shifted columns

The classic symptom — dates in the description column, amounts spilling into reference. Generic exporters guess column boundaries from whitespace and guess wrong.

Fix: use a converter that detects the statement's actual columns rather than slicing by position. stmtify maps each value to the right column from the statement's own header, and you can drag columns into order in the review table if a field still looks off.

Problem: debits and credits flipped

Money out shows as money in, or both land in one column. This happens when a statement uses a single amount column with “Dr/Cr” markers, or lists credit before debit.

Fix: the running balance is the source of truth — each transaction must move the balance the right way. stmtify uses balance continuity to decide the side, so an unmarked amount is placed correctly. If a single row is still wrong, edit it in the table before exporting.

Problem: descriptions split across rows

Long payee names and references often wrap onto a second or third line, and weaker tools turn each line into its own broken transaction.

Fix: a statement-aware parser groups wrapped lines back into one transaction. If you spot a stray fragment, merge it into the description cell in the review table.

Problem: a transaction is missing

Rare, but it can happen on short or unusually formatted statements — a line gets skipped.

Fix: open the source-highlights view, which shows exactly which lines on your statement became transactions. Anything left un-highlighted was skipped. Add the missing entry with the + button on the row at the matching date, type in the details, and export.

The golden rule: review, then download

Whatever tool you use, never trust the export blindly. Reconcile the opening and closing balances, spot-check rows around page breaks, and confirm the debit/credit split. stmtify is built around this: it shows you what it read, lets you fix anything, and only then exports.

Convert your bank statement with stmtify — it runs entirely in your browser, so your statement is never uploaded to a server. It's free, needs no signup, and works with statements from any bank.