Localization & Formats

Money and dates in AccessPoint follow your jurisdiction, not a hardcoded convention. This panel holds the five tenant-wide settings that decide how they are presented: the default currency, an optional date-format override, the fiscal-year start month, the organization's English spelling and its time zone.

Where to Find It

Open Settings from the app toolbar and choose Localization & formats.

Settings Reference

Currency

Each fee schedule — that is, each requestor category — states the ISO currency its rates are in. Jurisdiction packs ship this, so importing the UK pack gives you £ fee schedules and the Canadian pack gives CA$ ones, side by side in the same tenant. The tenant default set here covers everything else, and it is seeded automatically from your first jurisdiction pack.

Amounts are never converted between currencies. The code only controls display: a rate recorded as 25 in a £ schedule is £25, and nothing in AccessPoint restates it as anything else. If your office genuinely charges in two currencies, that is a matter of two fee schedules, not an exchange rate.

Dates

By default, dates follow the selected interface language, so each user reads them in the convention their language expects. An administrator can override that by pinning a house format here — ISO, day/month/year, month/day/year, or long form — when the office wants one convention everywhere regardless of who is looking.

Two things behave deliberately differently:

• Generated letters render dates long-form in the letter's own language ("7 August 2026" / "7 août 2026") unless a format is pinned. A letter is a document a person reads, so it reads naturally in their language.
• Evidence packages and audit exports always use ISO dates, whatever is set here. They are verification artifacts, and an unambiguous date is part of what makes them verifiable.

English Spelling

English is one language in AccessPoint; how it is spelled is a setting of your organization:

• United States — color, license, organization (the default).
• Canada — colour, licence, organization.
• United Kingdom — colour, licence, organisation, programme.

It applies to everyone who uses AccessPoint in English: every screen, the headings and labels of the documents and reports AccessPoint produces, its messages, and the English the AI features write. With the Automatic date format, English dates follow it too — 2026-10-07 in Canada, 07/10/2026 in the United Kingdom, 10/7/2026 in the United States — and British English letters write dates day first (7 October 2026). It never changes another language, a language code, or text people wrote.

Jurisdiction packs set it when nobody has chosen one: a Canadian pack sets Canada; a UK, Irish, Australian, New Zealand, Indian or South African pack sets United Kingdom; a US pack sets United States. Whatever you save here always wins.

The Universal baseline pack, which every organization shares, arrives in your spelling. After you change the spelling, re-apply the Universal baseline (Settings > Jurisdiction packs, Add and update) to respell its names, descriptions and guidance — items you edited stay exactly as you wrote them. Reload the page after saving to see the new spelling everywhere.

Time Zone

The organization's time zone is the calendar every statutory due date is computed in. When it is set, a request's due date is counted from its received day in that time zone, whoever or whatever triggers the calculation: an officer in another province or state, an approver abroad, or AccessPoint itself releasing an intake hold or recording a payment overnight all get the same date. A received date picked by someone east of the organization's time zone keeps the day they picked.

When it is Not set (the default), each calculation runs in the time zone of the person who triggers it, and background work reuses the zone of the last person who did. Set it when your team works across time zones, and when a law in your jurisdiction changes on a date: settings that change on a date — exemptions, extension reasons, fees and mandatory assessments — are judged on a request's received date in this time zone.

Jurisdiction packs do not set it, with one exception: applying the Nova Scotia pack in an organization that has never set a time zone and has only Nova Scotia packs sets it to America/Halifax (recorded in the audit log as the pack import's change), so from then on every due date, "today" and displayed due day is computed on Halifax days. Change it here at any time.

Changing the setting does not rewrite due dates already stored: each request moves to the new time zone at its next deadline change (an extension, a clock pause or a received-date correction), and How this date was calculated shows the difference until then.

Calendar Days Follow the User

Received dates, statutory due dates, correspondence-log dates, and every "today" comparison — overdue, days remaining, My Day, relative report ranges — follow the user's local calendar, not the server's. A request created at 10:11 p.m. is received that day and its clock starts from that day, even when it is already tomorrow in UTC, so an evening intake never loses or gains a day against the statutory deadline. This is automatic and needs no configuration: the web part sends the browser's time zone with every call. When your organization sets a time zone (above), statutory due dates follow the organization's calendar instead. Timestamps are still stored as UTC instants, which is what evidence packages and audit exports show.

Fiscal Year

The fiscal-year start month drives two things: FY-style case numbering and the periods used by fiscal reports. Jurisdiction packs seed it, so an imported pack usually gets it right for your jurisdiction without intervention.

Changing it mid-year only affects the year label on new case numbers. Numbers already issued are untouched — a case number is an identifier that has already been quoted in correspondence, so AccessPoint will not retroactively relabel it.

Tips

• Import a jurisdiction pack first: it seeds the default currency, the fee-schedule currencies, and the fiscal-year start month for you, and you adjust from there.
• Set the organization's time zone if your team works across time zones, or a law in your jurisdiction changes on a date, so every due date and every dated rule is counted the same way.
• Leave the date format unset unless you have a reason to pin one — following the interface language is usually what multilingual offices want.
• Set the fiscal-year start month before you begin issuing FY-style case numbers, so a single fiscal year's numbering stays internally consistent.

Related Pages

• Jurisdiction Packs — what seeds the default currency, the per-schedule currencies, and the fiscal-year start month.
• System Languages — the active languages that dates follow when no house format is pinned.
• Calendars — the other half of date handling: which days count as business days for due-date math.
• Numbering Configuration — the case-number pattern the fiscal-year start month supplies the year label to.
• Requestor Categories — the fee schedules that each state their own ISO currency.