How to set currency and year
These two settings decide whether CloudMonitor’s numbers can be handed to Finance without re-cutting them. The financial year start is what makes “year to date” mean your year rather than January’s, so a forecast lines up with the period your board actually reviews. The currency is the symbol every figure is presented in, and because amounts are never converted, changing it later strands every budget stored in the old one. Both live under Settings ▸ Workspace Settings ▸ Account, and both are worth setting once, early, and then leaving alone.
Financial year start
Section titled “Financial year start”Set the day and month your financial year begins. The day list adjusts to the month you pick, and February allows the 29th.
This drives the accounting presets in the top-bar Period filter:
Drives Financial Year to Date, Quarter to Date, Last Quarter, and Previous Financial Year.
Get it right and “Financial Year to Date” means what your finance team means by it. Get it wrong and every accounting-period figure in the product is quietly measuring the wrong window, which is the kind of error that survives a long time because nothing looks broken.
After you save, the presets use the new boundaries immediately, with no reload. Open the Period picker to check the dates that each preset now covers.
If one of these presets isn’t offered, it may sit outside the available data, exceed the 365-day limit, or cut through a month that CloudMonitor only holds as a monthly total. See older periods come in whole months. Nothing is wrong with your financial-year setting.
Reporting currency
Section titled “Reporting currency”Pick the currency every figure is shown in. A live preview shows example amounts at each level of precision: totals rounded to whole amounts, ledger rows keeping a decimal so they still add up, and per-unit rates keeping enough decimals that a sub-cent cost never reads as zero.
What changing it breaks
Section titled “What changing it breaks”Every budget stored in the old currency stops being evaluated. On the Budgets list they show Requires repair instead of an amount, and on Budgets & Forecasts you’ll see a banner saying no budget can be evaluated.
Fixing each one means opening it, retyping the amount in the new currency, and ticking the box confirming you did the conversion yourself. Save stays disabled until you do.
So: set the currency before you create budgets. If you must change it later, plan to repair every budget in the same sitting: a half-repaired set is worse than either state, because some budgets alert and some silently don’t.
Time zone
Section titled “Time zone”Also on this card. This sets the schedule your workspace’s data refresh runs to: pick the zone your finance team works in, and the nightly update lands overnight for them rather than mid-afternoon.
It does not change how dates are displayed. Dates and times across the app are always shown on your own device’s clock, so a colleague in another office sees the same event at their local time. Where a time matters, it’s labeled with the zone (for example “5:04 PM Australian Eastern Time”), which is what lets the two of you compare notes without confusion.
Most screens show just the date to keep tables readable: hover over any date to see the exact time it happened.
Saving and drafts
Section titled “Saving and drafts”On Account, Save writes the staged financial year, time zone and currency changes together. It never saves a draft from another tab; switching tabs keeps each draft staged.
When the active tab matches its last saved values, Save and Cancel are disabled. A change shows You have unsaved changes. Reverting every field makes it clean again.
On Account and the other independent tabs, Cancel restores only that tab’s last successfully saved values. Branding and Partner branding deliberately share one form boundary, so Save or Cancel applies to both of those tabs together. Cancel never leaves Workspace Settings or changes already saved data.
CloudMonitor asks before you leave Workspace Settings with any draft. Reloading or closing the page triggers the browser’s unsaved-changes warning.
A complete save shows Settings saved. After a partial failure, Earlier changes were saved, but the remaining settings could not be saved: appears with the reason. Completed writes stay saved; failed and unattempted changes stay drafted. Try again retries only those outstanding changes. Cancel discards them without reverting successful writes.
Related settings
Section titled “Related settings”The other Workspace Settings tabs include:
| Tab | What it does |
|---|---|
| Branding | Your own logo and the workspace’s starting appearance |
| Anomaly detection | The thresholds that decide what gets flagged |
| Billing | Your plan and seat usage |
Some tabs only appear when there’s something in them for your workspace, so your list may be shorter.
Optional modules now have their own Settings ▸ Features screen. See turning optional modules on and off.
Anomaly detection thresholds
Section titled “Anomaly detection thresholds”Worth knowing about while you’re here. A cost anomaly is only raised when a change clears both a minimum cost value change and a minimum percentage change.
Both, not either, which is why a huge percentage swing on a trivial amount stays quiet, and so does a small percentage move on something enormous. If the Anomaly Inbox is too noisy or too quiet, these two numbers are the dial.