ExpenseAI Support
Last updated: September 19, 2026
Need help with ExpenseAI? Contact us and we'll respond as soon as possible.
App Overview
ExpenseAI logs an expense the moment it happens: say it out loud, type one line, or snap a receipt. The AI reads the amount, merchant, category, and date; you glance at the draft and hit save. Everything is stored on your device; there is no account and no sync, and by default nothing you log ever leaves your iPhone.
Key Features
- Three ways in: hold the input bar and speak, type a line, or add from camera / photo library / manual form
- AI parsing into a draft — amount, merchant, category, date — with a confirm screen before anything is saved
- Receipts use on-device OCR by default; each cloud provider also offers an optional, separately authorized receipt-image mode
- One sentence can split into several entries (multi-entry mode, off by default)
- Pay-cycle timeline: your ledger runs from payday to payday (monthly / semi-monthly / biweekly / weekly), not calendar months
- Optional per-cycle budget: the home ratio bar turns into a budget strip once a payday is configured
- Statistics per cycle or per year with charts: totals, month-over-month, category share, trend bars, spending pace
- Expenses and income tracked separately — stats count spending only, income gets its own view
- Default AI runs on-device with Apple Intelligence; cloud providers (OpenAI, Qwen) optional with your own API key
- CSV export and import — files open directly in Numbers, Excel, or Google Sheets
- Currency is a display setting (defaults to USD); no exchange-rate conversion
- Light / dark / system theme
- Works without an account; your data stays on your device
Requirements
- iOS 17 or later
- On-device AI parsing needs Apple Intelligence support; on other devices ExpenseAI falls back to an on-device rough read (amount by pattern, title from the first words) that you correct by hand
- Cloud providers (OpenAI, Qwen) require your own API key and explicit permission before text is sent; sending receipt images requires a second, separate permission
- Voice input needs microphone and speech recognition permissions; receipts need camera or photo access
Troubleshooting
- Voice input doesn't transcribe: Check Settings › Privacy & Security › Microphone and › Speech Recognition, and make sure both are on for ExpenseAI. Recognition runs on the device — airplane mode is fine on supported devices.
- A receipt reads wrong: Shoot the receipt flat, fill the frame, and avoid glare. In the default on-device OCR mode, recognized text is kept in the entry's note so you can compare it with the photo. Cloud image mode reads the selected image directly.
- The AI got the amount or category wrong: Drafts are never auto-saved — fix it on the confirm screen before saving, or open the entry later to edit. A wrong date is a one-tap fix.
- Stats look off: Statistics count expenses only; income has its own view at the top of the stats page. Also check your pay-cycle rule in Settings — a cycle like "25th of each month" shifts which entries belong to the current period.
- Cloud parsing returns an auth error: The API key you entered was rejected by the provider. Re-enter it in Settings, and remember it is stored only on this device — a new phone means re-entering it.
- Moving to a new phone: Export a CSV in Settings, transfer it, and import it on the new device. Receipt photos are not part of CSV; they are only in a full device backup.
- I deleted an entry by mistake: Deletion is immediate and there is no server copy to recover from. A device backup (or a recent CSV) is the only fallback.
Privacy & Data
ExpenseAI stores all your entries, receipt photos, and settings locally on your device. There is no account, no cloud sync, and no third-party analytics. By default, parsing and receipt OCR run on-device. Cloud parsing only happens if you enable it with your own API key; optional receipt-image sharing requires an additional consent step. For full details, see the Privacy Policy and Terms of Use.
Tip: When you contact support, please include your iOS version, device model, and a short description of what you were doing when the issue happened. That helps us reproduce and fix it faster.