Help
What the messages mean
Every failure here is designed to tell you what happened, whether you were charged, and what to try next.
“This statement format is not supported yet.”
The parser did not recognise the transaction table, or the document is outside the supported scope. Nothing was charged. Try a PDF downloaded directly from your bank: a photo or screenshot is only read when the OCR layer is legible enough.
“We could not verify this statement's transactions.”
The arithmetic did not reconcile, required balances were missing, or a row was ambiguous. The preview shows you the first five rows and the validation report lists exactly which checks passed, failed, or were unavailable. Nothing was charged.
“That PDF is password-protected.”
Remove the password in your PDF reader and upload the decrypted file. We never ask for or store a PDF password.
“We could not read this scanned statement reliably.”
Scans are read with OCR, capped at 10 pages per document and needing reasonably level, unblurred text. Run OCR in your PDF reader first, or download the statement from your bank instead of scanning a printout. Nothing was charged.
Payment completed but downloads are missing
Unlocking happens when Stripe's verified webhook reaches us, not when your browser lands on the success page. That page polls until the entitlement exists, usually within seconds. If it stays pending for more than a few minutes, contact the operator with the conversion ID.
Deleting a conversion
Use Delete on the conversion page. Access is blocked immediately and files are removed in the background, with retries if storage removal fails.
Supported document scope
English-language USD checking and savings statements, one account per document, unencrypted and text-based, up to 20 MB and 50 pages. Support is defined by a versioned list of tested layouts rather than by bank brand. Unsupported or unverified layouts fail honestly and are never charged.
Still stuck? Contact the operator.