To make every Uber charge land in Commute, write one matching rule on the merchant text, apply it once to the old rows, then keep it for new ones. The catch is that one merchant name can cover two different things, so test the rule against a month of real rows before trusting it.
What does the rule need to say?
A rule has three parts: what to look for, where to look, and what to assign. Here that is: if the description contains UBER, assign Commute. Card and bank exports usually add extra text, so the description may read like a trip reference or a merchant string with a city. Check your own export instead of assuming a format.
Why will a one-line rule go wrong?
The same company may sell rides and food. Say a team of eight reimburses commute but meals go elsewhere. A plain UBER rule would put a $23.40 dinner order into Commute. So the rule needs an exception that is checked first.
| Order | If the description contains | Then assign | Why this order |
|---|---|---|---|
| 1 | UBER and EATS | Meals | Catches food orders before the broad rule |
| 2 | UBER | Commute | Everything left is treated as a ride |
| 3 | Anything else | Uncategorised | Stays visible for manual review |
Rules are checked in order and the first match wins, so the specific rule goes above the general one. If your tool does not apply them top to bottom, test with one known meal and one known ride.
How do I apply it to old rows in a spreadsheet?
If your card export lives in a sheet with the description in column B and the category in column C, put this in C2 and fill it down to your last row. It works in Excel and in Google Sheets.
- =IF(ISNUMBER(SEARCH("UBER",B2)), IF(ISNUMBER(SEARCH("EATS",B2)), "Meals", "Commute"), "")
- SEARCH ignores upper and lower case, so Uber and UBER both match.
- To keep existing categories, wrap it: =IF(C2<>"", C2, IF(ISNUMBER(SEARCH("UBER",B2)), IF(ISNUMBER(SEARCH("EATS",B2)), "Meals", "Commute"), "")) in a helper column, then paste values over once you have checked.
Did the rule do what I wanted?
Compare before and after. Say the month had 14 Uber rows adding up to $312.60, of which two were food orders totalling $41.30. Commute should now show $271.30 (312.60 minus 41.30) and Meals should show $41.30. If your Commute total is $312.60, the exception did not fire.
- Filter the description for UBER and note the row count and total.
- Run the rule on the old rows.
- Filter Commute and Meals and check that the two totals add back to the original.
- Open three random rows from each and read the description.
- Save the rule list somewhere the team can see it, so new joiners do not invent their own.
What does the team lead still have to decide?
- Does Commute mean home to office only, or does it include rides to client sites?
- Who reviews rows that the rule could not place?
- How often are the rules reviewed? Once a quarter is usually enough.
Rules handle the repetitive part. Judgement calls, like a ride that was part commute and part client visit, still need a person and a short note on the row.
A final tip for the first run: write down three rows you expect to see in each category before you apply the rule. For example, a Monday 8:40 am ride of $14.90 should be Commute, an order for $23.40 with the food keyword should be Meals, and a one-off $61.00 airport ride is worth a manual look. If those three behave as expected, the rule is probably fine.
Useful ideas start with a clearer picture of your own spending.
Explore your reports


