logging expenses
text it, the 💸 lands
every message is read for money actually spent. "tacos 250", "spent 89 on an uber", "cine 180 ayer" - no format, no keyword, your language. when an expense is found it is saved and your message gets a 💸 reaction. that reaction is the whole reply: nothing is typed back, the chat stays clean.
each expense gets an amount, a short description in your own words ("tacos" stays "tacos", never translated), a category, the date, and - in groups - who paid and who it was for.
several in one message
a message can carry more than one expense. each becomes its own row, in the order written; the message gets one 💸.
#41 coffee 45 · food
#42 lunch 180 · food
#43 parking 60 · transport 18:11
dates, currencies, categories
- backdates in words: "yesterday", "last friday", "el martes". without one the expense is now, in your timezone. a date in the future is ignored - it was a plan, not a spend.
- currency is the chat's default unless you say one: "20 usd", "€30", "300 pesos". mixed currencies stay separate in totals - nothing is converted.
- category is guessed from the words: food, groceries, transport, entertainment, health, services, shopping, home, other. say it to change it: "move it to transport".
#44 dentist 1,200 · health · fri 22
#45 hotel 140 USD · home · today 10:17
who paid, who it was for
in groups the speaker paid unless the message says otherwise ("ann paid 600 for dinner"), and an expense is for everyone unless it names people: "paid the cabs, just milo and me". that is all the splitting needs - see splitting and settling.
what is not logged
prices are not expenses. "the flight is 4,500", "budget 20k for the trip", "how much was the hotel?", a refund, an unpaid bill, a forwarded promo - none of these get a 💸. when teresa is not sure it does nothing, on purpose: a wrong 💸 in a group is the expensive mistake. if it missed one, say so.