Common upload mistakes

Uploading a personal bank statement while the business workspace is active will save all extracted rows as business transactions. There is no automatic reclassification — you must delete the affected rows and re-upload with the correct entity type.

Make checking the entity toggle the first step of every upload session. The current selection is always visible at the top of the Upload page.

Photographs of receipts taken with a phone camera often have distortion, shadows, glare, or low contrast. These reduce OCR extraction accuracy significantly. The parser can only work with what OCR extracts — it cannot recover text that the OCR engine cannot read.

Password-protected PDFs cannot be opened by the processing system. Remove the password protection before uploading. Most PDF viewers allow you to save a copy without password protection.

Extraction is not perfect. Some transactions will have wrong categories, amounts with incorrect decimal separators, or dates missing from the parsed output. Skipping Review and relying on the raw extracted data for reporting or invoicing will produce inaccurate results.

Always run a full review session immediately after upload while the source file is still fresh in memory.

Uploading the same bank statement twice will create duplicate transaction rows. There is no automatic deduplication by file content. If you accidentally uploaded a duplicate, use the source file filter in Review to find and delete the duplicate batch.

AI mode has a cost and a privacy implication. For most structured bank statement PDFs, Standard mode produces equivalent or better results. Try Standard mode first, then switch to AI mode only for documents where Standard mode performs poorly.