FICTIONAL SAMPLE · PRODUCT EDUCATION

Bank Statement to Excel Example

This is a fictional sample used to demonstrate the conversion and review workflow. It is not a customer bank statement. The supported sample produces three transaction rows in an Excel Transactions worksheet, ending at a balance of 2,295.50. Below are the expected fields and the checks to make before using an exported workbook.

Try the converter with your own supported statement ↗
Supported files and output

Accepted files: PDF, PNG and JPG. Maximum file size: 10 MB. PDF page limit: 5 pages. Output fields: Date, Description, Debit, Credit and Balance. Exports: Excel/XLSX and CSV. Statement processing: browser-side, for supported clear English transaction tables.

What does the sample input look like?

The fictional digital PDF sample contains a dated English transaction table with separate debit, credit and balance columns. Its opening balance is 1,000.00. The descriptions are deliberately marked SYNTHETIC, so they cannot be mistaken for a customer's financial activity.

This example uses the digital PDF sample specifically. Other sample files may use a different presentation; do not assume that identical-looking demonstration files have the same dates. Keep the exact input beside the output while reviewing. For a scan or photo, the scan-to-Excel workflow also explains image preparation and recognition limits.

Which transaction fields are extracted?

The following three rows match the sample's expected data and its previously verified CSV download. They show the same five fields used in Excel. A dash below represents a blank cell, not a zero amount.

Fictional sample output — three transactions
DateDescriptionDebitCreditBalance
2026-09-01SYNTHETIC Salary—2500.003500.00
2026-09-02SYNTHETIC Rent1200.00—2300.00
2026-09-03SYNTHETIC Coffee4.50—2295.50

The arithmetic follows the row sequence: 1,000.00 plus the 2,500.00 credit gives 3,500.00. Subtracting the 1,200.00 debit gives 2,300.00; subtracting 4.50 gives the final 2,295.50. These are fictional amounts used for a known check.

What does the Excel file contain?

The XLSX download contains a worksheet named Transactions, with Date, Description, Debit, Credit and Balance columns. Amounts are numeric cells displayed to two decimal places, while dates are exported as text. Empty debit or credit fields remain blank. The worksheet does not reproduce the original PDF's page design or turn account-summary labels into transactions.

You can open the workbook to inspect the cells and add your own checks in a separate working copy. Use the PDF-to-Excel guide for the complete workflow. The same reviewed rows can also be saved through the CSV export; CSV does not retain workbook formatting.

How should this workbook be checked?

  1. Confirm there are exactly three transaction rows, excluding the header and any opening-balance label.
  2. Compare the first and last rows with this exact PDF, then check the middle row. Look for omissions or duplicates.
  3. Match all dates and descriptions. Confirm that 2,500.00 is Credit, while 1,200.00 and 4.50 are Debit.
  4. Check decimals and every running balance, including the final 2,295.50. A matching final value alone is not enough.
  5. Keep the unedited export and source together before sorting rows or importing a working copy elsewhere.

Check totals without hiding errors

For this sample, 1000.00 + 2500.00 − 1204.50 = 2295.50. Compare that result with the PDF closing balance and all three source rows. Confirm that Salary increases the balance and Rent decreases it; swapping debit and credit changes the direction. In Excel, use =ISNUMBER(C3) to check that the Rent debit is numeric. A Currency format alone does not turn text into a number.

Equal missing debit and credit amounts could leave an ending balance unchanged. A balance match therefore cannot replace a source-row check or comparison with independent books. For copyable formulas and the separate ledger-matching steps, follow how to reconcile bank statement transactions in Excel.

What does this example prove, and what does it not?

It provides a known input and expected output for one supported synthetic table. It helps you recognize the five-column structure and perform a row-by-row review. It is not a customer case study, an accuracy percentage or a promise that another statement will convert successfully.

Real files can have different layouts, unclear text or ambiguous columns. OCR errors are possible, and unsupported tables can fail. Review your own output against its source, even if the sample works. The PDF transaction extraction walkthrough explains completeness checks; the OCR page covers scan recognition.

Try the converter with your own supported statement ↗