Currency & exchange rates

What a Currency column's amounts are IN, and who decides. The currency belongs to the record, not to whoever is reading it — everyone sees the same amount on the same record. Teams working in one currency never have to think about any of this; teams holding several can say so, mark individual columns, and supply the rates to total across them. The currency belongs to the record A deal worth $300 is worth $300 to everyone who opens it. RowFold takes the SYMBOL from the workspace's data, never from the reader — so a colleague in London sees $300, not £300. Your personal setting still matters, but only for how numbers are punctuated: whether that reads 1,234.50 or 1.234,50. That part genuinely is yours. The amount and its currency are not. Set the workspace's currency In Settings, each workspace you administer has a Currency setting. Leave it on Follow the owner and it uses the preference of whoever owns the workspace, which is almost always right and means a new workspace needs no setup at all. Choose a currency explicitly to pin it. Changing it never rewrites a stored amount and converts nothing. It changes what the numbers already on your records are understood to be in, so change it because it was wrong, not to convert your data. If you hold more than one currency Tick We record money in more than one currency in the same place. Until you do, there is one currency in the workspace and nothing anywhere asks you to pick one — that is deliberate, and it is why most teams never meet this page. With it on, each Currency column can carry its own currency: open Edit fields on the table and choose one on the column's row, or leave it following the workspace. A column's currency is ignored while the switch is off, so turning it back off cannot leave columns quietly formatting in a currency the workspace no longer claims to use. Exchange rates, and why you supply them Once a workspace records several currencies, Settings gains an Exchange rates table. You enter the rates: a pair, a number, and the date it took effect — “1 GBP = 1.27 USD from 3 Aug 2026”. RowFold does not fetch rates from a market feed, on purpose. A live rate moves every second, carries a spread the product cannot see, and would make a figure on your screen change with nobody editing anything. The rate you booked at is a fact; a rate scraped this morning is not. Add a newer rate for the same pair whenever it moves. Rates are kept by date, so the old ones stay true for the records they applied to. A rate entered for the same pair on the same day replaces the earlier one — that is a correction, not a second fact. Totalling a column that holds several currencies Summing a column of dollars and pounds by adding the numbers gives you a total of nothing. So wherever RowFold adds money up — a column total on the grid, a group subtotal in a report, a KPI or chart tile on a dashboard — it converts each record at the rate in force when that record was created and adds the converted amounts. That is how transaction-date conversion works in accounting, and it means the answer does not drift as rates move. Only the total converts. The records themselves keep the currency they were written in: a £250 deal still reads £250 in its row, next to a total that has counted it as $317. Restating the row would be the product asserting an amount nobody agreed. If a pair has no rate, nothing is guessed. The grid says Mixed currencies instead of a number; a report shows the total it could reach and states the shortfall beneath it — “38 of 41 — 3 need a GBP → USD rate”. No unconvertible row is quietly counted as zero or treated as parity, because a total that silently covers part of a column looks complete and isn't. A calculated column converts too. A Rollup totalling a linked table's money, a Lookup pulling one record's amount onto another row, and a formula reaching across a link all put the money into one currency first — each contributing record at its own date and its own currency — and print what they were converted from beside the figure where there is one original to name. The currency is the one belonging to the column the money came from, not to the calculated column, which declares none. Where one of them really does convert — its source column holds more than one currency, or one that is not what it reports in — the grid stops totalling, sorting, filtering and grouping by that column, because those are computed by the database over every matching row and it cannot apply a rate chosen per record; take that question to a report, whose aggregate column across the same link converts and totals correctly. This is decided by the data rather than by the switch, so a calculated column whose money is all in one currency keeps every one of those controls. Tips • Leave the multi-currency switch off unless you genuinely hold several currencies. It is the one thing that decides whether anyone in the workspace is ever asked about currency. • The currency picker on a field's row only appears for Currency fields. A Number field is just a number — if it is money, change its type first. • Enter a new rate whenever one moves rather than editing the old one. Records created earlier keep converting at the rate that applied when they were created. • A report or tile that adds money up shows the currency it converted into. The rows below it keep their own, so you can always see what was actually recorded. Good to know • Where a Rollup, Lookup or Formula really does convert money — its source column holds more than one currency, or one that is not what it reports in — the grid stops totalling, sorting, filtering and grouping by it, because those are computed by the database over every matching row and it cannot apply a per-record rate chosen by a per-record date. The summary cell says so and names why. A report's aggregate column across the same link converts and totals correctly; take the question there. A column whose money is all in one currency keeps every one of those controls, whether or not the workspace records several. • A Rollup or Formula that produces money takes the currency of the column it came from, and prints what it was converted from beside it — “$1,714.50 (£1,350.00)” — where there is one original to name. A rollup spanning three currencies has no single original and says nothing rather than picking one. • Money a formula reads from its OWN row is deliberately not converted: 20% of a £250 invoice is £50, not a dollar figure. Conversion applies where unlike currencies actually meet — across a link, and in a total. • Individual records can carry their own currency in the data and over the API, but there is no per-cell picker in the grid yet — in the app, currency is set per column. • Changing a workspace's currency reinterprets existing amounts; it does not convert them. If you have been recording dollars and switch to euros, those numbers are now euros. Who can do what • Only workspace admins can set the workspace currency, turn multi-currency on, or add exchange rates. • A column's own currency is part of the field, so it is set by whoever can edit fields. • Everyone reading the workspace sees the same currency on the same record, whatever their personal preference.