Convert PTSB bank statement to OFX

Why PTSB statements are tricky

PTSB writes amounts using comma as the decimal separator and dates in DD/MM/YYYY format. Amounts are in a single signed column — negatives are debits.

StatementEdge handles all of this natively — no per-bank template to configure, no manual column mapping. Drop the PDF, get back a clean reconciled file.

How it works

1. 1Drop your PTSB statement PDF. Digital or scanned — both work.
2. 2Our vision pipeline extracts every transaction with locale-correct numbers and dates.
3. 3We balance-check the result: opening balance + sum of transactions must equal closing balance. Any row that doesn't add up is flagged for review.
4. 4Download as CSV, Excel, QuickBooks (.qbo), Quicken (.qfx), Xero or Sage.

Other formats for PTSB

• PTSB → Excel.xlsx
• PTSB → CSV.csv
• PTSB → QuickBooks.qbo
• PTSB → Xero.csv

FAQ

Does StatementEdge work with PTSB for OFX export?

Yes. StatementEdge has been tested against PTSB's Ireland statement layout. Vision-based extraction means no template configuration — drop the PDF and it works.

What's the largest PTSB statement I can convert?

Up to 25 MB per file or 100 pages, whichever comes first. Multi-month consolidated statements work fine.

Can I convert scanned PTSB statements (not just digital PDFs)?

Yes. We detect text-layer PDFs and image-only scans automatically; both routes produce the same clean output.

What happens to my PDF after conversion?

Source PDFs are auto-deleted after conversion. We retain only the extracted, normalised data tied to your account.

Will the comma decimal format break my Excel or QuickBooks import?

No. We normalise to ISO numbers internally, then format the export to whatever target software (Excel, QuickBooks, Xero, Sage) expects.

Built for trust

Auto-reconciled

Every total is balance-checked — only genuinely uncertain rows are flagged.

EU residency

Stored in the EU, encrypted in transit and at rest.

No training

Provider settings prevent your data being used to train models.