Expense categories

Uber as commute, except when it is not: rules for a team in Canada

A rule to categorise Uber as commute for past and future rows, plus how to handle client trips that a merchant rule cannot tell apart, in Canadian dollars.

Editorial illustration for Uber as commute, except when it is not: rules for a team in Canada

A merchant rule can tell you who was paid but not why. That is the real limit when you file Uber as commute: the rule sees the merchant, while only the traveller knows if the ride was commute or a client visit. So use a rule for the default and a quick note for the exceptions.

What does the default rule do?

The default rule files every Uber ride as Commute, because that is the most common reason for a ride. Everything the rule gets wrong is then a small, countable list of exceptions, which is much easier to fix than coding every row by hand.

How do I catch the exceptions?

Ask the team to add a one-word note on a ride when it was for a client, such as Client or Airport. A second rule can then say: if the note contains Client, file as Client travel. The note takes the traveller a few seconds and removes the guesswork for whoever reviews the rows.

Ride (made-up)AmountNoteFinal category
Home to officeC$14.20noneCommute
Office to client siteC$22.80ClientClient travel
Home to airportC$58.00AirportClient travel
Office to home, lateC$19.10noneCommute

Commute here totals C$33.30 and Client travel C$80.80, for C$114.10 overall (14.20 plus 22.80 plus 58.00 plus 19.10).

How do I apply the rules to old rows?

  1. Export the last quarter of rows and filter on the merchant name.
  2. Apply the default rule so everything is Commute.
  3. Send the list to the team with the date, amount and a blank note column, and ask them to mark client trips within a week.
  4. Apply the second rule to the notes.
  5. Check that Commute plus Client travel equals the total you started with.

Past rows depend on memory, so expect some gaps. For those, leave the category as Commute and add the label Unverified in a note so it is clear that nobody confirmed the purpose.

How do I keep future rows tidy?

  • Tell the team once, in writing, what Commute means in your company.
  • Ask for a note on any ride that is not a normal commute.
  • Look at the rows that have a note but are still labelled Commute each month.
  • Review the rule list every quarter and date each change.

What are the limits?

A rule can make reports cleaner, but it cannot decide whether an expense is eligible for reimbursement or how any tax authority treats it. Those questions belong to your finance team or accountant. A tidy category is a good starting point for that conversation, not a replacement for it.

If you work with a spreadsheet, put the default rule in one helper column and the note-based override in another, so you can see both before you decide the final label. A simple final column can then pick the override when there is one: =IF(E2<>"", E2, D2), where D is the default label and E is the override.

How do I get people to add the notes?

Make it easier than skipping it. Send the list of rides in a short message every month, already filtered to the traveller's own rows, and ask them to reply only about the ones that were not a normal commute. People will answer five lines but not a spreadsheet of fifty. Say a team of five averages eight rides each a month: that is 40 rows, but perhaps only six need a note, so a monthly reminder takes each person a minute or two.

Thank people when they do it, and fix the rule list when a pattern shows up. If three people mark the same route as Client, such as the ride to a regular customer's office, that deserves its own rule with the destination name if the statement shows one.

SPENDIXAI JOURNAL

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

Explore your reports