Common conversion problems and what to try next.

Start with the original bank download whenever possible. Converted, printed-and-scanned or edited PDFs are more likely to lose structure.

“No transaction rows were detected”

Confirm that the file is a bank or payment-account statement, is not password protected and is under 20 MB. Try downloading it again directly from the bank. If it is a scan, use a clearer, upright version with complete page edges.

Credits appear as debits—or everything has one direction

Check whether the PDF groups transactions under section headings or uses a single signed-amount column. Do not rely on the export until the running balances and reported credit/debit totals agree.

Opening or ending balance is missing

Search the PDF for aliases such as previous balance, brought forward, start balance, new balance, closing balance or balance carried forward. If the value exists but was missed, treat the conversion as incomplete and report the anonymised layout.

Descriptions or amounts are garbled

This usually indicates OCR or unusual PDF character encoding. Use the original downloadable PDF instead of a screenshot, improve scan quality, and inspect minus signs, decimal separators and visually similar characters such as 0/O and 1/I.

Browser freezes or runs out of memory

Close unnecessary tabs, use an updated desktop browser, and try a smaller PDF. OCR of many high-resolution pages can consume substantial device memory because processing happens locally.

How to report a new layout safely

Never email an unredacted statement. Remove names, addresses, account numbers, card details and reference information. Describe the bank, statement type, missing fields and expected totals at theonlineentrepreneurship@gmail.com.