A PDF-to-spreadsheet conversion is useful only when the resulting rows remain traceable to the source. Here is a small review checklist for a monthly transaction table.

Start with structure. Keep the original PDF unchanged and separate opening balances, closing balances and statement summaries from actual transaction rows. A page total should not silently become an extra payment in the output.

Check dates and number formats. Confirm whether the statement uses day/month or month/day ordering. Watch for decimal commas, thousands separators and dates with a missing year. Keep a note of the interpretation rather than relying on the spreadsheet application’s automatic guesses.

Review direction and signs. Some statements have separate debit and credit columns; others use a signed amount. Inspect both an incoming and an outgoing example. Do not assume that brackets, a trailing minus or a CR marker mean the same thing across every source document.

Read wrapped descriptions. A merchant reference may continue on the next line or page. Make sure that those fragments stay with their transaction rather than shifting dates and amounts onto neighbouring rows. Similar descriptions are not automatically duplicates.

Reconcile deliberately. Compare row counts and, where the statement supplies compatible balances, opening balance plus the signed transactions against closing balance. A mismatch is a reason to inspect exceptions, not to invent a balancing row. Retain unusual rows in a review list until they have been checked against the PDF.

For the conversion stage, one browser-based resource is: https://bank-statement-converter.online/

Use a redacted or non-sensitive sample when exploring a workflow, read the tool’s current privacy information before uploading a financial document, and review output before any downstream import. This checklist is about data quality and auditability, not financial advice or a guarantee that any automated extraction is error-free.

#DataQuality #Spreadsheets #PDF