On Android, supported bank alerts are prepared for review after local safety filtering, sender checks, parsing, sanity checks, and deduplication. Salli review queue containing locally parsed supported bank alerts

​
Review an item

Confirm the:
  1. amount and expense/income direction;
  2. merchant or payer;
  3. detected account;
  4. category; and
  5. transaction time.
Low-confidence amounts receive an explicit warning. Nothing uncertain should be confirmed without inspection.

​
Confirm

Choose or correct the category, then confirm. The item moves into Activity and all derived totals update.

​
Ignore

  • Not mine / ignore removes this review item without creating a transaction.
  • Always ignore similar creates an inspectable local rule tied to the institution and normalized merchant or message phrase.
You can remove ignore rules from More → Corpus & rules.

​
Duplicate alerts

Salli derives a stable event identity from sender, normalized message content, amount, direction, account, and time evidence. Repeated delivery of the same event does not create multiple reviews or ledger entries. Distinct same-value transactions remain separate.

​
Unsupported formats

Messages from recognized senders with unsupported formats may enter the encrypted unmatched queue, capped at the newest 50. They are outside the ledger and every financial metric. From the queue you can dismiss, export, retry after parser improvements, or add an ignore phrase.

​
Messages rejected before storage

  • OTP and security codes;
  • declined/failed alerts;
  • promotional content;
  • personal or unrelated messages;
  • unknown senders;
  • malformed amounts; and
  • values beyond configured sanity limits.

How the parser works

Read the developer-level capture, filtering, confidence, and validation architecture.