AI and MCP

How to categorise all your Uber transactions using an AI assistant

Asked on a money forum: how to categorise every Uber transaction with an AI assistant. Numbered steps, a worked example, checks and an honest limit.

Editorial illustration for How to categorise all your Uber transactions using an AI assistant

Asked on a money forum: 'I have months of Uber charges mixed into my statements and I want an AI assistant to tag them all as travel in one go, how?' Short answer: yes, it can be done, but the sturdy way is to have the assistant find and tag the existing charges once, then turn that into a rule so you never repeat the exercise.

The steps we would follow

  1. Import your statements first. An assistant can only work on rows that exist in your tracker, so get the bank and card statements in and reviewed.
  2. Connect the assistant with the narrowest scope that works. Start read-only, and ask it to list every transaction whose description contains Uber.
  3. Read the list yourself. Uber charges come under several narrations, and some may not be rides at all.
  4. Tell the assistant what to label each group, then widen the scope only if you want it to make the change itself. Otherwise change them in the app.
  5. Add a rule for the merchant name so next month's charges are tagged on arrival, instead of asking again.

A made-up example so you can see the arithmetic

Say last month had nine ride charges: ₹212, ₹348, ₹96, ₹410, ₹187, ₹265, ₹143, ₹520 and ₹305. Add them up: 212 + 348 = 560, plus 96 = 656, plus 410 = 1,066, plus 187 = 1,253, plus 265 = 1,518, plus 143 = 1,661, plus 520 = 2,181, plus 305 = 2,486. So you expect the assistant to report nine transactions totalling ₹2,486 for the month.

If it says ten, or ₹2,100, stop. It either picked up something that is not a ride or missed rows that are spelled differently. Matching count and total is the single best check you have.

What trips people up?

  • Uber Eats or other non-ride charges that carry the same merchant name and would be filed under travel by mistake.
  • Reversals and refunds, which should reduce the total rather than add to it.
  • Charges from a card or wallet you have not imported, which no instruction can find.
  • Duplicate rows from importing the same statement twice. SpendixAI flags possible duplicate imports, but still glance at the list.

Does it need AI at all?

Not always. SpendixAI categorises in stages: your own rules first, then your history and similar merchants, and only after that, if you have AI switched on, an AI model for what is left. For a merchant as regular as a cab app, a plain rule does the job and the result is the same every month. The assistant is useful for the first sweep, for the odd narrations, and for the awkward question such as 'which of these were airport trips'.

Where is the line on privacy?

You choose what the assistant may reach. Start with read-only, and you can disconnect any time. The built-in AI categorisation works from a cleaned-up merchant name and an amount band, not your name, account numbers or balances, and it can be switched off by feature, given a monthly budget, or disabled entirely, in which case unmatched rows are held for review.

Quick checklist before you call it done

  • Count and total of Uber rows match your own sum.
  • Food orders are under food, rides under travel.
  • One rule exists for the merchant name.
  • Next month, glance at the first five Uber rows to confirm the rule fired.

If you made a wrong bulk change, correct a couple of rows by hand. Corrections feed back as history, which is what makes the next import cleaner.

SPENDIXAI JOURNAL

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

Explore your reports