Tags add a second label to transactions in a Space. Use them for questions that cut across the Space's main structure: who paid, which trip an expense belongs to, whether a cost is reimbursable, or which project created it.
Build a small tag system
Create tags with a clear name and, optionally, an emoji. Useful patterns include:
- Person: Paid by Maya, Paid by Leo;
- Status: Needs review, Reimbursed;
- Project: Kitchen repair, Rome trip;
- Type: Utilities, Food, Transport.
Start with the few tags you will actually use. “Coffee,” “Café,” and “Hot drinks” create fragmented totals when one tag would answer the same question.
Apply and review tags
- Open or create a transaction.
- Select the relevant tag.
- Save the transaction.
- Check that the tag appears in the transaction list.
- Review related transactions together before a settlement or planning meeting.
MoneySpaces has been redesigned since this screenshot. If the tag picker looks different, consult Settings → Tutorials in the current app.
Tags versus separate Spaces
Use a tag when the transactions belong to one shared balance but need another filter. Use a separate Space when the money needs a distinct balance, membership list, or privacy boundary.
Example: keep a single “Apartment” Space and tag expenses Rent, Utilities, and Household. Create a separate “Portugal Trip” Space if the trip has different members and should not affect the apartment balance.
For debts, tags such as “Paid by Sam” or “Owed to Priya” can document responsibility, but agree on one convention. A tag is a record, not a money transfer or legally binding settlement.
Monthly cleanup
Once a month, merge duplicate naming conventions in your workflow, correct missing tags, and retire tags that no longer answer a useful question. Avoid renaming a tag without telling collaborators, because they may continue using the old convention.
