Money tips

Control AI costs in an expense app with a cap and an off switch

How to keep AI costs in an expense app under a monthly cap in Australia: set a dollar ceiling, a hard stop and an off switch, with A$ examples you can copy.

Editorial illustration for Control AI costs in an expense app with a cap and an off switch

To keep AI costs in an expense app under control, decide a monthly dollar ceiling before you switch anything on, make sure the app stops at that ceiling rather than only warning you, and turn AI off for any job that a plain rule can do. Then look at the usage figure once a week. The worked numbers below are in Australian dollars and are made up to show the arithmetic, not to suggest what any provider charges.

Why AI costs creep up without you noticing

Each AI request in an expense app is tiny. The bill grows because of volume and repetition: a year of old statements imported in one go, the same file uploaded again after an error, a receipt reader running on every photo, a chat feature that you start using daily. Nobody sees a running total, so the first sign is the invoice.

The other source of surprise is that features you never chose can be switched on by default. Before anything else, find the settings page for AI and read what each switch controls.

Step 1: Pick the number first

Work out what AI is actually for in your setup. If it only sorts the transactions that your own rules cannot, the volume is small and predictable. Say your rules and history handle most rows, leaving about 60 unmatched rows per account each month. With three accounts that is 180 rows. Suppose, purely for illustration, that each AI-sorted row costs A$0.02.

SituationRows sent to AIMade-up cost per rowMonth total
Ordinary month180A$0.02A$3.60
Importing a big backlog of old statements1,200A$0.02A$24.00
Same statement file uploaded four times by mistake720A$0.02A$14.40

A cap of A$5 would be comfortable for the ordinary month and would have stopped the other two situations well before they cost A$24.00 or A$14.40. That is the point of choosing the ceiling from your normal month, then adding a little headroom.

Is a warning enough, or do I need a hard cap?

A warning tells you; a hard cap acts. They protect you from different things.

  • Warning at around 80 per cent of the ceiling: useful when you are watching, useless when you are on holiday or the notification is buried.
  • Hard cap: the feature stops until next month or until you raise the limit. This is what protects you from a loop, a backlog or a mistake you did not see.
  • Per-feature off switch: the cleanest control. If rules already categorise your groceries and fuel, the AI step has nothing useful to do for those rows.
  • Master off switch: for a month where you want certainty, such as when you are importing a large archive.

Ask what happens to the work when a cap bites. The kinder behaviour is that the unmatched rows wait for you to review by hand instead of being guessed or dropped.

Which jobs deserve AI and which do not?

A fair test is whether the job repeats. Your weekly supermarket shop, your rent, your phone plan and your fuel stops all repeat, so a rule you write once handles them for free. AI earns its keep on the long tail: a one-off merchant with an odd name, a transfer description you cannot decode, or a statement layout the app has never seen.

  1. Write rules for everything that repeats.
  2. Let history and similar-merchant matching handle the rest.
  3. Allow AI only for what is still unmatched.
  4. Review the AI's answers for the first month, correcting anything wrong so the correction becomes history.
  5. Lower the cap once the unmatched pile shrinks.

What should I verify before trusting a cap?

  • Does the cap stop the feature, or only send an email?
  • Does it reset on the first of the calendar month, or on the date you subscribed?
  • Do retries and failed attempts count towards the cap?
  • Are optional features, such as reading an unfamiliar statement layout or scanning receipts, inside the same cap?
  • Can you see usage so far this month without contacting support?
  • If you switch AI off, are unmatched items held for review, or silently put in a catch-all category?

A five-minute weekly habit

On the same day each week, open the AI usage figure and compare it with the ceiling. If it is above a quarter of the month's cap after the first week, find out why before the second week starts. A big import or a re-upload is the usual reason, and both are easy to fix once you spot them.

Keep a one-line note of the cap, the date you set it and who can change it, especially if a partner or accountant shares the account. When the ceiling changes, change the note, so you always know which number you agreed to.

SPENDIXAI JOURNAL

Useful ideas start with a clearer picture of your own spending.

Explore your reports