Bank App Screenshot to Excel: Transactions from a Phone

To move a bank app screenshot to Excel, capture the transaction list in screens that overlap by a few rows, read each image into a table with a picture-to-table tool, then stack the tables and remove the rows that appear twice. It works for a short list. For a full month, download the statement PDF instead.

What does a bank app screenshot hold for Excel?

A bank app screenshot holds only what the screen shows: usually a date heading, a short merchant name, an amount and sometimes a category icon. It rarely shows a running balance on each line, the full description the bank records, or reference numbers. That is less than a statement carries, and the gaps matter later.

Compare what you typically see on a phone with what a statement prints:

Apps differ, so treat this as a guide to check against your own screen, not a rule. The point is to know what you will not get. Without a balance on each line, you cannot prove that no transaction was missed between two screenshots. Without full dates, every "Yesterday" has to be turned into a real date by hand.

Some app screens also show pictures of deposited or paid checks. Those images are not table data at all, and what happens to check images during conversion explains why converters skip them.

Capturing a long transaction list in overlapping bank app screenshots

To capture a list longer than one screen, scroll so that the last two or three transactions of one screenshot appear again at the top of the next. That overlap is your proof that nothing fell between captures. Without it, a transaction hidden by a sticky header or a fast scroll can vanish with no trace.

A capture routine that holds up:

1. Set the date range first, if the app lets you filter, so you only capture the period you need.
2. Hide balances or masks you do not need only if the app offers it. Do not crop rows out.
3. Take the first screenshot with the top of the list visible, including its date heading.
4. Scroll up slowly until the last two or three rows of that screen sit near the top, then capture again.
5. Repeat to the end of the period, keeping the overlap every time.
6. Name or number the images in capture order before you move them off the phone.

Some phones offer a scrolling or long screenshot that captures a whole list in one tall image. It saves stitching, but check the result. Very tall images can be scaled down by the reader tool, which shrinks the type. Apps with lists that load more rows as you scroll can also leave gaps in a long capture.

Turn the phone's text size to normal or slightly larger before capturing, and use a light theme if the app has one. Dark text on a light background tends to read more reliably than the reverse.

Reading bank app screenshots into spreadsheet rows

A picture-to-table reader turns each screenshot into rows. Excel's own Data from Picture feature works on the phone apps and on Windows, Mac and the web, and Microsoft's page says to crop the image so it shows only the data you want. You review flagged cells, correct them and insert the result.

Before reading, crop each screenshot to the list itself. Status bars, the app's search box, tab bars and promotional banners otherwise come through as rows of noise. Keep the date headings inside the crop, since they carry the dates for the rows below them.

Expect the reader to treat a phone layout loosely. Bank apps often put the merchant name on the left and the amount on the right on one line, with a smaller grey line underneath for a category or time. That second line can become its own row. Delete those rows, or keep them in a separate column if the category is useful to you.

After each screenshot is read, paste its rows into one sheet below the previous capture, and add a column with the screenshot number. That number is what lets you find the overlap later.

How do you stitch bank app screenshots without duplicate transactions?

Stitch screenshots by removing only the rows in the overlap between one capture and the next. Build a key from date, description and amount for each row, then flag a row in a later capture when the same key appears in the last few rows of the capture before it. Delete those and check the seam by eye.

The reason to look only at the seam is that real transactions repeat. Two coffees of 3.40 at the same café on the same day are two genuine debits. Removing every duplicate in the sheet would delete one of them.

A worked example

The captures below are an example from a made-up account, newest first as many apps list them. Capture 1 ends with three rows that capture 2 repeats at its top.

With the captures in columns A to D starting on row 2, build the key in E2 and fill down:

=TEXT(B2,"yyyy-mm-dd")&"|"&C2&"|"&D2

Then flag overlap rows in F. For a row in capture 2, the formula counts how often its key appears in the last three rows of capture 1, here rows 4 to 6:

=IF(A2=2, COUNTIFS($E$4:$E$6, E2) > 0, FALSE)

Rows 7, 8 and 9 come back TRUE. They are the overlap, so delete them. The two café rows in capture 1 are untouched, because the check never compares capture 1 with itself. The stitched list has six rows, including both coffees and the Book Shop row that only capture 2 held.

On a longer job, adjust the range to the tail of each previous capture in turn. If the app shows a balance at the top of the list on two dates, compare the change in balance with the sum of the stitched rows between them. A match is the closest thing to proof a screenshot job can give.

Pending items, date headers and icons in bank app captures

Bank app screens carry pieces that no statement has. Pending transactions, group headings such as "Today", category icons and running monthly totals all show up in captures, and each needs a decision. Most should be removed or turned into proper columns before the data is used.

How to handle each:

• Pending items. These may later post with a different amount, such as a fuel pre-authorization, or drop off. Delete them, or capture again once they have posted.
• Relative dates. Replace "Today" and "Yesterday" with the real date, based on the day you took the screenshot. Do this before you lose track of when that was.
• Date headings as rows. When a date appears once above its transactions, fill it down into a date column, then delete the heading rows.
• Icons and logos. Usually ignored by the reader, but sometimes read as a stray letter. Check the first character of each description.
• Monthly summaries. Lines such as "Spent this month" are not transactions. Delete them.
• Amount colour. Some apps show credits in green with no plus sign. The reader cannot see colour, so check the sign of every incoming amount.

Why is a PDF statement still better than a bank app screenshot?

A statement PDF is better because it is complete, checkable and already text. It covers the whole period with an opening and closing balance, uses full dates and descriptions, and in most cases the characters are stored in the file, so nothing has to be recognized from a picture. Screenshots are a workaround for when the statement is not available.

Choose screenshots only when:

• you need a few recent transactions that have not reached a statement yet
• the app is the only access you have, such as a shared account where you cannot download statements
• the list is short enough to check by eye

For anything longer, look for the statement download in the app or on the bank's website. Many banks also show transaction history as a web page you can copy, which converting an HTML bank statement to Excel covers. If someone has already saved your screenshots as an image-only PDF, making a scanned PDF searchable adds a text layer, and converting a scanned PDF to Excel takes it the rest of the way.

FastBankConvert works from the statement PDF rather than screenshots, and it is built to tell you before download when the balances do not add up, the check that screenshots cannot give you. It is getting ready to open, and you can join from the home page.