Separate receipt import from statement import

Statement imports and receipt scans solve different problems. Statements contain many transactions and need to be tied to an account. A receipt is usually for one purchase, so scanning it should quickly create one transaction rather than use the bulk-import flow. I suggest splitting both into distinct features:

Import Statements (existing);

• For account CSVs, PDFs, or screenshots.

• Handles multiple transactions at once.

• Could add suggestion to link an account and warning before importing if no account is selected.

• Use the same interface no matter the file format.

Receipt Scanning (new):

• Designed to create one transaction from a receipt.

• Accepts a PDF, screenshot, photo, or direct camera input.

• Could be available from the + / Quick Add button, with a press-and-hold choice for text, dictation, screenshot, photo, or file.

• Extracts the total, merchant/description, date, category, and transaction type, then lets the user review and edit everything before saving.

• Treats multiple pages in the same file as one receipt.

• Clearly explains whether the receipt image is stored or discarded after scanning.

Splitting these opens the way for even more improvements:

• Read line items and suggest a split. For example, a Costco receipt with clothing and groceries could suggest a clothing amount and put the rest under groceries.

• Save receipt details as notes or a new special receipt details fields (sub-total, taxes, discounts, individual line items, etc.)

• Saving a receipt as attachement to the transaction

Though these go beyond what I’m asking now, let me know if I should open a separate request for these.