This is the full developer documentation for Tovari # Tovari documentation > Documentation for Tovari — personal finance, budgeting and bill tracking. Welcome to the Tovari documentation. This site is served at [www.tovarifinancial.com/docs](https://www.tovarifinancial.com/docs) and is searchable from the box at the top of the page. ## What is here today [Section titled “What is here today”](#what-is-here-today) * **[Quick start](/docs/quick-start/what-tovari-does)** — ten pages taking you from signing up to a categorized register and a Safe to Spend number you can trust. Every page covers both the web app and the mobile app. * The generated **[API reference](/docs/api)**. * Site-wide search, and a machine-readable [`/llms-full.txt`](/llms-full.txt) corpus. The Quick start in walk order: 1. [What Tovari does](/docs/quick-start/what-tovari-does) 2. [Create your account](/docs/quick-start/create-your-account) 3. [Add your first account](/docs/quick-start/add-your-first-account) 4. [Connect a bank with Plaid](/docs/quick-start/connect-a-bank-with-plaid) 5. [The budget interview](/docs/quick-start/the-budget-interview) 6. [Reading your register](/docs/quick-start/reading-your-register) 7. [Categorizing spending](/docs/quick-start/categorizing-spending) 8. [Your first envelope](/docs/quick-start/your-first-envelope) 9. [Scheduling a bill](/docs/quick-start/scheduling-a-bill) 10. [Understanding Safe to Spend](/docs/quick-start/understanding-safe-to-spend) ## What is coming [Section titled “What is coming”](#what-is-coming) * **Feature guides** — the register in depth, reconciliation, transfers, reports, imports, and household sharing. ## Elsewhere [Section titled “Elsewhere”](#elsewhere) * [Tovari home](https://www.tovarifinancial.com/) * [Privacy policy](https://www.tovarifinancial.com/privacy) * [Terms of service](https://www.tovarifinancial.com/terms) # Page not found > That page does not exist — it may have been renamed or moved. Try the search box at the top of the page, or start again from the [documentation home](/docs). # Accounts > What an account is in Tovari, the balances it shows, and how accounts work on the web and in the mobile app. ## What accounts are for [Section titled “What accounts are for”](#what-accounts-are-for) An account in Tovari stands for one real place your money sits or is owed: a checking account, a savings account, an investment account, a credit card, or a loan. Everything else in Tovari hangs off accounts — transactions belong to one, the budget spends the money they hold, and Safe to Spend counts only the accounts you tell it to. You can create an account by hand or let a linked bank create it for you. Either way it behaves the same afterwards. ### The type decides more than the icon [Section titled “The type decides more than the icon”](#the-type-decides-more-than-the-icon) Each account is one of five types — **Checking**, **Savings**, **Investment**, **Credit Card**, or **Loan**. The type decides: * which of the four groups the account is filed under: **Cash Accounts** (checking and savings), **Investments**, **Credit Cards**, and **Loans**; * whether its balance counts as something you own or something you owe; * which extra fields you are offered — an interest rate on deposit accounts and cards, a credit limit on cards; * whether the account can count toward [Safe to Spend](/docs/quick-start/understanding-safe-to-spend) at all. Only checking and savings accounts can. Investment accounts, credit cards and loans are excluded and cannot be opted in. A new checking account starts included in Safe to Spend; a new savings account starts excluded. You can change that later on a checking or savings account. ### The balances Tovari shows you [Section titled “The balances Tovari shows you”](#the-balances-tovari-shows-you) Tovari works out an account’s balances on the server and sends you the answers, so every place you look at an account agrees: * **Cleared** — the part of the account that has settled at the bank. * **Uncleared** — what you have recorded that has not settled yet. * **Working balance** — the headline figure, and the one to read when you want “what is in here”. These are meanings, not a sum to reproduce: read the figures Tovari gives you rather than adding them up yourself. ### Investment accounts linked to a brokerage [Section titled “Investment accounts linked to a brokerage”](#investment-accounts-linked-to-a-brokerage) A linked investment account does not use the three balances above. A brokerage reports what an account is worth rather than a stream of purchases to reconcile, so Tovari shows the value it last reported, and the change **since the last update** rather than a monthly one. Opening the account shows its **value history** — dated values, newest first, each with the change from the one before. A linked investment account never receives transactions, so a register would only ever be empty. The history is a record, not a worksheet: values are never edited or reconciled. An investment account you keep by hand is unaffected — it uses the balances above and has an ordinary register. Either way, investment accounts stay out of [Safe to Spend](/docs/quick-start/understanding-safe-to-spend). #### “As of” and “checked” are different claims [Section titled ““As of” and “checked” are different claims”](#as-of-and-checked-are-different-claims) * **as of** — the brokerage said when the value was true, and that is the moment shown. * **checked** — the brokerage gave a value but no time to attach to it, so Tovari shows when it looked. Some brokerages share only an account’s total, and report no time of their own. Tovari never presents its own reading time as the brokerage’s. #### Before the first value arrives [Section titled “Before the first value arrives”](#before-the-first-value-arrives) A newly linked investment account shows a dash until the brokerage sends its first figure. Tovari asks as soon as the account is linked and keeps asking, so this normally clears on its own. A dash means “not yet”, never “zero”. If Tovari needs your permission before it can ask, the account says so and offers a **Reconnect** button — see [Keeping a connection healthy](/docs/features/bank-connections#keeping-a-connection-healthy). ### Closing an account is not deleting it [Section titled “Closing an account is not deleting it”](#closing-an-account-is-not-deleting-it) Closing an account archives it. Its transactions stay, your history stays intact, and the account simply drops out of your everyday lists. You can bring closed accounts back into view whenever you want to look at them. ### The last four digits [Section titled “The last four digits”](#the-last-four-digits) The optional last-four-digits field is for your own recognition. Tovari does not check it for uniqueness, and it is never used on its own to decide anything — if two of your accounts end in the same four digits, Tovari treats a possible match as “no match” rather than guessing. * Web ### Finding your accounts [Section titled “Finding your accounts”](#finding-your-accounts) **Accounts** is in the left-hand navigation, and your accounts also appear in the navigation itself under an expandable list so you can jump straight to one. The screen opens with three tiles across the top — **Total Assets**, **Total Liabilities** and **Net Worth** — and then one collapsible section per group, in the order **Cash Accounts → Investments → Credit Cards → Loans**. ### Adding one [Section titled “Adding one”](#adding-one) Press **Add Account** in the header. You are offered **Connect a bank** and **Add manually**; choosing manual opens the **Add Account** dialog with name, type, bank, last four digits, starting balance, and — on a checking or savings account — the **Include in Safe to Spend** switch. ### Editing one [Section titled “Editing one”](#editing-one) Click an account to open its detail panel. **There is no Save button**: every change you make is saved for you a moment after you stop typing, and the panel tells you when it has saved. Closing an account is done from the same panel, via **Close Account**, with a confirmation. ### Housekeeping [Section titled “Housekeeping”](#housekeeping) * **Search** and a **Show Closed** switch sit in the header. Closed accounts are hidden until you turn that switch on. * **Reordering** is drag-and-drop, and it works **only inside one group** — you cannot drag an account into another group, because the group follows the account type. * **Collapsing** a group is a convenience for the visit you are in; it is not remembered next time. * **Favorites** are a personal marker: starring an account pins it to the top of the navigation list, and it is yours alone — starring an account in a shared household does not change what anyone else sees. ### On a phone browser [Section titled “On a phone browser”](#on-a-phone-browser) Opening the web app on a phone gives you the same accounts, laid out as a full-screen list with an **Add account** control and a full-screen editor instead of a side panel. Two things are not in this layout: **favorites**, and drag-to-reorder. Use **View Desktop Site** in the **More** menu if you need them. * Mobile ### Finding your accounts [Section titled “Finding your accounts”](#finding-your-accounts-1) **Accounts** is one of the tabs in the bottom bar. The screen lists your accounts grouped exactly the way the web groups them, with two differences worth knowing: * the groups are ordered **Cash Accounts → Credit Cards → Loans → Investments**; and * the **Investments** group is hidden entirely until you have at least one investment account. Which type lands in which group is identical to the web — only the order differs. ### Adding one [Section titled “Adding one”](#adding-one-1) Tap **Add account** in the screen header. The sheet leads with **Connect a bank**; below a divider marked **OR TRACK IT MANUALLY** is the manual form — account type as a row of chips, then name, bank, last four digits and starting balance. Tap **Add Account** to finish. During first-run setup the same sheet is reached from **Add an account**. ### Editing one [Section titled “Editing one”](#editing-one-1) Tapping an account opens the **Edit account** sheet, carrying the fields the account’s type allows: bank, last four digits, credit limit and interest rate. Closing an account is available here too. ### What the app does not do [Section titled “What the app does not do”](#what-the-app-does-not-do) * **There is no Safe to Spend switch.** The app sets that flag from the account type when the account is created — checking included, everything else excluded — and cannot change it afterwards. To change an account’s Safe to Spend inclusion, use the web app. * **There are no favorites and no drag-to-reorder.** Both are web features; the order you set on the web is respected here. ## When your bank and your records disagree [Section titled “When your bank and your records disagree”](#when-your-bank-and-your-records-disagree) For a bank-connected account, Tovari sometimes notices that the balance your records add up to and the balance your bank reports have drifted apart — usually because a transaction was delivered twice, or one the bank never sent. When that difference has held across a couple of daily checks, a card appears in the account’s editor, **directly above the Starting Balance field**, showing three lines: what your records say, what your bank says, and the difference between them. The card exists so you don’t fix the difference the wrong way. **Don’t change the Starting Balance field to make the number match** — that silently rewrites your account’s history. Instead, choose **Record the difference**. Tovari adds a single dated entry in a “Starting Balance” category that closes the gap. It’s an ordinary transaction: it shows up in your register, and you can delete it at any time. Before it’s recorded, Tovari shows you the exact amount, its date, and the category it will book to, and asks you to confirm. One thing worth knowing: if the transaction that was missing later arrives on its own, your recorded entry can briefly count it twice. Tovari re-checks every day and will flag it on the same card if that happens, so you can remove the entry — the card will suggest exactly that when it sees a recorded correction and the difference pointing in the same direction. The card never guesses *why* the numbers differ, and it never launches a new bank connection. If a difference keeps coming back after you’ve recorded it, the card points you at your existing bank connection to review — it won’t quietly add a second one. This surface is web and mobile-web only; the difference always rides the account itself, so there is no separate inbox or badge for it. ## Related pages [Section titled “Related pages”](#related-pages) * [Add your first account](/docs/quick-start/add-your-first-account) — the step-by-step version, as part of the Quick start. * [Connect a bank with Plaid](/docs/quick-start/connect-a-bank-with-plaid) — let a bank create and fill an account for you. * [Understanding Safe to Spend](/docs/quick-start/understanding-safe-to-spend) — which accounts count toward the number, and why. * [Transactions](/docs/features/transactions) — the register inside an account, what its statuses mean, and how reconciling an account against a statement works. * [Reading your register](/docs/quick-start/reading-your-register) — the transaction list inside an account. * [Where each feature works](/docs/platform-parity) — the platform map for every documented feature. # Bank connections > How connecting a bank works, how much history comes in, the Starting Balance entry, and what to do when a connection needs attention. ## What a bank connection does for you [Section titled “What a bank connection does for you”](#what-a-bank-connection-does-for-you) Connecting a bank lets Tovari bring your balances and transactions in on their own, so you are reading your money instead of typing it. A connected account behaves like any other account afterwards — you can rename it, categorize its transactions, budget against it and reconcile it. You sign in to your bank inside your bank’s own secure window, and you choose there which accounts to share. **Tovari never sees your bank credentials.** Connecting is always optional. Accounts you keep by hand sit alongside connected ones, and you can connect a bank on the day you sign up, months later, or never. ### One connection per bank [Section titled “One connection per bank”](#one-connection-per-bank) A household has one connection per institution. If you try to connect a bank that is already connected, Tovari stops and tells you which one it is rather than creating a second connection to the same place — additional accounts at that bank are added from the connection you already have. ## How much history comes in [Section titled “How much history comes in”](#how-much-history-comes-in) When a connection is made, Tovari imports some of the account’s past transactions so your register does not start empty. How far back it goes depends on where you connect from, and that is the one real difference between the platforms — see the **Web** and **Mobile** tabs below. Two things are worth knowing whichever way you connect: * **A short window** gets you running quickly with a small, tidy register. * **A long window** gives your reports and your typical-spending figures real history to work with, but takes longer to import and brings in far more to review. The first import runs in the background. Transactions appear in your register as they arrive rather than all at once, so an account that looks thin a minute after connecting is usually still filling. ### If the account already has transactions [Section titled “If the account already has transactions”](#if-the-account-already-has-transactions) Linking a bank to an account that **already holds transactions in Tovari** imports only new activity from that point forward. No past history is pulled in, so connecting cannot duplicate the rows you already have — the account keeps everything you entered, and Tovari picks up from today. ## The Starting Balance entry [Section titled “The Starting Balance entry”](#the-starting-balance-entry) However much history is imported, there is always some that came before it. Tovari accounts for it with a single entry named **Starting Balance**, written into the account when the connection is set up. This applies when the connection creates the account, and when it links to an account that has no transactions in it yet. If you link a bank to an account you have already been keeping by hand, no Starting Balance is added — the starting balance you already gave that account, and the rows you entered since, already cover everything before the connection. And when the account you link is empty but carries an opening balance you typed in yourself, that figure is replaced by the Starting Balance Tovari works out from your bank. It stands in for everything that happened before the imported window. Without it, an account holding ninety days of transactions would show ninety days’ worth of money rather than what is actually in it; with it, the account lines up with what your bank reported at the moment the connection was made. Two things follow from that: * **It is a real entry in your register**, not a hidden adjustment. You can see it, and it explains a balance that would otherwise look unaccounted for. * **It is not a promise that the two figures always match afterwards.** Your bank’s balance and the balance Tovari shows both move as activity lands, and they can differ for a while — a card swipe your bank has authorized may reach your register a little later. That is ordinary and self-correcting; [reconciling](/docs/features/transactions) against a statement is how you confirm a period is genuinely square. ## What happens to a transaction you already entered [Section titled “What happens to a transaction you already entered”](#what-happens-to-a-transaction-you-already-entered) If a payment arrives from your bank that you had already typed in yourself on the same account, Tovari **updates your row rather than adding a second one** — your category, your payee and your note stay exactly as you wrote them. Matching is only ever done within a single account, so a row on one account is never quietly attached to activity on another. The full explanation of how a bank row moves from pending to cleared is on the [Transactions](/docs/features/transactions) page. ## Keeping a connection healthy [Section titled “Keeping a connection healthy”](#keeping-a-connection-healthy) Banks periodically require you to sign in again, and connections can hit trouble at the bank’s end. Tovari shows a connection’s state on the account it belongs to: | State | What it means | What to do | | ----------------- | ------------------------------------------------ | ----------------------------- | | **Connected** | Working normally, with the time of the last sync | Nothing | | **Action needed** | Your bank wants you to sign in again | Reconnect | | **Sync issue** | Tovari is having trouble syncing this account | Reconnect | | **Disconnected** | The connection has been removed | Reconnect if you want it back | **Reconnecting repairs the connection you already have** — you do not lose the account, its history, or anything you edited. **Disconnecting is not deleting.** Everything already imported stays in your register; new activity simply stops arriving. The account remains, and you can go on using it by hand. ### Reconnecting to share an investment balance [Section titled “Reconnecting to share an investment balance”](#reconnecting-to-share-an-investment-balance) Before a brokerage will share what an account is worth it needs your permission specifically for that, and a bank you connected before Tovari offered investment balances was never asked. When that permission is missing the account shows **Reconnect to see this balance**. Use that button rather than adding the bank again: it repairs the connection you already have, keeps every account and edit, and asks for the extra permission on the way through. Adding the bank a second time would leave you with two connections to the same place. An account merely waiting for its first value shows a dash instead and needs nothing from you — see [Investment accounts linked to a brokerage](/docs/features/accounts#investment-accounts-linked-to-a-brokerage). * Web ### Connecting a bank [Section titled “Connecting a bank”](#connecting-a-bank) 1. On **Accounts**, press **Add Account** and choose **Connect a bank**. Setup offers the same choice. 2. Your bank’s secure window opens. Sign in and choose which accounts to share there. 3. Back in Tovari, a dialog lists the accounts you chose so you can confirm them. Anything already connected is marked **Already added** and left out, so it cannot be added twice. 4. Press the confirm button to finish. ### Choosing how much history to import [Section titled “Choosing how much history to import”](#choosing-how-much-history-to-import) The same dialog carries an **Import history** dropdown — this is where the window is chosen: | Option | What it imports | | ------------------------------ | ------------------------------------------------- | | **None (start fresh)** | No past activity — only transactions from now on | | **15 days** | The last two weeks or so | | **30 days** | About a month | | **60 days** | About two months | | **90 days** | About three months — the option Tovari preselects | | **120 days** | About four months | | **All available transactions** | All the history your bank makes available | The dropdown is not offered when the account you are linking already holds transactions; in that case Tovari says so on the spot and imports new activity only. ### Managing a connection later [Section titled “Managing a connection later”](#managing-a-connection-later) Open the account and look at its bank-connection block. It shows the bank’s name, the connection’s state, and when it last synced, along with **Disconnect** — and, when the connection needs attention, **Reconnect**. ### On a phone browser [Section titled “On a phone browser”](#on-a-phone-browser) Opening the web app on a phone gives you the same connection flow and the same **Import history** choices: the confirmation dialog and its dropdown are the same ones the computer layout uses. Managing an existing connection is done in the full-screen account editor, which carries the same bank-connection block — the connection’s state, its last sync, **Reconnect** where it applies, and **Disconnect** — sized for tapping. * Mobile ### Connecting a bank [Section titled “Connecting a bank”](#connecting-a-bank-1) 1. Open the **Accounts** tab and tap **Add account**, then **Connect a bank** at the top of the sheet. On a first run, the empty state’s connect button does the same thing. 2. Your bank’s secure flow opens. Sign in and choose which accounts to share there. 3. The app returns straight to your Accounts list, and the new accounts are in it. There is no follow-up confirmation dialog and no success message — the list you are already looking at is the confirmation. ### How much history the app brings in [Section titled “How much history the app brings in”](#how-much-history-the-app-brings-in) **Connecting a bank in the mobile app brings in about the last 90 days of transactions.** There is no window to choose: the app does not ask, and no dropdown appears anywhere in the flow. Ninety days is enough to give your register and your typical-spending figures something real to work with without pulling a long history down over a phone connection. If you want a different amount of history for a bank — none at all, or everything your bank makes available — connect that bank from the web app, where the history choice is offered. ### Managing a connection later [Section titled “Managing a connection later”](#managing-a-connection-later-1) Open the account from the **Accounts** tab. Its bank-connection block shows the bank and the connection’s state — **Connected**, or **Needs attention** with a short line saying whether the bank wants you to sign in again or the sync itself is having trouble. **Reconnect** repairs it in place, and the block also lets you unlink the connection. ### If the bank is already connected [Section titled “If the bank is already connected”](#if-the-bank-is-already-connected) Connecting a bank your household has already linked stops with a message naming that bank and pointing you back to **Accounts** to work from the existing connection. A second connection to the same bank is never created. ## Related pages [Section titled “Related pages”](#related-pages) * [Accounts](/docs/features/accounts) — what an account is, and how connected and manual accounts sit side by side. * [Transactions](/docs/features/transactions) — the register, what pending means, and reconciling. * [Getting set up](/docs/features/getting-set-up) — where connecting a bank fits into setup. * [Connect a bank with Plaid](/docs/quick-start/connect-a-bank-with-plaid) — the step-by-step version, as part of the Quick start. * [Where each feature works](/docs/platform-parity) — the platform map for every documented feature. # Bills > Scheduled bills in Tovari — why they are a forecast and never post themselves, what Enter and Skip do, and how suggested recurring payments work. ## What a scheduled bill is [Section titled “What a scheduled bill is”](#what-a-scheduled-bill-is) A scheduled bill tells Tovari that a certain amount is expected to leave (or arrive in) a certain account on a certain date, and to keep expecting it on whatever rhythm you set — monthly, weekly, twice a month, quarterly, yearly, and so on. A one-time item is allowed too, for a single future payment you want counted. ### A schedule is a forecast, never an entry [Section titled “A schedule is a forecast, never an entry”](#a-schedule-is-a-forecast-never-an-entry) **Tovari never posts a bill for you.** A schedule cannot create a transaction on its own, no matter how long it has been due. Its job is to let your projections and your [Safe to Spend](/docs/features/safe-to-spend) figure take the payment into account before it happens. The only thing that turns an expected payment into a real one in your register is you. That is the single most important thing on this page, and it is why a bill can sit unpaid for weeks without anything appearing in your account. ### Next due is measured from the schedule, not from today [Section titled “Next due is measured from the schedule, not from today”](#next-due-is-measured-from-the-schedule-not-from-today) Each bill carries its own **next payment date** — the first occurrence Tovari still considers outstanding. Everything else is worked out from there, which has two consequences worth knowing: * **A bill whose first payment is in the past shows up overdue straight away**, dated on the day it was actually due, rather than quietly starting from today. * **An occurrence you never dealt with does not expire.** It stays outstanding, and shows as overdue on its real date, until you enter it or skip it. A backlog is visible rather than silently discarded. The next payment date is editable at any time, which is the manual way to reset a schedule or push it past an occurrence you do not want to deal with individually. ### Enter and Skip [Section titled “Enter and Skip”](#enter-and-skip) Every outstanding occurrence offers the same two actions, and only one of them writes anything. | Action | What it writes | What it does to the schedule | | --------- | -------------------------------------------------------------------------------------------------- | --------------------------------------- | | **Enter** | Records the payment in the register, prefilled from the bill — payee, category, account and amount | Moves the schedule past that occurrence | | **Skip** | Nothing at all | Moves the schedule past that occurrence | So **Skip** means “this one did not happen, move on”. It does not cancel the bill, and the next occurrence appears as normal. **Enter does not blindly create a row.** If your bank has already reported that payment, Tovari attaches the occurrence to the transaction that is already there instead of leaving you with two copies of the same payment. And if the payment is still pending at your bank, Tovari says so and asks you to confirm rather than entering a duplicate on top of money that is already in flight. Where no existing transaction fits, the occurrence is recorded as a new, not-yet-cleared row. **When more than one bank row could be this payment, Tovari asks you which.** Occasionally a handful of pending or not-yet-cleared rows in the same account are an equally good fit for an occurrence — a subscription that charges the same amount every week, say. Rather than guess, Tovari marks the occurrence **Choose payment** and lists every row it is torn between, each with its date, description and amount, so you can pick the one that is actually this bill. If none of them are, **None of these** posts the occurrence as its own new row instead. The same tied bank rows are marked in the register too, so you can start the same choice from whichever side you noticed first — the schedule or the bank activity — and picking from one clears the mark from the other. ### Pausing, finishing and deleting [Section titled “Pausing, finishing and deleting”](#pausing-finishing-and-deleting) A **paused** bill keeps its history and its settings but has nothing outstanding, so it offers no Enter or Skip at all. A schedule that has run to its end — a one-time item you entered, or a recurring one that reached its final payment — is treated as **completed** and is hidden from the everyday list until you ask to see completed items. Deleting a bill removes the schedule; the transactions you already entered from it stay in your register. ### Suggested recurring payments [Section titled “Suggested recurring payments”](#suggested-recurring-payments) When a bank connection shows the same payment arriving over and over with no schedule to match it, Tovari offers it as a **suggestion**: a proposal for a bill you have not created yet. Nothing is scheduled until you save it, and you can dismiss a suggestion you do not want (and restore it later if you change your mind). A suggestion arrives prefilled — the payee, the rhythm it appears to follow, a category, a first date, and **the typical amount**. That amount is an estimate drawn from what the payment has actually been, not a promise about the next one, and Tovari offers you a choice of figures to start from. Every field is yours to change before you save, and each suggestion shows the recent payments it was inferred from so you can check the pattern rather than take it on trust. **Where suggestions appear.** They are offered on the computer layout and in the Tovari mobile app. They are **not** part of the phone-browser layout — open Tovari on a computer, or use the mobile app, to review them. * Web ### The Bills & Schedule screen [Section titled “The Bills & Schedule screen”](#the-bills--schedule-screen) **Bills & Schedule** is in the left-hand navigation. Its header shows how many bills are active and what they add up to each month — out, in, and the net of the two — scoped to whichever accounts you have filtered to. The toolbar above the list carries: * **Add Bill**, which opens the editor panel. * An **account** filter, defaulting to all accounts. * Type filters — **All**, **Recurring**, **One-time**. * **View Options**, which is where **Show Completed Items** lives. * **Search bills**. ### Creating and editing a schedule [Section titled “Creating and editing a schedule”](#creating-and-editing-a-schedule) The editor panel takes the amount and whether it is money out or in, the account, a category, an optional memo carried onto the transaction when you enter one, the frequency with whatever day-of-month or day-of-week control that frequency needs, and the first payment date. It autosaves — there is no Save button. If you set a first payment in the past, the editor checks that you meant it before keeping the date. Once a schedule is running, its **next payment** date is editable directly. ### Entering and skipping [Section titled “Entering and skipping”](#entering-and-skipping) Outstanding occurrences appear at the top of the account’s register, in the **Scheduled Bills** section, each with a tick to enter it and a cross to skip it, and each showing the balance the account is projected to have once it lands. ### Suggested recurring [Section titled “Suggested recurring”](#suggested-recurring) The Bills screen carries a **Suggested Recurring** block among the bills themselves, collapsed by default with a count in its header, so a proposal and the schedules you already have line up column for column. The register carries the same suggestions in its own collapsed section, and a transaction that belongs to a detected recurring payment is marked in the row so you can open the proposal from where you noticed it. ### On a phone browser [Section titled “On a phone browser”](#on-a-phone-browser) Opening the web app on a phone gives you the bills as two tabs — what is **Upcoming** this month, and **All bills**, which includes paused and completed ones — under a band showing what is still owed this month. You can add, edit, pause, enter and skip from here, and search the list (the search is per-visit and is not remembered). Not in this layout: **suggested recurring payments**, per-column sorting, filtering by several accounts at once, and the balance projection chart. Use **View Desktop Site** in the **More** menu if you need them. * Mobile ### The Bills screen [Section titled “The Bills screen”](#the-bills-screen) **Bills** is one of the tabs in the bottom bar. The screen shows your schedules as a timeline, grouped and ordered by when each is next due, under a band summarising the month. A row of **All**, **Recurring** and **One-time** stays on screen beneath it for the switch you make most often. **Search** is its own control in the header: tap it and the list narrows as you type. Closing the field clears what you typed, and the search is never carried over to your next visit. The rest — which accounts to include, the sort, and whether paused or completed schedules are shown — lives in the **Filter & Sort** sheet behind the funnel in the header, where nothing changes until you commit it with **Done** or the **Show N bills** button at the foot of the sheet, and **Reset** puts the sheet back to its defaults. A dot on the funnel means a filter is narrowing the list; an active search does not raise it, because the search field is already there in front of you. ### Creating and editing a schedule [Section titled “Creating and editing a schedule”](#creating-and-editing-a-schedule-1) Tap the **+** in the header for the **New Bill** sheet: amount, account, category, frequency and first payment, then **Save**. Tapping an existing bill opens the same sheet to edit it. ### Entering and skipping [Section titled “Entering and skipping”](#entering-and-skipping-1) There are two routes to the same two actions: * **The action strip.** A bill due within the next week shows an inline **Enter** / **Skip** pair under its row. If an Enter fails, that button becomes **Try again** in place, and Skip stays available — a failed Enter has not used the occurrence up. * **Swipe or long-press.** On iOS, swipe a row right for **Enter** and **Skip**; swipe left for **Pause** or **Resume**, **Edit** and **Delete**. A long swipe fires the first action of the set it revealed, which on the left side is deliberately the reversible one, so a careless swipe can never delete a schedule. On Android, long-press the row for the same menu. A paused bill has nothing outstanding, so it offers no Enter or Skip rather than an action that would be refused. ### Suggested recurring [Section titled “Suggested recurring”](#suggested-recurring-1) The app carries a **Suggested recurring** strip, collapsed by default with the count visible, that opens into one card per proposal — each showing the payee, the rhythm, the typical amount and the payments behind it, with the options to schedule it or dismiss it. If you have no bills at all yet, the empty screen leads with those suggestions, so your first bill can come from what your bank already shows. ## Related pages [Section titled “Related pages”](#related-pages) * [Scheduling a bill](/docs/quick-start/scheduling-a-bill) — the short version, as part of the Quick start. * [Transactions](/docs/features/transactions) — the register the Scheduled Bills section sits in, and what an entered bill looks like once it is there. * [Safe to Spend](/docs/features/safe-to-spend) — how outstanding bills shape the headline figure. * [Budget](/docs/features/budget) — the monthly envelopes your bills are paid out of. * [Bank connections](/docs/features/bank-connections) — where the activity behind a suggestion comes from. * [Where each feature works](/docs/platform-parity) — the platform map for every documented feature. # Budget > How Tovari's envelope budget works — what an envelope is, what carries forward month to month, and how savings goals fit in. ## What the budget is for [Section titled “What the budget is for”](#what-the-budget-is-for) Tovari’s budget is an **envelope** budget. You pick the handful of categories that are worth managing actively, give each one a monthly amount, and Tovari tells you what is left in each as you spend. That is deliberately separate from categorizing. Every transaction you have already carries a category, whether or not you budget it — see [Categories](/docs/features/categories). Budgeting is the smaller, deliberate selection you make on top of that. ### An envelope is something you turn on [Section titled “An envelope is something you turn on”](#an-envelope-is-something-you-turn-on) **Nothing becomes an envelope by itself.** Tovari never decides a category deserves a monthly amount, however much you spend on it. A category is an envelope only because you turned it on, and it stays one until you turn it off. **The choice is not a monthly one.** Turning a category into an envelope is a one-time decision: it stays an envelope in every following month, and what you revisit each month is the amount, not the membership. Categories you leave alone are still tracked in full — they are grouped together on the budget screen and still appear in your reports; they simply have no monthly amount and nothing carrying forward. **Only spending categories can be envelopes.** Income categories, and the built-in ones Tovari maintains for you, are never offered as candidates and cannot be turned into envelopes. ### What carries forward [Section titled “What carries forward”](#what-carries-forward) An envelope keeps a running balance. Whatever you did not spend in a month is added to what is available the following month, so an envelope you underspend gets roomier and one you have been saving into builds up. Three things decide where that running balance starts. * **It accumulates from the month you turned the envelope on.** Tovari does not invent a history for a category from before it was an envelope. * **Turning it on while you are looking at an earlier month pulls the start back to that month** — and so does setting a monthly amount for an earlier month. For as long as the envelope stays on, the start of the accumulation only ever moves earlier, never later. * **Removing an envelope and adding it back later starts the running balance fresh from the month you added it back.** The monthly amount you last set comes back with it automatically, so the envelope reappears with a figure already filled in — but the leftover it had built up before does not come back with it. If you want that history kept, leave the envelope on and set its amount to zero rather than removing it. Overspending does not follow you around either. If you spend more than an envelope holds, that month shows you over, and the next month starts from the amount you set rather than from a debt. Every one of these figures — what is available, what has been spent, what is left, what rolled over — is worked out by Tovari and handed to you. They are numbers to read rather than sums to reproduce: the running balance depends on the whole stretch of months the envelope has been on, so adding up a couple of targets and receipts will not reliably reconstruct it. ### Savings goals [Section titled “Savings goals”](#savings-goals) A **goal** is a yearly amount you want a category to reach, marked so that it appears on your dashboard. It is not a separate thing you create and maintain: it is a mark on that category’s year target, so the goal amount and the target are always the same figure and can never disagree. Two things follow from that: * A goal needs a year target first. Until the category has one, the goal control is unavailable rather than quietly inventing an amount for you. * A goal is a yearly view of one category, not a second monthly plan. A category can carry a goal whether or not it is also an envelope. Progress is worked out by Tovari and is **signed**: a goal you have gone past reads as the amount you are over, never as a reassuring zero. Do not try to reproduce it from your register — refunds, adjustments and money moved between your own accounts are all accounted for in that figure for you. A goal appears on your [dashboard](/docs/features/dashboard) during the year it is set for, so one you mark for next year will not show up today. **Setting a category’s year target is done in the web app on a computer** — that is still the only place a target is created. Once a category has one, opening it on a phone browser also offers a **Track as Goal** checkbox, so you can mark or unmark an existing target’s category as a goal from there too; the checkbox stays disabled until a target exists. The native mobile app shows your budget but carries no goal control at all. * Web ### Finding the budget [Section titled “Finding the budget”](#finding-the-budget) **Budget** is in the left-hand navigation. The screen keeps a header band of the period’s headline figures pinned at the top while the categories scroll beneath it, and offers three views from the switcher beside the title: * **Tracking** — how the month is running. * **Monthly** — the grid of envelopes for one month, with an editable amount on each row. * **Planning** — a whole year at a time, one column per month, with a year target per category. Switching views is not a reload: an edit made in one is already there in the other. ### Turning a category into an envelope [Section titled “Turning a category into an envelope”](#turning-a-category-into-an-envelope) Press **Budget a category** in the header. The picker lists the categories you are already spending on but not budgeting, grouped by section and searchable, each with a **Budget this** action. The category is promoted into the grid for that month and every month after it. The **All Other Categories** row leads to the same categories, alongside what each one actually cost you — useful when you want the spending to choose for you. ### Setting amounts [Section titled “Setting amounts”](#setting-amounts) Click a budgeted amount cell and type. The budget screen autosaves; there is no Save button. Selecting a row opens the details panel beside the grid: the month’s amount, what has been spent, what is left, what rolled over, recent averages, and the same month a year earlier. In **Planning** the panel also carries the category’s **year target** and an action that spreads that target across the months still to come. ### Marking a goal [Section titled “Marking a goal”](#marking-a-goal) Open a category’s details panel in **Planning**, set its **year target**, then tick **Track as Goal**. The category appears on the dashboard’s savings-goals card for that plan year. To change a goal’s amount, change that year target — they are the same figure, which is why the dashboard and the budget can never quote you two different goals. To remove a goal, untick **Track as Goal**; the target itself is left alone, so the category keeps its yearly plan and simply stops appearing on the dashboard. ### Turning an envelope off [Section titled “Turning an envelope off”](#turning-an-envelope-off) Open the category’s editor from the budget screen and use its **remove from budget** action. The category itself is untouched — it keeps its name, its history and its transactions; it simply stops having a monthly amount. Remember that adding it back later restarts the running balance from the month you add it back, while bringing the last amount you set with it. ### On a phone browser [Section titled “On a phone browser”](#on-a-phone-browser) Opening the web app on a phone gives you the same budget as one scrolling list: a **Left to budget** band at the top, income, then your sections with an editable amount box on each envelope’s row, so planning a month never leaves the list. A **Not budgeted** list at the foot offers the categories you are not budgeting yet, and **Add category** creates a new one. Tapping an envelope opens a sheet with what a row cannot show — what rolled over, the recent average, and the option to remove the envelope. If the category already has a year target, the sheet also offers a **Track as Goal** checkbox for it. Year targets themselves and the year-at-a-time Planning view are not in this layout; use **View Desktop Site** in the **More** menu when you need them. * Mobile ### Finding the budget [Section titled “Finding the budget”](#finding-the-budget-1) **Budget** is one of the tabs in the bottom bar. The screen has two views, chosen from the switcher at the top: * **Budget** — how the month is going, envelope by envelope, with what is left on each. * **Plan** — the editing view, where you set each envelope’s amount for the month. The band at the top carries the month’s headline figures and the control for moving between months. ### Turning a category into an envelope [Section titled “Turning a category into an envelope”](#turning-a-category-into-an-envelope-1) At the foot of the **Plan** list is a single **Add category** card. It opens a searchable list of the categories you already have but are not budgeting — tap one and confirm to promote it — and its footer offers to create a new category if the one you want does not exist yet. The **Budget** view also carries a drawer of the categories you are not budgeting, so you can promote one from where you noticed it. ### Setting amounts [Section titled “Setting amounts”](#setting-amounts-1) In **Plan**, each row has an amount box you edit in place; the change is saved when you leave the box, and a failure is reported on that row rather than swallowed. **Auto-fill** offers suggestions — such as what the category has recently averaged — that you can apply to one category or to a whole section, which is quicker on a phone than typing every figure. ### Seeing where an envelope stands [Section titled “Seeing where an envelope stands”](#seeing-where-an-envelope-stands) Tap a budgeted category to open its sheet: its amount, what has been spent, what is left, what rolled over, and its recent average. Removing the envelope is offered from the same sheet. ### What the app does not do [Section titled “What the app does not do”](#what-the-app-does-not-do) * **No savings goals.** Marking a category as a goal is done in the web app on a computer. Goals you have already marked still appear on the dashboard. * **No year-at-a-time planning.** Year targets, and spreading one across the remaining months, are part of the computer layout. ## Related pages [Section titled “Related pages”](#related-pages) * [Categories](/docs/features/categories) — where your categories came from, and why every transaction has one. * [Your first envelope](/docs/quick-start/your-first-envelope) — the short version, as part of the Quick start. * [The budget interview](/docs/quick-start/the-budget-interview) — the guided first pass at choosing envelopes. * [Bills](/docs/features/bills) — the recurring outgoings your budget has to survive. * [Safe to Spend](/docs/features/safe-to-spend) — what your envelopes feed into. * [Dashboard](/docs/features/dashboard) — where your savings goals and budget summary are shown. * [Where each feature works](/docs/platform-parity) — the platform map for every documented feature. # Categories > Where your categories came from, why every transaction has one, and how to rename, reorganize and remove them. ## Where this works [Section titled “Where this works”](#where-this-works) **Managing your categories is a web feature, and it needs the computer layout.** Renaming a category, moving it to a different section, changing its icon or colour, and removing one are all done in the web app on a computer. That is why this page has no separate mobile section: there is one place to do this, and it is a computer. The categories themselves are used everywhere. Putting a transaction in a category, and creating a new category from the budget, both work on a phone browser and in the Tovari mobile app. ## Categorize everything, budget selectively [Section titled “Categorize everything, budget selectively”](#categorize-everything-budget-selectively) Tovari’s rule is that **every transaction carries a category**. Nothing sits blank waiting to be labelled, and nothing drops out of your reports because it was never filed. That is not the same as budgeting. Categorizing is complete and happens for you; budgeting is a small, deliberate selection you make on top of it — a handful of categories you want to manage month to month. See [Budget](/docs/features/budget) for that half. ## Your categories are already yours [Section titled “Your categories are already yours”](#your-categories-are-already-yours) When your account was created, Tovari’s ready-made catalog was **copied into your own categories**. You did not adopt a shared list that Tovari continues to own: you got your own copy on day one, so from the very first transaction there was always somewhere sensible for it to go. Because it is a copy, it is yours to shape: * Rename anything. “Groceries” can become “Food shop” without breaking anything that already points at it. * Move categories between sections, and create sections of your own. * Give a category a different icon or colour — the same one is then used everywhere that category appears. * Add categories the catalog never had, and remove ones you will never use. Changes you make affect only your own household’s categories. ## The Uncategorized fallback [Section titled “The Uncategorized fallback”](#the-uncategorized-fallback) Every household has a protected **Uncategorized** category. It is always there, it cannot be renamed away or deleted, and it is where a transaction lands when nothing could confidently place it. That is what makes “every transaction has a category” true rather than aspirational — Tovari would rather leave a row visibly waiting for you than guess at it. You can also move a row into Uncategorized on purpose, when you want to come back to it. ## Deleting a category does not lose transactions [Section titled “Deleting a category does not lose transactions”](#deleting-a-category-does-not-lose-transactions) When you delete a category, the transactions that were filed under it are **moved to Uncategorized**. They are not deleted, and they are not left pointing at nothing — they simply need re-filing, and they are easy to find because Uncategorized is where they now are. Two related actions are worth telling apart: * **Remove from budget** takes a category out of your monthly envelopes. The category stays, with all its history; it just stops having a monthly amount. See [Budget](/docs/features/budget). * **Delete** removes the category itself, and moves its transactions to Uncategorized as above. ## Where category management lives [Section titled “Where category management lives”](#where-category-management-lives) Categories are managed from the **Budget** screen — that is where the whole list is, grouped into sections. ### Adding a category [Section titled “Adding a category”](#adding-a-category) Press **Budget a category** in the budget header. The picker lists the categories you already have but are not budgeting, grouped by section and searchable, so the usual answer to “I need a category for this” is one that already exists. When it genuinely does not, create a new one from the same screen; you choose its name, its section, and its icon and colour. ### Editing a category [Section titled “Editing a category”](#editing-a-category) Open a category from the budget screen to reach its editor. It carries the category’s identity — name, section, icon, colour, and whether it is one of your budgeted envelopes — and the two destructive actions described above. It autosaves; there is no Save button. ### Sections [Section titled “Sections”](#sections) Sections are the headings your categories are grouped under, on the budget screen and in every category picker. You can add, rename and remove them, and move categories between them. ## Related pages [Section titled “Related pages”](#related-pages) * [Budget](/docs/features/budget) — choosing which categories to manage actively, and what carries forward. * [Categorizing spending](/docs/quick-start/categorizing-spending) — how Tovari decides which category a new transaction belongs in, and what it will never overwrite. * [Transactions](/docs/features/transactions) — changing a row’s category, one at a time or in bulk. * [Payees](/docs/features/payees) — setting a default category for a payee. * [Where each feature works](/docs/platform-parity) — the platform map for every documented feature. # Dashboard > The screen you land on — what each figure means, and the different set of cards you get on a computer, on a phone browser, and in the mobile app. ## What the dashboard is for [Section titled “What the dashboard is for”](#what-the-dashboard-is-for) The dashboard is the answer to “where am I?” — the screen you land on after signing in, and the one to come back to when you want the state of your money in a few seconds rather than a few minutes. It leads with **Safe to Spend**, then shows a set of cards that each open the screen behind them. Nothing on the dashboard is edited in place: a card is a summary and a way in. ## The dashboard is different on each of the three surfaces [Section titled “The dashboard is different on each of the three surfaces”](#the-dashboard-is-different-on-each-of-the-three-surfaces) Tovari runs in three places, and **each of them shows a different set of cards** — chosen for the room available and for what you are likely to want there. A computer has space for the long view; a phone leads with what you can act on now. That means this page is not a single list of cards with different layouts. Read the tab for the place you are actually using, and the [platform map](/docs/platform-parity) if you want to compare them side by side. ## Every figure comes from Tovari [Section titled “Every figure comes from Tovari”](#every-figure-comes-from-tovari) **No dashboard figure is worked out by the screen showing it.** Safe to Spend, your balances, your net worth, your budget totals and your spending breakdowns are all calculated by Tovari and sent to the app, which draws them. Two consequences: * **The surfaces cannot disagree.** The same figure on a computer, a phone browser and the mobile app is the same figure, not three independent sums that happen to line up. * **A figure only changes when your data does.** If a number looks wrong, the answer is in the underlying transactions, accounts or bills — not in the card. Numbers that are still loading, or that could not be loaded, are shown as such rather than as a zero. A dash means “not known yet”, never “nothing”. * Web ### The top of the screen [Section titled “The top of the screen”](#the-top-of-the-screen) The header carries **Safe to Spend** with the end of your planning window, and four figures across from it: **Income Received**, **Total Budgeted**, **Total Spent** and **Net Worth**. Net Worth is a point-in-time figure, so when you are looking at a period longer than a month it is labelled as being *as of today* — the others describe the period you picked. That period is yours to choose: **This month**, **Last month**, **Last 3 months**, or a specific month. An **Add Transaction** control sits in the same row. ### The cards [Section titled “The cards”](#the-cards) The computer layout carries the fullest set: * **Balance projection** — where your balance is heading across the coming weeks, given what is scheduled. * **Spending by category** and **Spending by payee** — where the money in the chosen period went. * **Savings goals** — progress against the goals you have set. * **Watched categories** — the budget categories you have chosen to keep an eye on. * **Upcoming bills** — what is due next. * **Account balances** — every account at a glance. Each card opens the screen behind it, so the dashboard stays a starting point rather than a place you work in. ### On a phone browser [Section titled “On a phone browser”](#on-a-phone-browser) The phone-browser dashboard is a shorter, tap-first set rather than the computer layout squeezed down: * **Safe to Spend** across the top; tapping it opens the account-by-account breakdown as a full-height sheet. * Three quick figures — **Income**, **Spent** and **Net Worth**. * **Your budget** — the month’s categories in brief, with a way through to the Budget screen. * **Upcoming Bills** — what is due next, with a way through to Bills. * **Recent Activity** — the latest transactions, with a way through to Accounts. The spending-by-category, spending-by-payee, savings-goals, watched-categories and account-balances cards are not in this layout. Use **View Desktop Site** in the **More** menu, or open Tovari on a computer, to see them. * Mobile ### The Home tab [Section titled “The Home tab”](#the-home-tab) The dashboard is the **Home** tab. Its header band leads with **Safe to Spend**: the figure, the state written out in words — never colour alone — the end of your planning window, and three tiles showing what is expected in, what is expected out, and roughly what that leaves per day. **Breakdown** on that band opens the account-by-account view. As you scroll, the band collapses to a compact strip that keeps the figure and the way into the breakdown on screen. The header also carries a notifications control and a control for adding a transaction from anywhere. ### The cards [Section titled “The cards”](#the-cards-1) Below the band, the Home tab shows: * A month strip: **Budgeted**, **Spent** and **Left**. * **Your budget** — the month’s categories, with a way through to the Budget screen. Until you have budgeted anything, a card offers to set that up instead. * **Balance projection** — where your balance is heading, given what is scheduled. * **Favorite accounts** — the accounts you have starred. * **Coming up** — the bills due next. * **Recent activity** — your latest transactions. ### When you are new, or something is wrong [Section titled “When you are new, or something is wrong”](#when-you-are-new-or-something-is-wrong) Until you have an account connected, Home offers a card for connecting one and a short list of next steps, so an interrupted setup is easy to finish. If the app is offline it says so and keeps showing the last figures it has, marking them as not current; if a figure genuinely cannot be loaded you get a retry rather than a misleading zero. ### What is not here [Section titled “What is not here”](#what-is-not-here) The spending-by-category, spending-by-payee, savings-goals, watched-categories and account-balances cards are part of the computer layout only. Reports in the mobile app cover some of that ground; the rest is on the web. ## Related pages [Section titled “Related pages”](#related-pages) * [Safe to Spend](/docs/features/safe-to-spend) — what the headline figure is built from. * [Accounts](/docs/features/accounts) — the balances behind the account cards. * [Transactions](/docs/features/transactions) — the activity every figure here is built on. * [Budget](/docs/features/budget) — your envelopes, and where the savings goals shown here are created. * [Getting set up](/docs/features/getting-set-up) — what happens before you first land here. * [What Tovari does](/docs/quick-start/what-tovari-does) — the overview, as part of the Quick start. * [Where each feature works](/docs/platform-parity) — the platform map for every documented feature. # Data and privacy > Download a complete copy of your Tovari data, and how to ask for your account to be erased. ## What this covers [Section titled “What this covers”](#what-this-covers) Two things you can do with your own data: take a complete copy of it with you, and ask for it to be erased. Taking a copy is self-service and takes about a minute. Erasure is handled by a person, on request — see below. Web only Data and privacy is in the web app, on a computer or in a phone browser. It is not in the Tovari mobile app. ## Downloading a copy of your data [Section titled “Downloading a copy of your data”](#downloading-a-copy-of-your-data) Choose **Export my data**. Tovari packages everything up — you will see *Preparing your export…* while it works — and then offers **Download (.zip)**. ### What is in the archive [Section titled “What is in the archive”](#what-is-in-the-archive) Your accounts, transactions, budgets, bills, payees and profile are all packaged into the ZIP, one file per section. The app shows you a **What’s included in your export** breakdown listing each section and how many records it holds, so you can check the archive is complete before you download it. Not included: security logs, raw bank connection credentials, and Tovari’s own internal reference data. All amounts in the archive are in cents, in US dollars. If you share a household, the sections that belong to one person — your preferences and your favourites — contain only your own records. ### How long the download stays available [Section titled “How long the download stays available”](#how-long-the-download-stays-available) Two different clocks apply, and it is worth knowing which is which: * **The download link is short-lived.** It is good for about fifteen minutes from the moment you ask for it. If it lapses, come back to the page and download again — you do not need a new export. * **The export itself lasts a day.** After roughly 24 hours it is cleared, and the page will tell you *This export is no longer available. Request a new export.* ### Asking for another one [Section titled “Asking for another one”](#asking-for-another-one) There is a short cooldown after an export is ready before you can generate a fresh one, so a repeated click cannot queue up several copies of the same archive. Once it lifts, **Generate a new export** produces a current one. ## Asking for your account to be erased [Section titled “Asking for your account to be erased”](#asking-for-your-account-to-be-erased) There is no delete button, and that is deliberate rather than an omission — erasure is permanent and is handled by a person. Email **** and Tovari will permanently delete everything within 60 days of confirming it is you. If you want a copy of your data, take the export **before** you ask for erasure. Once the erasure is done there is nothing left to export. ## Related pages [Section titled “Related pages”](#related-pages) * [Accounts](/docs/features/accounts) — the accounts that make up most of an export. * [Transactions](/docs/features/transactions) — the register the transaction records come from. * [Where each feature works](/docs/platform-parity) — what is available on which platform. # Email verification > Why Tovari asks you to confirm your email address, and what to do when the code does not arrive. ## Why Tovari asks [Section titled “Why Tovari asks”](#why-tovari-asks) Your email address is how Tovari reaches you — a password reset, an invitation to a household, a reply when you report something. Confirming it once proves the address works and belongs to you. Tovari emails you a code shortly after you sign up. Until you enter it, Tovari asks for it whenever you sign in. ### One answer, everywhere [Section titled “One answer, everywhere”](#one-answer-everywhere) Whether your address is confirmed is a single fact about your account, not a per-device setting. Confirm it in the web app and the mobile app already knows; confirm it in the app and the web app does too. There is nothing to repeat on your other devices. ### If the code does not arrive [Section titled “If the code does not arrive”](#if-the-code-does-not-arrive) Ask for another one. Tovari limits how often it will send, so that a stuck inbox cannot turn into a flood: * There is a short wait — about **30 seconds** — between one request and the next. * You can request up to **five** codes in an hour. * If Tovari has already emailed you very recently, signing in again will not send another copy on top of it. That is deliberate quiet, not a failure. If you hit the limit, Tovari says so and tells you to try again shortly rather than silently doing nothing. Check your spam folder before spending requests — the message comes from Tovari’s own address, and a first message from a new sender is the one most likely to be filtered. * Web ### Confirming your address [Section titled “Confirming your address”](#confirming-your-address) After you sign up — or the next time you sign in with an unconfirmed address — Tovari shows the verification step with a field for the code from your email. Enter it and you go straight on to what you were doing. ### Asking for another code [Section titled “Asking for another code”](#asking-for-another-code) The same screen offers to send a new code. The button tells you when it is available again rather than failing quietly if you press it too soon. ### On a phone browser [Section titled “On a phone browser”](#on-a-phone-browser) The verification step appears the same way in the phone-browser layout, sized for a phone keyboard. * Mobile ### Confirming your address [Section titled “Confirming your address”](#confirming-your-address-1) The app shows the verification step over the top of the app after sign-in, with the same code field and the same resend option. Entering the code dismisses it and returns you to where you were going. ### Asking for another code [Section titled “Asking for another code”](#asking-for-another-code-1) Requesting a new code works exactly as it does on the web, and the same waiting periods apply — they belong to your account, not to the device, so switching between the app and the web app does not give you a fresh set of attempts. ## Related pages [Section titled “Related pages”](#related-pages) * [Signing in](/docs/features/signing-in) — the three ways into your account. * [Legal policies](/docs/features/legal-policies) — the other thing Tovari may ask for at sign-in. * [Getting help](/docs/features/getting-help) — if a code never arrives at all. * [Where each feature works](/docs/platform-parity) — what is available on which platform. # File import > Bring transactions into Tovari from a CSV, OFX or QFX file you download from your bank. ## What file import is for [Section titled “What file import is for”](#what-file-import-is-for) File import is how you bring history into Tovari from a file your bank gives you, rather than by typing it in or linking the bank. It is the right tool for a bank Tovari cannot link, for the years of history a fresh link does not reach back to, and for the one-off statement you want in your register. An import always goes into **one account that you choose**. Nothing is written to your register until you have seen exactly what will be added and confirmed it. ### The files Tovari reads [Section titled “The files Tovari reads”](#the-files-tovari-reads) Tovari accepts three extensions, up to **5 MB** per file: * **`.csv`** — a spreadsheet-style export. You tell Tovari which column means what. * **`.ofx`** — a banking-format download. Nothing to map; the format already names its fields. * **`.qfx`** — the same thing under a different extension. QFX is an OFX dialect, and Tovari reads it exactly as it reads OFX. If your bank offers a “Quicken” download and it lands as `.qfx`, it will work. If your bank offers a choice, take OFX or QFX: the mapping step disappears and there is less to get wrong. ### Tovari checks the file against what you already have [Section titled “Tovari checks the file against what you already have”](#tovari-checks-the-file-against-what-you-already-have) Before you see anything, Tovari compares every row in the file against your existing register and your scheduled bills, and sorts them for you: * **New Transactions** — nothing like this is in your register. These import. * **Needs Review** — close to something you already have, but not close enough for Tovari to decide on its own. You confirm or skip each one. * **Matched — Register** — this row *links to a register entry* you already have, rather than becoming a second copy of it. * **Matched — Bills** — this row *enters a scheduled bill* that was waiting for it. * **Already Imported — Skipped** — Tovari has seen this exact transaction before and will not add it again. This is why importing the same statement twice is safe: the second pass lands almost entirely in the last group. Web only File import is available in the web app on a computer. It is not in the phone-browser layout and not in the Tovari mobile app. ## Starting an import [Section titled “Starting an import”](#starting-an-import) Open the register for the account you want to import into and choose **File Import** in the row of actions above the transactions. Pick your file, and Tovari begins reading it. While it works you will see it *Reading* your file, and then *Identifying unfamiliar merchants…* — Tovari is turning raw bank descriptions into payee names you will recognise. ## Mapping the columns of a CSV [Section titled “Mapping the columns of a CSV”](#mapping-the-columns-of-a-csv) A CSV has no standard shape, so Tovari shows you its best guess at what each column means and lets you correct it. You can set: | Field | What it is | | ---------------------- | ------------------------------------------------------------------------------- | | **Date** | The transaction date. | | **Description** | The raw text your bank supplies. Tovari turns this into a payee name. | | **Amount** | A single signed column, if your bank uses one. | | **Debit** / **Credit** | Two separate columns, if your bank splits money out and money in. | | **Check #** | The cheque number, if the file carries one. | | **Post Date** | The date the transaction settled, where that differs from the transaction date. | Use **Amount** on its own, or **Debit** and **Credit** together — whichever matches your file. You can also tell Tovari how many rows to skip before the data starts (useful when a bank puts a title or an account summary above the header row) and which date format the file uses. ### Save the mapping and you only do this once [Section titled “Save the mapping and you only do this once”](#save-the-mapping-and-you-only-do-this-once) Tick **Save this mapping for future imports of this account** and Tovari keeps the column layout for next time. Banks rarely change their export format, so the next import of the same account skips straight past this step. ## Reviewing before anything is written [Section titled “Reviewing before anything is written”](#reviewing-before-anything-is-written) The review screen is the last stop before your register changes. Transactions are listed under the five groups above, each showing its **Date**, **Payee**, **Category** and **Amount**. * Use **Include** or **Skip** on any single row to change your mind about it, and **Restore** to bring back something you skipped. * Where a whole group can be actioned at once, **Confirm all** and **Skip all** do it in one go. * A row that still needs your decision is marked **Confirm to import**. * A row flagged **Possible duplicate in file** appears more than once inside the file you uploaded — worth a look, because that is your bank’s doing rather than Tovari’s. * You can correct a payee name in place while you are here. When you are happy, the button at the bottom tells you exactly what you are about to do — **Import 6 Transactions**, or whatever your count is — and only those transactions are written. **Cancel** discards the whole import; nothing you did on this screen has touched your register yet. ## Related pages [Section titled “Related pages”](#related-pages) * [Transactions](/docs/features/transactions) — the register your imported transactions land in. * [Bank connections](/docs/features/bank-connections) — linking a bank so transactions arrive on their own. * [Payees](/docs/features/payees) — how Tovari turns raw bank text into names you recognise. * [Where each feature works](/docs/platform-parity) — what is available on which platform. # Getting help > Reporting a bug, sending a suggestion or asking a question from inside Tovari, and what happens next. ## Telling Tovari something is wrong [Section titled “Telling Tovari something is wrong”](#telling-tovari-something-is-wrong) Reporting a problem sends a message straight to the people who build Tovari, with enough context attached that they can usually work out what happened without a back-and-forth. You do not need to find an email address or open a support site. Open the help button in Tovari and report it from there. On a PC or Mac, and in a phone browser, that button sits in the bottom-right corner of the screen, labelled **Ask Tovari** on a computer. In the Tovari mobile app it is the help control in the header at the top of the screen, on Dashboard, Accounts, a register, Budget, Bills and Reports — tap it and choose **Ask about this screen**. See [Help chat](/docs/features/help-chat) for what else that panel does. Reporting works the same way in all three, and everything you send reaches the same place. ## Reporting it in the chat [Section titled “Reporting it in the chat”](#reporting-it-in-the-chat) The quickest way is to just say what happened. If you tell the assistant what you were doing, what you expected and what happened instead, it can write the report for you. It may ask one or two follow-up questions first if it needs more detail. Once it has enough, it shows you the draft: the kind (bug, suggestion, or question), a summary, and a description, exactly as it would be filed. You can edit any of it before sending. Nothing is filed until you choose **File it** — the assistant never sends a report on your behalf, and **Cancel** discards the draft without sending anything. As with the form, your current screen, the browser or device you are using, and the app version are attached automatically, so you never need to describe those yourself. If the assistant is unavailable, filing still works — the panel falls back to the same plain form described below. You can also switch to that form yourself at any time with **Report a problem instead**. ## What you send [Section titled “What you send”](#what-you-send) The form asks for two things: * **Summary** — a short line describing the issue. Up to 200 characters. * **Description** — the detail: what you did, what you expected, what happened instead. Up to 5,000 characters. You also choose what kind of report it is: | Kind | Use it for | | -------------- | ------------------------------------------------ | | **Bug** | Something is broken or behaving wrongly. | | **Suggestion** | Something works, but it could be better. | | **Question** | You want to know how something is meant to work. | The kind matters for what happens afterwards, so it is worth picking honestly rather than filing everything as a bug. ### Be specific about the money, not with the money [Section titled “Be specific about the money, not with the money”](#be-specific-about-the-money-not-with-the-money) The most useful reports name the screen, what you were doing, and what you expected instead. You do not need to include account numbers or balances — Tovari’s team can already see your account when they investigate, and a report is not the place to type sensitive details. ## What happens next [Section titled “What happens next”](#what-happens-next) **You get an acknowledgement by email**, so you know it arrived rather than wondering: > Thanks for letting us know — your report is filed and the team can see it. **For a bug or a suggestion, you get a second email when it is fixed and live** — not when someone starts on it, and not when it merges, but when the change is actually running in Tovari: > This is now fixed and live in Tovari. **A question does not get that second email**, because a question is not something a release makes true. If you asked a question, watch for a reply instead. Either email can be replied to directly, and the reply reaches support. If something is still happening after you were told it was fixed, replying to that message is the fastest way to reopen it. ## Related pages [Section titled “Related pages”](#related-pages) * [Data and privacy](/docs/features/data-and-privacy) — exporting your data, and asking for erasure. * [Signing in](/docs/features/signing-in) — if the problem is getting into your account at all. * [Where each feature works](/docs/platform-parity) — what is available on which platform. # Getting set up > What happens after you sign up — the two setup steps, what you can skip, and how setup differs on the web and in the mobile app. ## Setup starts the moment your account exists [Section titled “Setup starts the moment your account exists”](#setup-starts-the-moment-your-account-exists) Once you have signed up, Tovari walks you through setup. It is short on purpose: **two steps, in this order, and both of them can be skipped.** 1. **Add your accounts** — the places your money actually sits. 2. **The budget interview** — which of your spending you want to manage with an envelope. That is the whole of setup, and it is the same two steps in the same order wherever you signed up. When you finish (or skip), you land on your dashboard with a working app. ## Step 1 — Add your accounts [Section titled “Step 1 — Add your accounts”](#step-1--add-your-accounts) Setup opens on **Add your accounts**. You have two ways to add one, and you can mix them freely: * **Connect a bank.** The account is created for you, and its balances and transactions keep themselves up to date. See [Bank connections](/docs/features/bank-connections). * **Add one by hand.** You give it a name, a type, and a starting balance, and you record its transactions yourself. See [Accounts](/docs/features/accounts). Everything you add appears in a short list on the step as you go, so you can see what you have so far and add another. **You do not have to add anything here.** The button at the bottom reads *Skip for now* until you have at least one account, and reads *Continue* once you do. Adding accounts later from the Accounts screen works exactly the same way — nothing about setup is a one-time offer. ## Step 2 — The budget interview [Section titled “Step 2 — The budget interview”](#step-2--the-budget-interview) The second step asks **what do you want to budget?** — a few short questions, each answered by tapping as many choices as apply. This is not a list of things Tovari will start tracking. **Tovari already tracks all of it.** Its full category library is added to your household the moment you sign up, so every transaction can be categorized from day one. The interview asks the narrower question: of everything already being tracked, which handful do you want to *manage* with a budget envelope and a monthly target? That is why there is no “choose what to track” step anywhere in setup. There is nothing to choose — you already have everything. **Picking nothing is a valid answer.** Your spending is still categorized, your register still works, and you can flag an envelope at any time from the Budget screen. ## What setup does not ask you for [Section titled “What setup does not ask you for”](#what-setup-does-not-ask-you-for) * **It does not ask you to connect a bank.** Manual accounts are a first-class way to use Tovari, and you can add a connection later. * **It does not ask you to categorize anything.** That happens as transactions arrive. * **It does not ask you to set amounts.** The interview flags which categories you want to budget; you set the numbers later on the Budget screen. If something goes wrong part-way through the interview, Tovari tells you how much of your selection it saved and offers both a retry and a way straight to the dashboard — you are never stuck on the last step of setup. * Web ### What the accounts step looks like [Section titled “What the accounts step looks like”](#what-the-accounts-step-looks-like) The window splits: Tovari branding on the left, the step itself on the right, headed **Add your Accounts** with the line *Add the accounts you want to track. You can always add or edit more later.* Two short help links sit under it — one for adding an account, one for connecting a bank. With no accounts yet, the body is a large dashed panel reading **Add your first account**. Once you have one, the panel is replaced by your account list plus an **Add another account** button. Choosing to add an account offers the same two options described above; picking the manual route opens the **Add Account** dialog with name, type, bank, last four digits, starting balance, and — on a checking or savings account — the **Include in Safe to Spend** switch. The footer button reads **Skip for now** with no accounts and **Continue →** once you have one. ### What the budget interview looks like [Section titled “What the budget interview looks like”](#what-the-budget-interview-looks-like) The interview takes over the right panel entirely, headed **What do you want to budget?** with its questions rendered as rows of multi-select chips. The footer button counts your picks: it reads **Skip for now →** with nothing selected and **Budget *N* items →** otherwise. Either way, the next thing you see is your dashboard. ### On a phone browser [Section titled “On a phone browser”](#on-a-phone-browser) Opening the web app on a phone runs the **same two steps in the same order**. The branding panel is dropped — it would squeeze the content to nothing on a narrow screen — so each step fills the width under a compact step header, and the account list, the add controls and the footer button behave exactly as described above. * Mobile ### What the accounts step looks like [Section titled “What the accounts step looks like”](#what-the-accounts-step-looks-like-1) Setup opens on **Add your accounts**, with the line *Connect a bank or add an account manually. You can always add more later.* and two short help links under it — one for adding an account, one for connecting a bank. With nothing added yet the body reads *No accounts yet. Add one to get started.* Each account you add appears as a card showing its name and, where known, its bank. **Add an account** opens a sheet that leads with connecting a bank and, below a divider, the manual form — account type as a row of chips, then name, bank, last four digits and starting balance. The button at the bottom reads **Skip for now** until you have an account and **Continue** after that. ### What the budget interview looks like [Section titled “What the budget interview looks like”](#what-the-budget-interview-looks-like-1) The second screen is headed **What do you want to budget?** with the subline *Pick the categories you want to keep an eye on. You can change these any time.* Each question is a row of tappable chips sized for a finger — tap to select, tap again to clear — and a help link explains the step. The button at the bottom counts your picks in the same way as the web: **Skip for now →** with nothing selected, **Budget *N* items →** otherwise. Finishing takes you to the Home tab. If only part of your selection could be saved, the screen says how many of how many were added and offers **Retry** alongside **Continue to Dashboard →**. ### After setup [Section titled “After setup”](#after-setup) The Home tab keeps helping for a while: until you have accounts and a budget, it offers a card for connecting an account and a short list of next steps, so an interrupted setup is easy to pick up again. ## Related pages [Section titled “Related pages”](#related-pages) * [Accounts](/docs/features/accounts) — what an account is, the balances it shows, and how to add, edit and close one. * [Bank connections](/docs/features/bank-connections) — linking a bank, choosing how much history to bring in, and keeping the connection healthy. * [Transactions](/docs/features/transactions) — the register, the four statuses, and reconciling. * [Dashboard](/docs/features/dashboard) — what you land on when setup is done. * [Safe to Spend](/docs/features/safe-to-spend) — the headline number setup is feeding. * [Create your account](/docs/quick-start/create-your-account) — the step before this one. * [The budget interview](/docs/quick-start/the-budget-interview) — the step-by-step version, as part of the Quick start. * [Where each feature works](/docs/platform-parity) — the platform map for every documented feature. # Help chat > The in-app assistant that answers how-to questions from this documentation, takes you to the right screen, and files a bug or suggestion for you. ## What the assistant is for [Section titled “What the assistant is for”](#what-the-assistant-is-for) There is a help button in Tovari. Open it and you can ask how something works in your own words — “how do I add a transaction”, “what does uncleared mean”, “how do I set a budget” — and get an answer without leaving the screen you are on. Where that button sits differs by where you are running Tovari, and **Asking a question** below says where to find it in each. It answers **from this documentation**. That is the whole basis of what it knows: it reads the pages you are reading now and explains what they say. It is not searching the web, and it is not making things up from general knowledge. The assistant is available everywhere Tovari runs: on a PC or Mac, in a phone browser, and in the Tovari mobile app. ## What it can and cannot see [Section titled “What it can and cannot see”](#what-it-can-and-cannot-see) **It cannot see your money.** The assistant has no access to your accounts, balances, transactions, budget figures or payees. It knows which screen you are on and it knows the documentation, and that is all. So it can tell you *where* your working balance is shown and what the number means, but it cannot tell you *what* your balance is. That is a deliberate limit rather than a missing feature. Your financial data never goes into the assistant. ## It only talks about Tovari [Section titled “It only talks about Tovari”](#it-only-talks-about-tovari) The assistant is limited to Tovari and its documentation, on purpose. Ask it something outside that and it will say so plainly rather than attempting an answer: > I can only help with Tovari and its documentation. That one is outside what this assistant covers. **A refusal is the assistant working correctly, not failing.** Three kinds are worth recognising: * **Not about Tovari** — general knowledge, other software, writing tasks. Declined as above. * **Advice about your own money** — whether to pay off a card first, whether to save or invest. The assistant will not weigh in on what you should do with your money. It will offer to explain how Tovari’s tools work instead — budget envelopes, Safe to Spend, and the reports that show where your money actually went. * **A Tovari question the documentation does not cover** — this one is not a refusal so much as an honest gap. The assistant says the documentation does not cover it and offers a **Report this gap** button underneath. Press it once and the question is filed for you — there is no form to fill in and nothing to write, because your question is the report. You get the issue number back in the chat, and the usual acknowledgement email. The third case is the one worth taking it up on. It is how the gaps in these pages get found. ## What changed recently [Section titled “What changed recently”](#what-changed-recently) The assistant knows what has shipped in the **three most recent releases**, so you can ask whether something is new or was recently changed without going hunting: > what’s new in this release > > has anything changed recently > > what was fixed in the latest version Answers about releases link to [What’s New](/docs/whats-new), where the full notes for every version live. Two limits are worth knowing. It only goes back three releases — ask about something older and it will say so rather than guess. And release notes describe what *changed*, never how a feature *works*: ask how to do something and you get the documentation page for it, which is the right answer. A feature not appearing in the recent notes only means it did not change recently, not that Tovari lacks it. ## Asking a question [Section titled “Asking a question”](#asking-a-question) **Where the button is.** On a PC or Mac it sits in the bottom-right corner of the screen, labelled **Ask Tovari**; in a phone browser it is the same corner button without the label. In the Tovari mobile app it is the help control in the header at the top of the screen, on Dashboard, Accounts, a register, Budget, Bills and Reports. Tapping it there offers two things — **Ask about this screen**, which opens the assistant, and **Documentation**, which opens the written guide for that screen in your browser. One control, because a phone’s header has room for one. Open the assistant and it greets you with the screen you are on and two or three suggested questions relevant to that screen — tap one instead of typing if it matches what you wanted. The suggestions are tailored to the screen, so the ones on Budget differ from the ones on Accounts. Type into **Ask about how Tovari works** and send. Answers take a few seconds; you will see a thinking indicator while it works. Nothing is streamed word by word — the answer arrives complete. Every answer that comes from a documentation page **links to that page**, so you can read the full version if the short answer was not enough. ### Take me there [Section titled “Take me there”](#take-me-there) When the answer is about something on a different screen, the assistant offers a **Go to…** button underneath it. Pressing it moves you to that screen inside Tovari. This is separate from the documentation link on the same answer: the link opens the page that explains the feature, the button takes you to the feature itself. * Web On a PC or Mac the assistant opens as a panel above the help button, and the panel stays open when you navigate — so you can read the answer and land on the new screen at the same time. * Mobile On a phone the assistant opens as a sheet from the bottom of the screen — in a phone browser and in the Tovari mobile app alike. Swipe it down or use your device’s back gesture to dismiss it; in a phone browser you can also press Escape. Navigating closes the sheet, because it would otherwise cover the screen you asked to be taken to. A few destinations have no equivalent on the phone you are using, and there the assistant simply offers no button rather than sending you somewhere that does not exist. In a phone browser that is mainly the Review Center. In the mobile app the Review Center **is** there — it is the **Alerts** tab — and the two reports the app does not carry, Net Worth and Safe to Spend, are the ones with no button. You still get the answer and its documentation link either way. ## Reporting a bug or a suggestion [Section titled “Reporting a bug or a suggestion”](#reporting-a-bug-or-a-suggestion) The assistant is also how you tell Tovari something is wrong. Describe what happened — what you were doing, what you expected, what happened instead — and it writes the report for you, asking a follow-up question or two if it needs more detail. It then shows you the draft exactly as it would be filed: the kind (bug, suggestion or question), a summary and a description. **You can edit any of it, and nothing is sent until you press File it.** **Cancel** discards the draft and files nothing. Your current screen, the browser or device you are using, and the app version are attached automatically, so you never have to describe those. That review step is for reports you and the assistant wrote together, about something only you witnessed. A **documentation gap** is different — the report is your own question, which you just typed — so that one files on a single press with no draft to check. See *It only talks about Tovari* above. If the assistant is unavailable, **filing still works** — the panel falls back to a plain form. That matters: reporting a problem must never depend on the assistant being up. Reporting is also never restricted by your plan. The full picture of what happens after you file — the acknowledgement email, and the second email when a bug or suggestion is actually fixed and live — is on [Getting help](/docs/features/getting-help). ## When the assistant is limited [Section titled “When the assistant is limited”](#when-the-assistant-is-limited) Answering questions costs Tovari money, so there are limits. If you ask a great many questions in a short time, the assistant will tell you plainly that you have reached a limit and roughly when you can ask again. There are also occasions when it is briefly unavailable altogether. In every one of those cases the assistant still points you at the documentation page for the screen you are on, and **filing a bug or suggestion still works**. You never lose the ability to reach the team. ## Related pages [Section titled “Related pages”](#related-pages) * [Getting help](/docs/features/getting-help) — what happens after you file a report, and the emails you get. * [Where each feature works](/docs/platform-parity) — the platform map for every documented feature. * [Data and privacy](/docs/features/data-and-privacy) — what Tovari stores, exporting your data, and asking for erasure. # Household > Sharing your Tovari books with one other person — inviting them, what they can see, and removing them. ## What a household is [Section titled “What a household is”](#what-a-household-is) A household is one shared set of books. Everyone in it sees the same accounts, the same register, the same budget and the same bills — because for a couple running one financial life, two separate copies of the truth is the problem, not the feature. ### A household holds two people [Section titled “A household holds two people”](#a-household-holds-two-people) Tovari is built for you and one other person. When your household is full, the invite screen says so: > Your household is full. A household can have two people — remove a member or revoke a pending invite to add someone new. A pending invitation counts toward the two. If you invited the wrong address, revoke it and the place frees up immediately. ### What the other person can see [Section titled “What the other person can see”](#what-the-other-person-can-see) Everything in the shared books: accounts and balances, every transaction, the budget, bills, payees and reports. Sharing a household is sharing the money, not a filtered view of it — invite someone you would show your bank statements to. A few things stay yours alone rather than being shared, because they describe how *you* use Tovari rather than what the money did — your register view preferences and your favourite accounts among them. ### Invitations expire [Section titled “Invitations expire”](#invitations-expire) An invitation is good for **seven days**. After that it stops working and you send a new one. That is a security property, not an inconvenience: an invitation link that lived forever in an old inbox would be a standing key to your finances. * Web ### Finding your household [Section titled “Finding your household”](#finding-your-household) Open **Settings**, then **Household**. It lists who is in the household and any invitation still waiting to be accepted. ### Inviting someone [Section titled “Inviting someone”](#inviting-someone) Choose to add someone and enter their email address. Tovari emails them an invitation and shows you the link, so you can pass it on yourself if the email is slow or goes astray. They do not need a Tovari account first — accepting the invitation walks them through creating one, and they land in your household rather than in books of their own. ### Managing who is in it [Section titled “Managing who is in it”](#managing-who-is-in-it) * A pending invitation can be **revoked** before it is accepted, which frees the place immediately. * A member can be **removed**. Tovari asks you to confirm, because it ends their access to the shared books. Removing someone does not delete anything they entered. The transactions, payees and budget decisions they made stay exactly where they are — the books are the household’s, not the person’s. ### On a phone browser [Section titled “On a phone browser”](#on-a-phone-browser) The Household section works the same way in the phone-browser layout: the same roster, the same invite flow, the same revoke and remove actions. * Mobile ### Finding your household [Section titled “Finding your household”](#finding-your-household-1) Open **Settings**, then **Household**. The app shows the same roster and the same pending invitations as the web app. ### Inviting and managing [Section titled “Inviting and managing”](#inviting-and-managing) Inviting someone, revoking an invitation that has not been accepted, and removing a member all work in the app. The two-person limit and the seven-day invitation lifetime are properties of your household, so they behave identically wherever you are looking. ## Related pages [Section titled “Related pages”](#related-pages) * [Data and privacy](/docs/features/data-and-privacy) — what a shared household means for an export. * [Settings](/docs/features/settings) — where the Household section lives. * [Accounts](/docs/features/accounts) — the accounts a household shares. * [Where each feature works](/docs/platform-parity) — what is available on which platform. # Legal policies > When Tovari asks you to accept its terms and privacy policy, and what happens if you would rather not. ## When Tovari asks [Section titled “When Tovari asks”](#when-tovari-asks) Tovari asks you to accept its policies twice in the life of an account: once when you first sign up, and again whenever one of them is updated. There are three: the terms of use, the privacy policy, and the cookie policy. You will not be asked at any other time, and you are not asked once per device. ### Accepting once covers every device [Section titled “Accepting once covers every device”](#accepting-once-covers-every-device) Acceptance belongs to your account. Accept on the web and the mobile app already knows; accept in the app and the web app does too. Whichever one you happen to sign in to next simply lets you straight through. ### Reading before accepting [Section titled “Reading before accepting”](#reading-before-accepting) The current text of each policy is available to read in full at the moment you are asked — you do not have to accept it to find out what it says, and you do not have to leave Tovari to read it. The same documents are linked from Tovari’s website. ### Who the policies are from [Section titled “Who the policies are from”](#who-the-policies-are-from) Tovari is a product of Tovari Financial, which is the trading name of Ewing Technology Partners, LLC. You will see the product called “Tovari” in most places and “Tovari Financial” in others — both names mean the same product from the same company, and the policies say so in their own text. Accepting them is an agreement with that company, whichever of the two names brought you to it. ### If you would rather not accept [Section titled “If you would rather not accept”](#if-you-would-rather-not-accept) You can decline. Tovari does not delete anything, and it does not accept on your behalf — it simply cannot continue without acceptance, so you are offered two ways forward: go back and look again, or sign out. Your data stays exactly as it is while you decide. If you sign back in later and accept, everything is where you left it. If you would rather your data were removed instead, see [data and privacy](/docs/features/data-and-privacy). * Web ### Being asked [Section titled “Being asked”](#being-asked) When there is something to accept, Tovari shows it after you sign in, over the app, naming each policy that needs your acceptance. Open any of them to read the full text in place, then accept. ### Reading them at any other time [Section titled “Reading them at any other time”](#reading-them-at-any-other-time) The terms and the privacy policy are linked from Tovari’s website, so you can read the current version whenever you like without signing in. ### On a phone browser [Section titled “On a phone browser”](#on-a-phone-browser) The same panel appears in the phone-browser layout, sized for a phone, with the same full text available to read before you accept. * Mobile ### Being asked [Section titled “Being asked”](#being-asked-1) The app shows the same acceptance step after you sign in, over the top of the app, listing what needs accepting and letting you read each document in full before you decide. Accepting here clears it for the web app too — there is nothing to repeat when you next open Tovari on a computer. ## Related pages [Section titled “Related pages”](#related-pages) * [Signing in](/docs/features/signing-in) — the step this one follows. * [Email verification](/docs/features/email-verification) — the other thing Tovari may ask for at sign-in. * [Data and privacy](/docs/features/data-and-privacy) — exporting or erasing your data. * [Where each feature works](/docs/platform-parity) — what is available on which platform. # Payees > Who you paid — creating payees as you type, matching rules, merging duplicates, and the default category a payee carries. ## Where this works [Section titled “Where this works”](#where-this-works) **The payee directory is a web feature, and it needs the computer layout.** Browsing your payees, editing their matching rules, merging duplicates and setting default categories are all done in the web app on a computer. That is why this page has no separate mobile section: there is one place to manage payees, and it is a computer. **Picking a payee — or creating one by typing a name that does not exist yet — while you are entering a transaction works everywhere**: on a computer, on a phone browser, and in the Tovari mobile app. Only the directory, the matching rules, merging and default categories are computer-only. ## What a payee is [Section titled “What a payee is”](#what-a-payee-is) A payee is who a transaction was with: the shop, the utility, the employer. Tovari keeps them as their own list rather than as free text on each row, so that “Corner Store” is one thing you can rename once, set a default category for, and report on — instead of a dozen spellings of the same name scattered through your register. Banks rarely send a tidy name. What arrives is raw card-terminal text, and part of a payee’s job is to be the readable name that sits in front of it. ## Creating one as you go [Section titled “Creating one as you go”](#creating-one-as-you-go) You never have to create a payee up front. Type a name into a transaction’s payee field, and if it does not exist yet, Tovari creates it as part of saving that transaction. The same is true when you set up a bill. That works on a computer, on a phone browser, and in the mobile app — a payee created on your phone mid-purchase is exactly the same payee you will see in the directory later. ## Matching rules [Section titled “Matching rules”](#matching-rules) A matching rule tells Tovari that raw bank text belongs to a particular payee. Each rule is a piece of text plus how it should match: * **contains** — the bank text has this text somewhere in it. * **exact** — the bank text is exactly this. * **starts with** — the bank text begins with this. Rules are used when Tovari works out who a piece of incoming activity was with, whether it arrived through a bank connection or a file you imported. The more specific rule wins, so a narrow rule can safely sit alongside a broad one. Rules are a way of teaching Tovari your own bank’s shorthand once, instead of renaming the same merchant every month. ## Default categories [Section titled “Default categories”](#default-categories) A payee can carry a **default category**, which is applied to new transactions for that payee. Where that default came from decides whether Tovari may ever change it: * **A default you set yourself is frozen.** No automatic pass will move it, now or later. What you chose stands until you change it. * **A default Tovari worked out for itself can be improved.** Suggestions drawn from Tovari’s ready-made category list, from your bank’s own description of the payment, or from what Tovari has learned about that merchant are all treated as provisional, and can be replaced by a better answer later. Setting a default only affects transactions from then on. If you want it applied to what is already in your register, Tovari offers to do that as a separate, explicit step, and tells you afterwards what it changed and what it deliberately left alone — rows you had categorized by hand are never overwritten, and money moving between your own accounts is never touched. ## Merging duplicates [Section titled “Merging duplicates”](#merging-duplicates) The same shop can end up as two payees — one you typed, one that arrived from your bank under a different spelling. **Merge** folds them together: pick the payee to keep and the ones to fold into it, and every transaction, matching rule and bill that pointed at the duplicates is moved across to the one you kept. The duplicates are retired, and nothing is lost from your register. Merging is the right tool for tidying up; it is not the same as deleting. ## Deleting a payee [Section titled “Deleting a payee”](#deleting-a-payee) Deleting a payee retires it: it stops being offered when you are entering a transaction, and it drops out of the directory. Transactions you have already recorded against it keep the name they were given, so your history does not change under you. Bills that used the payee are detached from it and keep their own name, so they stay editable — and because that is the one part of a delete that changes something you can see elsewhere, Tovari asks you to confirm when a bill is involved. Deleting also discards what Tovari had learned about that payee, including its matching rules, so that a future import cannot quietly re-create the payee you just removed. If what you actually want is to consolidate two spellings of the same merchant, merge them instead. ## Where payee management lives [Section titled “Where payee management lives”](#where-payee-management-lives) Open a payee field — in the register on the **Transactions** screen, or in the bill editor on **Bills & Schedule** — and the dropdown that appears carries **Edit Payees** at its foot. That opens the directory, landing on the payee the field was sitting on, so correcting a payee never means losing your place. Opening it from a blank field gives you the whole list. The directory lists your payees with a search box. Selecting one shows its name, its default category, and its matching rules; you can add a payee, add and remove rules, merge a selection of payees, and delete one. It autosaves as you type — there is no Save button. ## Related pages [Section titled “Related pages”](#related-pages) * [Transactions](/docs/features/transactions) — the register, where payees are set on individual rows. * [Categories](/docs/features/categories) — the categories a payee default points at. * [Categorizing spending](/docs/quick-start/categorizing-spending) — the order of signals Tovari uses to place a transaction, and what it will never overwrite. * [Bills](/docs/features/bills) — schedules carry a payee too. * [Where each feature works](/docs/platform-parity) — the platform map for every documented feature. # Reports > The seven Tovari reports, the periods they cover, and which of them you can read on your phone. ## What reports are for [Section titled “What reports are for”](#what-reports-are-for) Your register tells you what happened. Reports tell you what it added up to — where the money went, who you paid, how this month compares with the last six, and what is likely to be left at the end of the month. Every report is worked out on the server from the same transactions your register shows, so a report and the register can never quietly disagree. ### The seven reports [Section titled “The seven reports”](#the-seven-reports) | Report | What it answers | | ------------------------ | -------------------------------------------------------------------------- | | **Spending by Category** | Where the money went, broken down by category and set against your budget. | | **Spending by Payee** | Who you paid, how much, and how often. | | **Spending by Month** | How each month compares with the ones around it. | | **Income vs Expenses** | Both sides side by side, month by month. | | **Net Worth** | What you own against what you owe, over time. | | **Cash Flow** | Money in and out, including what is still scheduled to happen. | | **Safe to Spend** | The full working of the number on your dashboard. | ### Choosing the period [Section titled “Choosing the period”](#choosing-the-period) Every report covers a period you choose. The presets are **This Month**, **Last Month**, **Last 3 Months**, **Last 6 Months**, **Year to Date** and **Last Year**, and you can set a **Custom range** of your own instead. **Cash Flow is the one report that looks forward.** Because it projects rather than summarises, it also offers **Next 3 Months**, **Next 6 Months** and **Next 12 Months**. Those forward periods are not offered on the other reports — a rollup of what already happened has no future to show — so if you pick one on Cash Flow and then move to another report, the period falls back to a historical one. ### Narrowing what is counted [Section titled “Narrowing what is counted”](#narrowing-what-is-counted) Two filters change what a report counts, rather than when: * **Budget Only** limits the spending side to categories you actually budget, so one-off categories you never planned for stop crowding the picture. Income is never filtered this way. The toggle appears on **Spending by Category**, **Spending by Month** and **Income vs Expenses**; the other four reports are not budget-scoped and do not offer it. * **All Accounts** lets you narrow a report to particular accounts. Cash Flow starts from your Safe to Spend accounts instead, because that is the set the projection is about, and tells you which scope it used underneath the figures. Transfers between two of your own accounts are never counted as spending or income in any report. Moving money from checking to savings is not an expense, and Tovari treats it that way everywhere. * Web ### Finding your reports [Section titled “Finding your reports”](#finding-your-reports) **Reports** is in the left-hand navigation. The seven reports run across the top as tabs, and the period, **Budget Only** and account filters sit in the header above whichever one you are reading. All seven are available. ### Reading a report [Section titled “Reading a report”](#reading-a-report) Each report opens on a set of headline figures, then its chart, then the detail beneath. The period you choose carries across as you move between reports — if you were reading the last six months of spending by category, switching to spending by payee keeps those six months — except where the report you are moving to cannot offer that period, as with Cash Flow’s forward ranges. ### Following a number to its transactions [Section titled “Following a number to its transactions”](#following-a-number-to-its-transactions) Two reports let you keep going rather than stopping at the chart: * On **Spending by Month**, open a month to see the payees that made it up. * On **Spending by Payee**, open a payee to see the individual transactions behind the total. This is the fastest route from “that month looks wrong” to the transaction that explains it. ### On a phone browser [Section titled “On a phone browser”](#on-a-phone-browser) The reports are all here in the phone-browser layout, in a header that wraps the same tabs and filters into a narrower space. For sustained reading — comparing months, following a payee down to its transactions — the computer layout has considerably more room. * Mobile ### Finding your reports [Section titled “Finding your reports”](#finding-your-reports-1) **Reports** is in the app’s main navigation. Rather than a row of tabs, the report name at the top of the screen *is* the switcher: tap it to open the list and choose another report. ### The five reports in the app [Section titled “The five reports in the app”](#the-five-reports-in-the-app) The app builds **Spending by Category**, **Spending by Payee**, **Spending by Month**, **Cash Flow** and **Income vs Expenses**, each with a one-line description in the switcher so you can tell them apart at a glance. ### Choosing the period and narrowing the figures [Section titled “Choosing the period and narrowing the figures”](#choosing-the-period-and-narrowing-the-figures) Three period chips sit under the report name for the common choices, and the filter sheet opens the full list of presets along with the account filter and the **Budget Only** toggle. Cash Flow’s chips include its forward-looking periods, drawn differently so you can see at a glance which ones are projections rather than history. When a report is narrowed, that stays visible at rest, not just while the filter sheet is open: the filter control in the header carries a small dot, and a row of chips — **Budget only**, and **N accounts** when you have picked specific ones — sits above the report itself. Tapping either chip reopens the same filter sheet. The **Budget Only** chip only ever appears on a report that actually supports that scope. ### Following a number further [Section titled “Following a number further”](#following-a-number-further) Rows open in place rather than pushing a new screen. Expand a category to see the top payees behind it, a payee to see the recent transactions that make up its total, or a month to see its detail. ### What the app does not do [Section titled “What the app does not do”](#what-the-app-does-not-do) The app does not build **Net Worth** or the **Safe to Spend** report — both are in the web app, on a computer or in a phone browser. The Safe to Spend figure itself is on your app dashboard; it is the full breakdown that is web-only. ## Related pages [Section titled “Related pages”](#related-pages) * [Safe to Spend](/docs/features/safe-to-spend) — what the number means and how it is worked out. * [Budget](/docs/features/budget) — the budget the **Budget Only** scope filters against. * [Transactions](/docs/features/transactions) — the register the reports are built from. * [Where each feature works](/docs/platform-parity) — what is available on which platform. # Review Center > The four queues where Tovari collects transfers, recurring bills, uncategorized spending and possible duplicates for you to confirm. ## What the Review Center is for [Section titled “What the Review Center is for”](#what-the-review-center-is-for) Tovari notices things it is fairly sure about but will not act on by itself: two transactions that look like the same money moving between your accounts, a charge that looks like it repeats every month, spending with no category, a transaction you typed that your bank then sent through as well. Rather than guessing, Tovari puts each of these in a queue and asks you. The Review Center is where those queues live, so the decisions are in one place instead of scattered through your register. Nothing here changes your money. Confirming a suggestion changes how Tovari *files* something you already have. ### The four queues [Section titled “The four queues”](#the-four-queues) | Queue | What is in it | | ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **Detected Transfers** | Money that moved between two of your own accounts. Confirming the pair stops it counting as spending. | | **Recurring Bills** | Charges that look like they repeat. Adding one puts it on your schedule. | | **Uncategorized** | Transactions with no category yet. | | **Possible Duplicates** | Two records of what looks like one charge — either something you typed and your bank then sent through as well, or two copies your bank sent of the same purchase. | ### Why the first two are worth doing [Section titled “Why the first two are worth doing”](#why-the-first-two-are-worth-doing) Two of the queues tell you what confirming them will change, because both affect numbers you rely on elsewhere: * **Uncategorized spending stays out of your category budgets until it is filed.** Until you file it, your budget is reporting less spending than actually happened, and the queue shows you the running total that is sitting unfiled. * **Adding a bill puts it on your schedule and into Safe to Spend’s bills due.** The queue shows the monthly effect of adding everything in it, so you can see what it would do before you commit. ### Two kinds of duplicate [Section titled “Two kinds of duplicate”](#two-kinds-of-duplicate) A duplicate can come from either side. Sometimes you typed a purchase and your bank sent the same one through afterwards. Sometimes your bank simply sent the same purchase twice — that one used to sit in your register unnoticed, and Tovari now finds it. Because a merchant you visit twice in a day is perfectly normal, Tovari only raises a bank-sent repeat when the same charge shows up doubled on other days too. If it is just a busy day at the same coffee shop, nothing is raised. When you keep one copy and remove the other, the card tells you first if your balance will move, and asks you to tick a box confirming the amount before it does anything. Nothing is removed until you say so, and if you would rather leave both, **Not a duplicate** always clears the card. ### Nothing you dismiss comes back [Section titled “Nothing you dismiss comes back”](#nothing-you-dismiss-comes-back) Rejecting a suggestion is remembered. If you say something is not a transfer, not a bill, or not a duplicate, Tovari will not suggest it again. * Web ### Finding it [Section titled “Finding it”](#finding-it) **Review Center** is in the left-hand navigation, carrying a count when there is anything waiting. When there is nothing, it tells you so: *You’re all caught up — nothing needs review.* ### Working a queue [Section titled “Working a queue”](#working-a-queue) The four queues sit in a rail down the side; choosing one shows its items. Each queue has a primary action and a “not this” action — **Approve transfer** and **Not a transfer** on a detected pair, and the equivalent pair on each of the others. Where a queue supports it you can work in bulk rather than one at a time: **Approve all** on detected transfers, and multi-select with **Clear selection** on uncategorized spending. Tovari tells you how many of the batch succeeded rather than reporting a silent all-or-nothing. ### Changing your mind [Section titled “Changing your mind”](#changing-your-mind) Adding a recurring bill can be undone from the queue after the fact — the row shows it was **Added to schedule** and offers to reverse it. A bulk categorization offers **Undo — restore categories**, which puts the previous categories back rather than clearing them. ### On a phone browser [Section titled “On a phone browser”](#on-a-phone-browser) **The Review Center is not in the phone-browser layout.** To work these queues, open the web app on a computer or use the Tovari mobile app, where they appear as **Alerts**. * Mobile ### Finding it [Section titled “Finding it”](#finding-it-1) In the app the Review Center is the **Alerts** tab. Same queues, same decisions, named for how it behaves on a phone — a short list of things waiting for you. ### Working a queue [Section titled “Working a queue”](#working-a-queue-1) Alerts opens as an inbox: one card per queue, each with its count and a plain-language line saying why the items are there. Tapping a card opens that queue’s items. Each queue has its own pair of verbs on the bar at the bottom of an item, so the action always reads as the decision you are actually making: | Queue | Confirm | Reject | | ----------------------- | ------------------------------------------------------------------------------------------ | ------------------- | | **Detected transfers** | **Approve transfer** | **Not a transfer** | | **New recurring bills** | **Add to schedule** | **Not a bill** | | **Uncategorized** | **File transaction** | **Skip for now** | | **Possible duplicates** | **Merge into one**, or **Keep one, remove the other** when both copies came from your bank | **Not a duplicate** | ### What the app does not do [Section titled “What the app does not do”](#what-the-app-does-not-do) The app works the same four queues as the web app. For the bulk actions — approving every detected transfer at once, or categorizing a multi-selection in one pass — use the web app on a computer. ## Related pages [Section titled “Related pages”](#related-pages) * [Transactions](/docs/features/transactions) — the register these suggestions are drawn from. * [Bills](/docs/features/bills) — where a confirmed recurring bill lands. * [Categories](/docs/features/categories) — what you are filing uncategorized spending into. * [Safe to Spend](/docs/features/safe-to-spend) — the number a newly scheduled bill feeds into. * [Where each feature works](/docs/platform-parity) — what is available on which platform. # Safe to Spend > What the Safe to Spend number is built from, which accounts can and cannot count toward it, and the two settings that shape it. ## What the number answers [Section titled “What the number answers”](#what-the-number-answers) Safe to Spend answers one question: **how much can I spend right now without breaking something I have already committed to?** It is not your bank balance, and it is not what is left in your budget. It is what remains after Tovari has set aside the commitments falling between today and the end of your planning window. **Tovari works the number out and hands it to your screen.** The apps display it; they never calculate it. That is why the dashboard, the breakdown and the mobile app always agree — there is one definition of the number, in one place. ## What goes into it [Section titled “What goes into it”](#what-goes-into-it) Safe to Spend is built from four things: * **The balances of the accounts you have included** — your everyday spending accounts, as described in the next section. * **The commitments still to come** between today and the end of the window: scheduled bills and one-off items on those accounts that have not been recorded yet. * **Income expected inside the window**, so a paycheck landing on Friday counts toward what you can spend before it. * **Your budget**, which shapes the guidance shown alongside the figure. Tovari does not double-count. A bill you have already entered — or one your bank has already taken and reported — is money that has already moved, so it is not set aside a second time. **Do not try to foot the number by hand.** The pieces above are described so you can understand what moves it, not so you can reproduce it: which commitments fall inside your window, and which ones are already covered, is exactly the work Tovari is doing for you. ## Which accounts count [Section titled “Which accounts count”](#which-accounts-count) | Account type | Counts toward Safe to Spend? | | --------------- | ------------------------------------- | | **Checking** | Yes, by default — you can turn it off | | **Savings** | No, by default — you can turn it on | | **Investment** | Never | | **Credit card** | Never | | **Loan** | Never | Only checking and savings accounts can ever be part of the pool. **Investment accounts, credit cards and loans can never be included — that is by design, not a setting anyone can find.** A credit line is money you would owe rather than money you have, and an investment balance is not money you can spend this afternoon. Counting either would make the number a comfortable lie. New accounts follow the defaults above: create a checking account and it joins the pool immediately; create a savings account and it stays out until you say otherwise. **Closing an account takes it out of the pool.** Archiving an old checking account changes the number without you having to remember to switch anything off first. ## The two things you can change [Section titled “The two things you can change”](#the-two-things-you-can-change) Neither of these invents money. One moves the horizon; the other moves the warning line. * **Planning window** — how far ahead the number looks, expressed as **1**, **2** or **3** upcoming paychecks. Two is the default. A longer window sets aside more of what is coming, so the figure is smaller and steadier; a shorter one is more immediate and moves around more. * **Cushion** — the point at which Tovari starts warning you that things are getting tight. **Automatic** derives it from your own typical spending; **Fixed amount** lets you name a figure. **The cushion changes the warning only, never the number.** If you have no scheduled income yet, there are no paychecks to count, so Tovari falls back to the end of the current month and tells you it has done so. Scheduling your pay as a recurring income item is what turns the window on. ## Why the number moved [Section titled “Why the number moved”](#why-the-number-moved) Safe to Spend is a live figure, so it changes as your money does. The usual reasons: * a bill’s due date passed into or out of your window; * a paycheck arrived, or its next date moved; * you entered, edited or deleted a transaction on an included account; * your bank imported activity on an included account; * you included or excluded an account, or closed one; * you changed the planning window. The breakdown is the place to look: it shows the figure account by account, so you can see which account is carrying the commitments. * Web ### Where you see it [Section titled “Where you see it”](#where-you-see-it) The number leads the dashboard, under the heading **Safe to Spend**, with the end of your planning window shown beside it. **Reports** also carries a Safe to Spend tab. ### The breakdown [Section titled “The breakdown”](#the-breakdown) Opening the breakdown shows, for each included account, its **Balance**, the **Bills Due** against it in the window, and what is **Clear to Spend** there — plus your typical spending, your budget envelopes, and the total. It is the fastest way to see why the headline is what it is. ### Including or excluding an account [Section titled “Including or excluding an account”](#including-or-excluding-an-account) The switch is **Include in Safe to Spend**, in the account editor. It appears only on checking and savings accounts — there is nothing to switch on the other three types, so no switch is drawn. ### Changing the window and the cushion [Section titled “Changing the window and the cushion”](#changing-the-window-and-the-cushion) 1. Open **Settings**. 2. Choose **Safe to Spend**. 3. Pick 1, 2 or 3 paychecks for the planning window, and choose **Automatic** or **Fixed amount** for the cushion. The section previews what your choice does before you commit it, and tells you if someone else in your household changed the same settings while you had the page open. ### On a phone browser [Section titled “On a phone browser”](#on-a-phone-browser) The number leads the dashboard here too, and tapping it opens the breakdown as a full-height sheet with the same per-account detail. The **Include in Safe to Spend** switch is in the full-screen account editor, on checking and savings accounts, exactly as on the computer layout. The settings live on one stacked Settings screen rather than behind a side rail: scroll to the **Safe to Spend** card and the same window and cushion controls are there. * Mobile ### Where you see it [Section titled “Where you see it”](#where-you-see-it-1) Safe to Spend is the figure at the top of the **Home** tab, with the state in words beneath it — never colour alone — the end of your planning window, and tiles for what is expected in, what is expected out, and roughly what that leaves per day. ### The breakdown [Section titled “The breakdown”](#the-breakdown-1) **Breakdown** on the Home band opens the account-by-account view: each included account with its balance, what is due against it, and what is clear to spend there. ### Changing the window and the cushion [Section titled “Changing the window and the cushion”](#changing-the-window-and-the-cushion-1) 1. Open the app menu from the screen header. 2. Choose **Settings**. 3. Expand the **Safe to Spend** section. The controls are the same pair as the web — a 1 / 2 / 3 paycheck window and an automatic or fixed cushion — with a preview of the effect. The window control stays disabled, with an explanation and a way to add one, until you have a scheduled paycheck for it to count. ### Changing which accounts count [Section titled “Changing which accounts count”](#changing-which-accounts-count) **This one is done in the web app.** The account editor in the mobile app has no **Include in Safe to Spend** switch. When you create an account here, its inclusion follows the type you chose — checking joins the pool, everything else does not — and changing it afterwards is done from the web app on a computer or a phone browser. Everything else about Safe to Spend behaves identically. ## Related pages [Section titled “Related pages”](#related-pages) * [Accounts](/docs/features/accounts) — account types, and what closing one does. * [Dashboard](/docs/features/dashboard) — where the number is shown, alongside everything else. * [Transactions](/docs/features/transactions) — the register activity that moves it. * [Understanding Safe to Spend](/docs/quick-start/understanding-safe-to-spend) — the short version, as part of the Quick start. * [Scheduling a bill](/docs/quick-start/scheduling-a-bill) — how commitments and paychecks get into the window. * [Where each feature works](/docs/platform-parity) — the platform map for every documented feature. # Settings > What lives in Tovari's settings on each platform, and where to go when a setting is not where you expected. ## What is in Settings [Section titled “What is in Settings”](#what-is-in-settings) Settings holds the decisions that are about your *account* rather than about your money: who else is in your household, how you sign in, which accounts feed Safe to Spend, your plan, and getting a copy of your data. ### Most settings are not in Settings [Section titled “Most settings are not in Settings”](#most-settings-are-not-in-settings) This is worth knowing before you go looking. Tovari deliberately keeps a setting next to the thing it affects, so the great majority of what you can change lives on the feature’s own screen rather than here — whether an account counts toward Safe to Spend is on the account, whether a category is budgeted is on the budget, and how your register is filtered and sorted is on the register. If a setting is not in Settings, look at the thing it changes. * Web ### Finding it [Section titled “Finding it”](#finding-it) **Settings** is in the left-hand navigation. It opens with a list of sections down the side. ### The sections [Section titled “The sections”](#the-sections) | Section | What is in it | | ------------------ | ---------------------------------------------------------------------------- | | **Security** | Two-factor authentication — turning it on, and turning it off. | | **Household** | Who shares your books, and inviting or removing someone. | | **Safe to Spend** | How your Safe to Spend number is worked out. | | **Billing** | Your plan and its status. | | **Data & Privacy** | Downloading a copy of your data, and how to ask for erasure. | | **Profile** | The account you’re signed in as — name, email and household role, read-only. | ### On a phone browser [Section titled “On a phone browser”](#on-a-phone-browser) All six sections are here in the phone-browser layout, as a list of cards you open one at a time rather than a side rail. Setting up two-factor is possible here, but scanning a QR code from the same phone that is displaying it is awkward — a computer is easier. * Mobile ### Finding it [Section titled “Finding it”](#finding-it-1) **Settings** is in the app’s navigation, laid out as a list of cards. ### The sections [Section titled “The sections”](#the-sections-1) The app carries a subset of the web app’s settings: | Section | What is in it | | ----------------- | ----------------------------------------------------------------------- | | **Security** | Unlocking the app with Face ID or Touch ID, on devices that support it. | | **Household** | Who shares your books, and inviting or removing someone. | | **Safe to Spend** | How your Safe to Spend number is worked out. | | **Billing** | Your plan and its status. | Signing out is here too, at the bottom. The app’s Security section is not the same as the web app’s: here it is a single toggle for Face ID or Touch ID unlock (see [signing in](/docs/features/signing-in)); turning two-factor authentication on or off is still done in the web app. ### What the app does not do [Section titled “What the app does not do”](#what-the-app-does-not-do) Two sections are web-only. **Data & Privacy** — downloading a copy of your data — and **Profile** — the account you’re signed in as — are both in the web app, on a computer or in a phone browser. Turning two-factor authentication on or off is also web-only; completing a two-factor code when you sign in works in the app, it is only the setting up and removing that is elsewhere. ## Related pages [Section titled “Related pages”](#related-pages) * [Two-factor authentication](/docs/features/two-factor-authentication) — what the Security section does. * [Household](/docs/features/household) — sharing your books with one other person. * [Safe to Spend](/docs/features/safe-to-spend) — the number the Safe to Spend section shapes. * [Data and privacy](/docs/features/data-and-privacy) — exporting your data, and erasure. * [Where each feature works](/docs/platform-parity) — what is available on which platform. # Signing in > The three ways to sign in to Tovari, what happens when you mix them, and how to get back in if you forget your password. ## The three ways in [Section titled “The three ways in”](#the-three-ways-in) Tovari accepts three kinds of sign-in, and all three work in the web app and in the mobile app: * **Email and password** — the account you create with an email address and a password. * **Google** — sign in with a Google account. * **Apple** — sign in with an Apple account. They are not separate accounts. All three lead to the same Tovari account as long as they carry the same email address. ### Choosing a password [Section titled “Choosing a password”](#choosing-a-password) A Tovari password must be at least **8 characters**. The signup form shows the requirements as you type, along with a strength indicator, so you can see when a password is accepted before you submit it. ### Signing in with Google or Apple on an account that had a password [Section titled “Signing in with Google or Apple on an account that had a password”](#signing-in-with-google-or-apple-on-an-account-that-had-a-password) This is the one behaviour worth reading before it happens to you. If you created your account with an email and password and later sign in with Google or Apple, Tovari links the two to the same account rather than refusing you or creating a duplicate — but **your old password stops working**. Tovari tells you so at the time: > Password sign-in for this account was reset when you signed in. To sign in with your email and password again, use “Forgot Password” to set a new one. Nothing in your data changes, and you stay signed in. If you intend to keep using a password as well, set a new one when it suits you; if you plan to use Google or Apple from now on, there is nothing to do. ### Apple only sends your email once [Section titled “Apple only sends your email once”](#apple-only-sends-your-email-once) Apple gives an app your email address on the **first** authorization only. Tovari records the link to your Apple account at that first sign-in, so later sign-ins recognise you even though Apple no longer sends the address. ## Getting back in [Section titled “Getting back in”](#getting-back-in) Choose **Forgot Password** on the sign-in screen and Tovari emails you a code to set a new one. Tovari’s account emails are branded, but if that branding ever fails to render, the message is sent in its plain form instead of not being sent at all — a reset is never blocked by how the email looks. * Web ### Signing in [Section titled “Signing in”](#signing-in) The sign-in screen offers the email and password fields, with **Google** and **Apple** buttons beneath them. If a sign-in method is not configured for your Tovari deployment, its button is not offered rather than failing when you press it. ### Creating an account [Section titled “Creating an account”](#creating-an-account) **Sign up** collects your name, email and password, with the password requirements and strength meter shown as you type. After signing up you are taken through [getting set up](/docs/features/getting-set-up) — adding your first account and the budget interview. ### Staying signed in [Section titled “Staying signed in”](#staying-signed-in) Tovari keeps you signed in between visits and quietly renews your session in the background, so a long session does not drop you back to the sign-in screen mid-task. ### Signing out [Section titled “Signing out”](#signing-out) Sign out from your account menu. It ends the session on this device. ### On a phone browser [Section titled “On a phone browser”](#on-a-phone-browser) Sign-in, sign-up and password reset all work the same in the phone-browser layout, laid out in steps rather than one long form. * Mobile ### Signing in [Section titled “Signing in”](#signing-in-1) The app’s sign-in screen offers the same three methods: email and password, **Google**, and **Apple**. Apple sign-in uses the system sheet, so it works with Face ID or Touch ID. ### Creating an account [Section titled “Creating an account”](#creating-an-account-1) You can sign up in the app. It collects the same details as the web app and applies the same password rules, then takes you through the same setup steps. ### Unlocking with Face ID or Touch ID [Section titled “Unlocking with Face ID or Touch ID”](#unlocking-with-face-id-or-touch-id) If your device has Face ID or Touch ID set up, the app offers to skip your password on future sign-ins. You will see the checkbox on the sign-in and sign-up screens (checked by default when you sign up), and a one-time prompt the first time you sign in without it. From then on, opening the app shows an unlock screen instead of the sign-in form — a successful scan gets you straight in, and “Use password instead” is always there if you would rather type it. This only works on this one device, and only where a biometric is already enrolled with the OS. Turn it on or off any time from **Settings → Security**. It is a faster way back into an account you are already signed into — it is not a replacement for two-factor authentication, which still runs at sign-in exactly as before. ### If you have two-factor turned on [Section titled “If you have two-factor turned on”](#if-you-have-two-factor-turned-on) Signing in asks for your six-digit code on a dedicated screen after your password is accepted. See [two-factor authentication](/docs/features/two-factor-authentication). ### Signing out [Section titled “Signing out”](#signing-out-1) Sign out from **Settings**. It ends the session on the device and returns you to the sign-in screen. ## Related pages [Section titled “Related pages”](#related-pages) * [Email verification](/docs/features/email-verification) — confirming your address after you sign up. * [Two-factor authentication](/docs/features/two-factor-authentication) — adding a second step. * [Getting set up](/docs/features/getting-set-up) — what happens after your first sign-in. * [Where each feature works](/docs/platform-parity) — what is available on which platform. # Transactions > The register — what the four statuses mean, how a bank transaction settles, reconciling against a statement, and what each platform offers. ## The register [Section titled “The register”](#the-register) The register is one account’s list of transactions. You reach it by opening an account, and everything you do with a transaction — adding, editing, categorizing, clearing, reconciling — happens there. Transactions arrive in three ways: you type them in, a connected bank imports them, or you post one from a scheduled bill. Whatever the source, they are the same kind of row afterwards. ## The four statuses [Section titled “The four statuses”](#the-four-statuses) Every transaction is in exactly one of four states. Three of them are yours; one comes from your bank. ### Uncleared [Section titled “Uncleared”](#uncleared) The starting state for anything you enter yourself. It means: this has happened as far as you are concerned, but it has not settled at the bank yet. ### Cleared [Section titled “Cleared”](#cleared) You have seen it on the bank’s side and marked it so. Moving a row between uncleared and cleared is a single click or tap on its status control. ### Reconciled [Section titled “Reconciled”](#reconciled) Set by reconciling the account, never by hand. A reconciled row is **locked**: its status control no longer moves it, so a statement you have already footed cannot be quietly un-footed later. ### Pending — and why it is not the same as uncleared [Section titled “Pending — and why it is not the same as uncleared”](#pending--and-why-it-is-not-the-same-as-uncleared) **Pending means the row came from your bank connection.** Your bank has authorized the payment but has not posted it yet — this morning’s card swipe, say. Only a connected bank can put a row into this state; **anything you enter yourself is uncleared, never pending.** That distinction is worth holding on to, because the two look similar at a glance and mean different things. *Uncleared* is your statement about a transaction. *Pending* is your bank’s. Pending rows are shown apart from the settled list so they cannot quietly move a figure you were reading, and their amounts are the bank’s provisional ones — a restaurant tip or a fuel hold can change before the payment posts. ## How a pending transaction settles [Section titled “How a pending transaction settles”](#how-a-pending-transaction-settles) When the bank posts the real transaction, Tovari **updates the row that is already there**. It does not delete it and insert a replacement, and it does not add a second row beside it. That has consequences you can rely on: * **Your edits survive.** A category, payee, or note you added while the row was pending is still there after it posts. * **You never get a duplicate.** The pending row and the posted transaction are one row through the whole lifecycle, not two rows you have to tidy up. * **A payment you already entered is matched, not doubled.** If you typed the payment in yourself and your bank later reports it, Tovari attaches the bank’s version to *your* row and keeps everything you wrote on it. * **Matching only ever happens inside one account.** A row on one account is never matched to activity on another, so a similar-looking payment somewhere else in your household cannot be swallowed by mistake. If the bank ends up not posting an authorized payment at all, the pending row does not linger forever — Tovari reconciles what it is holding against what the bank still reports outstanding. ## Reconciling an account [Section titled “Reconciling an account”](#reconciling-an-account) Reconciling is how you agree an account with a statement. You enter the statement’s ending balance, mark rows cleared or uncleared until the difference reaches zero, and finish — and Tovari then locks the matched rows as **reconciled**. Two things about it are worth knowing before you start. **Tovari re-checks the match itself before locking anything.** The figure on your screen may be a few seconds old, and someone else in your household may have changed a transaction while you were working. So when you press finish, the match is verified again, and rows are locked only if it still holds. If it no longer holds, **nothing is locked** and you are asked to refresh and try again. That refusal is the protection working: it is what stops a stale screen from locking a period against numbers that have already moved. **Pending rows do not stand in your way.** A transaction your bank has authorized but not posted is left out of the cleared total, exactly as an uncleared row is, so an outstanding pending payment can never be the reason a reconciliation will not balance. Once an account is reconciled, reconciling again finds nothing new to lock — the rows from last time are already reconciled, and only rows you have cleared since will be picked up. ## Transfers between your own accounts [Section titled “Transfers between your own accounts”](#transfers-between-your-own-accounts) Money moved between two of your own accounts is not spending. Tovari records such a movement as a pair of linked rows — one on each account — and leaves the pair out of your spending and income figures because they are *linked*, not because of the category they carry. Marking a transaction with a category named “Transfer” does not, on its own, exclude it from anything. ## Figures Tovari works out for you [Section titled “Figures Tovari works out for you”](#figures-tovari-works-out-for-you) The register header shows the account’s **Cleared**, **Uncleared**, **Working Balance**, and — when the account has pending bank activity — a **Pending** figure. Each row also carries a running balance. All of these are worked out by Tovari and sent to your screen; the app displays them rather than computing them, so every place you look agrees. Read them as meanings rather than as a sum to reproduce: adding the columns up by hand is not how they are defined. * Web ### The layout [Section titled “The layout”](#the-layout) The register is a resizable grid with columns **Status**, **Date**, **Payee**, **Notes**, **Category**, **Amount** and **Balance**. Click the **Date** header to flip the sort, and drag a column edge to resize it — your widths are remembered. Two sections sit apart from the settled list: * **Scheduled Bills** — occurrences that have not been recorded yet, each with a way to enter it or skip it. * **Pending** — *not yet posted* — the bank rows described above. ### The action row [Section titled “The action row”](#the-action-row) Above the grid: **Add Transaction**, **Add Scheduled Item**, **File Import**, **Export**, and **Reconcile**. Export produces a spreadsheet of the register as you are currently filtering it. ### Adding a transaction [Section titled “Adding a transaction”](#adding-a-transaction) **Add Transaction** opens a dialog naming the account the row will land in, with fields for date, payee, amount, category and a note. Nothing is written until you click **Add Transaction** in the dialog; **Cancel**, **Esc** or a click outside closes it and writes nothing. The **Category** field is also where you turn the new row into a transfer — pick a tracked account from the transfer group instead of a category, and Tovari creates the matching row in that account for you. It offers the account list once you have typed an amount, since a transfer needs a figure and a direction to work from. **Add Scheduled Item** opens the same dialog dated tomorrow. What actually decides the outcome is the **date**, not the button: a date in the future is saved as a scheduled item that posts on that day and does not move your balance yet — the dialog says so, and its button reads **Schedule Item**. Pull the date back to today and it becomes an ordinary transaction again. ### Finding transactions [Section titled “Finding transactions”](#finding-transactions) The header carries a search box and a **View** panel holding the date range, an uncleared-only switch, an uncategorized-only switch and a bank-text switch. Searching and filtering are done by Tovari across the whole account, not just the rows already on screen, so a match further back is still found. To drop a search and get the whole account back, click the **✕** at the right of the search box — it appears as soon as you have typed something — or press **Esc** while the box has focus. **Your View settings are remembered per account**, so an account you always read a particular way opens that way next time. Search is deliberately not remembered — a search restored behind your back would silently hide rows. ### Editing [Section titled “Editing”](#editing) Click a row to edit it in place; the same row is where you set the payee and the category. The circle in the **Status** column moves a row between uncleared and cleared, and on a reconciled row it shows a lock and does nothing. Selecting several rows brings up a bar that can categorize them all at once, link them as a transfer to another account, or merge a matching pair into a single transaction. ### On a phone browser [Section titled “On a phone browser”](#on-a-phone-browser) Opening the web app on a phone gives you the same register as a full-screen list: search, filters, the pending section, a transfer review section, and a tap-to-edit sheet, with swipe actions on a row. Three things are not in this layout: **reconciling**, **file import** and **export**. All three need the room of the computer layout — use **View Desktop Site** in the **More** menu, or open Tovari on a computer. * Mobile ### Getting there [Section titled “Getting there”](#getting-there) The register is not its own tab. Open the **Accounts** tab and tap an account; the register opens inside that tab, so the tab bar stays put and the back gesture returns you to your accounts. ### The layout [Section titled “The layout”](#the-layout-1) Instead of a grid, the register is a stack of labelled bands: * The header band carries the account’s **working** figure with **cleared** and **uncleared** beneath it, and a line about pending activity when the account has any. * **Upcoming** — scheduled occurrences not yet recorded. * **Pending at the bank** — the pending rows, with the same “authorized but not posted” meaning described above. * The settled transactions, grouped under date headers. Rows are compact — payee, category and amount — and an uncategorized row is highlighted so it is easy to spot. ### Filtering and the header controls [Section titled “Filtering and the header controls”](#filtering-and-the-header-controls) A filter control sits under the header, with chips showing what is currently applied so you can clear a filter with one tap. **Bank transaction text** — the bank’s own description under each row — is a switch inside that filter sheet. The header itself carries every register action directly, with nothing behind a menu. Beside the back arrow and the notification bell sits **Reconcile account**; on the other side are help, **Search**, and **Add a transaction**. Scheduling is a choice inside the Add sheet rather than a separate command, and an account’s name, type and connection are edited from the Accounts screen — swipe a row on iOS, or press and hold on Android. ### Editing [Section titled “Editing”](#editing-1) Tap the circle at the left of a row to move it between uncleared and cleared; its label states what the tap will do. A reconciled row shows a padlock and does not move. Tap **Add a transaction** in the header to open the **New transaction** sheet — date, payee, category, amount and note. A **Transaction / Scheduled** switch at the top of that sheet decides which you are creating: leave it on Transaction for money that moves once, or choose Scheduled to step through how often it repeats, how much, and when it stops. You can change your mind either way without losing the sheet. Tapping an existing row opens the same sheet to edit it, without the switch — an existing transaction’s kind cannot change underneath you. If you enter a payment your bank has already reported as pending, the app offers to settle the two together rather than leaving you with a duplicate. ### Reconciling [Section titled “Reconciling”](#reconciling) **Reconcile account**, the scales button next to the notification bell, runs the same reconciliation as the web: enter the statement’s ending balance, work the difference to zero, and finish. Tovari re-checks the match before locking, exactly as described above, and confirms when the account is reconciled. ## Related pages [Section titled “Related pages”](#related-pages) * [Accounts](/docs/features/accounts) — the balances an account shows and what closing one does. * [Bank connections](/docs/features/bank-connections) — where pending rows come from, and how much history a connection brings in. * [Payees](/docs/features/payees) — the payee list behind the Payee column, and the default category a payee can carry. * [Categories](/docs/features/categories) — where your categories came from, and how to rename or remove one. * [Bills](/docs/features/bills) — the register also surfaces recurring payments it has spotted in your bank activity but that have no schedule yet, so you can turn one into a bill from where you noticed it. * [Safe to Spend](/docs/features/safe-to-spend) — what your register feeds. * [Reading your register](/docs/quick-start/reading-your-register) — the short version, as part of the Quick start. * [Categorizing spending](/docs/quick-start/categorizing-spending) — putting each row in the right category. * [Where each feature works](/docs/platform-parity) — the platform map for every documented feature. # Two-factor authentication > Turning on a second sign-in step with an authenticator app, using it, and turning it off again. ## What two-factor authentication does [Section titled “What two-factor authentication does”](#what-two-factor-authentication-does) With two-factor turned on, signing in takes two things instead of one: your password, and a six-digit code that changes every thirty seconds. Someone who learns your password still cannot get in without the device that generates the code. It is off unless you turn it on. ### It uses an authenticator app [Section titled “It uses an authenticator app”](#it-uses-an-authenticator-app) Tovari’s second factor is an **authenticator app** — the kind that shows rotating six-digit codes, such as the one built into your phone or password manager. Setting it up means scanning a QR code once. **There is no text-message or email option.** If you are looking for one, it is not that it is hidden — Tovari does not offer it. ### Who can turn it on [Section titled “Who can turn it on”](#who-can-turn-it-on) Two-factor is for accounts that sign in with an **email and password**. If your account signs in with Google or Apple, Tovari does not offer it, and says so rather than letting you start. The reason is worth stating plainly: Tovari has **no backup codes**. For an account that signs in through Google or Apple, a second factor would become a step you could not satisfy if you lost your authenticator — so that combination is refused rather than offered and regretted. For the same reason, keep your authenticator app somewhere you will still have it — a password manager that syncs between your devices is safer than a single phone. ### Turning it on takes two steps [Section titled “Turning it on takes two steps”](#turning-it-on-takes-two-steps) Scanning the QR code is not enough on its own. Two-factor becomes active only once you enter a code from your authenticator to prove the pairing worked. If you close the setup before that, nothing changes and your next sign-in is unaffected. * Web ### Turning it on [Section titled “Turning it on”](#turning-it-on) Open **Settings**, then **Security**. The two-factor card shows whether it is on and offers to set it up. Setting up walks you through it: Tovari shows a QR code, you scan it with your authenticator app, then you type the six-digit code it shows you. Once that code is accepted, two-factor is on. If the card tells you your account is not eligible, that is the Google or Apple case described above. ### Signing in with it on [Section titled “Signing in with it on”](#signing-in-with-it-on) After your password is accepted, Tovari asks for the current six-digit code from your authenticator before finishing the sign-in. ### Turning it off [Section titled “Turning it off”](#turning-it-off) Turning it off asks for **both your password and a current code**. That is deliberate: it is the same proof as signing in fresh, so that someone at an unlocked screen cannot quietly remove your second factor. If either is wrong, two-factor stays on. ### On a phone browser [Section titled “On a phone browser”](#on-a-phone-browser) Both setting up and turning off work in the phone-browser layout, in a sheet rather than a dialog. The QR code is awkward to scan from the same phone that would display it — if you can, set it up on a computer, or use an authenticator that lets you type the key by hand. * Mobile ### Signing in with it on [Section titled “Signing in with it on”](#signing-in-with-it-on-1) If two-factor is on for your account, the app asks for your six-digit code on its own screen after your password is accepted. Enter the current code from your authenticator and you are in. ### What the app does not do [Section titled “What the app does not do”](#what-the-app-does-not-do) **Two-factor is turned on and off in the web app, not in the app.** The app’s Settings carries no two-factor card. Open the web app — on a computer or in a phone browser — to set it up or remove it. ## Related pages [Section titled “Related pages”](#related-pages) * [Signing in](/docs/features/signing-in) — the three ways into your account, and which of them can use two-factor. * [Settings](/docs/features/settings) — where the Security section lives. * [Getting help](/docs/features/getting-help) — if you have lost access to your authenticator. * [Where each feature works](/docs/platform-parity) — what is available on which platform. # Where each feature works > Which parts of Tovari you can use on a computer, on your phone's browser, and in the Tovari mobile app. Tovari runs in three places, and they are not identical. This page is the map: for every part of Tovari that has documentation, it says whether you can use it on a computer, on your phone’s web browser, and in the Tovari mobile app. Read it before you assume something you did in one place is available in another. ## The three places [Section titled “The three places”](#the-three-places) **On a computer, in your browser.** The full web app, with the left-hand navigation. This is the widest version of Tovari. **On a phone, in your browser.** The same web app, opened on a phone. It rearranges itself into a bottom tab bar and full-screen sheets, and it deliberately leaves out a few screens that need room to be useful. You can switch to the computer layout at any time with **View Desktop Site** in the **More** menu. **In the Tovari mobile app.** The app you install on your phone. It is a separate app, not the website in a wrapper, so it has its own screens — and, in a few places, its own names for things. ## The matrix [Section titled “The matrix”](#the-matrix) | Feature | On a computer | On a phone browser | In the mobile app | What to know | | ------------------------- | ------------- | ------------------ | ----------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Accounts | Yes | Yes | Yes | Add, edit, reorder and close accounts anywhere. The mobile app sets an account’s Safe to Spend inclusion from the account type and offers no switch for it — change that in the web app. | | Bank connections | Yes | Yes | Yes | Linking a bank, seeing when it last synced, and reconnecting it are available in all three. Choosing how much past activity to bring in is offered on a computer and a phone browser only; the mobile app brings in about the last 90 days. | | Bills | Yes | Yes | Yes | Scheduled bills are a forecast. Tovari never posts one for you — you enter or skip each occurrence yourself, and entering one attaches it to a matching bank transaction rather than duplicating it. Suggested recurring payments are offered on a computer and in the mobile app, but not in the phone-browser layout. | | Budget | Yes | Yes | Yes | The envelope budget, the month walk and the rollover work the same in all three. | | Categories | Yes | No | No | **Web only, on a computer.** Renaming a category, moving it between sections, changing its icon or colour, and deleting one all need the computer layout. Categories you already have are usable everywhere, and you can still create a one-off category on a phone. | | Dashboard | Yes | Yes | Yes | Each version shows a different set of cards. The computer layout shows the most — your spending by category and by payee, your savings goals, account balances and watched categories, alongside Net Worth and your income, budgeted and spent totals. The phone browser and the mobile app each show a shorter set built around Safe to Spend, your budget, what is coming up and recent activity. | | Data and privacy | Yes | Yes | No | **Web only.** Downloading a copy of your data is done in the web app, on a computer or a phone browser. The mobile app does not offer it. | | Email verification | Yes | Yes | Yes | Verifying a new email address works from wherever you signed up. | | File import | Yes | No | No | **Web only, on a computer.** Importing a CSV, OFX or QFX file — including the column-mapping step — needs the computer layout. | | Getting help | Yes | Yes | Yes | Reporting a bug, a suggestion or a question is available in all three, and reaches the same place. On a computer and in a phone browser it is behind the help button in the bottom-right corner; in the mobile app it is behind the help control in the header on Dashboard, Accounts, a register, Budget, Bills and Reports, under **Ask about this screen**. In each, the assistant can write the report for you to confirm, and a plain form is always available — including when the assistant is not. | | Getting set up | Yes | Yes | Yes | The guided setup — accounts first, then the budget interview — runs wherever you create your account. | | Help chat | Yes | Yes | Yes | Answers how-to questions from this documentation, offers to take you to the right screen, and can write up a bug or suggestion for you to confirm. It has no access to your accounts or balances, and it only discusses Tovari. On a computer it opens as a panel from the **Ask Tovari** button in the bottom-right corner; on a phone it opens as a sheet, from that same corner button in a phone browser and from the header on the main screens of the mobile app. In the mobile app the header control offers **Ask about this screen** and **Documentation** — on a computer the two are separate, the docs button sitting beside the notification bell. The **Go to…** button appears only for screens the version you are on actually has — the Review Center in a phone browser, and the Net Worth and Safe to Spend reports in the mobile app, get the answer without the button. | | Household | Yes | Yes | Yes | Inviting someone to your household and managing who is in it are available in all three. | | Legal policies | Yes | Yes | Yes | You are asked to accept updated terms wherever you sign in; accepting in one place clears it everywhere. | | Payees | Yes | No | No | **Web only, on a computer.** The payee directory — matching rules, merging duplicates and default categories — needs the computer layout. Picking a payee, or creating one by typing a name that does not exist yet, while you are entering a transaction works on a phone browser and in the mobile app. | | Reports | Yes | Yes | Yes | The mobile app offers a subset of the reports: Net Worth and the Safe to Spend report are web only. | | Review Center | Yes | No | Yes | In the mobile app this is the **Alerts** tab, with the same queues. It is not in the phone-browser layout — open it on a computer or use the mobile app. | | Safe to Spend | Yes | Yes | Yes | The number is calculated by Tovari, not by the screen you are looking at, so all three always agree. | | Settings | Yes | Yes | Yes | The mobile app carries a subset of the settings sections; see each feature’s own page for where a specific setting lives. | | Signing in | Yes | Yes | Yes | Email and password, Google, and Apple sign-in are available in all three. | | Subscription | Yes | Yes | Yes | You can see your plan and its status everywhere. **Purchases and plan changes are made in the mobile app** — the web app shows your subscription but cannot change it. | | Transactions | Yes | Yes | Yes | The mobile app offers a subset of the register’s features. Exporting your transactions to a spreadsheet is done in the web app, on a computer. | | Two-factor authentication | Yes | Yes | Yes | You can complete a two-factor code when signing in on all three. Turning two-factor on or off is done in the web app. | ## What this page does not list [Section titled “What this page does not list”](#what-this-page-does-not-list) Tovari also contains internal building blocks — shared navigation chrome, reference data and similar plumbing — that no one uses directly and that have no documentation of their own. Those are intentionally left off this page. If something you can actually see and use in Tovari is missing here, that is a gap in this page; please tell us. ## How this page is kept accurate [Section titled “How this page is kept accurate”](#how-this-page-is-kept-accurate) This page is updated whenever a feature gains or loses a platform, in the same change that ships that work. It is reviewed by hand rather than generated, because “does this exist on the phone” is a judgement about what a person can actually do, not something a script can read off the code. A test in the Tovari repository checks that every documented feature has a row here, so a new feature cannot quietly ship without appearing on this page. # Add your first account > Create an account by hand, and understand the four groups Tovari sorts your accounts into. **Step 2 of the Quick start.** You are signed in with a verified email and no accounts yet. By the end of this page you have one account you created by hand. Right after sign-up, Tovari walks you into onboarding and asks for accounts first — so you may meet this screen before you ever see the dashboard. The steps below work identically from onboarding and from the Accounts screen later. ## The five account types [Section titled “The five account types”](#the-five-account-types) Every account you create is one of five types: **Checking**, **Savings**, **Investment**, **Credit Card**, or **Loan**. The type is not cosmetic. It decides which group the account is filed under, which fields the editor offers you (a rate for deposit accounts and cards, a credit limit for cards), whether the balance counts as an asset or a liability, and — as [Understanding Safe to Spend](/docs/quick-start/understanding-safe-to-spend) explains — whether the account can ever count toward your Safe to Spend number. **Investment** behaves differently from the rest once you link it to a brokerage: Tovari shows the value the brokerage reports rather than a running balance you reconcile, and opening the account shows its value history instead of a transaction list. See [Investment accounts linked to a brokerage](/docs/features/accounts#investment-accounts-linked-to-a-brokerage). ## The four groups [Section titled “The four groups”](#the-four-groups) Accounts are grouped, never mixed into one flat list: | Group | Holds | | ----------------- | -------------------- | | **Cash Accounts** | Checking and savings | | **Investments** | Investment accounts | | **Credit Cards** | Credit cards | | **Loans** | Loans | Every type lands in exactly one group, so nothing can go missing from the list. The two platforms order the groups differently — see the tabs. * Web ### Add the account [Section titled “Add the account”](#add-the-account) 1. Go to **Accounts** in the left navigation. 2. Press **Add Account** in the header. A small chooser offers **Connect a bank** and **Add manually**. 3. Choose **Add manually**. The **Add Account** dialog opens. 4. Fill in the form: * **Account Name** — required. The placeholder suggests something like *Everyday Checking*. * **Account Type** — required. Pick one of the five types. * **Bank (Optional)** — the institution’s name, for your own reference. * **Account Number (Optional)** — the last few digits only. Tovari does not check it for uniqueness, but it is not inert: it is searchable, and it is one of the clues Tovari uses when it spots a movement between two of your own accounts. Enter it accurately if you know it. * **Starting Balance (Optional)** — the balance the account holds today, before you record anything in Tovari. * **APY (Optional)** on a checking, savings, or credit card account, and **Credit Limit (Optional)** on a credit card (used to show your utilization). * **Include in Safe to Spend** — shown only for checking and savings. A new checking account arrives with it on; savings arrives off. 5. Press **Add Account**. The account appears immediately under its group heading, and the header tiles — **Total Assets**, **Total Liabilities**, **Net Worth** — update. ### Group order and layout [Section titled “Group order and layout”](#group-order-and-layout) The web Accounts screen lists the groups in this order: **Cash Accounts → Investments → Credit Cards → Loans.** Each group is a collapsible section. You can drag accounts to reorder them, but only **within one section** — dragging cannot move an account between groups, because the group is decided by the account type. Collapsing a section is a per-visit convenience; it is not remembered between sessions. ### Editing and closing [Section titled “Editing and closing”](#editing-and-closing) Click an account to open its detail panel and change any field. Closing an account uses **Close Account** in the account editor — it is a soft close: history is preserved and the account is archived out of your list rather than deleted. * Mobile ### Add the account [Section titled “Add the account”](#add-the-account-1) 1. Open the **Accounts** tab in the bottom tab bar. 2. Tap the **Add account** control in the screen header. (On a first run, the empty state offers **Connect a Bank** and a manual path directly.) The **Add account** sheet slides up. 3. The top of the sheet is the recommended **Connect a bank** card. Below the divider marked **OR TRACK IT MANUALLY** is the manual form. 4. Fill it in: * **Account Type** — a row of chips; tap one. * **Account Name** — placeholder *Everyday Checking*. * **Bank** and **Last 4** — side by side, both optional. * **Starting Balance**. 5. Tap **Add Account** at the bottom of the sheet. During onboarding the same sheet is reached from **Add an account** on the accounts step. ### What differs from the web [Section titled “What differs from the web”](#what-differs-from-the-web) * **Group order.** The native Accounts screen orders the groups **Cash Accounts → Credit Cards → Loans → Investments**, and it hides the **Investments** group entirely until you have at least one investment account. The web keeps Investments in second place at all times. The grouping itself — which type lands where — is identical. * **No Safe to Spend switch in the editor.** The add sheet sets the flag for you from the type you pick (checking on, everything else off), and the **Edit account** sheet has no toggle for it. To change an account’s Safe to Spend inclusion after it exists, use the web app. * The editor is a sheet (**Edit account**), not a side panel, and it carries **Bank**, **Last 4**, **Credit Limit**, and **APY** as the type allows. ## Where you are now [Section titled “Where you are now”](#where-you-are-now) You have one account with a starting balance and no transactions in it. You can repeat this page for every account you want to track by hand — or let the bank fill one in for you, which is the next page: [connect a bank with Plaid](/docs/quick-start/connect-a-bank-with-plaid). # Categorizing spending > Everything gets a category — automatically where Tovari is confident, and by you where it is not. What you set yourself is never overwritten. **Step 6 of the Quick start.** You can read your register. Now make it mean something. ## Categorize everything, budget selectively [Section titled “Categorize everything, budget selectively”](#categorize-everything-budget-selectively) Tovari’s rule is that **every transaction carries a category**. There is a protected **Uncategorized** category in every household, and a transaction that no rule could place lands there rather than being left blank. Nothing falls out of your reports because it was never labelled. That is separate from budgeting. Categorizing is complete and automatic; budgeting is a deliberate, small selection you make on top of it — see [your first envelope](/docs/quick-start/your-first-envelope). ## What Tovari does for you [Section titled “What Tovari does for you”](#what-tovari-does-for-you) Your household adopted the whole category catalog at sign-up, so there is always somewhere for a transaction to go. When a row arrives — from a bank connection or a file import — Tovari works down a fixed order of signals to place it: 1. A default you have set yourself on the payee. This beats everything. 2. What the bank’s own description says about the *kind* of payment it is — a card payment or a transfer looks like one in the description even when the merchant name suggests otherwise. 3. Defaults Tovari has learned for that payee. 4. Its merchant dictionary, matched against the raw bank text. If none of those answers confidently, the row lands in **Uncategorized** and waits for you. Tovari would rather leave a row for you than guess. There is one extra check on every automatic answer: money coming *in* is never automatically filed under a spending category, and money going *out* is never automatically filed under an income category. (Credit cards and loans are exempt, because on a liability account the signs run the other way.) ## What you set is never overwritten [Section titled “What you set is never overwritten”](#what-you-set-is-never-overwritten) This is the promise the automation is built around: **a field you have edited yourself is never reprocessed.** If you recategorize a row, later automatic passes skip that row’s category — including bulk recategorization and the periodic sweep that re-runs improved rules over old transactions. If you rename a payee, the same protection applies to the name. The two protections are independent: a row whose payee you fixed can still have its category improved automatically, and vice versa. Payee defaults follow the same principle. A default *you* chose for a payee is frozen; ones Tovari worked out for itself can be improved later. ## Transfers are not spending [Section titled “Transfers are not spending”](#transfers-are-not-spending) Money moving between two of your own accounts is a transfer, and Tovari excludes it from spending and income by the link between the two sides, never by which category it carries. So paying your credit card from checking never inflates your spending — it just moves the money. * Web ### Change one row’s category [Section titled “Change one row’s category”](#change-one-rows-category) 1. Open the register and click the **Category** cell on the row. 2. A dropdown opens with a **Search categories** box. Type to narrow, then pick one. The list includes **Uncategorized** at the top so you can deliberately put a row back. The payee works the same way, in the **Payee** column, and offers to create a payee on the fly if you type a name that does not exist yet. ### Change many rows at once [Section titled “Change many rows at once”](#change-many-rows-at-once) Select rows with their checkboxes. A bar appears at the bottom with a **Categorize or transfer** picker; choose a category to apply it to the whole selection, or **Clear Selection** to start over. Rows you have already categorized by hand are deliberately left alone by the automatic passes, so a later sweep will not undo the work you do here. * Mobile The thesis is identical on mobile — everything is categorized, the same **Uncategorized** fallback applies, and the same “what you set is never overwritten” rule holds. What differs is that editing happens in sheets rather than in an inline grid. ### Change one row’s category [Section titled “Change one row’s category”](#change-one-rows-category-1) 1. In the register, tap the transaction. The **Edit transaction** sheet opens. 2. Tap the **Category** control. The category picker slides up with a **Search categories** field at the top and categories grouped by section. 3. Tap the one you want; the picker closes back to the sheet. 4. Tap **Save**. The same picker appears in the **New transaction** sheet when you are entering a row by hand, so a transaction can be categorized at the moment you create it. ### Spotting what needs attention [Section titled “Spotting what needs attention”](#spotting-what-needs-attention) Uncategorized rows are easy to find without a filter: in the register list their category label is drawn in amber rather than the usual muted grey. ### No bulk categorize on mobile [Section titled “No bulk categorize on mobile”](#no-bulk-categorize-on-mobile) The multi-select bulk action bar is a web feature. On mobile you categorize a row at a time through the sheet above; for a large clean-up, use the web app. ## Where you are now [Section titled “Where you are now”](#where-you-are-now) Your register reads correctly: every row has a payee and a category, and the ones you fixed will stay fixed. Now pick the few you want to actively budget: [your first envelope](/docs/quick-start/your-first-envelope). # Connect a bank with Plaid > Link a bank so balances and transactions arrive on their own — and choose how much history to import. **Step 3 of the Quick start.** You have at least one account you typed in yourself. This page adds one that keeps itself up to date. A connected account imports its balances and its transactions on its own. You can keep manual accounts alongside connected ones — nothing forces you to connect anything. ## Choosing how much history to import [Section titled “Choosing how much history to import”](#choosing-how-much-history-to-import) When you connect, Tovari asks how far back to import. It matters: * **A short window** gets you running quickly with a small, tidy register. * **A long window** gives your reports and your typical-spending figures real history to work with, but takes longer to import and brings in a lot of rows to review. Whatever window you choose, Tovari writes a single **Starting Balance** entry standing in for everything that happened before the imported window, so the account lines up with your bank instead of starting from zero. One case overrides the choice: if the account you are attaching to **already has transactions in Tovari**, only new activity is imported, so linking cannot duplicate the history you already have. The web app tells you this on the spot and hides the history picker. * Web ### Connect [Section titled “Connect”](#connect) 1. On **Accounts**, press **Add Account** and choose **Connect a bank**. (Onboarding offers the same chooser.) 2. Plaid’s own secure window opens. Choose your institution, sign in, and **choose which accounts to share inside that window**. Tovari never sees your bank credentials. 3. Back in Tovari, a dialog appears — **Confirm accounts to add** — listing the accounts you just chose in Plaid so you can confirm them. There is nothing to tick: every account listed is added. Anything already connected is shown with an **Already added** mark and is left out, so it cannot be added twice. When you are attaching to one existing account, the dialog reads **Choose the account to link** instead and you pick the single Plaid account that matches it. ### Pick the history window [Section titled “Pick the history window”](#pick-the-history-window) The same dialog carries an **Import history** dropdown. The choices are: | Option | What it imports | | ------------------------------ | -------------------------------------------------------- | | **None (start fresh)** | No history — only activity from now on | | **15 days** | The last two weeks or so | | **30 days** | About a month | | **60 days** | About two months | | **90 days** | About three months — the preselected default | | **120 days** | About four months | | **All available transactions** | Everything your bank makes available (roughly two years) | Pick one, then press **Add accounts** (or **Link account** when you are linking a single account). The first import runs in the background; transactions appear in the register as they land. * Mobile ### Connect [Section titled “Connect”](#connect-1) 1. Open the **Accounts** tab and tap **Add account**, then the **Connect a bank** card at the top of the sheet. On a first run, the empty state’s **Connect a Bank** button does the same thing. 2. Plaid’s secure flow opens natively. Choose your institution, sign in, and choose your accounts inside that flow — exactly as on the web, where the selection is also made inside Plaid. 3. The app returns straight to the Accounts list and the new accounts appear there. **This is the first real difference from the web:** there is no follow-up confirmation dialog and no history picker on mobile. There is no success toast either — the list you are already looking at is the confirmation. ### There is no history picker on mobile [Section titled “There is no history picker on mobile”](#there-is-no-history-picker-on-mobile) The native connect flow imports a **fixed 90 days** of history. There is no dropdown and no choice to make. Ninety days is enough to give the register and your typical-spending figures something to work with without pulling your entire history down over a phone connection. If you want a different window — none at all, or every transaction the bank has — connect that institution from the web app instead, where the **Import history** dropdown is offered. ### One connection per institution [Section titled “One connection per institution”](#one-connection-per-institution) If you try to connect a bank the household has already linked, the app stops and tells you so by name, with a pointer to open it from **Accounts**. It will not create a second connection to the same institution. ## Where you are now [Section titled “Where you are now”](#where-you-are-now) You have a connected account whose transactions are arriving on their own, plus whatever you added by hand. Next Tovari asks what you want to budget: [the budget interview](/docs/quick-start/the-budget-interview). # Create your account > Sign up, verify your email, and — if you want it — turn on two-factor sign-in with an authenticator app. **Step 1 of the Quick start.** You start with nothing and finish signed in, with a verified email address and — optionally — an authenticator app protecting your sign-in. ## What you need [Section titled “What you need”](#what-you-need) An email address you can read right now. Verification is not optional: until your email is confirmed, the app will not let you past the verification screen. Tovari also supports signing in with **Google** or **Apple**. Those buttons live on the sign-in screen rather than the sign-up form, and each is shown only when it is configured for the build you are using. One thing to know before you choose: an account that signs in with Google or Apple cannot add an authenticator app as a second factor — the sign-in provider is already supplying one. * Web ### Sign up [Section titled “Sign up”](#sign-up) 1. Open the sign-up page. The heading reads **Create your account**. 2. Fill in **First name**, **Last name**, **Email address**, and **Password**. The password field shows the minimum length inline, and a strength meter and a requirements checklist update as you type. 3. Confirm the password in **Confirm password**. 4. Press **Create account →**. You reach that form from the sign-in page — the line **Don’t have an account?** links to it. The same sign-in page carries the **Google** and **Sign in with Apple** buttons if you would rather not keep a password. ### Verify your email [Section titled “Verify your email”](#verify-your-email) You land on **Verify your email**. Tovari has emailed you a **6-digit code**. 1. Type the code into the six boxes. 2. Press **Verify email**. If the mail has not arrived, **Resend code** sends another. Resending is deliberately rate-limited: you must wait about half a minute between requests, and there is an hourly cap on how many you can ask for. If you hit the cap, wait and try again — nothing is wrong with your account. ### Turn on two-factor sign-in (optional) [Section titled “Turn on two-factor sign-in (optional)”](#turn-on-two-factor-sign-in-optional) Two-factor sign-in in Tovari means an **authenticator app** producing a six-digit code — for example Google Authenticator, 1Password, or Authy. There is no code-by-email option. 1. Go to **Settings**, then the **Security** section in the left rail. 2. The two-factor card shows **Off**. Press **Turn on**. 3. Scan the QR code with your authenticator app. If you cannot scan, the setup key is printed underneath for manual entry. 4. Enter the six-digit code your app shows in **Authenticator code**, then press **Turn on two-factor**. **Step 4 is what actually switches it on.** Starting the setup only reserves a secret; until you enter a working code, two-factor is still off and your next sign-in is unchanged. From then on, signing in shows **Two-factor verification** — enter the code from your authenticator app and press **Verify**. To switch it off later, the same card offers **Turn off**. Turning it off requires your password *and* a fresh code from the app; if either is missing, it stays on. If your account signs in with Google or Apple, the card explains that two-factor is not available for it and offers no switch. * Mobile The Expo app handles sign-up, verification, and the two-factor challenge at sign-in. Setting two-factor **up** is the one part that is web-only — see the end of this tab. ### Sign up [Section titled “Sign up”](#sign-up-1) 1. On the sign-in screen, find **New to Tovari?** and tap **Create account**. The next screen’s heading reads **Create your account**. 2. Fill in **Full name**, **Email**, **Password**, and **Confirm password** — all four are required, and **Full name** comes first. A rules checklist under the password field ticks off as you satisfy each rule; it never blocks the button — the server is the authority. 3. Tap **Continue**. ### Verify your email [Section titled “Verify your email”](#verify-your-email-1) The **Verify your email** gate appears with six code cells and the address the code went to. 1. Enter the 6-digit code. The screen submits as soon as the sixth digit lands, or you can tap **Verify email**. 2. Need another? Tap the resend control. It disables itself and counts down — **Resend in M:SS** — using the wait the server tells it, so the app never guesses the cooldown. There is also an hourly cap. On success a brief confirmation shows and the gate clears into the app. ### Signing in with two-factor [Section titled “Signing in with two-factor”](#signing-in-with-two-factor) If two-factor is on for your account, signing in on mobile shows **Two-factor verification** with the prompt to enter the code from your authenticator app. Enter it and tap **Verify**. ### Setting two-factor up [Section titled “Setting two-factor up”](#setting-two-factor-up) **Do this in the web app.** The mobile app ships the sign-in challenge only — its Settings screen has **Household**, **Billing**, and **Safe to Spend** sections and no Security section, so there is nowhere in the app to enroll or disable an authenticator. Once you have turned it on from the web, the mobile challenge above works immediately. (For reference, mobile Settings is reached from the **Menu** control in the screen header, then **Settings**.) ## Where you are now [Section titled “Where you are now”](#where-you-are-now) You are signed in with a verified email address, and your household exists but has no accounts in it. Next: [add your first account](/docs/quick-start/add-your-first-account). # Reading your register > The four transaction statuses, the balances above the list, and how to add a transaction by hand. **Step 5 of the Quick start.** Your accounts have transactions in them — some typed in, some imported. This page is how to read them. The register is one account’s transaction list. Open it by choosing the account. ## The four statuses [Section titled “The four statuses”](#the-four-statuses) Every transaction is in exactly one of four states. Three of them you control; one comes from your bank. ### Uncleared [Section titled “Uncleared”](#uncleared) The default for anything you enter yourself. It means: this has happened as far as you are concerned, but it has not settled at the bank yet. A transaction you post from a scheduled bill also starts here. ### Cleared [Section titled “Cleared”](#cleared) You have seen it on the bank’s side and marked it so. Toggling a row between uncleared and cleared is a single click or tap on its status control. ### Reconciled [Section titled “Reconciled”](#reconciled) Set by reconciling the account, not by hand. When you reconcile, you enter the balance from a statement, Tovari re-checks your cleared rows against it on the server, and — only if they agree — locks the matched rows as reconciled. A reconciled row is **locked**: its status control no longer toggles, so a footed statement cannot be silently un-footed later. Reconcile has its own guide; for now it is enough to know that reconciled is a stronger, deliberate form of cleared. ### Pending [Section titled “Pending”](#pending) **Pending is bank provenance.** It appears only on rows that came from a connected bank and have been authorized but not yet posted — a card swipe this morning, say. You can never put a row into pending yourself; anything you type in is uncleared. Two consequences worth knowing: * When the bank posts the real transaction, Tovari **transitions the same row in place** rather than deleting it and inserting a new one, so any category, payee, or note you added while it was pending survives. * If you had already entered that payment by hand on the same account, sync matches your row instead of adding a second one. Pending rows are shown apart from the settled list so they never quietly move a number you were reading. ## The balances above the list [Section titled “The balances above the list”](#the-balances-above-the-list) The register header shows several figures, all calculated on the server: * **Cleared** — the settled part of the account. * **Uncleared** — what you have recorded that has not settled. * **Pending** — shown when the account has pending bank activity. * **Working Balance** — the headline figure for the account. These are meanings, not a sum you should reproduce yourself: read the numbers the app gives you rather than adding them up. Each row also carries a running **Balance** column, computed server-side in the register’s own order. * Web ### The layout [Section titled “The layout”](#the-layout) The register is a resizable data grid with columns **Status**, **Date**, **Payee**, **Notes**, **Category**, **Amount**, and **Balance**. Click the **Date** header to flip the sort. Above and around the settled list sit two extra sections: * **Scheduled Bills** — occurrences that have not been recorded yet. See [scheduling a bill](/docs/quick-start/scheduling-a-bill). * **Pending** — with the subtitle *not yet posted* — the bank rows described above. Its amount column is reference only until the bank posts a final figure, and its balance column is a projection including the pending row. ### Changing a status [Section titled “Changing a status”](#changing-a-status) The circle in the **Status** column is the control. Click it to move a row between uncleared and cleared. On a reconciled row the control shows a lock and does nothing — it reads *Reconciled (locked)*. ### Adding a transaction by hand [Section titled “Adding a transaction by hand”](#adding-a-transaction-by-hand) Press **Add Transaction** in the header action row. A dialog opens, naming the account the row will land in, with fields for date, payee, amount, category and a note — the same dialog is where you set the payee and the category, which the next page, [categorizing spending](/docs/quick-start/categorizing-spending), covers. Nothing is saved until you press **Add Transaction** in the dialog. **Add Scheduled Item** opens the same dialog dated tomorrow. Any future date is saved as a scheduled item that posts on that day rather than a transaction that moves your balance now, and the dialog tells you so before you save. The action row also carries **Reconcile**, **File Import**, and **Export**. * Mobile ### Getting there [Section titled “Getting there”](#getting-there) The register is not its own tab. Open the **Accounts** tab and tap an account row; the register is pushed inside that tab, so the tab bar stays put and the back gesture returns you to the list. ### The layout [Section titled “The layout”](#the-layout-1) Instead of a grid, the native register is a set of labelled bands stacked down the screen: * The teal header band shows the **WORKING** figure with **CLEARED** and **UNCLEARED** beneath it, and — when the account has pending activity — a line reading *N pending · ≈$X not yet posted*. * **Upcoming** — the scheduled occurrences band. * **Pending at the bank** — the pending rows, in their own band with a clock glyph, exactly the same “authorized but not posted” meaning as the web’s Pending section. * The settled transactions themselves, grouped under date headers. Rows are compact: payee, category dot and name, amount. An uncategorized row shows its category label in amber so it is easy to spot. ### Changing a status [Section titled “Changing a status”](#changing-a-status-1) Tap the circle at the left of a row. Its accessibility label states what the tap will do — *Cleared, tap to mark uncleared* or *Uncleared, tap to mark cleared*. A reconciled row reads *Reconciled — locked* and shows a padlock instead of a tick; tapping it does nothing. ### Adding a transaction by hand [Section titled “Adding a transaction by hand”](#adding-a-transaction-by-hand-1) Tap **Add a transaction** in the register header. The **New transaction** sheet slides up with **Date**, payee, category, amount and note fields; **Save** commits it. A **Transaction / Scheduled** switch sits at the top — leave it on Transaction for money that moves once, or choose Scheduled to set up something that repeats. Tapping an existing row opens the same sheet as **Edit transaction**, without that switch. If you enter a payment that the bank has already flagged as pending, the app offers to settle the two together rather than leaving a duplicate — the confirmation reads *Settle this bill against your bank?* with **Enter and settle**. ### Entering an amount [Section titled “Entering an amount”](#entering-an-amount) Tapping the amount opens your phone’s own number pad, with a **Done** button above it to put it away. The amount itself has no minus sign: whether the money is going out or coming in is set by the **Outflow / Inflow** switch beside it, not by how you type the figure. Reconciling is the one exception. A credit card or loan statement balance is normally negative, so the **Statement ending balance** field carries a **+/−** button to flip the sign. ## Where you are now [Section titled “Where you are now”](#where-you-are-now) You can read any account and tell a settled row from one that is still in flight. Next: making sure each row says what it was for — [categorizing spending](/docs/quick-start/categorizing-spending). # Scheduling a bill > Put a recurring payment on the calendar, and learn exactly what Enter and Skip do. Schedules forecast; they never post on their own. **Step 8 of the Quick start.** Your register reads correctly and your envelopes are set. The last piece is what has not happened yet. ## Schedules forecast — they never post on their own [Section titled “Schedules forecast — they never post on their own”](#schedules-forecast--they-never-post-on-their-own) This is the most important thing on the page. A scheduled bill in Tovari is a **forecast**. It tells the app that $X is expected to leave account Y on date Z, so your projections and your Safe to Spend number can take it into account. **Nothing is ever written to your register automatically.** A schedule cannot create a transaction; only you can, with **Enter**. If you never touch a scheduled occurrence, no transaction exists for it — the occurrence simply stays outstanding. ## Enter and Skip [Section titled “Enter and Skip”](#enter-and-skip) Each bill carries a cursor: the next occurrence Tovari still considers unpaid. Both actions move it, and only one of them writes anything. | Action | What it writes | What it does to the schedule | | --------- | ------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------- | | **Enter** | Creates a transaction dated at the occurrence, prefilled from the bill — payee, category, and signed amount — as an **uncleared** row | Advances the cursor past that occurrence | | **Skip** | Nothing at all | Advances the cursor past that occurrence | So **Skip** is “this one didn’t happen, move on”, not “delete the bill”. The schedule itself is untouched and the next occurrence appears as normal. One refinement on **Enter**: if your bank has already posted that exact payment, Tovari can recognise the existing row and settle the occurrence against it rather than creating a second copy. ## Overdue occurrences stay put [Section titled “Overdue occurrences stay put”](#overdue-occurrences-stay-put) Tovari measures “next due” from that cursor, not from today. An occurrence you never entered does not quietly disappear when its date passes — it stays outstanding and shows as **overdue** on its real date. A bill whose first payment is in the past therefore surfaces immediately, overdue, exactly as it should. The consequence is that a backlog is visible rather than silently discarded, and you clear it by entering or skipping each occurrence. * Web ### Create the schedule [Section titled “Create the schedule”](#create-the-schedule) 1. Open **Bills & Schedule** in the left navigation. 2. Press **Add Bill** in the toolbar. The editor panel opens. 3. Fill it in: * **Amount**, and whether it is an expense or income. * **Category** and **Account**. * **Memo** — optional; it is carried onto the transaction when you enter one. * **Frequency** — one-time, weekly, biweekly, twice-monthly, monthly, quarterly, or annually, with the day-of-month or day-of-week controls the frequency needs. * **First Payment** (or **Date** for a one-time item). 4. The editor autosaves — there is no Save button. If you set a first payment in the past, the editor asks whether you meant it: **Yes, schedule it** keeps the past date (and the occurrence surfaces overdue straight away), or **Use today** moves it forward. Once a schedule is running, **Next Payment** is editable, which is how you reset or nudge the cursor by hand. ### Enter or skip an occurrence [Section titled “Enter or skip an occurrence”](#enter-or-skip-an-occurrence) Scheduled occurrences also appear at the top of the account’s register, in the **Scheduled Bills** section. Each row ends with two small buttons: * The tick — **Enter** — posts the transaction and advances. * The cross — **Skip** — advances only. Each row also shows a projected balance, so you can see what the account looks like after the occurrence lands. * Mobile **Enter and Skip do exactly the same thing here as on the web** — same two verbs, same cursor, same forecast-only rule. What is different is how you reach them: mobile puts them on the row itself rather than in a grid of icon buttons. ### Create the schedule [Section titled “Create the schedule”](#create-the-schedule-1) 1. Open the **Bills** tab in the bottom tab bar. 2. Tap **Add a bill** in the header. The **New Bill** sheet opens. 3. Fill in the amount, **Account**, category, frequency, and **First payment**. 4. Tap **Save**. (Tapping an existing bill opens the same sheet as **Edit Bill**.) ### Enter or skip an occurrence [Section titled “Enter or skip an occurrence”](#enter-or-skip-an-occurrence-1) There are two routes, and they offer the same two verbs in the same order: * **The action strip.** A bill due within the next seven days shows an inline **Enter** / **Skip** pair directly under the row. If an Enter fails, the button becomes **Try again** in place — you do not have to hunt for a banner — and Skip stays available, because a failed Enter has not consumed the occurrence. * **Swipe (iOS).** Swipe the row right to reveal **Enter** and **Skip**. Swipe left instead for **Pause**/**Resume**, **Edit**, and **Delete**. A long swipe fires the leftmost action of the set it revealed, which on the left-swipe side is deliberately Pause — the reversible one — so a careless full swipe can never delete a schedule. On Android, long-press the row for the same menu instead of swiping. A **paused** bill has no outstanding occurrence, so it offers no Enter or Skip at all rather than an action the server would refuse. ## Where you are now [Section titled “Where you are now”](#where-you-are-now) Tovari knows what you have, what you spent it on, what you are budgeting, and what is coming. That is everything the last page needs: [understanding Safe to Spend](/docs/quick-start/understanding-safe-to-spend). # The budget interview > The second onboarding step asks one question — what do you want to budget — and why there is deliberately no step asking what to track. **Step 4 of the Quick start.** Your accounts exist. Onboarding now asks its second and last question before handing you the app. ## Onboarding is two steps, not five [Section titled “Onboarding is two steps, not five”](#onboarding-is-two-steps-not-five) 1. **Add your accounts** — the page you just finished. 2. **The budget interview** — this page. That is the whole of it, on both platforms. ## There is no “what to track” step, on purpose [Section titled “There is no “what to track” step, on purpose”](#there-is-no-what-to-track-step-on-purpose) Most budgeting apps open with a long checklist of categories to pick from. Tovari does not, because **the entire category catalog is adopted into your household automatically when you sign up**. Nothing is left un-tracked, so there is nothing to ask about. That is the “categorize everything, budget selectively” thesis in practice. The interview asks only the second half of it: of everything Tovari is already tracking, which handful do you actually want to *manage* with a budget envelope? Answering it is optional. Picking nothing is a perfectly valid answer — every category is still tracked, and you can flag envelopes later from the Budget screen at any time. See [your first envelope](/docs/quick-start/your-first-envelope). * Web ### What you see [Section titled “What you see”](#what-you-see) The right-hand panel takes over with the heading **What do you want to budget?** and the explanation that everything else is tracked automatically and you can add targets any time on the Budget screen. Below it are a few short lifestyle questions, each with a row of multi-select chips — tap as many as apply, across as many questions as you like. ### Finishing [Section titled “Finishing”](#finishing) The footer button counts your picks: * With nothing selected it reads **Skip for now →**, and continues without sending anything. * With picks selected it reads **Budget *N* items →** and flags them. If something goes wrong or only part of the set could be set up, a notice appears with a retry and an explicit **Continue to Dashboard →**, so you are never stuck at the last step of onboarding — including if you are offline. * Mobile The Expo app runs the **same two steps in the same order**, and the interview asks the same question from the same catalog — this is genuine parity, not a reduced mobile version. What differs is the native chrome around it. ### What you see [Section titled “What you see”](#what-you-see-1) The accounts step ends with two buttons: **Add an account**, and then **Continue** (or **Skip for now** if you added none). Tapping past it moves you to the interview screen, headed **What do you want to budget?** with the subline *Pick the categories you want to keep an eye on. You can change these any time.* Each question renders as a row of tappable chips sized for a finger; tap to select and tap again to clear. ### Finishing [Section titled “Finishing”](#finishing-1) The primary button at the bottom counts your picks exactly as the web footer does — **Skip for now →** with nothing selected, **Budget *N* items →** otherwise — and lands you on the dashboard. If only part of the set could be saved, the screen shows how many of how many were added, with **Retry** and **Continue to Dashboard →** side by side. ## Where you are now [Section titled “Where you are now”](#where-you-are-now) Onboarding is done and you are looking at the app with real accounts behind it. Time to read what is in one: [reading your register](/docs/quick-start/reading-your-register). # Understanding Safe to Spend > Which accounts count toward the headline number, which can never count, and the two settings that shape it. **Step 9 — the last page of the Quick start.** Everything you have done so far feeds one number. This is how to read it. ## What the number means [Section titled “What the number means”](#what-the-number-means) Safe to Spend is the money you can spend without breaking a commitment you have already made. Tovari starts from the balances of your everyday spending accounts, sets aside what is already committed between today and the end of your planning window, and accounts for income arriving in that window. **It is computed on the server, in full, every time you look at it.** The apps display it; they never work it out. That is deliberate: it depends on your accounts, your outstanding bill occurrences, your entered transactions, and your budget, and there is exactly one definition of it so the dashboard and the rest of the app can never disagree. ## Which accounts count [Section titled “Which accounts count”](#which-accounts-count) | Account type | In the pool? | | --------------- | ------------------------------------ | | **Checking** | Yes by default — you can turn it off | | **Savings** | No by default — you can turn it on | | **Investment** | Never | | **Credit card** | Never | | **Loan** | Never | Only checking and savings accounts are ever eligible. Investment accounts, credit cards, and loans **can never be included** — that is by design, not a setting anyone can find. A credit line is money you would owe, not money you have. New accounts follow the defaults above: create a checking account and it joins the pool straight away; create a savings account and it does not until you say so. **Closed accounts drop out.** Closing an account removes it from the pool, so archiving an old checking account changes the number without you having to remember to untick anything. ## The two things you can tune [Section titled “The two things you can tune”](#the-two-things-you-can-tune) Neither of these invents money; they change the horizon and the warning line. * **Planning window** — how many upcoming paychecks the number looks ahead: **1**, **2**, or **3**. Two is the default. A longer window sets aside more upcoming commitments, so the number is smaller and steadier; a shorter one is more immediate. * **Cushion** — the point at which the number starts warning you that things are getting tight. **Automatic** derives it from your own typical spending; **Fixed amount** lets you name a figure. The cushion changes only the warning, never the number itself. If you have no scheduled income yet, Tovari cannot count paychecks, so it falls back to the end of the current month and tells you it has done so. Adding a scheduled paycheck (as a recurring income item — see [scheduling a bill](/docs/quick-start/scheduling-a-bill)) is what turns the window on. * Web ### Include or exclude one account [Section titled “Include or exclude one account”](#include-or-exclude-one-account) The switch is **Include in Safe to Spend**, labelled *Count this account’s balance toward your disposable-cash number*. It appears in the account editor — both the Accounts screen’s detail panel and the register’s account dialog — and only on checking and savings accounts. There is nothing to toggle on the other three types, so no switch is drawn. ### Change the window and the cushion [Section titled “Change the window and the cushion”](#change-the-window-and-the-cushion) 1. Open **Settings**. 2. Choose **Safe to Spend** in the left rail — it sits between **Household** and **Billing**. 3. Pick 1, 2, or 3 paychecks for the planning window, and choose **Automatic** or **Fixed amount** for the cushion. The section previews what your choice does before you commit it, and warns you if someone else in your household changed the same settings while you had the page open. ### Reading it [Section titled “Reading it”](#reading-it) Safe to Spend has its own tab on **Reports** as well as the dashboard headline, with the account-by-account breakdown behind it. * Mobile **The inclusion rules are identical** — checking in by default, savings out by default, and investment, credit card, and loan accounts never eligible whatever you do. ### Where the settings live [Section titled “Where the settings live”](#where-the-settings-live) 1. Tap the **Menu** control in the screen header. 2. Choose **Settings**. 3. Expand the **Safe to Spend** accordion section. (The other sections are **Household** and **Billing**; each opens in place rather than pushing a new screen.) The card there is the same pair of controls as the web: a **1 / 2 / 3** paycheck window and the automatic-or-fixed cushion, with a preview of the effect and the same “someone else changed this” resolution band. The window control is disabled — with an explanation and a way to add one — until you have a scheduled paycheck for it to count. ### Changing which accounts count [Section titled “Changing which accounts count”](#changing-which-accounts-count) **Use the web app for this one.** The native account editor has no **Include in Safe to Spend** switch. On mobile the flag is set when you create the account, from the type you choose — checking joins the pool, everything else does not — and cannot be changed afterwards from the phone. Everything else about Safe to Spend behaves identically. ## That is the Quick start [Section titled “That is the Quick start”](#that-is-the-quick-start) You have an account, a bank connection, a categorized register, a budget envelope, a scheduled bill, and a Safe to Spend number that accounts for all of it. To go deeper, read [Transactions](/docs/features/transactions) for the register in full — what each status means, how a bank transaction settles, and how to reconcile against a statement — and [Safe to Spend](/docs/features/safe-to-spend) for the whole of the number you just met. # What Tovari does > Tovari answers one question — how much can I safely spend right now — and every other part of the app exists to make that answer trustworthy. Tovari is a personal finance app built around a single question: **How much money can I actually spend right now, without breaking something later?** That answer is the **Safe to Spend** number. Everything else in Tovari — accounts, the register, categories, envelopes, scheduled bills — exists to make that one number trustworthy. ## The thesis [Section titled “The thesis”](#the-thesis) Most budgeting apps show you a balance. A balance overstates things: it still contains the rent that leaves on the first, the card payment you already authorized, and it knows nothing about the paycheck that has not landed yet. Tovari starts from the money in your everyday spending accounts, sets aside what is already committed between today and your upcoming paychecks, and shows you what is genuinely left over. The result is one figure you can act on. Three things follow from that, and they shape how the whole app behaves. ### 1. Safe to Spend is computed on the server [Section titled “1. Safe to Spend is computed on the server”](#1-safe-to-spend-is-computed-on-the-server) Tovari does not add the number up in your browser or on your phone. The figure, its planning window, and its “getting tight” cushion are all worked out by the backend and sent to the apps already resolved, so the web app and the mobile app can never disagree about your money. You choose two things about it: the **planning window** — how many upcoming paychecks it looks ahead, one, two, or three, with two as the default — and whether the cushion that turns the number amber is worked out automatically from your own typical spending or fixed at an amount you name. The cushion changes only when Tovari starts warning you, never the figure itself. ### 2. Only everyday spending accounts count toward it [Section titled “2. Only everyday spending accounts count toward it”](#2-only-everyday-spending-accounts-count-toward-it) Checking and savings accounts can be part of the Safe to Spend pool. Investment accounts, credit cards, and loans never can — that is by design, not a preference someone can flip. A credit line is not cash you have, and a retirement balance is not money you can spend on groceries. [Understanding Safe to Spend](/docs/quick-start/understanding-safe-to-spend) covers exactly which accounts are in, which are out, and what you can change. ### 3. Categorize everything, budget selectively [Section titled “3. Categorize everything, budget selectively”](#3-categorize-everything-budget-selectively) Every transaction in Tovari carries a category — there is a protected **Uncategorized** category so a row can never be left without one. That is what makes your reports and your typical spending a complete picture rather than a sample. Budgeting is separate and opt-in. You flag the handful of categories you actually want to manage as envelopes and leave the rest categorized but unbudgeted. Nothing is flagged as an envelope for you. ## What Tovari tracks [Section titled “What Tovari tracks”](#what-tovari-tracks) | Piece | What it is for | | ----------------------- | --------------------------------------------------------------------------------------------------------- | | **Accounts** | Where your money is. Grouped as Cash Accounts, Investments, Credit Cards, and Loans. | | **Register** | Every transaction on an account, with a running balance and a status telling you how settled each row is. | | **Categories** | What a transaction was for. Applied to everything, automatically where Tovari is confident. | | **Envelopes** | The categories you chose to budget, with amounts that carry forward month to month. | | **Bills and schedules** | What is coming, and when. Forecast only — Tovari never posts a payment behind your back. | Movements between two of your own accounts are treated as transfers rather than spending, so paying your credit card off from checking never shows up as a new expense. ## Where to start [Section titled “Where to start”](#where-to-start) Work through the Quick start in order. Each page picks up exactly where the last one left off, from an empty screen to a categorized register you can trust. 1. [Create your account](/docs/quick-start/create-your-account) 2. [Add your first account](/docs/quick-start/add-your-first-account) 3. [Connect a bank with Plaid](/docs/quick-start/connect-a-bank-with-plaid) 4. [The budget interview](/docs/quick-start/the-budget-interview) 5. [Reading your register](/docs/quick-start/reading-your-register) 6. [Categorizing spending](/docs/quick-start/categorizing-spending) 7. [Your first envelope](/docs/quick-start/your-first-envelope) 8. [Scheduling a bill](/docs/quick-start/scheduling-a-bill) 9. [Understanding Safe to Spend](/docs/quick-start/understanding-safe-to-spend) # Your first envelope > Flag a category as budgeted, give it a target, and understand what carries forward month to month. **Step 7 of the Quick start.** Everything is categorized. Now choose the few categories you want to manage actively. ## What an envelope is [Section titled “What an envelope is”](#what-an-envelope-is) An envelope is a category you have flagged as **budgeted**. Flagging it gives you a monthly target, a spent figure, a remaining figure, and a balance that carries forward. Categories you do not flag are still fully tracked — they appear in your reports and in the **All Other Categories** bucket on the budget screen. They simply have no target and no carry-forward. ## Two rules worth knowing up front [Section titled “Two rules worth knowing up front”](#two-rules-worth-knowing-up-front) **Nothing is flagged for you.** Tovari never decides a category deserves an envelope. The budget interview during onboarding was your first opportunity, and every envelope after that is one you chose deliberately. **The flag is not per-month.** Flagging a category as budgeted persists — it stays an envelope in every following month until you remove it. You are not re-declaring your budget each month; you are adjusting the targets on envelopes that are already there. ## Carry-forward starts where you started [Section titled “Carry-forward starts where you started”](#carry-forward-starts-where-you-started) An envelope’s running balance is anchored to the month you flagged it, so it never invents history from before it existed. Flagging while viewing an earlier month pulls that anchor back so the earlier month takes part; re-flagging in a later month leaves the earlier anchor alone. Removing an envelope and flagging it again starts a fresh running balance from that point. The rollover figure itself is computed on the server and shown to you — do not try to reconstruct it by hand from targets and spending. * Web ### Flag your first envelope [Section titled “Flag your first envelope”](#flag-your-first-envelope) 1. Open **Budget** in the left navigation and make sure you are on the month you want. 2. Select the **All Other Categories** row to open its panel. Under *What this usually costs* it lists the categories you are spending on but not budgeting, with what each one actually cost this month. 3. Find the one you want and press **Budget this** on its row. The category is promoted out of the bucket and appears in the budget grid as its own line, in that month and every month afterwards. ### Give it a target [Section titled “Give it a target”](#give-it-a-target) Click the budgeted amount cell on the category’s row and type the figure. The budget screen autosaves — there is no Save button. Selecting the category’s row opens its detail panel, which shows its target, what has been spent, what remains, what rolled over, and its recent average. * Mobile The rules are identical on mobile — the same persistent flag, the same “nothing is flagged for you”, the same server-computed carry-forward. The route to them is a drawer and a sheet instead of a grid and a side panel. ### Flag your first envelope [Section titled “Flag your first envelope”](#flag-your-first-envelope-1) 1. Open the **Budget** tab in the bottom tab bar. 2. Scroll to the **Not budgeted** drawer at the bottom of the list — its header shows how many categories are in it — and tap to expand. 3. Tap the category you want. The **Budget *name*** sheet opens. 4. Tap **Add to budget**. The sheet closes only once the change has actually saved, and shows the failure inline if it did not. The category moves out of the drawer and into the budgeted list. ### Give it a target, and see where it stands [Section titled “Give it a target, and see where it stands”](#give-it-a-target-and-see-where-it-stands) Tap a budgeted category to open its sheet. It shows **Target**, **Spent**, **Remaining**, **Rolled over**, and a **3-mo average**, and closes with **Done**. To set the amount, use the **Auto-fill** sheet from the category row — it offers suggestions (such as recent averages) that you can apply to that one category or to its whole section, which is quicker on a phone than typing figures into a grid. ## Where you are now [Section titled “Where you are now”](#where-you-are-now) You have at least one real envelope with a target, and you know that flagging it was a one-time decision rather than a monthly chore. Next, put your recurring outgoings on the calendar: [scheduling a bill](/docs/quick-start/scheduling-a-bill). # What's New > Release notes for Tovari, newest first. Every released version of Tovari, newest first. Each entry is the release note published with that version. * [2026.09.04.1](/docs/whats-new/2026-09-04-1) * [2026.09.03.1](/docs/whats-new/2026-09-03-1) * [2026.09.02.3](/docs/whats-new/2026-09-02-3) * [2026.09.02.2](/docs/whats-new/2026-09-02-2) * [2026.09.02.1](/docs/whats-new/2026-09-02-1) * [2026.09.01.1](/docs/whats-new/2026-09-01-1) * [2026.08.31.2](/docs/whats-new/2026-08-31-2) * [2026.08.31.1](/docs/whats-new/2026-08-31-1) * [2026.08.30.1](/docs/whats-new/2026-08-30-1) * [2026.08.29.1](/docs/whats-new/2026-08-29-1) * [2026.08.28.1](/docs/whats-new/2026-08-28-1) * [2026.08.23.1](/docs/whats-new/2026-08-23-1) * [2026.08.20.1](/docs/whats-new/2026-08-20-1) * [2026.08.18.1](/docs/whats-new/2026-08-18-1) * [2026.08.15.1](/docs/whats-new/2026-08-15-1) * [2026.08.11.1](/docs/whats-new/2026-08-11-1) * [2026.08.09.1](/docs/whats-new/2026-08-09-1) # 2026.08.09.1 > What's new in this release of Tovari. ## New features [Section titled “New features”](#new-features) **Web dashboard hero conformance: standardised header, Safe to Spend states, period selector, Balance Projection footer** (KAN-850) The top of your dashboard now has a cleaner, more consistent look, bringing your greeting, the Add Transaction button, the month selector, and your key numbers together in one refreshed header. Safe to Spend uses clearer color-coded states so you can tell at a glance whether you’re comfortable, running tight, or about to overspend, with a bold warning when your spending would take you below what’s safe. A new period selector lets you view your spending for this month, last month, or the last three months, and the Spending by Category and Spending by Payee breakdowns update to match. Your Balance Projection can now be filtered to all accounts, just checking, or just savings, and it marks where today falls along the timeline. It also shows your lowest projected balance and the date it’s expected, highlighted in red whenever that balance is projected to drop below zero. Together these updates make it easier to read your financial picture and see what’s coming. **Enable Google Sign-In for the mobile app (iOS + Android builds)** (KAN-852) The Tovari mobile app now lets you sign in with your Google account, so you no longer need a separate email and password to get into the app on your phone or tablet. Choose the ‘Sign in with Google’ option on the login screen, pick your Google account, and you’re in — the same quick sign-in the web app already offered, now on both iPhone and Android. If you’re new to Tovari, signing in this way sets up your account for you in a single step. If you already use an email and password, nothing changes — that sign-in keeps working exactly as before. The app also switches cleanly between different Google accounts, so signing out and back in with a different account works the way you’d expect. **Update Balance Projection widget to match iOS/Android design spec** (KAN-854) The Balance Projection now gives you a clearer, easier-to-read picture of where your balance is headed in the days ahead. It highlights the lowest point your balance is expected to reach and the exact date it happens, so you can spot a tight spot before it arrives. A clearly marked zero line and a shaded area below it let you see at a glance whether — and when — your balance might dip into the negative. The highlight on your lowest point turns red when your balance is projected to fall below zero, and if you’re already below zero the view says so in plain language. The refreshed look matches the rest of the app for a more consistent, polished experience. **Review Center (web) / Alerts (iOS + Android): detected-item queues with approve-before-apply** (KAN-906) Tovari now has a Review Center on the web and an Alerts tab on iPhone and Android — one place that gathers everything Tovari has noticed but hasn’t acted on yet. You’ll find money you moved between your own accounts that is still being counted as spending, repeating charges that could become scheduled bills, and transactions still waiting to be filed into a category. Nothing is ever applied on its own: every item shows you exactly what it will change before you approve it, and anything you approve can be undone. A count sits beside Review Center and on the bell so you can tell at a glance whether anything needs you, and it disappears completely when nothing does. Reviewing transfers has moved out of the transaction register into this one place, so you are never asked the same question in two different spots. **Native mobile signup: Phase 1 — account creation through budget interview (iOS + Android)** (KAN-908) You can now create a Tovari account directly from the iPhone and Android apps, without having to start on the web. Signing up guides you through it one step at a time: enter your name, email, and password, confirm your email with a code we send you, then review and accept the Terms of Use and Privacy Policy. From there the app helps you get going right away with a brief welcome, adding your first accounts, and a short setup where you choose the spending categories you want to budget. Returning users can sign in with an email and password, use Sign in with Apple or Google, and complete two-step verification when it is turned on for the account. And if something goes wrong along the way, such as a wrong password, a locked account, no connection, or a session that has expired, the app now explains clearly what happened and how to continue. **Web Dashboard Board: rebuild from scratch per Claude Design brief (supersedes KAN-819, KAN-850)** (KAN-929) Your dashboard has a refreshed design that gives you a clearer, at-a-glance view of your money. At the top, your Safe to Spend amount now shows one of three plainly labeled states — healthy, getting tight, or negative — so you always know where you stand, and you can open a breakdown to see how each of your accounts and your upcoming bills add up to that figure. Key numbers like your net worth and total spending now sit together in one row, and dedicated cards track your financial goals, account balances, spending by category and by payee, and the budget categories you’re watching. A month selector lets you step back through earlier periods to compare your spending over time, and the balance projection at the bottom can now include your investment accounts alongside your other balances. Together these give you a faster, more accurate read on your finances the moment you open the app. **Safe to Spend settings: user-configurable planning window + “getting tight” threshold (web, mobile web, Expo)** (KAN-938) You can now tell Tovari how far ahead to plan your Safe to Spend number and when to warn you that money is getting tight. In Settings, choose whether the figure covers your next one, two or three paychecks — it now covers two by default, so the number reflects a little more of the road ahead than it did before. You can also let Tovari work out your safety cushion automatically or set an amount of your own, and a live preview shows exactly what your new number will be before you save it. Because these settings belong to your household rather than to one person, both of you always see the same figure and the same status, and you’re told if your partner changes something while you’re editing. If Tovari doesn’t have enough spending history yet, it now says so plainly and offers to set a starting cushion, instead of calling a very small balance healthy. Everywhere the number appears — your dashboard, your reports and your phone — it now reads from one place, so the amount, the status and the wording always match. **Web Dashboard Board: reconcile rebuilt UI against Claude Design brief & mocks (KAN-929 follow-up)** (KAN-1014) The dashboard did not look the way it was designed to: the header felt boxed-in, spacing and text sizes were inconsistent, and some details didn’t match the rest of the app. It now matches the intended design — the colored header stretches across the full width of the page, and the cards below line up with cleaner, more consistent spacing. Your Safe to Spend amount stands out more clearly: it shows in green when you’re in good shape, amber when things are getting tight, and inside a solid red box with a “Needs Attention” tag when you’re short. Opening the Safe to Spend breakdown now slides the details in right under the header instead of covering the page, and every amount going out is shown in red so shortfalls are easy to spot. When an account is short, the breakdown also tells you plainly which account it is and by how much, with a suggestion for what to do about it. The month controls and buttons at the top of the dashboard now work and look the same as they do on the Budget screen. **Show when a scheduled bill already has a matching pending bank transaction (web + mobile) instead of flagging it red as overdue** (KAN-1015) When a payment for one of your scheduled bills had already arrived at your bank but hadn’t finished going through, the app used to mark that bill red as if you had missed it — even though the money was already on its way. Now the bill shows a clear “payment pending” look instead: a blue highlight, a PENDING tag, and a note that the payment is at your bank and will take care of the bill automatically once it finishes. A bill that is truly late, with no payment on the way, still shows red, so that warning keeps its meaning. If you try to mark a bill as paid while a matching payment is already pending, the app now pauses and asks you to confirm first — showing you the pending payment — so you don’t accidentally record the same payment twice. This works the same on the website, on your phone’s browser, and in the iPhone and Android apps. ## Fixes [Section titled “Fixes”](#fixes) **Row-menu “Make recurring” still offered on transfer legs whose counterpart hasn’t arrived** (KAN-631) When you move money between your own accounts, the app records both sides of that movement so it isn’t counted as spending. But if only one side had come in from your bank so far, the menu on that row still offered to turn it into a recurring bill. Setting one up would have counted the same movement twice — making your Safe to Spend and your projected balances look lower than they really are. That option is now correctly hidden on both sides of every transfer, whether or not the matching side has arrived yet. Everything else on the row menu is unchanged, and ordinary transactions can still be made recurring exactly as before. **mergePayees does not repoint bills.payee\_id (leaves bills on an inactive payee)** (KAN-640) When you merged two payees together or deleted a payee, any bills connected to that payee could get stuck — trying to edit one of those bills failed with a confusing “Payee not found” message. That no longer happens. Merging payees now moves their bills over to the payee you keep, and a bill only takes on the kept payee’s name if you had not given it a custom name of your own. Deleting a payee now simply unlinks its bills, and each bill keeps its name so nothing disappears from your schedule. Bills that were already stuck from earlier merges or deletions are repaired automatically, so you can edit them again. **deletePayee / softDeleteOrphanedPayees can deactivate a payee a bill still references** (KAN-641) When you deleted a payee, or when the app automatically tidied up payees that no longer seemed to be in use, a bill that still relied on that payee could be left pointing at one that had been removed. That bill would then stop working and could no longer find its payee, even though you had never touched the bill itself. Now, deleting a payee cleanly releases it from any bills that were still using it, so those bills continue to work normally. The automatic cleanup also leaves a payee in place whenever a bill still depends on it, so it can never strand one of your bills. Any bills that were already affected by this problem are repaired automatically and open and work as expected again. **summarize() counts ended-but-active recurring bills in the Bills hero totals and activeBillCount** (KAN-780) The totals at the top of the Bills screen were counting bills that had already finished. A recurring bill that reached its end date or its final payment — like a paid-off loan or an expired subscription — was still included in your active bill count and in the Monthly Out and Monthly In amounts, making them look higher than they really were. Those finished bills are now left out of the totals, so the numbers at the top reflect only the bills that will actually come due again. Finished bills still appear in your bills list, so nothing disappears — the count at the top may simply be smaller than the number of bills you see listed. This correction applies on both the web and the mobile app. **GET /bills/due computes status/daysUntil from server-UTC today instead of the client timezone** (KAN-781) The bill details shown on the Budget screen could judge due dates by the wrong day. Because the app was checking the date against a clock in a different time zone than yours, looking at your budget in the evening could show a bill that is actually due tomorrow as due today, or a bill due today as already overdue. The app now uses your own local calendar day when deciding whether a bill is upcoming, due today, or overdue. A bill due tomorrow now correctly shows as due in one day, and a bill due today no longer appears overdue. Nothing else about your bills changed — amounts, due dates, and paid status are exactly as they were. **Stale transfer suggestions never retired — review list doesn’t re-apply refutation on read** (KAN-815) When Tovari spots money that appears to move between two of your own accounts, it lists these as possible transfers for you to review and link together. Previously, some of these suggestions stuck around even after they clearly no longer qualified, such as a card payment or an everyday purchase that was never a transfer between your accounts. Because each suggestion was only checked at the moment it was first created, these outdated, false matches lingered indefinitely and could never clear on their own. That was risky, because confirming one of them would have wrongly hidden a real expense or deposit from your reports. Now the possible-transfers list re-checks every suggestion each time you open it and automatically removes any that no longer qualify, so you only see genuine transfer matches that are worth reviewing. **Fix “Enter now” on a pending row duplicating the charge when the bank posts it** (KAN-816) Previously, if you marked a pending charge as entered before your bank officially posted it, the app could add the bank’s posted version as a separate transaction, counting the same charge twice and throwing your account balances off. Now, entering a pending charge early settles that same transaction in place when the bank posts it, so the charge is only ever recorded once and your balances stay accurate. Any duplicate charges this problem had already created have been cleaned up and the affected balances corrected. You can safely enter a pending charge ahead of the bank without worrying about it doubling up later. **Entering a scheduled bill after its bank payment already imported creates a permanent duplicate (entered-occurrence merge only runs bank→entered, never entered→bank)** (KAN-931) When you had a scheduled bill on a connected bank account and its real payment had already been imported from your bank, marking that bill as paid used to add a second, separate line for the very same payment. The two entries never linked together on their own, so the duplicate stayed until you spotted it and manually matched or removed one — throwing off your balances and spending totals in the meantime. Now, before adding a new entry, the app checks the account for a payment that already arrived from your bank and matches the bill. When it finds a clear, confident match, it marks the scheduled bill as paid by that existing payment instead of creating a duplicate, keeping the actual bank amount even when it differs a little from the bill’s usual figure. If there’s any doubt, it leaves your entry exactly as it worked before, so nothing is ever combined by mistake. **Web Reports payee tab silently applies hidden budget-only scope with no visible toggle** (KAN-948) The Spending by Payee view in Reports was quietly leaving some of your spending out of the picture. If you had turned on “Budget Only” in the Income vs Expenses report, that same narrowing was silently applied to your payee totals too — even though the payee view offers no such option and gave no sign it was happening. This is now fixed: Spending by Payee always shows your complete spending for the chosen time period, across everything you spent, on both the web and the mobile app. If some payee totals look higher than before, that is the previously hidden spending being counted again — the numbers are now complete. The Income vs Expenses report keeps its Budget Only option and works exactly as it did before. **Auto-link matcher data defect: 0/180 transfer legs auto-linked in prod (KAN-836 exposes symptom, does not fix it)** (KAN-982) When you moved money between two of your own accounts — like paying your credit card from your checking account — the app often failed to recognize the two sides as one transfer, so the payment could show up as if you had spent that money. The app now recognizes these matching pairs far more reliably and connects them automatically, keeping money you moved between your own accounts out of your spending totals. Credit card payments brought in from your bank now land in the Credit Card Payment category consistently, instead of sometimes being labeled as loan payments. On the Reports screen, the Budget Only filter is now visible on the Spending by Category and Spending by Month views, and it switches off automatically when you move to a view where it doesn’t apply — so a report always shows exactly what its filter says. On your phone, editing one side of a linked transfer no longer offers the option to make it recurring, since moving money between your own accounts isn’t a bill. Transactions already in your history keep their current categories; these improvements apply as new activity comes in. **KAN-836 shipped the rejected option — spend universes were decomposed, not aligned** (KAN-997) The Budget screen’s monthly spending total was counting money you moved between your own accounts as if it were spending, so the total there could disagree with the totals shown in Reports and in the yearly budget view. Your Safe to Budget amount was also being reduced by those same account-to-account moves, making it look like you had less to work with than you really did. Both are fixed: the monthly total now matches Reports and the yearly view exactly, and moving money between your accounts no longer counts against what you can budget. Because of this, some people will see their Safe to Budget amount go up — that higher number is the correct one. Transfer categories still appear everywhere you pick a category, so you can keep labeling those moves the same way you always have. **Tab key does not reliably advance to the next form field — skips fields in Account creation and Bill entry forms** (KAN-1041) Previously, pressing the Tab key while filling out a form didn’t always move to the next field — it could silently skip over items like the account type when adding a new account, or the category and account when scheduling a bill, forcing you to reach for the mouse. Now Tab reliably advances through every field in order with nothing skipped, and Shift+Tab moves back through them the same way. This works across the New Account form and the bill scheduler, including their dropdown menus, which you can now open and choose from entirely with the keyboard. A subtle outline also appears around whichever control you’ve tabbed to, so it’s always clear where you are on the form. **payee\_mappings not repointed by POST /payees/merge; loadNormalizationContext reads it with no is\_active filter** (KAN-1116) When you merged two payees into one, the app was quietly leaving traces of the old payee behind, so newly imported transactions could still be matched to the payee you thought was gone — merging now carries everything over to the payee you kept. Deleting a payee that your scheduled bills relied on also used to unlink those bills silently, with no warning; the app now tells you how many scheduled bills would be affected and asks you to confirm before going ahead. Your bill names are preserved either way, so nothing on your schedule loses its label. Separately, if you deleted a transaction and later tried to enter it again, the app could wrongly refuse to save the new copy; that now works — re-entering a deleted transaction saves normally, while accidental double entries are still caught. Together these fixes make merging and deleting payees safe and predictable, with no leftover connections behind the scenes. ## Improvements [Section titled “Improvements”](#improvements) **Reconcile budget totals universe with canonical spend universe (Total Spent vs totalOutflowCents)** (KAN-836) On your dashboard, the total for how much you’ve spent could differ from the spending totals shown on other screens, with nothing to explain why. The gap came from money moving into or out of accounts you don’t track in the app: your dashboard total counted those movements while the other screens left them out. Now, whenever any of that untracked activity is part of your spending total, a short note appears just beneath it telling you how much of the total it accounts for. If the figure ever looks off, you can see the reason at a glance and reconcile it against your other screens. The totals themselves haven’t changed — you simply get the explanation that was missing before. **Shared accessible Select/dropdown primitive for the remaining div-onClick sites app-wide** (KAN-1054) Many of the app’s dropdown menus and pickers — like the category picker in the transaction register, the account filters on the Bills and Reports pages, and the account type selector — could only be used with a mouse: pressing Tab skipped right over them and the arrow keys did nothing. Now every one of these menus can be reached with the Tab key and used entirely from the keyboard. Arrow keys move through the choices, Enter picks the highlighted one, and Escape closes the menu and returns you to where you were. Screen readers also announce these menus properly now, so it is clear what each control is and which option is highlighted. Everything looks exactly the same as before — nothing moved or changed visually. Clicking anywhere outside an open menu now closes it in a few more places, matching how the rest of the app already behaves. **AccountFormModal: add focus trap, role=dialog, and Escape-to-close** (KAN-1055) The window for adding or editing an account now behaves the way you would expect a pop-up window to. Pressing the Escape key closes it, just like clicking Cancel or clicking outside it. When you move through the window with the Tab key, your place now stays inside the window instead of wandering off into the page behind it. When the window closes, you are returned to the spot you were working from before it opened. And if you use a screen reader, the window now announces itself properly, including whether you are adding a new account or editing an existing one. # 2026.08.11.1 > What's new in this release of Tovari. ## New features [Section titled “New features”](#new-features) **Mobile nav rework: Reports tab restored, Alerts moved to menu, dashboard indicator cleanup, root-screen menu icon** (KAN-1209) Reports is back in its usual spot at the bottom of the mobile app, so you can jump straight to it from any screen without hunting for it. Alerts now lives in the new menu, which you open with the three-line button at the top left of the Home, Accounts, Budget and Reports screens — and a small amber count on that button still tells you at a glance how many items are waiting for you. The menu also gets you to your bills and schedule, settings and help from anywhere, and opening Alerts from it gives you a back button to return to whatever you were doing. On the Home screen, the small circle with your initial has been replaced by that menu button. The “Updated a moment ago” note and the “Needs Attention” tag under your Safe to Spend amount are gone, since the amount already turns red and tells you how far short you are when money is tight; the “Healthy” and “Getting tight” labels still appear as before. **Mobile: Unify screen headers into a shared ScreenHeader (chrome + band contract)** (KAN-1290) The app’s main screens now share one consistent look at the top: the same colors, the same centered title, and the same controls in the same places, so nothing shifts or changes as you move between tabs. Bills now has its own spot in the bottom navigation bar, so your bill schedule is always one tap away instead of tucked inside the home screen. Adding something new now happens from a plus button at the top of each screen — including a new one on your home screen — replacing the old raised button in the middle of the bottom bar. The Reports section gains a new Income vs Expenses report that lays out what came in and what went out month by month, with a breakdown showing exactly where the gap between them came from. Searching your bills now lives inside the filter panel alongside your other choices, and the filter button shows a small dot whenever a search or filter is narrowing what you see. ## Fixes [Section titled “Fixes”](#fixes) **Review Center’s “Safe to Spend drops to $X” disagrees with the dashboard hero for any household not on window 1** (KAN-1072) You can tell the app how far ahead to plan when it works out what’s safe to spend, and that setting now applies everywhere that figure appears. Until now the review area — where you confirm the recurring bills and payments the app has spotted — quietly ignored your choice and always planned just one paycheck ahead, so the amount it showed you could differ from the amount on your dashboard. Both places now look at the same setting, so the two figures agree and change together whenever you adjust how far ahead you want to plan. If the app ever can’t read your preference, both places fall back to the same sensible default instead of drifting apart. Your saved setting is unchanged, and each household’s figure is based only on its own choice. **KAN-982 shipped PRIMARY-level PFC matching where its own binding ruling required DETAILED — re-opens the false-link class** (KAN-1163) When money left one of your accounts and a similar amount arrived somewhere else around the same time, the app could occasionally treat the two as a transfer between your own accounts even when they were unrelated — for example, a bill payment matched against a deposit that happened to be the same size. Because transfers are kept out of your spending and income totals, those amounts could quietly disappear from your budget, your reports, and your safe-to-spend number without anything looking wrong. The app is now much stricter about connecting two items on its own: it only links them automatically when your bank’s own information clearly identifies both sides as a transfer. When the match is less certain, the app shows you the pair as a suggestion so you can confirm or dismiss it yourself instead of deciding for you. Everything you have already entered or approved stays exactly as it is. **payee\_mappings read path and the orphan sweep still yield dead-payee ids — KAN-1116 fixed only the merge write path** (KAN-1164) After you merged two payees together or deleted one, the app could still quietly match newly imported transactions to the payee that no longer exists, so those transactions came in attached to a name you had already cleaned up — and the old spelling variations it had learned stayed behind even after the payee was gone. Imports now always match to a payee that is still in your list, so a merge or a delete really is the last time you have to think about that name. Cleaning up an unused payee now also clears the spelling variations it had learned, instead of leaving them behind where they could resurface later. Deleting a payee that is still attached to a bill continues to stop and ask you first, and the counts the app reports back after a merge or delete are unchanged. The rest of this release is behind-the-scenes tidying, with no change to how anything looks or behaves. ## Improvements [Section titled “Improvements”](#improvements) **Enforce idempotency keys on all write endpoints** (KAN-26) If a save was interrupted — a dropped connection, a slow response, or a second tap on a button — the app could quietly apply the same change twice, leaving a duplicate payee, a repeated bill edit, or a transfer confirmed more than once. Saving now recognizes a repeated attempt as the same action and returns the original result instead of doing the work again, so a retry can no longer double up your data. This covers your accounts, bills, payees, transfers, and the transaction register, including reconciling an account and saving your register view. When a save is retried, the numbers you see back — such as how many transactions were reconciled — are the ones from the original save rather than freshly recalculated figures that could look wrong. And if an attempt fails partway through, nothing is left half-applied, so simply trying again works cleanly. **Deleting a Plaid-settled transaction leaves the bill cursor/history stranded** (KAN-438) When you deleted a transaction that had been used to mark a bill as paid, the bill stayed marked as paid and moved on to its next due date, with no way to put it back — the payment you removed also quietly skewed the app’s sense of what that bill normally costs. Deleting such a transaction now returns the bill to the date it was due and removes the payment from its history, so the bill shows up as unpaid again exactly as you would expect. This works the same whether you entered the payment yourself, brought it in from a file, or the app matched it to your bank automatically, and it also works when the payment was part of a transfer between two of your accounts. If your bank later withdraws a transaction that was paying a bill, the app now leaves it in your register with its usual undo option instead of removing it behind your back. Separately, entering a bill whose payee has since been removed now posts the payment with the payee left blank rather than attaching a name you no longer use, and an import containing one of these bills still brings in every other transaction as normal. **No persisted Google-identity linkage (google\_sub) — blast radius grew with native client** (KAN-876) Signing in with Google is now more dependable. The app now remembers your actual Google account, not just its email address, so if you ever change the email on your Google account you will still land in your own Tovari account instead of being turned away or mixed up with someone else. If you try to sign in with a Google or Apple account whose email is already tied to a different sign-in identity, you now get a clear explanation of what happened and what to do, instead of a vague failure message. When you ask us to erase your account, we now also disconnect Sign in with Apple on your behalf, so the app no longer appears in your Apple settings afterward. We also fixed a rare timing glitch where signing out at just the wrong moment could leave the app appearing signed in. Finally, sign-in error messages are now announced immediately to people using screen readers. # 2026.08.15.1 > What's new in this release of Tovari. ## New features [Section titled “New features”](#new-features) **Budget: retire the “Reserved” forecast – adopt the reserve-free math contract on the month header + mobile** (KAN-1626) Your budget’s monthly summary now gives you a truer picture of your plan. Previously, the app quietly set aside an estimated amount for spending in categories you hadn’t budgeted, which shrank your headline number and could even make you look over-budgeted when you weren’t. That hidden set-aside is gone: your headline now simply shows your expected income minus what you’ve actually planned, and past months show what really came in and went out. Spending outside your budget lines now appears as an “Everything else” line you control – you can set an amount for it each month, and it behaves like any other budget line, with a gentle one-time reminder if that spending has been adding up. Because of this change, your headline number will rise by the amount that was previously set aside and some over-budgeted warnings will disappear – this is a correction to how the number was calculated, not extra money to spend. One note for shared households: the “Everything else” amount is shared, so setting it updates the plan everyone sees. **Mobile header plan – Phase 2-4 reconciliation: Reports figure, breakdown runway bar, STS copy table, chrome-row search (HDR-4/6/7/9)** (KAN-1639) Each report in the mobile app now leads with the number that matters: the top of the screen shows a big headline total – your total income for the category and month views, total spent for payees, and your net cash flow – with three quick time-period choices right underneath, and you can switch between reports just by tapping the report’s name at the top. The breakdown screen now shows the colored bar that illustrates where your balance goes, right under its heading, and it always matches the bar on your dashboard exactly. The wording that describes how your safe-to-spend money is doing now reads the same everywhere – the dashboard and the breakdown can never show two different phrases for the same situation. Searching your bills is also easier: instead of being tucked away in the filter panel, the search now sits right at the top of the Bills screen, narrows the list as you type, and shows a live count of how many bills match. ## Fixes [Section titled “Fixes”](#fixes) **Opening-plug re-arm cannot clear a stale plug whose correct value is $0 (‘already-balanced’ skip leaves the drifted row); KAN-930 monitor’s rearmOpeningPlug remedy is a no-op for this class** (KAN-1239) Until now, changing anything about a transaction from a linked bank account stopped the app from helping with the rest of it – rename a purchase and its category would never be filled in for you again, or pick a category and the messy bank text would stay messy forever. Now your changes are protected one piece at a time: whatever you set by hand stays exactly as you left it, and the app keeps tidying up only the parts you have not touched. Separately, when a linked account’s starting balance no longer needs the small opening adjustment the app originally added to make things line up, that adjustment is now removed on its own instead of lingering and quietly throwing the account’s balance off. We also fixed a problem with the tool our support team uses to rebuild an account’s history from scratch: bills that had already been marked paid are now cleared out and put back on schedule properly, so those payments are recognized again once the history reloads. The rest of this release is behind-the-scenes tidying with no change to how the app behaves. **Mobile header snaps between full and collapsed states instead of animating with the scroll** (KAN-1353) When scrolling on the mobile app, the header used to jump abruptly from its full size to its compact size in a single snap, which looked jarring. Now the header shrinks smoothly as you scroll, animating gradually from the full header into the compact one – and expanding back just as smoothly when you scroll up. This happens across every main screen: Home, Accounts, Budget, Bills, Reports, and the account register. We also removed the unused “Help & support” item from the menu, which now shows Alerts, Bills & schedule, and Settings. **clean-user-account erasure can be resurrected by the login-time orphan heal** (KAN-1360) When an account was deleted, the system could sometimes fail to fully remove the associated login credentials. If this happened, the next sign-in attempt would detect the orphaned credentials and automatically recreate an empty account under the same identity, effectively undoing the deletion. The deletion process now removes login credentials first and only proceeds with the rest of the erasure after confirming they were successfully cleared. If credential removal fails, the deletion stops and reports the issue rather than leaving the account in a state where it can be silently resurrected. Rerunning the deletion after resolving the underlying issue completes it cleanly. **Mobile web login offers Google but no Sign in with Apple** (KAN-1434) When signing in from a phone browser, the only quick sign-in option offered was Google – the option to sign in with an Apple account was missing entirely, even though it was available to people using a computer. Which options you saw depended on the size of your screen. Now both options appear everywhere, so you can sign in with Apple from your phone’s browser just as easily as from a computer. The two buttons are stacked full width on smaller screens so the labels are easy to read and comfortable to tap. **other.sharePct in the category range report uses a different, incoherent denominator than sibling rows** (KAN-1540) Percentages in your reports now always add up the way you would expect. Before, if a category or a payee ended a period with more refunded back to you than you spent or earned, its percentage could show up as a negative slice and push another percentage above 100%, which made the whole breakdown hard to trust. Now a refunded line keeps its real amount but simply shows a dash instead of a percentage, and every remaining percentage is measured against the same total, so the shares you see never add up to more than the whole. The Income vs Expenses report also gains a new breakdown showing which income sources and which spending categories contributed most to the period, with an amount and a share for each. And the Spending by Category chart now says “of spending” when you hover a slice, which is a clearer description of what that percentage actually measures. **sigma-collapse floor missing on gateEnterMergeCandidates / pending-bill indicator path (unfloored learned band)** (KAN-1559) When a bill had been paid the exact same amount several times in a row, Tovari would only recognize that bill again if the next payment matched to the penny, so a payment that came in a cent or two different showed up as a separate, unmatched charge and the bill kept looking unpaid. Bills like that are now recognized within a sensible range around the amount you set, so the payment lines up with the bill automatically and the bill stops showing as still due. Amounts that are genuinely far off are still left alone for you to review, and if you have set your own upper and lower limits for a bill, those limits are respected exactly as you entered them. Separately, changes you make to a transaction that came from your bank are now remembered more reliably: edits are held onto correctly on every transaction, and repeating the same change no longer causes the app to keep track of it over and over. The rest of this update is behind-the-scenes work that protects those behaviors from quietly breaking in the future. **Mobile header: negative Safe to Spend not legible + Home/Budget lack an offline banner (HDR-2, HDR-3)** (KAN-1604) When your Safe to Spend went negative, the amount appeared in a soft colour that was easy to mistake for a healthy balance – at the exact moment it mattered most. It now shows in a clear red alert with a short line telling you how much you are over, so an over-budget month is obvious at a glance and stays visible as you scroll. We also added an “Offline – showing your last sync” banner to the Home and Budget screens, so when you lose your connection you can tell your numbers are from your last sync rather than live. **Home runway card: doubled top spacing + low-contrast legend amount ink (HDR-8)** (KAN-1627) The Home screen’s spending breakdown card had a bit too much empty space at the top, and the dollar amounts in its legend were shown in a dark red that was hard to read against the card’s dark background. The card now opens with balanced spacing, and each amount appears in a brighter, easy-to-read red. Together these make it clearer at a glance where your balance is going. The improvement shows up automatically the next time you open Home – nothing to turn on. **Plaid attach mode is a second path to same-institution consent clobbering (no update-mode targeted attach)** (KAN-629) Before this fix, linking a bank to an account you were already tracking by hand could quietly create a second connection to a bank you had already connected – and that second sign-in could cause your original connection to stop receiving new activity, with no warning or error. Now, when you link a bank to one of your accounts and that bank is already connected, the app recognizes it and simply asks which of the bank’s accounts belongs to yours, using the connection you already have. Your existing connected accounts keep updating normally, and no duplicate connection is created. If your account already has its own history, only new activity from today onward comes in, so nothing you entered by hand gets duplicated. And if you genuinely have a separate login at the same bank, you can still say so and connect it on its own. ## Improvements [Section titled “Improvements”](#improvements) **Migrate remaining modals onto useModalDialog and fix BottomSheet’s backward-focus-leak** (KAN-1080) Pop-up windows across Tovari now behave consistently when you use the keyboard. Previously, if a pop-up was open but nothing on it was selected, pressing Tab could jump you onto the page hidden behind it, and pressing Escape did nothing at all – and several pop-ups, including the one that confirms closing an account, could not be dismissed with Escape or reached with the keyboard in the first place. Now every one of these windows keeps your place inside it while you tab through, closes when you press Escape, and returns you to whatever you were on when it opens and closes. The confirmation for closing an account starts on Cancel, so a stray press of Enter never archives an account by accident, and both of its choices now work properly with the keyboard. On phones, the sliding panels that come up from the bottom of the screen no longer let a backward tab slip out onto the screen behind them. Screen readers also announce these windows correctly now. **Fix the mint-inside-mutationFn idempotency key defects across the clients** (KAN-1298) When you approved or dismissed a suggested transfer, or filed an alert from your review list, and the action could not go through, the app said nothing at all – the item could appear handled when nothing had actually been saved. Those actions now tell you plainly when something went wrong, leave the item exactly as it was so you can try again, and clear the message as soon as the next action succeeds. Undoing an approved transfer behaves the same way: if the undo does not take, the transfer stays linked rather than looking reversed when it is not. Separately, adding, renaming, deleting, and merging payees, along with saving your register view settings, are now protected against being applied twice if a request is sent more than once on a shaky connection. Each of your decisions counts exactly once, and pressing a button again after a failure retries that same decision instead of creating a duplicate. Together these changes make review and payee actions honest about what saved and what did not. **Converge PUT /dashboard/safe-to-spend-settings on the shared X-Idempotency-Key reader (hand-rolled parser at upsertSafeToSpendSettings.ts:26)** (KAN-1355) Actions you take in Tovari are now safer to repeat. If a request was sent twice – because a connection dropped, a button was tapped again, or the app quietly retried in the background – the app used to sometimes treat the second attempt as brand new work. Setting up your categories could add ones you never chose, and undoing a recurring bill suggestion could come back with an error saying there was nothing to undo, even though the undo had already worked. Now a repeated request simply returns the result of the original one, so you see the same answer instead of a confusing error or an unexpected change. If a repeat genuinely asks for something different from the first attempt, the app stops and says so rather than silently doing both. We also cleaned up records left behind by the older behavior, so past activity is consistent with how the app works today. **No reconciliation sweep for the removeMember compensation-failed residual state** (KAN-1401) Removing someone from your household now behaves more predictably when something goes wrong behind the scenes. Previously, if a removal could not be completed, the app reported a general failure even when the real cause was a temporary problem on our side, so there was no way to tell whether trying again would help – now a temporary problem is reported as exactly that, and trying again is the right next step. If the same removal request reaches us twice, from a double tap or an automatic retry on a shaky connection, the person is removed only once and the repeat simply returns the same result instead of acting a second time. When a removal does fail partway through, the app now puts that person’s access back exactly as it was before the attempt, so nobody is left half-removed. We also added continuous background monitoring that catches the rare case where a failed removal leaves someone’s sign-in out of step with their membership, so it can be spotted and corrected quickly. Nothing about how you remove a member changes – the steps are the same, the results are just more dependable. **Apply CognitoClientError -> 503 mapping to acceptInvite.ts Cognito calls (second KAN-1363 residual producer)** (KAN-1438) We tidied up the messages Tovari shows when something goes wrong while signing in, resetting a password, or joining a shared household by invitation. Before, if our sign-in service was momentarily busy or unreachable, you could be told your email or password was wrong – so you would retype perfectly good details and get nowhere; now you are told plainly that the service is temporarily unavailable and to try again in a moment. When you accept an invitation and choose a password the service will not accept, you now get a clear explanation of what needs to change instead of a vague “try again later”, so you can finish joining right away. Invitation errors also no longer hint at whether an email address already has an account – every problem with an invite now gives the same neutral response, which keeps your details private. And in the rare cases where something unexpected happens, you will see a plain, readable message rather than raw technical text. None of this changes your accounts, balances, or day-to-day use of the app. **Register action row uses div onClick – Add Transaction and Reconcile are not keyboard-reachable** (KAN-251) If you use a keyboard instead of a mouse, several buttons in the transaction register were impossible to reach – you could see them, but tabbing never landed on them and pressing Enter did nothing. That included Add Transaction, Add Scheduled Item, Edit account and Reconcile at the top of the register, the row menu with Edit, Make recurring and Delete, the Save and Cancel buttons when editing a row inline, and the prompt that offers to match a possible transfer. All of these are now proper buttons: they take focus as you tab, show a clear focus outline, and respond to Enter. Buttons that are not available right now – Reconcile before an account has loaded, or Save while a save is already in progress – are correctly skipped over and cannot be triggered by accident. Screen readers now announce these controls by name and, for the row menu, whether it is open or closed. Nothing about the register’s appearance or behavior changes when you use a mouse, and one control, the small circle that marks a transaction cleared, is still mouse-only and is being handled separately. **Merged bill\_payment\_history rows keep source=‘manual\_entry’ so the observed learned band never narrows** (KAN-511) When you recorded a bill payment yourself and your bank later reported the real charge, the app kept your typed figure on record and often listed the bank’s version of it as a second, duplicate payment – and bills paid at merchants whose bank descriptions carry extra text, such as a payment reference or a longer company name, were also often missed entirely and treated as brand-new spending. Those payments are now recognised and combined into one, using the amount your bank actually charged, so a bill that varies month to month still lines up even when the amount and the date differ slightly from what you entered. Because the app now learns from real charges, it gets better at spotting each bill over time, while still leaving plenty of room for normal month-to-month variation and always respecting any amount range you set yourself. Your own edits are also protected more precisely: if you only changed a transaction’s category, that choice sticks while your bank’s final payee name and date still fill in as usual, instead of the whole transaction being frozen. And when your bank withdraws a transaction it reported in error, the app now clears it out even if you had already edited it, while carefully leaving alone anything tied to a reconciled statement, a transfer, or a bill payment you have already recorded. **AcceptInvitePage inputs are 14px – iOS auto-zooms the invite accept form** (KAN-523) Using Tovari on a phone is easier now. Several buttons and controls were too small to tap reliably – the retry button on cards that failed to load, the cancel and close buttons when adding an account, the account picker, the bank-history dropdown, and the link on your policy cards – and they are all comfortably sized on a phone from now on. When you accepted an invitation to join a household, tapping into a field would make the page jump and zoom in; the fields are now large enough that the page stays put, and the show-password control is easier to hit and works with a keyboard. On the policies screen you can also give your consent using just the keyboard, and opening the full policy no longer changes your consent by accident. On the bills screen, screen readers now correctly announce which tab you are on and read the matching list beneath it. Everything looks and behaves exactly as before on a computer. **Extract db-client PG error mapping to a testable mapPgError (40P01/57014 have zero test coverage)** (KAN-575) When a lot of activity happens at the same moment, the app occasionally has to stop and unwind a change part-way through so nothing is saved incorrectly. Until now, that brief moment was reported to you the same way as a genuine failure – a generic error message that gave no hint whether trying again would help. It now tells you plainly that things are busy and that nothing was changed, so you know the right response is simply to try again in a moment. This applies everywhere the app talks to your data, including signing in, managing payees, and loading your category and reference lists. Nothing about your accounts, transactions, or balances changes, and no action you took is affected. Behind the scenes, the way these interruptions are recognized and reported has also been reorganized so it stays consistent and easier to keep correct going forward. **Make-recurring seed anchors monthly bills to the 1st, not the transaction date** (KAN-630) When you turned a transaction into a recurring bill, the app set the monthly due day to the 1st no matter what day the original transaction fell on, so you had to correct it by hand every time; the bill now starts out on the same day of the month as the transaction you created it from, including the 29th, 30th, and 31st. Opening the Make Recurring window is also easier from the keyboard: your typing stays inside the window, and pressing Escape closes it without saving anything. If a payee suggestion list is showing, that first Escape just closes the list and leaves everything you have entered untouched, so a stray keystroke can no longer wipe out a bill you were part way through setting up. Finally, choosing Save on a transaction you opened but did not actually change now simply closes the editor instead of resaving the row, which had been quietly stopping bank-linked transactions from picking up later updates from your bank. Changing something and saving works exactly as before. **parseAccountIds fails open: a malformed UUID silently drops the whole account filter in every report handler** (KAN-652) When you filtered a report down to specific accounts, an account selection the app could not recognize was quietly discarded – instead of telling you, the report came back covering every account you have, with nothing on screen to signal that your choice had been dropped. Reports now say plainly that the account selection was not understood, so the totals you see always match the accounts you actually picked. Every report and every drill-down within a report answers the same way, so a detail view can no longer disagree with the summary it came from. Payee search has been corrected too: typing a percent sign or an underscore used to be treated as a stand-in for “any characters”, so those searches returned far more payees than they should have. Those characters are now matched exactly as typed, so searching for a payee whose name contains one finds that payee instead of a flood of unrelated ones. Nothing about your accounts, transactions, or balances changes. **Case (b) + “Enter now”: bank’s posted amount is never applied on same-id institutions** (KAN-822) We fixed several ways your bills and bank-linked transactions could fall out of sync when your bank removed, changed, or reversed a transaction. Previously, if a transaction that had already paid a bill was later pulled back by your bank, the bill’s due date and payment history could stay stuck as if it had still been paid. A similar problem could leave a transaction you’d manually matched to your bank feed in a confusing in-between state after that transaction disappeared from your bank. We also improved what happens when your bank posts a transaction for a slightly different amount than what you’d already recorded – instead of silently overwriting your entry, the app now adds a small adjustment so your account balance stays accurate while keeping the amount you entered intact. These changes make your bills, transaction history, and account balances more reliable and consistent after any change your bank makes to a transaction. **Category render metadata (color + icon) must come from the API on every endpoint mode – harmonize web and mobile category coloring** (KAN-941) Categories now display the same color everywhere in the app. Previously, a category could appear as a different color on the web dashboard, the web reports screen, and the mobile reports screen. Now the color you chose for a category is consistently used across all of these views. The only exception is charts that show a very large number of categories at once, where unique computed colors keep them visually distinct. The dashboard spending cards also now show the same percentage figures as the full reports screen, eliminating minor rounding differences that could appear between the two. **KAN-931 tech debt: Matching root cause (deliberately not widened into KAN-931): billScore’s name term in…** (KAN-957) Marking a scheduled bill as paid could leave you with the same payment listed twice – once from the bill and again when your bank’s copy of it arrived – and clearing that up meant deleting a row by hand. Bills paid at merchants whose bank descriptions carry extra text, such as a payment reference or a longer company name, were also often missed entirely and treated as brand-new spending. Now a bill you mark as paid is recognised as the same payment your bank sends, and the two are kept together as a single entry in your register, even for banks that report a payment while it is still pending. When the payment finally settles, the amount and date recorded against that bill are updated to match what your bank actually charged, so your payment history and the amounts the app learns from it stay accurate. Importing a file that includes a bill you have already paid no longer records the payment a second time, and the transaction still appears in your register as normal. When a bill is matched to a payment already in your register, the app now tells you so instead of implying a new entry was created, and your Safe to Spend figure updates right away. **KAN-931 tech debt: Hardening (belt-and-braces, deliberately deferred from KAN-931): add a DB unique constraint on…** (KAN-960) Previously, the app could record the same bill payment more than once. This could happen when an imported bank file contained two similar charges near a bill’s due date, when a bank connection re-processed a payment it had already recorded, or when a bill’s next payment date was moved back to a date that had already been paid and then entered again. Each duplicate quietly distorted the bill’s payment history and your spending picture. Now every bill payment can only be recorded once: if you try to enter a payment for a date that is already paid, the app clearly tells you instead of recording it twice, and file imports and bank syncs simply record the extra charge as a regular transaction rather than a second bill payment. Any duplicate bill payments that were recorded in the past are cleaned up automatically, with no transactions deleted. # 2026.08.18.1 > What's new in this release of Tovari. ## Fixes [Section titled “Fixes”](#fixes) **validatePassword accepts whitespace-padded passwords Cognito rejects** (KAN-1484) Passwords now need to be at least 12 characters instead of 8, matching the policy enforced by the authentication service. The app also trims leading and trailing spaces before checking a password, so a password that looks long enough but is mostly whitespace is now caught up front with a clear message instead of failing silently at the server. These changes apply everywhere you set or reset a password — sign-up, the reset-password flow, and the invitation acceptance screen — across the web app and the mobile app. **ForgotPasswordForm silent-return length guard surfaces no error to the user** (KAN-1711) When resetting a forgotten password, entering a new password that was too short and submitting the form would cause it to appear frozen with no explanation. The form silently rejected the submission without telling the user what was wrong. A second related issue also allowed submitting the form without filling in the password confirmation, again with no feedback. The password reset form now displays a clear error message when the new password does not meet the minimum length requirement. The submit button also stays disabled until both the new password and confirmation are filled in. These changes ensure the password reset process always communicates what is needed to proceed. ## Improvements [Section titled “Improvements”](#improvements) **Enable native Google sign-in on iOS and Android** (KAN-1664) You can now sign in to the Tovari mobile app using your Google account on both iPhone and Android devices. Tapping the Google sign-in button on the login screen authenticates you with your existing Google credentials, so there is no need to create or remember a separate password. If you already have a Tovari account linked to your Google email, you are signed in to that account automatically. This provides a faster, more convenient way to access your financial data on the go. **Extract shared MIN\_PASSWORD\_LENGTH constant across workspaces** (KAN-1712) Resetting your password now tells you exactly what’s wrong when your new password doesn’t meet the requirements, instead of appearing to do nothing. The password rules are also defined in one place across the web and mobile apps, so every screen that asks for a password shows the same, correct minimum length. This makes the reset-password experience clearer and more reliable. # 2026.08.20.1 > What's new in this release of Tovari. ## Fixes [Section titled “Fixes”](#fixes) **ReviewQueueRail unselected count chip renders hardcoded #eef3f6 fallback — –color-surface-muted is declared nowhere** (KAN-1051) The item counts next to each queue name in the Review Center sidebar were displaying with a background color that did not match the rest of the app, making the unselected counts look visually out of place. This mismatched styling appeared on every queue row that was not currently selected. The counts now render as clean text that matches the design used throughout the Review Center. Selected queue counts stand out with the app’s accent color, while unselected counts use a neutral tone that fits naturally with the sidebar. **RepeatPayeeFooterCard subline is false for payees with no saved category (suggestedCategoryId NULL)** (KAN-1138) When reviewing imported transactions, the repeat-payee summary card claimed that all listed payees already had a usual category saved, even when some of those payees had no saved category at all. The misleading message appeared alongside every payee name regardless of whether the app actually knew which category to use. The card now shows the saved-category claim only for payees that genuinely have one on file. Payees without a saved category still appear in the list but no longer carry the incorrect statement that new imports will be categorized automatically. The categorize action continues to work correctly for payees that do have a saved category. **Logout never revokes the refresh token — add POST /auth/logout with Cognito token revocation** (KAN-463) When you signed out of Tovari, the app was only signing you out on the screen — behind the scenes, the long-lived key that keeps you signed in on that device stayed usable for up to thirty days, so if it was ever stolen, signing out did not protect your account. That is fixed now. When you sign out — on the web or in the mobile app — Tovari immediately cancels that key with our servers, so it can no longer be used to get into your account. Signing out is still instant and reliable: even if your connection is slow or offline, you are never stuck on the screen. One thing to know: signing out on one device does not sign you out everywhere — any other device where you are signed in stays signed in until you sign out there too. **Opening-plug re-arm silently rewrites RECONCILED plug rows and moves their date — applyOpeningPlug’s ON CONFLICT guard omits status** (KAN-1752) We fixed a problem that could quietly undo part of a balance you had already confirmed. Previously, after you reconciled a connected bank account — confirming that its balance matched your statement — a later automatic refresh from your bank could silently change the account’s starting-balance entry, altering both its amount and the date it appeared on. That meant running balances inside a period you had already confirmed could shift without any warning. Now, once you reconcile an account, its starting-balance entry is locked in place: automatic refreshes will never change or remove it. Your confirmed balances stay exactly as you verified them. **Review Center keeps showing transactions categorized from outside it (payee apply-to-all, Plaid sync)** (KAN-1754) When you gave a payee a category and chose to apply it to all of that payee’s transactions, those transactions kept showing up in the Review Center as though they still needed a category, and the count next to Review Center kept including them. The only way to clear them was to reload the app. They now disappear from the list the moment you apply the category, and the count updates with them. The same refresh problem affected transactions arriving from a linked bank account, from entering a scheduled bill, and from a file import — all of these now update the Review Center right away too. Anything the app deliberately leaves for you to handle yourself, such as a transfer between your own accounts or a transaction whose category you set by hand, still stays in the list as before. **Uncategorized queue row renders the payee’s SUGGESTED category as if the transaction were already filed** (KAN-1755) We’ve polished the Review Center. Each queue now shows a clear “Queues” label and, when you pick a queue, a running total of what’s waiting there. When everything is caught up, the queue list now looks calm and clear instead of showing a leftover highlight, and the cluttered number badge next to each queue name is gone in favor of a simple count. Account icons on transfer matches now always show the right account type. For uncategorized transactions, we no longer quietly pre-fill a suggested category — instead you’ll see it offered as a clear “Suggested” option you can apply with one click, so what’s shown always matches what’s actually been filed. And the note about payees you’ve already categorized before now only appears for payees that actually have a usual category on file. **Account editor modal: Close Account button and Safe to Spend card are squashed once the modal scrolls** (KAN-1756) When you edited an account, parts of the edit window could come out the wrong size once the window was tall enough to scroll. The Close Account button was squeezed to about half the height of the Cancel and Save Changes buttons below it, and the Include in Safe to Spend card was too short for its own text, so the second line spilled out past the edge of the card. Both now stay the size they are meant to be: Close Account matches the buttons beside it, and the Safe to Spend card grows to fit its text. The window still scrolls exactly as before, and shorter windows that never scrolled are unchanged. **writePostingAdjustment/retirePostingAdjustment lack the reconciled-status fence KAN-1752 added to applyOpeningPlug** (KAN-1769) When you reconciled an account, certain automatic balance adjustments created during bank sync were not protected from being overwritten or removed by later sync updates. This meant that a subsequent bank sync could silently alter or delete a balance-correction entry that fell within a reconciled period, potentially changing your reconciled balance without warning. The app now protects all balance adjustments inside a reconciled period from automated changes, matching the same safeguard already in place for opening-balance entries. If a sync encounters a reconciled adjustment, it leaves it untouched rather than modifying or removing it. Your reconciled balances remain exactly as you attested them. **RepeatPayeeFooterCard headline “more from payees you have filed before” is false for non-qualifying repeat payees** (KAN-1781) When reviewing transactions that needed a category, the app listed repeat payees under a headline claiming they were payees “you have filed before.” In some cases, the listed payees had never actually been categorized — they simply appeared in more than one transaction, making the claim misleading. The headline now adjusts its wording to match reality. When every listed payee has a prior category on file, the original description appears as intended. When some do not, the wording accurately reflects that these are simply payees the app has seen before. **enterBillCore’s pre-lock fast path returns not\_outstanding for a same-key replay (missing findReplay re-probe)** (KAN-1791) We fixed a timing issue where entering a scheduled bill payment could show an error message even though the payment had actually gone through. This happened in rare cases when a payment confirmation was submitted more than once in quick succession, such as from a slow connection or an accidental double-tap. Now, if that happens, you’ll see your successful payment confirmed instead of a confusing error, with your account and budget totals updated correctly. No payments were ever duplicated by this issue — it only affected what was shown on screen. This makes entering bill payments more reliable, especially on slower or less stable connections. **Mobile: tapping a favorite account on the dashboard shows “coming soon” instead of navigating to the register** (KAN-1797) Tapping a favorite account on the mobile dashboard previously showed a placeholder screen instead of opening the account. Favorite accounts now navigate directly to their transaction register, the same view you reach from the Accounts tab. This makes the favorites section a genuine shortcut to your most-used accounts rather than a dead end. ## Improvements [Section titled “Improvements”](#improvements) **KAN-1026 coordination package: inter-panel disc glyph correction, transfer leg amount colour, rail header/summary, footer heading copy** (KAN-1049) The Review Center sidebar now displays a heading and a money summary for the selected queue, making it easy to see the total amount awaiting review at a glance. The approval impact section beneath each review item has been updated with a more natural, conversational heading and refined styling that is easier to read. Together these changes bring the Review Center’s visual presentation in line with its intended design. **Web queue rail rows stay interactive/active at all-clear (board 6a shows muted)** (KAN-1192) When all review queues are clear, the queue list in the Review Center now appears visually muted, matching the all-clear celebration shown beside it. Previously, queue rows kept their active highlight and interactive appearance even when there was nothing left to review, which made it look like items still needed attention. Selecting a highlighted row in that state had no effect. The queue list now clearly communicates that everything has been reviewed, and the active highlight only appears when a queue actually contains items waiting for your attention. **Mobile WhatChangesCard heading still reads third-person, diverging from web’s KAN-1049 sentence-case wording** (KAN-1780) The mobile app’s Review Center previously displayed its “What changes” heading using third-person wording and all-uppercase styling that did not match the web version. The heading now uses first-person phrasing, reading “What changes if I approve” and “What changes if I add it” instead of the former “What changes if you approve” and “What changes if you add.” The text also appears in standard sentence casing rather than all caps, making it easier to read and consistent with the web experience. **Mobile WhatChangesCard surface (background/heading color) diverges from Review Center Board** (KAN-1792) In the Review Center, the “you’ve filed this payee before” message on repeat-payee suggestions now only appears when you actually chose that category yourself in the past, instead of sometimes showing up for categories the app guessed or picked up automatically. On mobile, the “What changes” card on alert details now matches the clean white styling used everywhere else in the Review Center, with clearer text and a consistent look and shadow, replacing its previous tinted, slightly mismatched appearance. **RepeatPayee “filed before” claim is not provable from data (suggestedCategoryId can be auto-stamped)** (KAN-1793) The Review Center’s repeat-payee card could incorrectly claim you had previously categorized a payee when the category was actually assigned automatically by the system. This happened because the app treated any existing category suggestion as proof of a prior user decision, even when the suggestion came from an automated source. The card now checks whether the category was genuinely set by you before displaying that claim. Payees whose categories were assigned automatically no longer show the “filed before” language, so the guidance you see while reviewing transactions accurately reflects your own history. **Decide whether to disarm migration 128’s fleet-wide opening\_plug\_pending before it is consumed — the arming is live and unfired on prod** (KAN-1799) In some cases, a transaction you had already reconciled on a linked bank account could still be quietly rewritten or removed the next time your account synced. That could make an account you had already checked off as correct show a different balance than the one you confirmed. Reconciled transactions are now protected from being changed by a later sync, so once you’ve reconciled an account, it stays exactly as you left it. We also improved how the starting balance is calculated when a bank connection is first linked, so it lines up more precisely with your account’s actual history. Behind the scenes, we added better monitoring so our team can tell the difference between an account that’s fine because you’ve already reconciled it and one that genuinely needs attention. **Mobile transaction register header layout and search UX fixes** (KAN-1822) The transaction register on mobile now has a cleaner, more consistent header layout. The search icon is always visible in the toolbar so you can find transactions without opening a menu first. When you search, the Upcoming Bills, Transfers to Review, and Pending sections step out of the way so only matching results are shown. A vertical ellipsis menu provides quick access to Select/Match and Edit Account actions, and a dedicated Add button lets you create a new transaction right from the header. # 2026.08.23.1 > What's new in this release of Tovari. ## New features [Section titled “New features”](#new-features) **Pending-survivor match refusal (MSG\_SURVIVOR\_PENDING) and two-step Enter-then-Match ergonomics for underpaid bills** (KAN-1872) Settling a bill you paid for a different amount than usual is now a one-step task. When a payment that doesn’t match a bill’s usual amount shows up in your account, the Enter button offers to settle the bill against that payment directly — one confirmation, no duplicate entry to clean up afterward. You can also now match a payment that’s still processing at your bank to an entry you typed in yourself: a new “Match” option on the processing payment combines the two into one, keeping your notes and category, after you confirm it’s really the same payment. The confirmation message when entering a bill with a payment still processing has been corrected too — it previously warned that entering would create a second entry to clean up, when in fact the app combines them cleanly. These conveniences never act on their own; every combination happens only when you confirm it, and your automatic matching stays exactly as careful as before. ## Fixes [Section titled “Fixes”](#fixes) **bills.next\_payment\_date NULL-fallback divergence across ten read call sites, two incompatible semantics** (KAN-1744) Your bill balance forecast now lines up correctly with your other reports. Previously, the “actual balance” line on the Bills forecast could read differently than the same days shown on your Net Worth and Cash Flow reports, and a recently connected account’s older history could be partly left out of that line. Both are now fixed, so the balance you see for past days on your bill forecast always matches what your other reports show, and every connected account’s full history is counted correctly. Today’s balance and any future projections are unaffected — this only corrects how past days are calculated. We also added extra safety checks behind the scenes to keep your account balances accurate and prevent certain transfer payments from being counted twice. **25 Plaid pending rows frozen 19+ days on two accounts — they can never settle, and each one duplicates when its charge posts under a new id** (KAN-1801) Some pending card charges were getting stuck: they stayed marked as pending for weeks, never cleared on their own, and when the real charge finally arrived it showed up as a second copy — so the same purchase could appear twice and balances looked off. The app now double-checks older pending charges against your bank and automatically clears out any hold your bank no longer reports, so stale pending items no longer linger or create duplicates. If a cleared hold later turns into a real charge, it simply reappears in its place with any edits you made intact — nothing is lost. We also added a behind-the-scenes health check that shows us any account where pending charges are stuck, so problems like this can be spotted and resolved quickly. Existing stuck items on affected accounts will clear automatically the next time those accounts refresh with the bank. **enterBill.ts and skipBill.ts floor a NULL bills.next\_payment\_date cursor at ‘today’ via settlementFloorIso, so a legacy bill with no settle history cannot have a genuinely-overdue PAST occurrence entered or skipped** (KAN-1833) Previously, if you had an older recurring bill that had never been recorded as paid, trying to mark one of its past due dates as paid or skipped would fail. Now you can enter or skip that overdue payment right from the Bills screen, and it will be recorded on its actual due date. Doing this only affects the one payment you choose — it won’t pull in every missed payment from that bill’s history at once, so your account totals and spending outlook change by just that one amount. If a matching transaction already exists for that date, you’ll be shown that a match was found instead of creating a duplicate. This makes it possible to finally clean up long-standing bills that could never be settled before. **Plaid bill settlement anchors its date window on the settle-through cursor instead of the outstanding occurrence — every recurring bill stops auto-settling after its first payment** (KAN-1863) Previously, when a recurring bill was paid automatically from a linked bank account, only the very next payment would be matched and marked as paid — every payment after that stayed unmatched, even though the money had already gone out. This showed up most often right after connecting a bank account for the first time, when several months of a recurring bill’s payment history come in at once: only the first one would get marked paid, and the rest were left looking overdue or unpaid. Now, every outstanding payment for a recurring bill is matched and marked as paid as soon as its payment history comes in, not just the first one. This means your bills and account balances stay accurate without you needing to go in and mark past payments as paid by hand. A small number of very tightly spaced duplicate charges may still need a quick manual confirmation, but this is rare and does not affect normal monthly or weekly bills. **matchEngine.ts Pass 3 carries the identical cursor-anchored window defect on the import-commit path** (KAN-1870) We fixed several issues in how the app matches your bank transactions to your recurring bills and scheduled payments. Previously, one unusually large past payment could occasionally cause the app to accept too wide a range of amounts as a match going forward, which could let the wrong transaction get linked to a bill. We also fixed a case where, during a single automatic sync, a bill could be counted as paid a second time for a payment it had already matched, and a case where importing bank transactions from a file could link a payment to the wrong upcoming due date on a bill’s schedule. With these fixes, the app now consistently identifies the correct amount and the correct due date when matching your transactions to your bills. No action is needed — these corrections apply automatically going forward. **computeLearnedRange’s outlier band blow-out at small n** (KAN-1871) When a bill had only a few recorded payments, a single unusually large or small payment could cause the app’s automatic matching to become too permissive, potentially matching unrelated transactions to that bill during bank sync or file import. This happened because the tolerance range the app used to decide whether a transaction belonged to a bill would widen dramatically when one payment looked very different from the others in a short history. The matching tolerance is now capped so that it can never stretch beyond a reasonable range of the bill’s expected amount, regardless of how few payments exist or how unusual one of them was. Bills with consistent payment histories are unaffected. The fix only narrows the range the app considers, so no transaction that was previously refused will start matching incorrectly. **Regression from PR #711: the in-run re-settlement guard its PR body documents (lastSettledOccurrence) was never implemented — a short-period bill can settle a not-yet-due occurrence** (KAN-1875) When the app automatically matched bank transactions to a recurring bill with a short payment cycle, such as a weekly or biweekly bill, it could sometimes mark a future payment as settled before it was actually due. This happened when multiple qualifying transactions arrived from your bank during the same update. After matching one transaction to the current payment, a second transaction dated just a few days later could incorrectly settle the following week’s payment early, advancing your bill schedule past a date that had not yet arrived. The app now tracks which payment was most recently matched for each bill during a single bank update and prevents a subsequent transaction from settling a future occurrence too soon. Only transactions that fall within the correct window around each payment date can now match to that payment. ## Improvements [Section titled “Improvements”](#improvements) **Mobile Accounts: native Plaid relink / re-auth repair (update mode)** (KAN-754) When a bank connection stops working, the Tovari mobile app now lets you fix it right where you are. Before, tapping Fix on an account that needed attention only showed a message telling you to sign in on the web, so you had to put your phone down and start again on a computer. Now tapping Fix opens your bank’s sign-in inside the app, and as soon as you finish, the account goes back to normal on its own — no restarting, and no duplicate copy of the account left behind. You can do the same thing from an account’s edit screen, whether you opened it from your account list or from that account’s transactions. If your bank sends you out to its own website or app and you can’t find your way back, Tovari says so plainly and still offers the web option as a backup. **iOS Plaid OAuth continuation blocker (KAN-754 follow-up)** (KAN-861) Connecting a bank account that uses secure sign-in (such as Chase or Capital One) now opens the bank’s login page directly within the iOS app. Previously, these connections redirected to Safari, which could leave you stranded outside the app with no clear way back. The in-app flow keeps you in context throughout the entire linking process, so you return to your accounts automatically after signing in with your bank. This improvement applies to both new bank connections and reconnections when a bank asks you to re-authorize. The change was verified against production before going live, and the app falls back gracefully to the previous browser-based flow if anything unexpected occurs. # 2026.08.28.1 > What's new in this release of Tovari. ## New features [Section titled “New features”](#new-features) **Export Your Full Account Data** (KAN-464) 🌐 Web📱 iOS & AndroidSettings You can now download a complete copy of everything in your account — accounts, transactions, budget, bills, and payees — from Settings, Data & Privacy. Your export is ready in under a minute and stays available for a full day, and sensitive details like bank credentials are never included. **Search That Actually Finds Everything** (KAN-1909, KAN-1923, KAN-1927) 🌐 Web📱 iOS & AndroidTransactions & Register Search on your register now looks everywhere at once — posted transactions, pending charges, upcoming bills, and recurring suggestions all narrow down together as you type, on web and mobile alike. It also matches notes you’ve written and dollar amounts, not just names, so typing “45” finds every $45 transaction whether the money came in or went out. **A New Home for Help Docs** (KAN-1945) 🌐 Web Tovari now has a documentation site, reachable right from the site menu, with search built in from day one. It’s just getting started, but it’s the foundation for a full library of guides we’re building next. **Real Getting-Started Guides** (KAN-1946) 🌐 Web We published a complete set of getting-started guides — from creating your account to reading your first budget — covering both web and mobile side by side in every guide. **What’s New, Automatically** (KAN-1947) 🌐 Web Our documentation site now has a What’s New page that updates itself the moment something new actually ships, so you can see what’s changed without digging through anything. It only ever shows features that are truly live, never a preview of something still cooking. **In-App Help, One Tap Away** (KAN-1953) 🌐 Web📱 iOS & AndroidAccounts & Balances Look for the new help button on your Accounts screen and account setup steps. Tap it, and the right help article opens right where you are — no need to go hunting for answers. **Household Invites Come to Mobile** (KAN-1988) 📱 iOS & AndroidHousehold ManagementBudgetingReports & InsightsSettings Inviting someone to share your household is now built right into the app — send an invite by email and manage who’s on your account straight from Settings. **Touch Your Balance Timeline** (KAN-1990) 📱 iOS & AndroidAccounts & BalancesReports & Insights You can now drag your finger across the Balance Projection chart to see exactly what your balance will be on any given day. It snaps right to the day you’re pointing at, so checking a date ahead is as easy as a swipe. **Budget Categories Get Their Color Back** (KAN-1994) 📱 iOS & AndroidBudgeting Your budget categories on mobile now show their real icon and color instead of a plain letter, so they’re easier to spot at a glance. Planning also gets one-tap suggestions — like last month’s spending or a 3-month average — right above your keypad. **One Settings Screen, No More Jumping** (KAN-1995) 📱 iOS & AndroidSettings Settings on mobile is simpler now — tap Household, Billing, or Safe to Spend and it opens right there on the same screen instead of jumping you somewhere else. **Smarter Duplicate Detection** (KAN-2000) 🌐 Web📱 iOS & AndroidTransactions & Register The app can now catch a likely duplicate even when your bank describes it differently than you did — like a refund you entered yourself before the deposit showed up. Instead of quietly recording it twice, it flags the possible duplicate so you can confirm or dismiss it. **See What Interest Really Costs You** (KAN-2012) 🌐 Web📱 iOS & AndroidCategorization & AI Credit card and loan interest used to get lumped in with your regular debt payments, so you couldn’t tell how much of your money was going toward interest. Now interest charges show up in their own category, making it easy to see exactly what carrying a balance is costing you. ## Fixes [Section titled “Fixes”](#fixes) **Fix Broken Bank Connections In-App** (KAN-864) 🌐 Web📱 iOS & AndroidData Sync If one of your linked bank accounts runs into trouble, you can now fix it right in the app instead of disconnecting and starting over — just look for the reconnect option next to that account, on web or mobile. **Fixed Bills That Wouldn’t Save** (KAN-1144) 🌐 Web📱 iOS & AndroidBills & Reoccuring Some older bills got stuck pointing at a payee you’d deactivated, which caused a confusing error whenever you tried to edit them. We cleaned up the leftover data behind the snag, so those bills can be edited normally again. **Payee Deletion, Fully Cleaned Up** (KAN-1244) 🌐 Web📱 iOS & AndroidPayeesFile Import Deleting a payee didn’t always clean up completely — some of its old matching rules could quietly stick around instead of going away with it. Deleting a payee now clears everything tied to it, so nothing gets left behind. **Accurate Payee Info on Bills** (KAN-1282) 🌐 Web📱 iOS & AndroidBills & ReoccuringPayees In a rare case, entering a bill tied to a payee you’d already deactivated could briefly show that payee’s name attached to the wrong entry. That’s fixed now, so bills always show accurate payee information. **Stuck Bill Payments, Fixed** (KAN-1283) 🌐 Web📱 iOS & AndroidBills & Reoccuring Some older bill payments could get stuck if they’d been deleted and re-tried before, refusing to let you re-enter them. We tracked down the snag and cleared it up — those bills can be entered normally again. **Cleaner Bill Payment Deletes** (KAN-1285) 🌐 Web📱 iOS & AndroidBills & Reoccuring Deleting a bill payment could sometimes leave an invisible leftover behind, quietly throwing off how we predicted that bill’s due dates. Now deleting a bill payment removes it completely, the way it should. **No More Duplicate Bill Actions** (KAN-1302) 🌐 Web📱 iOS & AndroidBills & Reoccuring If you tapped Enter or Skip on a bill and a slow connection made the request go through twice, that retry could double up the action. Now a repeat request is recognized as the same one, so your bills post correctly every time. **More Reliable Bill Skipping** (KAN-1517) 🌐 Web📱 iOS & AndroidBills & Reoccuring Skipping a bill payment twice by accident — say, from a slow connection trying again — could cause a hiccup instead of skipping cleanly. Now a repeated tap is handled correctly the first time, every time. **Your Bill Details Now Stick** (KAN-1531) 🌐 Web📱 iOS & AndroidBills & Reoccuring When a bill payment you’d entered matched up with the real transaction from your bank, the name, payee, or category you’d set for it could quietly get overwritten by the bank’s own label. That’s fixed — your bill’s details stay exactly as you set them, even after the match settles. **Smarter Matching for Bills With Plain Names** (KAN-1560, KAN-1561) 🌐 Web📱 iOS & AndroidBills & Reoccuring Bills with plain, generic names like “Rent” or “Car Payment” were sometimes getting entered twice instead of matched to the right bill, especially when the bank’s description was messy. We sharpened how those payments get compared — and when we’re not fully sure it’s a match, we’ll ask you to confirm before combining them. **Bills That Went Up Aren’t Duplicates Anymore** (KAN-1582) 🌐 Web📱 iOS & AndroidBills & Reoccuring If a bill’s amount goes up and stays there, like a rent increase, the new payment could sometimes get flagged as a duplicate instead of matching your bill. We widened how we recognize a new amount once it lines up with your recent payment history, so it’s counted correctly instead of duplicated. **More Consistent Transaction Matching** (KAN-1583) 🌐 Web📱 iOS & AndroidTransactions & Register A rare inconsistency could make our system disagree with itself about whether a transaction came straight from your bank or was entered by hand, which could throw off matching. We closed that gap, so every transaction is classified the same way, every time. **More Accurate Automatic Categorization** (KAN-1605) 🌐 Web📱 iOS & AndroidCategorization & AI In rare cases, a transaction that changed right before our automatic cleanup pass ran — like becoming part of a transfer — could still get renamed or re-categorized anyway. We closed that gap, so once a transaction changes in a meaningful way, our automatic pass now leaves it alone. **Budget Income Numbers That Match** (KAN-1630) 🌐 Web📱 iOS & AndroidBudgetingReports & Insights If your budget uses more than one income category, the income totals on your month view and your year view could show different numbers. We tracked down the mismatch, so both views now always agree. **Bill Payments Match the Right Bill** (KAN-1800) 🌐 Web📱 iOS & AndroidBills & Reoccuring In a rare case, retrying to mark a bill as paid could show you details from a different bill instead of the one you meant. We closed that gap, so retrying always reflects the exact bill you’re working on. **More Duplicate Transactions Cleaned Up** (KAN-1817) 🌐 Web📱 iOS & AndroidTransactions & Register We ran another round of cleanup to catch duplicate transactions that a few accounts still had lingering in their register after our last fix. If you had any leftover duplicates, they’re gone now. **Steadier Bill Skipping** (KAN-1843) 🌐 Web📱 iOS & AndroidBills & Reoccuring Skipping a scheduled bill now happens as one safe, single step instead of two, so there’s no more tiny window where a quick follow-up action could catch it half-finished. **Your Own Entries Are Protected** (KAN-1866) 🌐 Web📱 iOS & AndroidTransactions & RegisterData Sync We found and fixed a rare glitch where a transaction you typed in yourself could quietly disappear during our routine account cleanup, if your bank later stopped mentioning it. That’s fixed now — anything you enter by hand stays exactly where you put it. **Merge Duplicate Transfer Payments** (KAN-1917) 🌐 Web📱 iOS & AndroidTransactions & Register If you paid a bill by transferring money, like a credit card payment, and the bank’s own record of that same payment showed up a few days later, you’d end up with two entries nothing could combine. Now, with your confirmation, those two entries can merge into one, and whenever a match button is grayed out we spell out why in plain text. **Corrected Projected Balances** (KAN-1924) 🌐 Web📱 iOS & AndroidTransactions & RegisterBills & Reoccuring If a bill payment was already pending at your bank, your register’s projected balance was still subtracting it a second time, making your future balance look lower than it really was. We fixed the math, so a pending payment only counts once. **Safe to Spend, Correctly Counted** (KAN-1925) 🌐 Web📱 iOS & AndroidReports & InsightsBills & Reoccuring Safe to Spend and your balance projection chart were subtracting some upcoming bill payments twice whenever your bank already had the payment pending, making both numbers look lower than they really were. We fixed the math across the board, so the numbers you see now are the real ones. **Help & Legal Pages That Actually Open** (KAN-1960) 🌐 Web Visiting our help docs or pages like Privacy and Terms sometimes just showed you the homepage instead. That’s fixed now, so those pages open correctly wherever you find the link. **Cleaner Auto-Categorization** (KAN-1965) 🌐 Web📱 iOS & AndroidCategorization & AIPayees We fixed a rare glitch in the background process that automatically sorts your transactions into categories — it could occasionally create a duplicate placeholder payee. That’s cleaned up now, so your payee list stays accurate. **Income Lands Where It Should** (KAN-1968) 🌐 Web📱 iOS & AndroidBudgeting For a small number of accounts, new income was landing in “Uncategorized” instead of your Income category. We found the cause and repaired the affected accounts, so income now sorts where it belongs. **A Roomier New Transaction Screen** (KAN-1989) 🍎 iOSTransactions & Register Adding a transaction on iPhone could get pretty cramped, with the keypad, calendar, and category list all competing for space. We opened it back up: now each one shows up only when you actually need it, so adding a transaction feels normal again. **No More False Overdue Bills** (KAN-1991) 🌐 Web📱 iOS & AndroidBills & Reoccuring Bills were sometimes shown as overdue in red even when we could already see the payment sitting at your bank, ready to clear. Now the Bills screen shows it as pending instead, so you’re not tempted to pay it again. **A Steadier Alerts Inbox** (KAN-1996) 🌐 Web📱 iOS & AndroidNotifications & E-Mail The Alerts inbox could get stuck showing a spinner and the wrong layout after you finished working through a queue. That’s fixed, and we also removed a “coming soon” placeholder that wasn’t hooked up to anything yet. **Know When Your Bank Feed Goes Quiet** (KAN-1997) 🌐 WebData Sync Every so often, a bank connection could quietly stop sending new transactions while the app kept telling you everything was current. Now, if your feed goes quiet for a few days, you’ll see a clear heads-up instead of a false all-clear. **Fixing Miscategorized Deposits** (KAN-1999) 🌐 Web📱 iOS & AndroidCategorization & AI Some deposits, like a refund or a mobile check deposit, were accidentally getting filed as loan or credit card payments instead of income. That mix-up could throw off your budget and spending reports — it’s fixed now, going forward. **Bills Post on the Day You Pay Them** (KAN-2011) 🌐 Web📱 iOS & AndroidBills & Reoccuring If you paid a scheduled bill after its due date, the transaction used to get dated back to the due date instead of the day you actually entered it. Now it’s dated today, so it has a much better chance of matching up automatically with your bank’s real transaction. **Your Data Export Is Fixed** (KAN-2013) 🌐 WebSettings Downloading your data from Settings has been broken from day one — every export failed and told you to try again, which never worked either. We found the glitch and fixed it, so exporting your data now works the way it always should have. # 2026.08.29.1 > What's new in this release of Tovari. ## New features [Section titled “New features”](#new-features) **Help Guides, Right Where You Need Them** (KAN-1949) 🌐 Web🍎 iOSAccounts & BalancesTransactions & RegisterData Sync Tap the new help button on any core screen — accounts, bank connections, transactions, Safe to Spend, or the dashboard — and a guide opens that's written for the exact device you're on. Each one answers the questions people actually ask, like which accounts count toward Safe to Spend, what happens when you close one, and how much bank history you can bring in. **Help Guides, One Tap Away** (KAN-1950) 🌐 Web📱 iOS & AndroidBudgetingBills & ReoccuringCategorization & AIPayees Budgeting, bills, categories, and payees each have their own built-in guide now — plain language, no finance degree required. Tap the new help button on any of those screens (web or mobile) and the right guide opens on the spot. **Your iPhone’s Number Pad, Finally** (KAN-2055) 🍎 iOS🤖 AndroidTransactions & RegisterBills & Reoccuring Entering amounts on your iPhone now uses your phone's own number pad — the one where holding backspace actually works and dictation does too. A Done button dismisses the keyboard, and the field you're filling in slides up so the keys never cover it. When you reconcile a credit card or loan, a new +/- button lets you flip to a negative statement balance. ## Fixes [Section titled “Fixes”](#fixes) **Joint Account Disconnects, Now Explained** (KAN-1998) 🌐 Web📱 iOS & AndroidAccounts & BalancesData Sync If two people in a household each use their own Tovari account to track the same joint bank account, one person reconnecting their bank could quietly knock the other's connection offline — and all either side saw was a generic "please sign in again" with no clue why it kept happening. Now the app recognizes this pattern and tells you what's going on, with a "Why did this happen?" section that explains what shared-account households can do about it. **No More Dead Ends on Your Dashboard** (KAN-2048) 📱 iOS & AndroidAccounts & Balances The "Connect a bank" and "Add an account" buttons on your mobile Dashboard were dropping you on a placeholder page instead of the real thing — a bit like a door that opens onto a wall. Both buttons now take you straight to connecting your bank or adding an account, right from the Dashboard. **Clearer Tab Bar on iPhone** (KAN-2050) 🍎 iOS The tab bar at the bottom of the iPhone app was showing inactive tabs in a washed-out color that was noticeably harder to read than the same bar on Android. We matched iPhone to Android's bolder shade, so every tab label is easy to spot no matter which phone you're on. # 2026.08.30.1 > What's new in this release of Tovari. ## Fixes [Section titled “Fixes”](#fixes) **Uncategorized Transactions Get a Second Chance** (KAN-2074) 🌐 Web📱 iOS & AndroidCategorization & AI Some transactions were stuck in Uncategorized for good — if the app wasn't sure about a merchant once, it gave up on that merchant forever, no matter how many times your accounts synced afterward. Categorization now gives an uncertain merchant another try after some time, with a sensible limit so it still knows when to stop guessing on the ones it truly can't identify. If you've had transactions stuck like this, keep an eye out — they should start clearing up as your accounts keep syncing. # 2026.08.31.1 > What's new in this release of Tovari. ## New features [Section titled “New features”](#new-features) **Four new help guides: file import, reports, Review Center, and data and privacy** (KAN-1951) 🌐 WebTransactions & RegisterFile ImportReports & InsightsAccount & Security Tovari's help site now covers four more areas of the app. There are new guides for bringing transactions in from a CSV, OFX or QFX file your bank gives you; for all seven reports, including which of them you can read on your phone; for the Review Center, where Tovari gathers transfers, recurring bills, uncategorized spending and possible duplicates for you to confirm; and for downloading a complete copy of your data or asking for your account to be erased. Each guide covers both the web app and the mobile app, and says plainly when something is available in only one of them. You can find them all under Features at tovarifinancial.com/docs, and search across them from any page. **Seven new help guides covering signing in, security, household sharing and settings** (KAN-1952) 🌐 WebAccount & SecurityHousehold ManagementSettings Tovari's help site now covers signing in, security and looking after your account. There are new guides for the three ways to sign in and what happens when you mix them, confirming your email address, turning on two-factor authentication with an authenticator app, sharing your books with one other person, the terms you are asked to accept, what lives in Settings on each platform, and how to report a problem and what happens after you do. Each guide covers both the web app and the mobile app, and says plainly when something is available in only one of them. You can find them all under Features at tovarifinancial.com/docs, and search across them from any page. ## Fixes [Section titled “Fixes”](#fixes) **Fixed mobile sign-in not staying signed in** (KAN-2069) 📱 iOS & AndroidAccount & Security Your sign-in wasn't sticking on mobile — close the app and reopen it, and you'd land right back at the login screen no matter how many times you'd already signed in. We tracked down what was resetting things and fixed it, so your session now stays put like it should. **Fewer Mystery Transactions** (KAN-2073) 🌐 Web📱 iOS & AndroidCategorization & AIPayees Plenty of transactions were landing in your register with the bank's messy shorthand and no category, even when the name practically said what the business was. Our automatic labeling was so worried about mixing up one business for another that it threw out perfectly good answers. It now knows the difference between recognizing a business and just reading the sign, so far more transactions show up already named and categorized — and it's as careful as ever before putting a well-known brand's name on anything. **A Bigger, Clearer Balance Chart** (KAN-2081) 🌐 WebReports & Insights The balance chart on your dashboard was hiding in the middle of its own card — shrunk down with wasted space on either side and squeezed too flat to read comfortably. It now stretches the full width of the card and stands taller, so the line showing where your money is headed is much easier to follow. The spending breakdown underneath lost its pointless blank gap at the bottom too. ## Improvements [Section titled “Improvements”](#improvements) **Stuck Transactions Finally Get Categorized** (KAN-2075) 🌐 Web📱 iOS & AndroidCategorization & AI A few merchants had the app stumped, and once it drew a blank it quit trying — so those transactions sat uncategorized no matter how long you waited. It's taking a fresh look at every one of them with a sharper eye, so they should start landing in the right categories on their own. **A clearer 14-day free trial for every new account** (KAN-2079) 🌐 Web📱 iOS & AndroidBilling & Subscriptions Tovari now offers a 14-day free trial for every new account, replacing the previous fixed early-access period. Your trial starts the day you sign up, so you get the full two weeks no matter when you join. We'll collect your payment details when the trial starts and remind you before it ends — your subscription then continues automatically at $11.99/month unless you cancel. This makes pricing clearer and fairer for everyone, no matter when they sign up. # 2026.08.31.2 > What's new in this release of Tovari. ## Fixes [Section titled “Fixes”](#fixes) **Two-Factor Message Now Names Apple Too** (KAN-2022) 🌐 WebAccount & Security If you sign in with Apple and went to turn on two-factor authentication, Tovari told you it wasn't available for accounts that sign in with Google — a confusing thing to read when you've never used Google. The message now names both Apple and Google, so what you're told matches how you actually sign in. **Clearer legal policies that name the company behind Tovari** (KAN-2104) 🌐 Web📱 iOS & AndroidAccount & Security Tovari's terms of use, privacy policy, and cookie policy did not say plainly that Tovari is a product of Tovari Financial, even though the app shows the shorter name almost everywhere. That left it unclear whether the policies you accepted covered the app you were actually using, and the sections that limit liability and cover legal costs named the product instead of the company behind it. All three policies now define the name up front: Tovari and Tovari Financial mean the same product from the same company, Ewing Technology Partners, LLC, and accepting the policies is an agreement with that company under either name. The terms also now state plainly how you accept them, and add standard sections that were missing. Because the wording changed, you will be asked once more to review and accept all three policies the next time you sign in. # 2026.09.01.1 > What's new in this release of Tovari. ## Fixes [Section titled “Fixes”](#fixes) **No More False Zero Balances** (KAN-2088) 🌐 Web📱 iOS & AndroidAccounts & BalancesData Sync Sometimes a bank connection would report a $0.00 balance that didn't match your real activity, and that number could get trusted anyway — even overwriting a correct balance when an account refreshed. We fixed it: a balance that doesn't add up is now recognized as unreliable and left alone, so your real numbers stay safe. **One Charge, Not Two** (KAN-2089) 🌐 Web📱 iOS & AndroidTransactions & RegisterData Sync Some transactions were showing up twice in your register after your bank refreshed its transaction history. You weren't seeing double — we tracked down the glitch and fixed it, so every purchase now shows up exactly once. **No More Broken Sign-Ups** (KAN-2113) 🌐 Web📱 iOS & AndroidAccount & Security Signing up with Google or Apple could occasionally hit a rare timing hiccup — if two sign-up attempts landed at the exact same instant, one could quietly break the other, leaving you with an account that could never sign in again. We tracked down the glitch and closed the gap, so simultaneous sign-ups now always leave you with one clean, working account. ## Improvements [Section titled “Improvements”](#improvements) **Bank Fees Now Show Up as Fees** (KAN-328) 🌐 Web📱 iOS & AndroidCategorization & AI Some overdraft charges and other bank fees were quietly getting labeled as if they came from your bank itself, instead of showing up as the fee they actually are. We fixed the mix-up, so those charges now get called out correctly every time. **Same Merchant, Every Time** (KAN-606) 🌐 Web📱 iOS & AndroidCategorization & AIPayees Some transactions with a masked card number in the description — the kind with a string of X's mixed into the digits — weren't being matched to the merchant you'd already categorized, and every so often that jumble of characters even showed up in the merchant's name. Both are fixed now, and we've cleaned up the handful of saved matching rules that got tangled up before the fix. **No More Invite Mix-Ups** (KAN-1441) 🌐 WebHousehold Management Every so often, accepting an invite to join a shared account could show a confusing error message even though it had actually worked. That mix-up is fixed — accepting an invite now gives you the same, correct answer no matter how many times the request happens to go through. **Purchases Recover on Their Own** (KAN-1888) 🍎 iOSBilling & Subscriptions If a brief connection hiccup ever got in the way of confirming a purchase or restoring your subscription, you used to have to sign out and back in to fix it. Now the app quietly tries again a few times on its own, so things sort themselves out without you lifting a finger. **No More Quietly Wrong Balances** (KAN-2086) 🌐 WebAccounts & BalancesData Sync Some account balances could quietly drift from what your bank actually reports, and nothing ever flagged it. Now Tovari catches that difference and shows it right on the account, and one tap adds a dated, removable correction — so your balance and your bank agree again, no guesswork required. # 2026.09.02.1 > What's new in this release of Tovari. ## New features [Section titled “New features”](#new-features) **A rebuilt Tovari website, with every page finally reachable from your phone** (KAN-2186) 🌐 Web The Tovari website has been rebuilt from the ground up. There are now six pages — a new home page built around Safe to Spend, a pricing page that compares Tovari side by side with the apps you may already be using, the founder's story, a page for the iPhone and Android apps, a support hub, and a changelog so you can see what is new. The biggest practical change is on your phone. Previously most of the site simply could not be reached from a mobile browser — the menu links disappeared at small screen sizes with nothing to replace them. There is now a proper menu, so every page is reachable from any device. The whole site is also faster, easier to read, and works properly with a screen reader or with animations turned off. ## Fixes [Section titled “Fixes”](#fixes) **You’ll Know When Your Numbers Are Stale** (KAN-1339) 📱 iOS & AndroidReports & Insights Tap into a different month on your Income vs Expenses report and, if the new numbers couldn't load, we used to quietly leave last month's totals on screen — under the new month's label, with no warning. That's fixed: now you'll get a clear heads-up whenever the numbers on screen didn't manage to refresh, so you always know what you're looking at. **Report Filters, Finally Honest** (KAN-1511) 🌐 WebReports & Insights If you cleared every account out of a report's filter, the label above the numbers still said "0 Accounts" — even though you were looking at every account's totals the whole time. We fixed the label: clearing the filter now honestly reads "All Accounts," so what it tells you finally matches what you're seeing. **Refunds No Longer Look Like Big Expenses** (KAN-1578) 🌐 WebReports & Insights In your spending report, a category where you actually got money back could show up with a giant, maxed-out bar — as if it were your biggest expense of the month. We found the mix-up and fixed the math, so it now displays correctly. **Faster Budgets as You Grow** (KAN-2185) 🌐 Web📱 iOS & AndroidBudgeting Turns out your budget page was quietly doing more work than it needed to as more people join Tovari — checking through everyone else's numbers just to add up yours. We found the shortcut and pointed it straight at your own data, so your rollover keeps loading quick no matter how big we get. Your budget itself didn't change, just how fast it shows up. **No More Duplicates After Reconnecting Your Bank** (KAN-2194) 🌐 Web📱 iOS & AndroidTransactions & RegisterData Sync Reconnecting a bank account that needed you to sign in again could quietly duplicate a transaction — the same purchase landing twice in your register and throwing off your balance. We already had a safeguard built to catch exactly that, but it wasn't running at the one moment it mattered most. Now it is, so reconnecting your bank keeps your register accurate instead of doubling up. ## Improvements [Section titled “Improvements”](#improvements) **Your Spending Charts, Now Accessible to Everyone** (KAN-651) 🌐 WebReports & Insights Screen readers can now read out the full category breakdown on your monthly spending chart, not just the total. And if you get around by keyboard, tabbing to a bar now opens the same payee details you'd get from hovering with a mouse — same information, no mouse required. **A Clearer “Done” for Your Dashboard Watchlist** (KAN-804) 🤖 AndroidBudgeting On Android, closing the "Watch on your dashboard" picker now shows a "Done" button instead of a plain X icon. Everything you pick there already saves on its own, so "Done" finally says what's actually happening — and it now matches what you already see on iPhone. **See Exactly Who You’re Sharing With** (KAN-1058) 📱 iOS & AndroidHousehold ManagementSettings Sharing Safe to Spend with a partner? Your Settings page now says their name instead of a generic "everyone," so it's clear at a glance exactly who's seeing what you see. **Safe to Spend Colors Now Match** (KAN-1059) 📱 iOS & AndroidBudgeting On your Safe to Spend card, the big total number was a slightly different shade of amber or red than the little status label right beside it. We matched the colors so the whole card now reads as one consistent picture at a glance. **Full Keyboard Access to the Sidebar** (KAN-1104) 🌐 WebFile ImportBudgetingAccount & Security Some of the buttons in your sidebar — the collapse arrow, the navigation links, your account list, even log out — weren't reachable if you get around by keyboard or screen reader. That's fixed now, along with the close button on the file import window, so everything responds properly no matter how you navigate. **Your Register Gets a Style Upgrade** (KAN-1334) 📱 iOS & AndroidTransactions & Register The Cleared and Uncleared totals on your register screen just got a small style upgrade — they now match the clean, consistent look you see everywhere else in the app. Same numbers, sharper presentation. **Clear Transactions Without a Mouse** (KAN-1504) 🌐 WebTransactions & Register The little status dot that marks a transaction cleared, uncleared, or reconciled used to only respond to a mouse click. If you get around by keyboard or screen reader, you can now tab to it, toggle it with Enter or Space, and it'll announce exactly which state it's in — including when it's locked because the transaction's already reconciled. **Full Keyboard Access to Your Register** (KAN-1505) 🌐 WebTransactions & Register A couple of controls in your transaction register — the circle you click to mark a pending charge cleared, and the arrows you use to expand or collapse a section — are now built as real buttons like the rest of the app. If you get around by keyboard, you'll always see exactly where you are, and screen readers will announce them correctly too. **A Keyboard-Friendly Actions Menu** (KAN-1506) 🌐 WebTransactions & Register If you get around with a keyboard or a screen reader, the actions menu on each transaction row — Edit, Delete, and the rest — finally behaves like a real menu. Arrow keys move you through the options, typing a letter jumps straight to what you want, and Escape closes it and sends your focus right back where you started. **Pop-Ups Get Proper Keyboard Manners** (KAN-1591) 🌐 WebAccounts & BalancesBudgetingHousehold ManagementTransactions & RegisterData SyncFile Import A handful of pop-up windows in the app weren't playing by the keyboard's rules — pressing Escape didn't always close them, and tabbing through could sneak you right past the window into the page behind it. We tracked them all down and gave them better manners: Escape closes them now, Tab keeps you where you belong, and closing one puts you right back where you left off. **Keyboard-Friendly Account Setup** (KAN-1592) 🌐 WebAccounts & Balances If you get around with just a keyboard, adding an account used to leave you stuck — the button was there, but Tab and Enter couldn't reach it. That's fixed now: tab to it, press Enter or Space, and it opens right up. **Updated Terms of Use and Privacy Policy — you will be asked to accept them once** (KAN-2187) 🌐 WebAccount & Security Our Terms of Use and Privacy Policy have been updated, so you will be asked to review and accept them the next time you sign in. Two things changed. The Terms no longer quote a subscription price — the price you pay is always shown to you before you are charged, either in the app or by the app store you subscribe through, and keeping a figure in the Terms only risked it going out of date. Both documents also no longer describe Tovari as invitation-only early access, because it is simply available now. The Privacy Policy also now correctly mentions signing in with Apple as well as Google. # 2026.09.02.2 > What's new in this release of Tovari. This release contains internal improvements only. # 2026.09.02.3 > What's new in this release of Tovari. ## Improvements [Section titled “Improvements”](#improvements) **We’ll Tell You When Your Card Fails** (KAN-416) If a payment doesn’t go through, Tovari now emails you right away with a link to update your card and the date we’ll try again — so an expired card can’t quietly end your subscription while you’re not looking. Cancelling gets the same treatment: you’ll get a confirmation that spells out exactly how long you still have access and how to come back if you change your mind. Both notes come from us, in plain language, with no surprises buried in the fine print. # 2026.09.03.1 > What's new in this release of Tovari. ## New features [Section titled “New features”](#new-features) **Help Is Now Just One Tap Away** (KAN-2133) 🌐 Web Stuck on something in the app? Tap the help button in the corner, ask in your own words, and get a plain-language answer with a link to learn more. If it can't help, reporting the problem to us is still just as easy, right in the same window. **Help That Knows Where You Are** (KAN-2134) 🌐 Web Open the help chat and it already knows what screen you're on — it says hello by name and offers a couple of quick questions people actually ask there, so you can just tap one instead of typing it out. Every suggestion is something it can actually answer, and if what you've really got is a bug or an idea, it points you the right way for that too. **Take Me There** (KAN-2135) 🌐 WebTransactions & RegisterReports & Insights Ask the in-app assistant how to do something on another screen, and it now hands you a 'Take me there' button that jumps you straight to it — no more hunting for the right page yourself. Ask how to add a transaction while you're on Bills, tap it, and you land right in your register. It skips the button when you're already looking at the screen in question, and takes you to the exact report or review list it mentioned, not just the general area. **Report a Bug or Idea, Right in Chat** (KAN-2136) 🌐 Web You can now report a bug or share an idea for Tovari right from the chat — no form required. Tell the assistant what happened and it'll ask a couple of quick questions, write up the report, and let you read and tweak every word before anything gets sent, so what we receive is exactly what you approved. And if you'd rather fill out a form, the old one is still just a tap away. **Your Investments, Finally Counted** (KAN-2191) 🌐 Web📱 iOS & AndroidAccounts & BalancesData SyncReports & Insights Your retirement and brokerage accounts finally show what they are actually worth. Until now a linked IRA, 401k or brokerage account sat at $0.00 — your bank was reporting a real balance, we just were not asking for it — which quietly dragged your net worth down with it. Now Tovari pulls the current market value straight from the institution, stamps it with the date it was reported, and shows how much it has moved since the last update. Open one of those accounts and you will see a running history of its value instead of an empty transaction list waiting for charges that were never coming. Your net worth and Net Worth report include the real figure too. Some older connections need a quick reconnect before the balance can come through — if yours does, you will see a note on the account telling you so. **Clear Your Search in One Click** (KAN-2243) 🌐 WebTransactions & Register You can now clear a register search in one click. An ✕ appears in the search box as soon as you type, and clicking it — or pressing Esc — brings the whole account back into view. Before, the only way out of a search was to select the text and delete it by hand. **What’s New That’s Actually New** (KAN-2246) 🌐 Web The What's New page on our website had quietly fallen three weeks behind — it was typed up by hand, and hands forget. It now fills itself in straight from the releases we ship, so the newest updates show up there the moment they go out, and a link at the bottom takes you to the full history of everything we have changed. **Adding a transaction now opens a proper window instead of a blank row you had to go hunting for** (KAN-2271) 🌐 WebTransactions & RegisterBills & Reoccuring Adding a transaction on the web now opens a window right in front of you, with the account name at the top and room for the date, payee, amount, category and a note. Before, it quietly tucked a blank row into the list — often somewhere off the screen — so the button looked like it had done nothing at all. And if you pick a date in the future, the window now says plainly that you are scheduling something for that day rather than spending money today. **Help That Knows Where You Are** (KAN-2272) 🌐 WebCategorization & AI Ask the help chat how to do something, and it now answers for the exact device you're on — no more skimming instructions for three platforms to find your paragraph. If a feature only exists somewhere else, it'll say so plainly and point you to where it lives, instead of walking you through steps that don't apply to you. It's also stopped calling your computer "a computer" — now it says PC or Mac, like a person would. ## Fixes [Section titled “Fixes”](#fixes) **No More Sneaky Duplicate Charges** (KAN-2195) 🌐 Web📱 iOS & AndroidTransactions & Register Every so often, if your bank sent us the same charge twice, we dutifully recorded it twice too — so one purchase could quietly show up twice in your account. That's fixed now: Tovari spots those repeat charges on its own and drops them into your review list so you can clear out the extra with one tap. We're careful about it, too — genuine same-day repeats, like grabbing coffee twice, are left exactly alone. **Help That Actually Reads Your Question** (KAN-2279) 🌐 Web Ask our help assistant a question from any screen, and it actually listens to what you asked — not just where you're standing. Before, "how do I add a transaction" from your dashboard got you a shrug and an offer to write instructions that already existed; now it just points you straight to them. **Help Chat Finally Knows How to Reach Support** (KAN-2287) 🌐 WebNotifications & E-Mail Ask the help assistant how to reach support and it used to shrug you off entirely, saying it could only help with in-app questions. That's fixed now, so "how do I email support" gets you a real answer. We also unlocked over a dozen help pages, including most of the getting-started guides, that were quietly unreachable no matter what you asked. ## Improvements [Section titled “Improvements”](#improvements) **Faster, More Accurate Balances** (KAN-63) 🌐 Web📱 iOS & AndroidAccounts & BalancesTransactions & Register Your account and register balances now show up faster, since we stopped re-adding every transaction in your history each time the screen loaded. While we were in there, we also corrected a handful of account balances that had quietly drifted out of sync over time — if yours was one of them, it's showing the right number now, with nothing for you to do. **Help Chat Gets Its Own Budget** (KAN-2137) 🌐 WebCategorization & AI The help chat in the app now runs on its own budget, so heavy use of other behind-the-scenes features can never quietly turn it off — and it can't slow anything else down either. If your household asks a lot of questions in a short stretch, we'll say so as a household, never singling anyone out, and tell you exactly when you can ask again. And if help ever needs a quick breather, you'll still get a link to the right article for what you're doing and an easy way to tell us something's wrong, so you're never left stuck. **Quieter Billing Behind the Scenes** (KAN-2189) 🌐 WebBilling & Subscriptions Our behind-the-scenes billing system was occasionally setting off a false alarm for our engineering team over a signal that didn't need attention. We found the hiccup and quieted it down — your bills, payments, and account were never affected. **Our Web Address Now Always Works** (KAN-2288) 🌐 Web However you type our web address now, you'll land right on our site. It used to drop you on a dead page if you left off the "www" — that's fixed for good. # 2026.09.04.1 > What's new in this release of Tovari. ## New features [Section titled “New features”](#new-features) **Your Venmo and Zelle Payments, Sorted** (KAN-2313) 🌐 Web🍎 iOS🤖 AndroidCategorization & AITransactions & Register Money you send to friends and family through Venmo, Zelle, Cash App or PayPal now lands in its own Personal Payments category instead of sitting uncategorized forever. It counts toward your spending, because that money really did leave your account. Payments to actual businesses stay where they belong — we look for a real person on the other end before filing anything. **Header controls no longer overlap on phones, and the transaction list’s hidden menu becomes visible buttons** (KAN-2370) 📱 iOS & AndroidTransactions & RegisterBudgeting On phones, an account with a long name used to spill its title across the buttons at the top of the screen, and the Budget screen's title, help button and month picker all printed on top of each other. Long names now shorten neatly and every control has its own space, with the month picker moved to its own row just below the title so it is easy to reach. The transaction list also loses its hidden "more" menu: Search and Reconcile are now buttons you can see at the top of the screen, and setting up a repeating payment is a simple Transaction or Scheduled choice at the top of the Add screen. Everything the old menu did is still there — the bank's own transaction wording is a switch in Filters, and account details are edited from the Accounts tab. **The help assistant knows what’s new — and telling us what it’s missing takes one tap** (KAN-2388) 🌐 WebNotifications & E-Mail Ask the in-app assistant what's new and it will actually tell you — it now knows what shipped in the last three releases, so "has anything changed recently?" finally gets a real answer instead of a shrug. And when you ask it something the help pages don't cover, "Report this gap" now does exactly that in a single tap: no form to fill in, no follow-up questions, just a thank-you and the ticket number. ## Fixes [Section titled “Fixes”](#fixes) **No Duplicate Transfers After a Reconnect** (KAN-2214) 🌐 Web🍎 iOS🤖 AndroidAccounts & BalancesTransactions & RegisterData Sync When your bank asked you to reconnect an account, a transfer you already had could quietly come back as a second copy, throwing off both your balance and your spending totals. We tracked that one down: a reconnect now recognizes a transfer it has seen before and updates the one you already have instead of adding a duplicate. **No More Double-Counted Bill Payments** (KAN-2298) 🌐 Web📱 iOS & AndroidBills & ReoccuringReports & Insights When your bank placed a hold on a bill payment a few days before its due date, we didn't connect the two — so the bill still looked unpaid and the same money came out of your projected balance twice. No, you weren't seeing double: that early hold now shows up on the scheduled bill as a pending payment, and it only counts against your balance once. **The search snippet now reads like the rest of the site** (KAN-2364) 🌐 WebBilling & Subscriptions One line of the Monarch comparison page still read like a product manual, and it happened to be the line Google shows in search results. It has been rewritten to match the rest of the site. The check that was supposed to catch this only looked at the body of the page and skipped the search summary, so it now reads both. **Investment balances now appear right after you connect an account** (KAN-2365) 🌐 Web📱 iOS & AndroidAccounts & BalancesData Sync When you connected an investment or retirement account, its balance could take up to four hours to appear. Until it did, the account showed a dash with nothing to explain the delay, which made it look as though the connection had failed. Whether you waited seconds or hours came down to chance. Tovari now asks your provider for the balance the moment you finish connecting, so the value typically appears within seconds. If your provider needs a little longer to prepare the data, Tovari keeps checking on its own and fills it in as soon as it is ready. **Investment balances now stay current on the web app** (KAN-2366) 🌐 WebAccounts & Balances On the web app, an investment or retirement account could keep showing an out-of-date balance, or none at all, even though the same account showed the correct value on your phone. Refreshing the page did not help, because the web app was reusing a saved copy of your account list. The only things that worked were closing the tab entirely or signing out and back in. Tovari now notices when an account's value is one your bank updates on its own, and refreshes it — including when you switch back to the tab. Accounts that only change when you record something still load instantly from the saved copy, so everyday screens are as fast as before. **Dashboard Loads Right Up After Policy Updates** (KAN-2393) 🌐 WebAccount & Security When we asked you to review updated policies, your dashboard sometimes got stuck showing “Couldn’t load” messages even after you’d already accepted them. That’s fixed now — accept the update and everything loads right back up on its own, no extra taps needed. ## Improvements [Section titled “Improvements”](#improvements) **The Help Assistant, Explained** (KAN-2138) 🌐 Web The help assistant now has its own guide: what it can answer, what it can't, and why it will never see your balances. You can also just ask the assistant about itself — and when a Tovari question isn't covered yet, it offers to pass that gap along so we can write it up. **Your Net Worth Always Adds Up** (KAN-2230) 🌐 WebReports & Insights Your net worth now always matches the balances on your accounts, right down to the penny. Before, if money moved while the report was loading, the total could come out slightly off — we found that gap and closed it. **A website that explains itself to people who have not heard of us yet** (KAN-2357) 🌐 WebBilling & Subscriptions Tovari's website now explains itself to people who have never heard of us. Every page has been retitled to say what it actually offers instead of just repeating the company name, and five new comparison pages lay out how Tovari stacks up against YNAB, Monarch, Copilot and Rocket Money — including, on each one, the things those apps genuinely do better than we do. There is also a page for anyone still hunting for a replacement since Mint closed down. Search engines can now read our price and product details directly from the pages, so a result can show more than a plain blue link. None of this changes anything inside the app itself. **A front door for the comparisons, in the site’s own voice** (KAN-2363) 🌐 WebBilling & Subscriptions The comparison write-ups now have a home you can actually find. A new Compare page gathers all five in one place, with a link to it in the footer of every page, where before you had to scroll most of the way down the pricing page to discover they existed. The writing has been reworked too, so it sounds like the rest of the site instead of a product manual, and the punctuation now matches everywhere. None of the comparisons themselves changed — same prices, same findings, same honest notes about what each competitor does better than we do. **A Cleaner Investment Header** (KAN-2368) 🌐 WebAccounts & Balances The header on an investment account no longer repeats the date its value was last checked. That date was already sitting right underneath it, at the top of the history list, so we took the duplicate out and gave the balance more room to breathe.