The bank statement PDF, as a file

Everyone knows what a bank statement is. Fewer people think about the PDF itself: why that format, what is inside the file besides the visible page, and why the copy in your downloads folder behaves differently from the one your bank emailed you.

That is what this is about. Not what a statement says, but what the file is.

Why banks chose PDF and stayed with it

A statement has to look identical on every machine that opens it, and it has to be awkward to change. PDF was built for exactly that: it is a page description, fonts and coordinates and all, rather than a document that reflows to fit a window.

There is a legal edge to it too. When a statement is evidence, in a mortgage application or a dispute, both sides need to be looking at the same page. A format that renders differently depending on the reader would be useless for that.

The cost of those properties is the one everybody runs into: a PDF is laid out for a page and not for a spreadsheet. The columns you can see are not columns inside the file. They are text at coordinates that happen to line up, which is why getting the transactions out is a real piece of work rather than a copy and paste.

What is inside the file

Open the document properties in any reader and you get a second layer of information most people never look at.

Property	What it tells you
Producer	The software that wrote the file, usually the bank’s report engine
Creator	The application the content came from
Created	When the file was generated, which is not the statement period
Modified	When it was last saved, which on an untouched download equals Created
Encryption	Whether it is password protected, and at what strength
Fonts	Embedded, so the page renders identically everywhere

The Producer field is the interesting one. A statement downloaded from a bank names a report generator. A statement that has been opened and saved in a PDF editor names the editor, and that is the first thing anyone verifying a statement looks at.

Below the properties sits the text layer: the actual characters, with their positions on the page. It is the reason a downloaded statement can be searched and selected while a scanned one cannot, and the difference decides whether OCR is needed or is a step backwards.

The password on the emailed ones

Banks that email statements often encrypt them, because email is not a private channel. The password is nearly always something you already know rather than something you were sent:

• Date of birth in a stated format, often DDMMYYYY
• Postcode or zip, sometimes without spaces
• The last four or six digits of the account or card number
• Customer number
• A combination, such as the first four letters of your surname plus your birth year

The covering email states which. If it does not, the bank’s help pages do, and calling to ask is faster than guessing, because several attempts can lock the file.

Once open, you can save an unlocked copy from most readers, which is worth doing before you need the file in a hurry. Do not send the unlocked copy by email; the encryption existed for a reason.

How long the download stays available

This is the part that catches people out, because the window is shorter than most assume and it varies by bank rather than by law.

Availability online	Typical
12 to 18 months	Several digital-first and smaller banks
2 years	Common across large retail banks
7 years	Generous, and usually a business account feature
Archived on request	Beyond the online window, often for a fee, taking days to weeks

Two practical consequences. If you close an account, download everything first: access usually goes with the account, sometimes immediately. And if you are likely to need a year of statements for a mortgage in six months, pull them now rather than later, because the oldest month drops off the end while you wait. The route for statements that have already fallen off is in the piece on old statements.

Statement PDFs by bank

The content is standardised. The file is not, and the differences are what makes automated conversion fiddly:

• Chase produces a text-layer PDF with a running balance, dates as MM/DD, and a summary box on page one.
• Bank of America splits deposits and withdrawals into separate sections rather than separate columns, so the sign has to come from the section heading.
• Capital One writes card statements with the transaction date and posting date side by side.
• Navy Federal and several credit unions produce statements that are noticeably closer to a printed layout, with more whitespace and fewer machine-readable cues.
• Wells Fargo carries a separate check images section that has no place in a spreadsheet at all.

There are notes for each of the ten largest issuers on the bank pages, including where each puts its running balance.

Turning the file into something you can use

If you need the transactions rather than the pages, the PDF is the starting point and not the destination. The converter here reads the file in your browser, rebuilds the columns, and walks the running balance to prove nothing was dropped. Nothing is uploaded, which for a document carrying your account number and a year of payees is the part worth caring about.

Whatever route you take, keep the original PDF. It is the copy with the bank’s own metadata in it, and if anyone ever needs to check that the statement is genuine, that copy is the one that can answer.