Salli is a functioning pre-release application, not yet a generally available consumer service. The local ledger, planning, insights, privacy controls, encrypted persistence, and Android SMS pipeline are implemented and tested. Several release gates still depend on real-world evidence and external approvals.

​
Implemented locally

  • Manual expense, income, transfer, split, note, label, and attachment flows.
  • Receipt OCR on supported physical devices.
  • Payday-cycle budgets, Safe to Spend, goals, runway, scheduled payments, and fixed or bidding seettu circles.
  • Account discovery, reconciliation, categories, merchant rules, reports, and reminders.
  • SQLCipher database encryption, optional device-auth app lock, JSON backup, CSV export, restore, and delete-all.
  • English, Sinhala, and Tamil interfaces, with immediate locale switching.
  • Android SMS capture, filtering, parsing, review, deduplication, and local evidence controls.

​
Release gates

Synthetic parser coverage is not the same as production bank validation. Bank templates must pass consented, redacted real-SMS golden tests before Salli claims dependable coverage.
  • Google Play approval for restricted SMS permissions.
  • At least 90 reviewed, redacted real messages across the P0 bank/format matrix.
  • Native Sinhala and Tamil review.
  • Physical-iPhone validation, especially receipt OCR.
  • Sri Lankan privacy/legal review and the final public policy.
  • Store accounts, signing, listings, and publisher approvals.

​
Known platform constraints

​
Translation status

The primary experience is localized in English, Sinhala, and Tamil. Sinhala and Tamil copy is still draft text pending native review. Financial values and locale-aware dates are formatted at the UI boundary.

​
Safety boundary

If a security code, OTP, promotional message, or unrelated SMS becomes a transaction, that is a release-blocking defect. Salli rejects those message classes before ledger creation and keeps uncertain supported alerts in a review queue.