Convert PDF Statements from PTSB to Excel

Upload a PTSB PDF statement, check the extracted transactions, and download them as Excel or CSV. The workflow handles separate debit and credit columns.

Private workspace. HTTPS upload. No credit card needed.

$9 for 25 pages, one-off, no subscription. See pricing

98% of numbers correct on 82 hand-checked pages How we measure

How to get your PTSB statement into Excel

  1. Download the PDF statement from PTSB online banking

    • Log in to Open24 Online Banking or the PTSB App (you need to be registered for eStatements).
    • In Open24, click the dropdown arrow next to the account, select View more transactions, then the Statements tab and View eStatements; in the app, select eStatements and the account.
    • Input the verification code and select View; the eStatement opens as a PDF (in the app, select the statement and click the download icon).
    • Save the statement for the period you need as a PDF.
    Go to PTSB Online Banking
  2. Upload it here

    Drop the PDF into the uploader on this page. Scanned statements and phone photos work too. The extracted rows open next to the statement so you can check them.

  3. Download Excel, CSV, or QuickBooks and Xero CSV

    Export the rows as an Excel workbook, a plain CSV file, or a CSV laid out for QuickBooks or Xero import.

What a PTSB statement looks like in Excel

One row per transaction, with separate debit, credit, and running balance columns. The rows below are made-up sample data, not a real statement.

sample-statement-2026-01.xlsx Jan 2026 · EUR
Sample bank statement rows with made-up data, amounts in EUR
Date Debit Credit Balance
2026-01-02 Salary - Example Employer Ltd 2,500.00 3,500.00
2026-01-05 Card payment - Sample Grocery Co 120.00 3,380.00
2026-01-09 Rent - Placeholder Properties 1,200.00 2,180.00
2026-01-14 Transfer from savings 300.00 2,480.00
2026-01-20 Utility bill - Demo Energy Co 80.00 2,400.00
2026-01-27 Card payment - Fictional Coffee Co 15.00 2,385.00

Supported input and export formats

  • PDF statements
  • Scanned PDF, JPG, PNG
  • Excel workbook
  • CSV rows
  • QuickBooks CSV
  • Xero CSV
  • Structured JSON

Why PTSB PDF Statements Won't Copy to Excel

PTSB keeps eStatements online for 24 months and removes access when an account closes, so older PTSB history often exists only as saved PDFs or paper duplicates. Statement PDFs list debits and credits in separate columns next to a running balance, and card and SEPA transfer details wrap onto extra lines, so copy-paste into Excel splits one transaction across rows.

As copied from the PDF

  • 10/03/2025 CARD PURCHASE LIDL GALWAY -27.90
  • 12/03/2025 CREDIT TRANSFER ACME LTD PAYROLL 2,315.00

As extracted for review

Date Description Amount
2025-03-10 CARD PURCHASE LIDL GALWAY −€27.90
2025-03-12 CREDIT TRANSFER ACME LTD PAYROLL +€2,315.00

eStatements available for 24 months

Open24 and PTSB App

Access ends when the account closes

Save PDFs before closing

Debits and credits in separate columns

Transaction table

Review rules for PTSB PDF formats

These extraction rules prepare rows for human review

Combine Debit and Credit Columns

Separate debit (paid out) and credit (paid in) columns are reviewed as one sign…

Join Wrapped Descriptions

Card and SEPA transfer descriptions that wrap onto a second line are joined int…

Read Euro Amounts as Numbers

Amounts printed with a euro sign or comma thousands separators are read as plai…

Output and review

What you can check after extracting PTSB statements

Use the output as a review workspace before importing it anywhere. The source statement stays visible while you confirm fields and download the format your accounting workflow expects.

Validation visible before export

  • Opening + transaction total is checked against closing balance
  • Duplicate, overlapping, and missing statement periods are surfaced by account
  • Saved client and bank mappings keep monthly batches consistent
  • Excel, CSV, JSON, QuickBooks CSV, and Xero CSV exports use the reviewed rows

Statement fields

  • Bank name and account identifier
  • Statement period and currency
  • Opening and closing balances

Transaction rows

  • Date and description
  • Debit, credit, amount, and balance
  • Rows that continue across pages

Review checks

  • Balance movement against transaction totals
  • Duplicate, overlapping, or missing statement periods
  • Ambiguous dates, signs, and wrapped descriptions

Export formats

  • Excel workbook
  • CSV transaction rows
  • Structured JSON
  • QuickBooks and Xero CSV layouts
Time Comparison

Replace copy-paste cleanup with a reviewable extraction

Compare manual copy-paste cleanup with structured extraction for PTSB statements

Manual Process

Copy-paste from PDF

Slow
Processing time Manual

Depends on page count, layout, and review needs

Date formats Inconsistent

Manual cleanup required

Multi-line text Breaks

Descriptions split into rows

Error rate Hard to review

Typos, misaligned columns

Source context None

No source verification

PDF2TEXT.AI

Reviewable extraction

Recommended
Processing time Assisted extraction

Extraction starts after upload and returns reviewable rows

Date formats ISO 8601

Standardized for review (YYYY-MM-DD)

Multi-line text Merged

Descriptions joined for review

Error rate Review first

Check amounts against the source statement

Source context Review view

Source statement kept nearby

Built for review, export, and repeat bookkeeping cleanup
Private Document Access

Your statements stay in your private workspace

Protected in transit with HTTPS and available only after account or workspace authorization.

HTTPS in transit

Your browser uses an encrypted HTTPS connection when uploading documents and downloading results.

Available for review

Originals and extracted results remain in your private workspace for review and export. Contact support to request deletion.

Authorized access

Uploaded originals and generated previews are checked against the owning account or workspace before delivery.

PTSB PDF to Excel: Frequently Asked Questions

Answers to common questions about bank statement PDF conversion

Why does copy-paste from PTSB PDF mess up my Excel spreadsheet?
PTSB keeps eStatements online for 24 months and removes access when an account closes, so older PTSB history often exists only as saved PDFs or paper duplicates. Statement PDFs list debits and credits in separate columns next to a running balance, and card and SEPA transfer details wrap onto extra lines, so copy-paste into Excel splits one transaction across rows.
Can I download CSV directly from PTSB instead?
Yes, for recent transactions in the PTSB App: open the account, select 'Download' above your recent transactions, and click 'Download CSV'. eStatements are PDFs, so convert those here and review the rows before importing them.
Can I import the extracted rows into QuickBooks or Xero?
Yes. Export reviewed transaction rows as Excel, CSV, structured JSON, QuickBooks-friendly CSV, or Xero-friendly CSV. Check fields against the source statement and use saved mappings to review duplicate, overlapping, or missing periods before importing recurring batches.
Does this work with scanned or photographed bank statements?
Yes. Our OCR reads both digital PDFs and scanned images. Upload a clear scan or phone photo (PDF, JPG, PNG), then review the extracted transactions before exporting.
Is it safe to upload my bank statement? What happens to my data?
Uploads use HTTPS and remain available only through your authenticated private workspace so you can review and export them. Privacy, retention, and deletion details are linked in the footer.

Convert a PTSB statement to Excel

Preview one statement free, up to five pages, review the extracted rows, then buy a page pack for this statement or choose a monthly plan when client batches repeat.

Private workspace. HTTPS upload. No credit card needed.

PDF, JPG, or PNG • Free preview • Page packs and monthly plans for continued work

Open the converter

pdf2text.ai is an independent tool and is not affiliated with, endorsed by, or sponsored by PTSB or any financial institution. All trademarks remain the property of their respective holders and are used here solely for descriptive purposes to identify file compatibility.