Skip to content

Personal finances: from a receipt to a budget

A transaction shows up on its own — with a check

Section titled “A transaction shows up on its own — with a check”

Three sources: email (invoices, receipts, bank notifications), fiscal receipts embedded in email, bank SMS. Each is parsed and turned into a suggestion, not a transaction outright — you confirm it.

Duplicates are caught ahead of time: a receipt by its fiscal identifiers (number, date, sign), everything else by merchant, amount and time. If a receipt and an SMS about the same purchase arrive separately, Yttri tries to work out on its own that they’re the same thing, either merging them quietly or showing a single “Merge” card instead of two transactions.

The category is a chain of guesses, not a blind one

Section titled “The category is a chain of guesses, not a blind one”

A category is picked through a chain: first, does Yttri remember this merchant from past transactions, then a pattern on the sender’s address or domain, then your own rule if you have one, and only if nothing matched — a model, down to a one-off guess the first time it meets a new merchant. A manual pick always overrides any of these.

Budgets and forecasts — simple tools, not an autopilot

Section titled “Budgets and forecasts — simple tools, not an autopilot”

A budget is a limit on one spending category per month, with no recalculation or reminders beyond the usual ones. The balance forecast is a rough extrapolation — “current balance plus the average flow over past periods” — not a calculation based on actual scheduled payments: treat it as a ballpark, not bookkeeping.

The payments calendar — one for the whole app

Section titled “The payments calendar — one for the whole app”

This isn’t a separate finance feature — it’s the same table behind upcoming payments in the regular Calendar module and in CRM deal milestones. Mark a payment paid or skipped from any of the cards, and all three places see the change at once.

Beyond mentioning an overdue payment in the morning brief, there are two separate background watchers: a rollup of payments due within a week plus anything overdue, and separately — if an active subscription’s expected charge didn’t go through (a missed charge, not a price hike), it’ll suggest removing the subscription, waiting a week, or postponing the check once.

A line in receivables shows up on its own once a billable task or project milestone closes — as long as you set a price on it ahead of time. There’s nothing to enter separately; it disappears by itself the moment the payment is marked paid anywhere in the app.