Invoice Parser — Extract, Verify & Export Payments
Drop invoices, get clean, verified payout data. IBAN/SWIFT checks, duplicate detection, vendor account-change warnings. Runs entirely in your browser — the PDF never leaves your machine.
Review desk, not payment approval
This tool is intentionally kept in Labs because invoice extraction is a high-stakes workflow. Use it to prepare and inspect payout data locally; keep your normal approval, callback, and bank review process in place.
- Local parsing only
- Human review required
- Export after checks
Drop your first invoice
Nothing to parse yet. Drop a PDF, image or paste text to start.
How the desk works
- 1. Drop invoices
PDFs (text or scanned) and photos. Everything is parsed locally in the browser.
- 2. Review the extracted fields
Beneficiary, bank, IBAN/SWIFT, amount, dates. Edit anything that looks off.
- 3. Check the safeguards
IBAN mod-97, SWIFT format, duplicate invoice number, vendor account change against your local history.
- 4. Export a payout file
One Wise CSV, ISO 20022 or SEPA PAIN.001 file for your whole batch.
Why finance teams use it
- One typo in an IBAN costs a bounced payment or worse — the checks catch them before the file leaves.
- Vendor account swapped mid-thread? Local history flags it so you can call to confirm.
- Duplicate invoice numbers are auto-detected — no double payments.
- Runs entirely in the browser. Finance data stays on your machine.
FAQ
Do you upload my invoices?
No. The whole pipeline — PDF parsing, OCR, validation, export — runs in your browser via WebAssembly.
Which formats can I import?
Native PDFs, scanned PDFs, and images (PNG/JPG/WebP). OCR runs locally with Tesseract when a PDF has no text layer.
Which payout files can I export?
Wise Business CSV, ISO 20022 pain.001, SEPA PAIN.001, and a plain CSV template.
What does the account-change warning use?
A local history stored in your browser only. Nothing is sent anywhere.
Do you validate IBAN and SWIFT?
Yes. IBAN uses mod-97, SWIFT/BIC checks length and structure.