Honest answers to obvious questions.
Pileform extracts handwritten receipts with lower confidence. The row is yellow-flagged for review before posting. Validating a flagged row takes seconds, instead of typing the receipt from scratch.
We infer it based on the supplier, the line items, and the regime. Then we yellow-flag the row so you can confirm before posting.
We never silently guess. The Adjustment column always reconciles.
Yes. UK VAT, EU VAT, GST, and zero-rated regimes are all supported. The Cyprus defaults are tuned for Cyprus practitioners; the engine handles any regime the receipt declares.
Yes. Connect Xero or QuickBooks and the entries you confirm post straight through — supplier invoices as Bills in Xero, journal entries in QuickBooks. Your chart of accounts syncs in, and bank-statement transactions post as double-entry too. You still get the Excel workbook, and you’re never locked in. Sage isn’t supported yet — tell us at contact@pileform.com.
Servers in Frankfurt (EU). Records are retained for the period you configure in Settings → Data & exports (default 10 years; range 6–30 years with country presets — Cyprus / UK / Ireland / Malta / Spain / Greece 6 years, Netherlands 7, Germany / France / Italy / Lebanon 10) to satisfy the strictest applicable tax-record statute. You can request earlier deletion of any individual job. GDPR-compliant. AI inference happens via Anthropic’s Claude API (US; contractually prohibited from training on your content). The rest of the stack (Cloudflare, Google Cloud) is EU-only. Full sub-processor list in our Data Processing Agreement.
Accuracy depends on the source PDF. Clean printed receipts extract reliably. Smudged thermal prints and handwritten receipts are harder. Pileform doesn’t quote a single accuracy figure because the answer depends on what the client provided.
The workbook returns rows in two states: high-confidence rows ready to post, and yellow-flagged rows for human review. The accountant’s time goes to the second category, not to every line.