Currency and time zones

Currency and time zone are set once for the organisation and inherited by every location and person unless they choose their own. This page explains the cascade and where each setting is used.

The cascade

Level	Set where	Decides
Organisation	Settings → Administration → Organisation (owner)	The default everything else inherits. The currency product prices are in and, unless a location overrides it, the currency snapshotted onto receipts.
Location	Settings → Business → Locations	This site's operating day (time zone) and the currency receipts issued here are recorded in.
Person	Their own Profile, or an administrator under Users	The zone that person reads every date and time in, and the zone their report bounds and daily buckets use. People have no currency setting.

At every level the first row of the picker, Organisation Default, means inherit: change the organisation's setting and everyone who never chose their own moves with it.

Currency

Amounts are stored as whole numbers of the currency's smallest unit. A currency with no minor unit in circulation is treated as whole units, so 1,500 means exactly 1,500 and prices are typed as whole numbers. Most currencies have two decimal places.
Because the number of decimal places is part of what a stored amount means, the organisation cannot switch to a currency with different decimal places once any receipt or product exists. Switching between currencies with the same decimal places is allowed at any time.
Money is shown as the currency code followed by the amount, for example USD 1,500.00, or 1,500 after its code for a whole-unit currency.
Receipts snapshot their currency at issue (the issuing location's if it has one, else the organisation's). Later changes never restate an issued receipt.
Product prices are organisation figures. A location with its own currency does not convert them; the same numbers are simply recorded under the other code. Only set a location currency for a branch that genuinely prices in it.
Reports label money columns with the organisation currency and export amounts in major units.

Time Zones

Every timestamp is stored in UTC. A time zone only changes how it is displayed and which calendar day it falls on.
The app never uses the device's zone. It uses the signed-in person's zone, or the organisation's if they have none, so a tablet with the wrong region or a manager travelling abroad still sees the shop's times consistently.
A receipt belongs to the place that issued it: the times printed on it (issue, reprint, signatures) are in the issuing location's zone, or the organisation's when it names no location — never the reader's. On screen, outside the printed document, the reader's zone applies as everywhere else.
Report periods are inclusive bounds in the reader's zone. A bound with no time covers the whole day. The Daily Sales Summary buckets receipts into the reader's days, which keeps a 23:30 receipt on its own day.
A location's zone describes that site's operating day and is inherited from the organisation unless set.
The pickers list around 400 zones and can be searched by city, region or UTC offset. A few zones whose official name still uses an older city name are shown under the current name (Kolkata, Kyiv) and are searchable either way.

Where each setting is used

Feature	Currency	Time Zone
Receipts	Snapshotted at issue from the location or organisation.	On the printed document: the issuing location's zone, else the organisation's. On screen: the reader's zone.
Products	Prices in the organisation currency.	—
Inventory	—	"Last Adjusted" and the trail shown in the reader's zone.
Reports	Organisation currency in column labels.	Bounds and day buckets in the reader's zone; the zone is named on screen and in the export's About sheet.
Dashboard, lists	Each receipt in its own currency; products in the organisation's.	Reader's zone.