Integrations
Post where you keep your books. Keep the file regardless.
Pileform turns the pile into a clean workbook, then posts the entries you confirm into Xero, QuickBooks, BTMS, or Esoft. Use something else? Export CSV. Building your own workflow? Webhooks and the API are there. Either way, the Excel is always yours.
Workbook
One Excel per supplier, proof embedded
Your review
Nothing posts until someone confirms it
Ledger
Xero · QuickBooks · CSV import
Works with the ledgers you already keep
Start here
Which one are you?
Pick the ledger you already keep your books in. We point you to exactly how Pileform fits.
Compare the routes
Three ways out, one source of truth.
Every route starts from the same reviewed workbook. What differs is where the confirmed entries land.
The Excel workbook, with each source document embedded as proof, comes with every route, including the two that post automatically. Posting is a convenience on top, never the only way to get your data out.
Xero
Supplier invoices post as Bills, plus manual journals and double-entry bank transactions. Your chart of accounts syncs in.
QuickBooks Online
Confirmed entries post as journal entries, with bank-statement transactions as double-entry. Your accounts sync in.
BTMS
Confirmed entries post to BTMS as coded journal entries (bank, purchase, and sales codes), with bank-statement transactions as double-entry. Your account codes map across.
CSV export
Not on Xero, QuickBooks, BTMS, or Esoft? Export a clean CSV you can import into any other ledger, alongside the Excel workbook.
EsoftExcel export
Confirmed supplier documents export as an Excel file formatted for Esoft's import (transactions plus accounts), ready to bring in through Esoft's standard import.
Webhooks & API
A webhook fires when a batch is ready, and API access lets you wire Pileform into your own workflow.
No lock-in
The Excel workbook, with receipts embedded as proof, is always yours. Disconnect any integration any time and keep every file.
Honest answers
Integrations & export.
Xero, QuickBooks Online, QuickBooks Desktop, and BTMS today, plus a ready-to-import Excel file for Esoft. Confirmed entries post as Bills and manual journals in Xero, journal entries in QuickBooks Online, qbXML entries queued for QuickBooks Desktop's Web Connector, and draft journals in BTMS through the on-premise connector, with bank-statement transactions as double-entry across all four. For anything else, export CSV.
Yes. Connect both and choose a default for posting. Each confirmed entry maps to the chart of accounts synced from the ledger you send it to, so the codes always match where it lands.
The entry stays in your review queue, unposted, with the error shown, so nothing is lost and nothing is half-posted. Posting is idempotent, so a safe retry never creates a duplicate. The Excel workbook is already yours regardless.
Yes. Every posting is recorded in a history log, what was suggested, the confidence, and the action you took, so there is an audit trail of exactly what went to your ledger and when. You can export or delete your data at any time.
You still get everything that matters: the Excel workbook per supplier with the receipt embedded as proof, plus a CSV export you can import wherever you keep your books. Posting is a convenience on top, not a requirement.
Yes. A webhook notifies your systems when a batch is ready, and API access is available for teams that want to wire Pileform into their own workflow. Talk to us if you want to build on it.
No. The Excel workbook is always yours, with the source receipts embedded. Disconnect any integration at any time and keep every file you’ve produced.
Clear the pile, post it anywhere.
Sign up free, no card. Run your first batch and review the workbook, then post it, export it, or keep it.