If you have ever stared at a photo of a printed price list, a scanned bank statement, or a dashboard screenshot and thought "I just need this in a spreadsheet," you know the usual options are bad. You either retype it cell by cell, or you run it through an OCR tool that hands back one long block of text, and then you spend twenty minutes splitting it into columns.

This post walks through a workflow that actually saves time, and, just as important, how to check the result so a misread number doesn't end up in a report.

1. Start with the best source you can get

OCR quality is decided before you upload anything. A few habits make a big difference:

  • Prefer the original file. If the table came from a PDF that has selectable text, use the PDF, not a screenshot of it.
  • Shoot straight on. When photographing paper, hold the phone parallel to the page and avoid shadows across the table. Skewed photos are the most common cause of columns drifting into each other.
  • Crop to the table. Headers, logos, and handwritten notes around the table can confuse table detection. Crop tightly if you can.
  • Keep the resolution. Messaging apps often compress images. Send the file to yourself as a document instead of a photo.

2. Use a tool that rebuilds the table, not just the text

Plain OCR answers "what characters are on this page?" What you need is "which characters belong to which row and column?" That second step, table structure detection, is what turns a picture into something you can sort and filter.

Tools built for this, such as ImageToExcel, detect the grid, keep rows and columns together, and export straight to an .xlsx file. They usually accept JPG, PNG, WEBP and PDF input, including multi-page scans, so the same flow works for a phone photo and a 12-page statement.

3. Review before you export

Never trust OCR output blindly, especially with financial data. A quick review routine:

  1. Check the totals. If the source has a total row, add the extracted column yourself with =SUM() and compare. A mismatch tells you immediately that something was misread.
  2. Look for classic swaps. 0 and O, 1 and l, 5 and S, and , versus . as decimal separators are the usual suspects.
  3. Count the rows. Compare the row count against the source. Merged or dropped rows are easier to spot by count than by eye.
  4. Watch merged cells. Headers that span several columns in the original often get flattened. Fix those by hand before you build formulas on top of them.

4. Clean up in Excel

Once the data is in a sheet, a few built-in features finish the job:

  • Text to Columns (Data tab) to split anything that landed in one cell.
  • TRIM and CLEAN to remove stray spaces and non-printing characters that break lookups.
  • Format as Table (Ctrl+T) so filters and structured references work right away.
  • VALUE() to turn numbers that were read as text back into numbers.

5. Specific cases worth knowing

  • Bank statements and credit card statements: dates and amounts matter most. Sort by date after export to catch rows that were read out of order.
  • Invoices and receipts: you usually only need a handful of fields (date, vendor, line items, total). Extract those into a consistent layout so you can stack many documents into one sheet.
  • Screenshots of web dashboards: these are usually clean, but check that negative numbers kept their minus sign or parentheses.

Wrapping up

Getting a table from an image into Excel is a two-part job: good extraction, then a fast, deliberate check. Spend thirty seconds on the source, let a table-aware converter do the heavy lifting, and always reconcile at least one total before you rely on the numbers.