One currency is the main one — it is the common denominator whenever a total mixes currencies. Any entry or annotation can be recorded in another currency, and the app converts to the main one using the rate you registered for that value's month. You also choose how you want to read amounts day to day: always converted to the main currency, or in the currency they were entered in. While only one currency is active, none of this shows up: the currency picker only appears when it is relevant.
The screen, top to bottom
| Block | What it decides |
|---|---|
| Main currency | The currency a total that mixes currencies is presented in. Only one can be, and the line right under the field repeats the choice with that currency's symbol, so there is no doubt about what it decides. |
| Amount display | Whether an amount appears converted to the main currency or in the currency it was entered in. That is the next section. |
| Currencies | The list of what is registered. Each row carries the currency, whether it is active, what it is worth today in the main currency, and the button that opens its rates. |
Turning on a second currency
- Add the currency. Enter the three-letter code (USD, EUR, GBP…) and the symbol. The code is what identifies the currency across the app.
- Leave it active. Inactive currencies stay registered but disappear from the screens — that is how you retire a currency you no longer use without losing the history already recorded in it.
- Confirm which one is the main. Only one can be, and it is picked in the field at the top of the screen. In the list, the main currency shows a main badge where the active switch would be: the reference currency does not get switched off.
- Register the rate. Through the Rates button on the currency's row. Without a rate for the pair, the app has no way to convert the amounts into the main one.
Each row states, under the name, what is already known about that currency: 1 US$ = R$ 5.4321 · since Jul/2026 when there is a rate, or a highlighted no exchange rate registered when there is not — which is the warning that amounts entered in it are not being converted. The main currency's row has no rate to show, because it is the reference; its Rates button opens every pair that involves it, and that is the answer to "why does my main currency look like it has no rates at all?" — they were all filed under the other currency of the pair.
With more than one active currency, the entry screens and the annotations that carry an amount start showing the currency picker. If you turned on a second currency and don't see the picker, check that it is really marked as active. A new entry already opens in your main currency — and when exactly two currencies are active, the picker is a single switch whose resting position is always the main one, whatever letter the codes happen to start with.
Amount display
Converting everything to the main currency is the default, and it is what makes the totals add up. But someone who enters a good part of their expenses in another currency usually wants to read that expense as it happened — 30 euros, not what 30 euros came to in reais that month. That is the choice:
| Option | What happens |
|---|---|
| Convert to the main currency | Every amount appears in the main currency, converted at the rate effective on its date. This is the default. |
| Keep the entry currency | Each amount appears in the currency it was entered in. |
The second option cannot hold everywhere, and there is a single rule for when it gives way: sums, averages and markers keep the currency as long as everything under them shares it; a mix always converts to the main currency. A month of euro-only expenses adds up in euros; the same month with one expense in reais in it adds up in the main currency, because adding euros to reais is not a number.
Nothing that is stored changes, and no calculation changes its result — what changes is the currency the result is written in. The budget is the exception that proves the rule: it is a number in the main currency, so the sum it is compared against is one too, always.
The option stays available even with a single active currency. Deactivating a currency does not erase the entries already made in it, so a history that mixes currencies survives the deactivation — and the way to read it has to stay within reach.
Rates are effective from a month
A rate is registered as 1 origin currency = X destination currency, with an effective date in MM/yyyy format. Each row applies from the given month until the next rate registered for the same pair. You don't need one for every month: if you registered a rate for 03/2026 and the next only for 09/2026, the months in between use March's.
That is the key difference from converting everything at today's rate: a trip taken two years ago keeps being worth what it was worth back then, and your history doesn't change shape every time the exchange rate moves.
How totals are computed
Amounts in different currencies are never summed before conversion. The app groups entries by month and by currency, converts each group's sum with that month's effective rate, and only then adds the results. A month with expenses in three currencies produces a correct total in the main currency, not a sum of incomparable numbers.
When you type an amount in a foreign currency, the app shows the calculation right under the field — typed amount × rate = converted amount. It is the quickest way to notice a missing rate, or a wrong one.
The app does not fetch rates automatically: each one is registered by you. That gives full control over which exchange rate was used — including your card's effective rate, which is usually more useful than the commercial one — but it means a currency with no registered rate is not converted.
One currency per record, not per item
In item-based annotations — checklist, budget, detailed list — the currency is chosen once for the whole annotation and applies to the total and to each item's amount. If you need to compare options in different currencies, use separate annotations: that way each converts with the right rate and the total still makes sense.
Import templates also store a default currency, so a statement from a foreign-currency account comes in with the right currency already set on every entry.