The question: how much is AI costing me in my expense app, and can I see or limit it? Work it out in three moves: find out which features use AI, set a monthly AI budget or switch the features off, and check the app's usage view regularly. In SpendixAI, AI runs only on the leftovers after your rules and history, and you can cap or disable it.
Where does AI actually run?
Not on everything. SpendixAI categorises in stages. First your own rules, then your history and similar merchants, and only if AI is on, an AI model for whatever is left. It uses the normalised merchant name and an amount band, not your name, account numbers, full statement text or balances. Optional features such as reading an unfamiliar statement layout do process the uploaded document, so check each one before enabling it.
What can I switch off or cap?
- AI can be switched off per feature.
- You can set a monthly AI budget.
- You can turn AI off entirely.
- When AI is off, unmatched items are held for review rather than guessed.
- AI credit packs are bought separately from Pro.
How do I work out my own load?
- Count how many rows you import in a typical month.
- Estimate how many are matched by your own rules, then by history.
- The remainder is what AI would see.
- Check the app's usage or billing view to confirm what was actually used.
- Set a monthly budget a little above that, and look at it again after a month.
Say you import a statement with 400 rows. Your rules catch 250 and your history and similar merchants catch 100. That is 250 + 100 = 350 handled without AI, leaving 400 - 350 = 50 rows for the AI model. If the app uses one credit per AI-categorised row, which you should confirm in your own plan, that import uses 50 credits, not 400.
Does it get cheaper over time?
Usually, yes. Every correction you make becomes history, and a rule you write catches a whole merchant at once. If next month's statement has 400 rows and 30 more are now caught by rules or history, only 20 reach the AI model. A small amount of tidying each month reduces how much the AI has to do.
| Month | Rows imported | Handled by rules or history | Left for AI |
|---|---|---|---|
| First import | 400 | 350 | 50 |
| Next month, after adding rules | 400 | 380 | 20 |
| AI turned off | 400 | 380 | 20 held for review |
What should I check about the numbers?
The figures above are made up to show the shape. Your own pack size and the number of credits an action uses are in the app, and prices can change, so read your plan page instead of trusting a forum example. Ask whether your dashboard or the connected assistant, if you use one, can show an AI usage summary, and compare it with what you bought.
What should I do when the budget runs out?
Decide this before it happens. With a monthly AI budget, rows that cannot be categorised once the cap is reached are held for review, not guessed. Open the held list, create a rule for the merchants that appear most often, and the next import will need less AI. If you need more capacity in a busy month, a credit pack is a separate purchase, so choose that deliberately instead of by default.
My routine
Set a budget, check usage once a month, add a rule for every merchant that appears in the AI leftovers, and turn off any optional AI feature you do not use.
Useful ideas start with a clearer picture of your own spending.
Explore your reports

