Expense categories

Rules that file Uber rides as commute across currencies in Europe

For a team lead in Europe, a method to file every Uber ride as commute across past and future rows, including trips paid in several currencies.

Editorial illustration for Rules that file Uber rides as commute across currencies in Europe

When your team travels across several countries, the same ride-hailing company shows up in different currencies, with different merchant strings. Write the rule on the merchant name, not on the amount, keep the currency on each row, and compare totals per currency before and after.

Why do multi-country teams get messy rows?

A consultant in one city pays in euros. A colleague on a short trip pays in another currency. The export may list the original amount, a converted amount, or both. If the rule or the report adds them together without caring about currency, a €15.00 ride and a 15.00 ride in a different currency look identical.

What should the rule match on?

  1. The merchant name, ignoring upper and lower case.
  2. Any extra words that separate rides from food orders, such as EATS.
  3. Nothing about the amount at first. Amount bands are useful later, but they behave differently across currencies.
  4. The currency is kept as it is on the row; the rule does not change it.

A worked example in euros

Say a team of six has these made-up Uber rows over a quarter, with every row in euros to keep the arithmetic simple.

MonthRide rowsRide totalFood-order rowsFood total
January9€146.202€38.00
February11€171.901€17.50
March8€129.403€52.10

Rides add up to €447.50 (146.20 plus 171.90 plus 129.40) across 28 rows, and food orders to €107.60 across 6 rows. Before applying the rule, filter on Uber and check that 34 rows total €555.10. After applying it, Commute should be €447.50 and Meals €107.60. Any difference means a row was filed by another rule first.

How do I handle trips in other currencies?

Filter the Uber rows by currency first and run the check per currency. Do not add figures in different currencies to compare them. If you need one total, convert each row at the rate your card or accounting tool used for that row, and note which rate source you chose. In a spreadsheet, add a currency column and use SUMIFS by currency, as below.

  • =SUMIFS($D$2:$D$500, $B$2:$B$500, "Commute", $C$2:$C$500, "EUR")
  • Here D is the amount, B the category and C the currency code. Repeat the line for each currency in use.

Who owns the rules?

Pick one person per region or per team. Two people editing the same rule list will, sooner or later, contradict each other. Write the rule list in one shared place with the date of each change.

A short closing checklist

  • Rule written, specific exception first, general rule second.
  • Totals compared per currency before and after.
  • A named owner and a quarterly review.
  • A saved copy of the data before any bulk change.

Keep the category a plain label. Questions about allowances, reimbursement limits or tax treatment belong with your finance team and should not be built into the category name.

One more trap in a multi-country team is the merchant text itself. The same company can appear with a city, a country code or a reference number added, and the pattern differs by card and bank. Read ten real rows from each card before writing the rule, and match on the stable part of the text, usually just the company name. If one card shows something very different, add one extra line for it rather than loosening the rule for everybody.

Finally, decide how you will treat a ride booked by one person and paid by another. The category should follow the purpose of the ride, but the owner of the row should follow the cardholder. Writing that in the rule list avoids an argument in the third month.

SPENDIXAI JOURNAL

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

Explore your reports