The Figure With a Squiggle in Front of It
A workspace can choose a second currency to read its dashboards in. Every converted figure is prefixed with a squiggle, carries a note naming the rate, and is kept off every document that leaves the building — and choosing your own base currency turns the whole thing off.
The board meets in dollars. The business trades in shillings. Both of those facts are permanent, and only one of them belongs in the accounts.
This is a reading aid, not an accounting feature, and the distinction is enforced rather than advised. Money is stored, invoiced, printed and accounted in your workspace's own locked currency. On top of that sits an optional preference: pick a second currency, and on-screen figures are shown converted into it at a live rate.
Where it applies, and where it is refused
| Surface | Converted? |
|---|---|
| Dashboards | Yes |
| On-screen reports and list views | Yes |
| Invoices | No |
| Statements | No |
| Receipts | No |
| Any PDF or export | No |
The separation is structural: there are two formatting functions, and they are documented against each other. One converts for reading; the other never does and is what documents call. A figure on a printed invoice cannot pick up a display conversion, because the function that produces it has no path to one.
Why a document must never carry an indicative figure
An invoice is a demand for a specific amount of a specific currency, and a statement is a claim about a balance. Both are relied on by somebody outside your business who has no way of knowing which rate was used or when. A converted total on either is not a helpful convenience — it is a number your customer will pay, dispute or reconcile against, struck at a rate nobody agreed.
Three refusals that make it honest
-
Choosing your own currency is the same as choosing none
Set the display currency to the one you already trade in and the whole feature switches itself off rather than converting at a rate of one. That means no squiggles, no notes, and no invitation to wonder whether a figure has been through a conversion.
-
An unavailable rate shows the real figure
When a rate cannot be obtained, the native amount is shown unchanged rather than a zero or a blank. A converted figure is either correct or absent, and the note beside it says which — "conversion is temporarily unavailable; showing shillings".
-
A record in its own currency is converted from that currency
Where a record carries its own currency — an invoice raised in another one — the conversion starts from that rather than from your base. And if the record is already in your display currency, it is left alone, because converting it to itself would add a squiggle to an exact figure.
The squiggle is the feature. It says this number was arrived at, not recorded.
The note is not decoration
When a conversion is active, the surfaces showing it carry a sentence naming both currencies, the exact rate to six decimal places, and the words "indicative only — invoices and statements remain in" your own currency. It is written that way on purpose: the two things a reader needs are the rate, so the figure can be checked, and the boundary, so nobody quotes a dashboard number in a negotiation.
A converted figure without a stated rate is the worst version of this feature. It is precise, plausible, and impossible to reconcile against anything — and it will be pasted into a board pack within a week.
What this is not
Worth being explicit, because the two get conflated constantly. Being able to invoice a customer in another currency is a different capability and it exists separately: an invoice can carry its own currency and its own rate, and the document is correct in that currency. The display preference sits above whatever each record is in and changes only how figures are read on screen.
And neither of them is a second set of books. The ledger is kept in one currency. An organisation that genuinely needs accounts in two currencies needs two entities or a consolidation process, and that is a conversation about structure rather than a preference.
What AWRA OpsHub does today
- An organisation-wide display currency preference, converting figures on dashboards, on-screen reports and list views at a live rate.
- A visible marker on every converted figure, so an indicative number is never mistaken for a recorded one.
- A note naming both currencies and the exact rate to six decimal places, closing on the statement that invoices and statements remain in the workspace currency.
- Two separate formatting functions — one that converts for screens and one that never does — with documents calling the second, so a printed figure has no path to a conversion.
- A display currency equal to the native currency treated as no preference at all, rather than converting at a rate of one.
- A conversion that returns nothing rather than a zero when a rate is unavailable, with the native figure shown and the note explaining why.
- Conversion from a record's own stored currency where it has one, rather than assuming every amount is in the workspace base.
- The same mechanism serving the partner portal, where commissions and payouts are denominated in shillings and a partner can read them in something else.
More we can add to your workspace
- A per-user display currency, so a finance lead and an overseas director can each read the same workspace in their own terms.
- A rate and date pinned to a saved or scheduled report, so a figure produced last month can be reproduced exactly rather than reconverted at today's rate.
- Converted figures in scheduled report emails, which today go out in the workspace currency because they leave the building.
- A choice of rate source per organisation, for businesses whose treasury policy names a specific reference rate.
- A historical rate for a historical figure, converting last year's revenue at last year's rate rather than at today's.
- A consolidated view across several workspaces in one currency, for groups running an entity per country.
Where we point you to a specialist
- We will not put a converted figure on an invoice, a statement, a receipt or an export. Those documents are relied on by people outside your business who cannot know which rate was used or when, and an indicative total on one of them is a number somebody will pay or dispute.
- We will not keep a second set of books. A ledger in two currencies is not a display preference — it is a different accounting structure with its own translation rules and its own disclosures, and an organisation that needs it needs the structure rather than a conversion on a dashboard.
- Which rate a group should use for management reporting is a treasury policy question owned by your finance function. We will show a live rate and name it precisely; adopting a particular reference rate as authoritative is a decision with consequences we are not the right party to take.
A rate pinned to a saved report is the contained piece here, and it is the one that turns an on-screen convenience into something a management pack can be built from — the same figures, reproducible next month.
From reading aid to reporting currency
The conversion, the marker and the note all exist. What turns this into something a group finance function can use is pinning rates and letting different readers choose differently.
A pinned rate per report
The rate and its date stored with a saved or scheduled report, so last month's figures reproduce exactly instead of moving with the market.
A per-user preference
One workspace read in two currencies by two people, without either of them changing what anybody else sees.
A group consolidation view
Several workspaces summarised in one currency, for organisations running an entity per country.
We publish scope, not dates.
Scope reporting currencyFive questions to ask about a display currency
Does it change what is stored?
A good answer sounds like
No.
What ours actually is
No. Storage, invoicing, printing and accounting all stay in the workspace's locked currency.
Can a converted figure reach a document?
A good answer sounds like
No, structurally.
What ours actually is
No. Documents call a formatting function that has no conversion path, and the two functions are documented against each other.
Is the rate visible?
A good answer sounds like
Yes, precisely.
What ours actually is
Yes — both currencies and the rate to six decimal places, in a note beside the figures.
What happens when the rate is unavailable?
A good answer sounds like
The real figure, and a reason.
What ours actually is
The native amount unchanged, with a note saying conversion is temporarily unavailable. Never a zero.
Is this the same as invoicing in another currency?
A good answer sounds like
No.
What ours actually is
No. That is a separate capability where the document itself carries a currency and a rate. This one sits on top of whatever each record is in.
Our take
Almost every complaint about currency in an operational system comes from a figure that had been converted without saying so. The design here answers that with three commitments rather than one: convert only for reading, mark every converted figure, and name the rate beside it. The refusals are what make it trustworthy — a display currency equal to your own switches the feature off rather than converting at one, and an unavailable rate produces the real number rather than a plausible zero. Where it stops short is reproducibility: a dashboard read at today's rate is a different number tomorrow, which is fine for reading and not fine for a management pack. Pinning a rate to a saved report is the change that closes that, and it is the only thing standing between this and a genuine reporting currency.
Decide whether you are reading or reporting
Reading in a second currency is a preference you switch on this afternoon. Reporting in one needs a pinned rate and a policy about which. Knowing which of the two you need makes the rest of the conversation short.
Talk through currency reportingFrequently asked questions
Does setting a display currency change my accounts?
Not in any respect. Amounts are stored, invoiced, printed and posted in your workspace's own currency, which is locked at registration. The preference affects how figures are drawn on dashboards, on-screen reports and list views, and nothing else.
What is the squiggle in front of the number?
An approximation mark, and it is deliberate. It says the figure was arrived at by conversion rather than recorded, so nobody quotes it as an exact amount. Where a figure carries no mark, it is the stored value in its own currency.
Why did nothing change when I set the display currency?
Almost certainly because you chose the currency you already trade in. A display currency equal to the workspace currency is treated as no preference at all, rather than converting at a rate of one and decorating every figure with a mark. Nothing is broken; the feature has correctly decided it has nothing to do.
Can I put the converted figures on an invoice for an overseas customer?
Not through this. What you want there is an invoice raised in that currency, which is a separate capability — the document carries its own currency and its own rate, and it is a real demand for a real amount. A display conversion on an invoice would be a number struck at a rate nobody agreed, on a document somebody is going to pay.
What rate is used?
A live rate between your workspace currency and the display currency, named to six decimal places in the note beside the converted figures. Because it is live, the same dashboard read a week apart shows different numbers — which is correct for reading and is exactly why a management pack needs a rate pinned to the report rather than to the moment it was opened.
Does it work in the partner portal?
Yes, on the same mechanism. Partner commissions and payouts are denominated in shillings, and a partner who reads in another currency sees the same indicative conversion with the same mark and the same note. The underlying amounts and the payouts themselves remain in shillings.
