Diagnose the file without weakening its security or changing its evidence. Confirm the real file type, open it locally, preserve the original, and create only a purpose-specific working copy when needed.
This illustration uses imaginary information. Check actual statement details directly against the source.
Identify the failure before changing the file
Record the service, exact error message, browser or device, file name, reported size, page count, and whether the failure occurs during selection, transfer, validation, or processing. An unsupported file, network interruption, password prompt, and unreadable scan require different remedies. Repeating random conversions can create extra sensitive copies without solving the cause.
Handle password protection and permissions safely
A bank statement can require a password to open or can restrict copying and extraction. Use the bank's documented password convention or obtain an unlocked download through the official account channel. Never send the password in the same message as the statement, and do not upload it to an unknown unlocking service.
Repair source and page quality problems
Download the statement again from the institution if the file is incomplete, zero bytes, corrupted, or missing pages. Prefer the bank-generated PDF over a print-to-PDF copy because printing can flatten text, crop page edges, alter scaling, or omit interactive content. Compare page count, period, and file properties after any conversion.
Safe upload troubleshooting sequence
Move from diagnosis to the least invasive correction while preserving the institution-issued original.
Verify locally
Confirm true file type, size, page count, openability, statement period, and that each page renders before changing anything.
Check protection
Determine whether a password, extraction restriction, or account-download rule is blocking processing. Use only authorized and trusted methods.
Create one working copy
If needed, make a clearly labeled purpose-specific copy, then verify page order, legibility, amounts, and completeness against the original.
Retest and close
Change one upload condition at a time, document the successful configuration, and remove temporary sensitive copies after confirmed use.
Test the upload with controlled changes
Try a current supported browser, stable network, permitted file size, and a sanitized filename without unusual control characters. Change one factor at a time and record the result. If the service publishes accepted formats or limits, use those requirements instead of guessing.
When the PDF has no usable text layer, try the image-based bank statement reader and verify every uncertain row against the source image.
A transaction expected in one statement can post in another period, remain pending, appear under a different description, belong to another account, reverse, or never complete. Test those possibilities before treating the statement as incomplete.
Text volume does not establish OCR quality. Acceptance depends on proving that the reconstructed ledger retains the source rows, column positions, signs, and balance logic.
Name the two balances, align their cutoff, and build a transaction bridge. Most mismatches stay confusing because a closed statement, live account, bookkeeping ledger, or extracted spreadsheet is compared without a shared time boundary.
Apply this guide to a statement
Review a traceable ledger that separates extracted facts, calculated totals, suggested categories, recurring candidates, and unresolved data concerns.
