About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.
Direct answer: Store instants in UTC (or offset-aware timestamps), resolve display and business rules using each tenant’s configured IANA or Windows time zone and financial calendar (period length, year-end, 4-4-5 variants where used), and never assume “Australia = Sydney” for every customer on a shared hosted application tier.
Why it matters
Australian customers span AWST, ACST, ACDT, AEST and AEDT. Queensland, the Northern Territory and Western Australia do not observe daylight saving; southern states shift to daylight time in summer—border and scheduling mistakes are common (editorial risk note). Payroll cut-offs, rostered jobs, interest accrual and statutory reporting depend on local midnight, not the host server’s default zone.
When many customers share one hosted ISV release, a single mis-set default time zone produces off-by-one-day reports, duplicate scheduled tasks after DST jumps, and reconciliation nightmares finance teams blame on “the cloud.” This is multi-tenant calendar design, not tuning a single Windows Server clock—that server-level topic is a different article.
How it works
Layers to separate
- Infrastructure time — hosts synchronised via NTP (UTC). Operators care; tenants should not inherit this for business logic.
- Tenant default time zone — chosen at onboarding; drives UI dates, “today” filters, business-day calculations.
- User override — field staff in Perth viewing Sydney-HQ reports may need explicit zone pickers.
- Financial calendar — fiscal year start, period numbering, locked periods, public holiday tables (state-level where relevant).
Scheduling jobs
Background tasks (statement runs, reminders, integrations) should read tenant context when computing “run at 02:00 local.” Cron expressions tied only to server local time are a defect in multi-customer hosting. DST transitions need tests: the skipped and repeated local hours must not double-charge or skip accrual.
Reporting boundaries
“Month to date” must use the tenant’s zone at generation time. Cross-tenant admin dashboards that aggregate counts should label the zone or normalise to UTC with footnotes.
Australian specifics
- Document which public holiday set applies (national + state).
- For groups with NZ operations, treat as separate calendar objects—not a single “Australasia” fudge.
- Financial year 1 July – 30 June is common but not universal; capture in tenant metadata.
Event stored (UTC) → render with tenant TZ → business rule "end of local business day" uses tenant calendar
What to choose and why
| Decision | Recommendation | Why |
|---|---|---|
| Storage | UTC + zone id | Unambiguous audit |
| Default on signup | Ask explicitly | No silent Sydney |
| Holidays | Per-state table where needed | Labour Day dates differ |
| Franchise groups | Parent template, child override | Sites span zones |
Document per-tenant defaults in the customer record your CS team can see during support calls.
Read next
Related articles you may want next.
- HostingTelling end customers about planned maintenance on a hosted ISV serviceGive customers clear maintenance notices with local times, expected impact, preparation steps and completion updates, including a practical path for urgent security work.Read article
- HostingFranchise and multi-company groups on one hosted ISV platformDesign access and data boundaries for franchise and multi-company customers, including group reporting, site permissions and changes in ownership.Read article
- HostingChoosing pilot users inside the customer's organisation before full go-liveChoose pilot users who reflect your customers’ real workflows, agree measurable acceptance criteria and use the results to decide when wider rollout is ready.Read article
Risks and limits
- Legacy columns storing local time without offset cannot be migrated casually—plan conversion projects.
- Integrations sending naive timestamps force guessing; prefer ISO-8601 with offset.
- Historical rule changes (government DST experiments) are rare but libraries must be patched.
- Not validated against a specific database or scheduler product in lab.
Sources
- IANA Time Zone Database — IANA; accessed 2026-11-16 — authoritative zone identifiers (
Australia/Sydney,Australia/Perth, etc.). - About daylight saving — NSW Government; accessed 2026-11-16 — southern-state daylight-saving dates; notes QLD, WA and NT do not observe DST.
Related reading
- Franchise and multi-company groups on one hosted ISV platform
- Choosing pilot users inside the customer's organisation before full go-live
- Telling end customers about planned maintenance on a hosted ISV service
- Software vendor hosting (related service context)
Learning notes
- Server time zone is for operators; tenant time zone is for business logic.
- UTC storage prevents silent ambiguity.
- DST weeks deserve automated regression tests.
- State public holidays belong in configuration, not constants in code.
- Ask every new customer their zone and fiscal year—do not guess Sydney.
This article was originally published on .