Bank statement PDF to Excel — reconciled against your receipts, not just converted.
Converters give you rows. The period needs more: statements and receipts in one workbook, transactions matched to their documents, double-entry rows ready to post. Pileform processes the statement inside the same drop as the rest of the pile.
The transactions are locked in a PDF the bank exported. A generic converter turns them into a raw table — and then the real work starts: matching each payment to its receipt, classifying each line, building the double entry by hand. The conversion was never the hard part.
Pileform reads the statement in the same pass as the receipts and invoices, so transactions come out matched, classified, and post-ready — not as another spreadsheet to reconcile.
Statements in the same drop as the receipts.
Add the statement PDFs to the period's pile — one drop, everything together. Transactions come out as double-entry rows, reconciled against the extracted receipts and invoices, in the same per-supplier workbook structure.
Reconciliation, not just rows.
Statement lines are matched against the period's extracted receipts and invoices. A supplier payment links to the supplier's invoices; what cannot be matched with confidence is flagged for review rather than guessed.
14/03 · ALPHAMEGA · −€214.60 matched to the Alphamega tab's March receipts, with the unmatched remainder flagged.Double-entry output.
Bank transactions come out as proper double-entry rows — not a one-column cash list. Confirmed entries post to Xero and QuickBooks as double-entry bank transactions, with the Excel always exportable.
Cyprus and international formats.
Statement layouts from Cyprus banks — including Greek-language layouts — and international banks flow through the same extraction. Scanned statements and digital PDFs both work; hard pages are retried automatically.
Multi-currency statements.
A EUR account, a GBP account, and a USD card statement in the same period keep their currencies. Nothing is silently converted; rounding gaps surface in explicit adjustment cells.
Part of the period, not a separate tool.
No second product, no separate export. Statements ride along in the period drop — a typical 200-page batch processes in about 12 minutes, statements included.
See statement rows matched to suppliers.
The sample workbook on the features page shows bank transactions sitting next to the supplier entries they were matched against.
Bank statement questions, answered.
Statement PDFs from Cyprus banks — including Greek-language layouts — and international banks flow through the same extraction engine. Both digitally-generated and scanned statement PDFs are supported; pages that are hard to read are retried automatically and anything uncertain is flagged for review rather than guessed.
No — that is the difference. The statement is processed inside the same period drop as the receipts and invoices, so transactions come out matched against their documents, classified, and as double-entry rows ready to post. A converter gives you a table; this gives you the period reconciled.
Both. Digitally-exported statement PDFs read cleanly; scanned or photographed statements go through the same pipeline with automatic retries on hard pages. Rows the engine is not confident about come back yellow-flagged so review time goes only where it is needed.
Currencies stay as the statement shows them — a GBP account stays GBP, a USD card stays USD. Nothing is silently converted to EUR, and any rounding gap is surfaced in an explicit adjustment cell so the workbook always reconciles to the statement balance.
Bank transactions appear as double-entry rows within the same workbook structure as the rest of the period — matched to supplier tabs where a match exists, flagged where it does not. Confirmed entries post to Xero or QuickBooks as bank transactions; the Excel and CSV exports are always yours.
Drop the statements with the receipts.
Sign up free, no card. Run a real period — statements included — and see the reconciliation before you commit to anything.