Expense categories

Business versus personal tags at import: a euro-based decision table

A decision table for a freelance translator or consultant in euros: which transactions get tagged business, which personal, and which need a human look.

Editorial illustration for Business versus personal tags at import: a euro-based decision table

You can tag business and personal transactions automatically if you decide the answer for each kind of payment in advance and write it as a rule. Most rows will then tag themselves, a few will need a look, and none will surprise you at the end of the quarter. This version uses euros and describes habits only, because rules about expenses differ from country to country.

Decide once, in a table

Write down your common payees and give each one an answer before you import anything. The table below is a pattern, not a template to copy; fill in your own.

Payee typeTagHow to automate
Co-working deskBusinessRule on the space's name
Train ticket to a clientBusinessRule on the rail operator, then review
Phone contractMixedDefault personal, check the work share
SupermarketPersonalRule on the chain's name
Streaming servicePersonalRule
Online course for workBusinessRule on the provider

What does this look like with real numbers?

Say a freelance translator pays €180 for the co-working desk, €46.80 for train tickets, €64.90 for the phone contract, €212.35 at supermarkets and €13.99 for a streaming plan. Business items: €180 + €46.80 = €226.80. Personal: €212.35 + €13.99 = €226.34. The phone contract is mixed; if you decide 60 percent is work, then 0.6 × €64.90 = €38.94 is business and €25.96 is personal. The business total becomes €226.80 + €38.94 = €265.74 and the personal total €226.34 + €25.96 = €252.30.

The split percentage is your own decision; keep a short note explaining how you chose it.

How to write rules that tag at import

  1. Use the stable text of each payee, not the whole string with a date or branch code.
  2. Assign a category whose side is already set, so you do not have to tag separately.
  3. Handle mixed payees by creating a Mixed category and reviewing it monthly, rather than guessing.
  4. Run the rules on a month you have already finished and compare with what you know.

What about spending across currencies?

If your clients pay in another currency or you travel, each expense can carry its own currency and totals can use a base currency with the rate saved against each transaction. SpendixAI offers this, but it is built around India and INR, so treat that as a feature to look for elsewhere rather than something on offer in euro countries. Whatever you use, choose the base currency before you import.

Which rows should always need a human look?

  • Anything over an amount you pick, say €150.
  • Anything from a merchant that sells both work and household goods.
  • Anything paid in cash.
  • New merchants you have never paid before.

SpendixAI follows the same shape in its own way: rules first, then history and similar merchants, then optional AI, and unmatched items can be held for review if you turn AI off.

A quarterly look back

Every three months, sort the business categories by amount and read the top ten rows. Ask whether each belongs there and whether you have the paper to show it. Then sort personal by amount and ask the reverse. Five minutes of this finds more errors than any amount of fiddling with rules, and it tells you which rules to tighten.

If you find a business purchase tagged personal, fix the row and ask why: was the merchant missing a rule, did a rule point at the wrong category, or was the card the problem? The answer tells you which of the three to repair.

Monthly close in ten minutes

Import the statement, check the held-back rows, update the one or two rules that failed, and export the business total if somebody needs it. If you cannot explain a row in one sentence, attach a note while you still remember.

SPENDIXAI JOURNAL

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

Explore your reports