How it works
- Drop a PDF, Excel (.xlsx), CSV or photo on a bank statement connection. What the file is gets decided from its content, not its name.
- Ziira finds the header and columns, says in plain words what it found ("214 transactions from 3 Jan to 28 Feb"), and shows a sample.
- You answer "Looks right" or fix one dropdown at a time. The first confirmed upload saves the layout, so the next file is one drop.
What it handles
- Multi-page PDFs, repeated headers and footers, wrapped description lines, opening and closing balance lines.
- Amounts with thousands separators, brackets, trailing minus, DR/CR and paid-in/withdrawn columns; running balances.
- Statement overlaps: uploading overlapping statements adds nothing twice, even across formats.
- Password-protected PDFs: the password is used once to open the file and is never stored or logged.
Photos and scans
Pictures are read with OCR, by default a self-hosted engine so nothing leaves the server. Because digits can be misread, a picture is never stored without you confirming, and lines whose running balance does not follow are shown for correction. No accuracy figure on real photos exists yet.
What it checks
- Cash sales over recent days well above cash deposits.
- Money received that matches no sale or invoice (cash deposits are left out).
- Duplicate payments.
Limits
- Daily or on-upload freshness, depending on how often you drop a statement.
- Limits: 10 MB per file, 50,000 rows, 300 pages for text PDFs. The old .xls format must be saved as .xlsx.
- Statement layouts were written from common shapes of public statements and tested on constructed files. Try a real statement from your bank before relying on it.