Skip to content
KiweelyKiweelyKiweely

Workday Preferred Display Language vs Preferred Locale: what each one changes, and why self-service items disappear

Preferred Display Language sets the language of Workday labels and notifications; Preferred Locale sets date, time and number formats. Country fields follow the business site location, not either one. Sign out and back in after changing language.

  • Checked against Workday on
  • Applies to Workday Localization & Translations
  • 6 min read
  • Published
  • By Kiweely
On this page

Workday separates Locale (how dates, times, and numbers format on screen) from Display Language (which language renders for UI labels, business process notifications, and translated tenanted objects), while anchoring localized data structures (such as address fields and government ID formats) to the business site Location country rather than user preferences. Understanding how those three layers interact—and how Workday walks its six-step fallback hierarchy—prevents missing self-service items, inverted DD/MM vs. MM/DD dates, and broken API parsing.

The Three Separate Localization Controls in Workday

Administrators and integration engineers frequently conflate Locale, Language, and Country Localization. In Workday (Concept: Country-Specific Information, Locales, and Languages), each governs a distinct concern:

Control Layer Where Admins Configure It Where Users Override It What It Changes (and What It Never Changes)
Control LayerLocale (Preferred Locale) Where Admins Configure ItEdit Tenant Setup - System (Default Locale) and Edit Location (business site locale) Where Users Override ItChange Preferences (Change My Account Preferences) -> Preferred Locale What It Changes (and What It Never Changes)Formats dates (11/15/2026 in US vs. 15/11/2026 in UK), clock notation, and number separators (1,234.56 vs. 1.234,56). Never changes country-specific HR compliance fields.
Control LayerDisplay Language (Preferred Display Language) Where Admins Configure ItEdit Tenant Setup - System (Preferred Display Language) and Edit Tenant Setup - Global (Enabled languages) Where Users Override ItChange Preferences -> Preferred Display Language (requires sign-out and sign-in) What It Changes (and What It Never Changes)Controls delivered Workday UI text, business process notifications, Maintain Non-English Custom Labels overrides, and translated tenanted object attributes.
Control LayerLocalized Country Fields Where Admins Configure ItEdit Tenant Setup - Global, Maintain Localization Settings, Maintain Address Components by Country Where Users Override ItNot user-overridable in account preferences What It Changes (and What It Never Changes)Driven by the business site location (or the country of the address/ID record). Controls extended address fields (separate House Number and Street Name), local script names, and statutory fields.

Workday’s Six-Step Display Language Resolution Order

When a worker signs in or receives a business process notification, Workday evaluates six settings in strict top-down precedence to choose the active display language (Concept: Country-Specific Information, Locales, and Languages):

  1. User’s selected Preferred Display Language (set via Change Preferences or on the Workday Account).
  2. User’s selected Preferred Locale (if mapped as a default locale for an Enabled Workday-supported language on Edit Tenant Setup - Global).
  3. Selected language of the user’s primary Business Site Location (Edit Location).
  4. Selected locale of the user’s primary Business Site Location (if associated with an enabled Workday-supported language; if no locale is set on the location, it inherits the tenant’s Default Locale).
  5. Selected Preferred Display Language of the tenant (Edit Tenant Setup - System).
  6. Selected Default Locale of the tenant (default is US English; if a resolved locale is not associated with an enabled Workday-supported language, Workday falls back to English).

[!IMPORTANT] Tenant-Wide Impact When Enabling a Language on Edit Tenant Setup - Global Checking Enabled next to a Workday-supported language (such as Spanish, French (Canada), or German) in Edit Tenant Setup - Global immediately flips the default display language for all users whose inherited or selected locales map to that language—unless those users explicitly set Preferred Display Language back to English via Change Preferences. You can also enable non-Workday-supported languages solely to translate tenanted business data for payroll or outbound integrations without changing the Workday UI.

Base Languages, Translatable Objects, and Allow Mixed-Language Transactions

Delivering a clean non-English self-service experience inside native Workday requires distinguishing Workday-delivered UI metadata from customer-created business objects (Concept: Translations and Steps: Manage Translations):

1. Every Object Has a Base Language (and Edits Can Reset Translations)

  • For Workday-delivered objects, the Base Language is the default tenant language (almost always English).
  • For user-created objects—such as a Job Requisition or Job Profile—the Base Language is the Preferred Display Language of the user who created that instance! If a hiring manager signed in with French creates a Job Requisition, its base language is French (Base Languages report, secured to the Data Translation domain in the System functional area).
  • When someone later changes the base-language text of a translated attribute, existing translations can reset or hide (if Hide Translation after Base Value Change is checked on Edit Tenant Setup - Global). Audit stale translations regularly with the Translation Base Value Change Audit report or the Translated Data with Base Value Changes report data source.

2. Why Items Disappear in Self-Service (Allow Mixed-Language Transactions)

When a general worker switches Preferred Display Language to a non-English language, Workday only displays items that have been translated into that language on employee self-service (ESS) and manager self-service (MSS) views—unless Allow Mixed-Language Transactions is enabled on their account:

  • Administrators enable Allow Mixed-Language Transactions per user on Edit Workday Account, in bulk on Manage Workday Accounts, or automatically on the Create Workday Account service step inside the Hire business process.
  • Workday’s Guidance: Enable Allow Mixed-Language Transactions for administrators, HR Partners, and translators (Custom Label Management for Non-English domain) who must access untranslated setup tasks—not as a shortcut for general employees, where half-English, half-translated menus cause errors.
  • Instead, run the Translation Status for User Language report and use Translations Hub, Translate Business Object (with an Effective as of date for effective-dated snapshots), or the inline globe icon (In-Context Translation widget, Data Translation: In-Context Translation domain) to translate every self-service Time Off Plan Display Name, Absence Reason, Custom Report (Translate Custom Reports), and Onboarding checklist label.

3. Overriding Workday’s Delivered Non-English Terms

If Workday’s delivered translation conflicts with regional company terminology—for example, replacing the delivered German term Urlaub with Abwesenheit across the Home page and Absence views—use Maintain Non-English Custom Labels and Maintain Non-English Custom Label Overrides (Custom Label Management for Non-English domain). Remember that custom labels start Disabled by default until you clear the Disabled checkbox and let the background preparation process complete.

How APIs Handle User Language, Locale, and Dates

When building external integrations, custom portals, or AI tools under a worker’s OAuth 2.0 session, observe four protocol rules so locale formatting never corrupts data:

  1. Discover the Signed-In User’s Preferences (userInfo/v1): Call GET /ccx/api/common/v1/{tenant}/userInfo (or the userInfo endpoint, secured by System Account as Self in the System scope) to read the authenticated user’s exact language, locale, timezone, currency, fullName, and workerID:
json
{
  "data": [
    {
      "workerID": "3aa5550b7fe348b98d7b5741afc65534",
      "userName": "mgarcia",
      "fullName": "Mateo Garcia",
      "language": "es",
      "locale": "en_US",
      "timezone": "America/Chicago",
      "currency": "USD"
    }
  ],
  "total": 1
}
  1. Wire Dates and Numbers Are Always Locale-Neutral ISO Formats: Regardless of whether a worker’s Preferred Locale formats UI dates as 15/11/2026 (en_GB / es_MX) or 11/15/2026 (en_US), Workday REST (yyyy-mm-dd), WQL (YYYY-MM-DD), and SOAP (xsd:date) payloads always transmit ISO-8601 dates and dot-decimal numbers (8.5, never "8,5"). Format dates for human display at the presentation layer using locale from /userInfo, and serialize back to ISO-8601 before calling Workday.
  2. Translated descriptor Strings Follow the Issuing Account’s Language: In user-delegated OAuth calls (REST, WQL, and JSON RaaS), object descriptor fields (such as a Time Off Type or Supervisory Organization name) resolve in the authenticated user’s configured Workday display language whenever a tenanted translation exists, falling back to the object’s base language.
  3. Exporting/Importing Translations via SOAP (Metadata_Translations): For automated localization pipelines, Workday provides the Metadata_Translations and Put Non-English Custom Labels / Get Non-English Custom Label Overrides web services alongside EIB spreadsheets.

Verification Checklist for Multilingual Self-Service

  1. Check Edit Tenant Setup - System and Edit Tenant Setup - Global to confirm which languages are checked Enabled and which locales map to them.
  2. Inspect representative business sites on Edit Location to verify inherited worker locales.
  3. Run Translation Status for User Language and Translation Base Value Change Audit before each semi-annual release or policy update.
  4. Sign in as a test worker in Sandbox, run Change Preferences, sign out, and sign back in to verify zero missing self-service items when Allow Mixed-Language Transactions is unchecked.

When organizations want multilingual frontline or employee self-service screens without running a tenant-wide language cutover, Kiweely Leaf (coming next) renders custom screens in your workers’ languages over standard Workday APIs, while Kiweely Bridge (coming next) lets employees ask Workday questions in their own language inside Claude, ChatGPT, and Gemini under their own Workday permissions.

Frequently asked questions

What is the difference between Preferred Locale and Preferred Display Language in Workday?

Preferred Locale controls how Workday formats dates (MM/DD/YYYY vs. DD/MM/YYYY), 12-hour vs. 24-hour times, and decimal/thousands separators, whereas Preferred Display Language controls the language of Workday UI labels, notifications, and translated business objects.

Why do Country-Specific Personal Information and Address fields stay in US format when a worker changes Locale to UK or Germany?

Workday determines localized country-specific fields (such as National ID types, Extended Address Formats, or local termination reasons) from the associated business site location or target country—not from the user's Preferred Locale.

Why did an employee stop seeing certain customer-created items after changing Preferred Display Language?

On employee and manager self-service views, Workday displays only items that have been translated into the user's Preferred Display Language unless Allow Mixed-Language Transactions is enabled on the user's Workday Account.

Why do newly saved translations not appear immediately before signing out?

After changing Preferred Display Language in Change Preferences, a user must sign out of Workday and sign back in to reload session-cached UI metadata and translated business data.

Sources checked

Related guides

All guides

Let Workday check the work.

Kiweely writes WQL and builds orchestrations in your own tenant, and Workday, not Kiweely, says whether they passed.

Get the next guide in your inbox.

One email a month with new guides and one Extend tip. Nothing else.

We’ll email you once to confirm. Unsubscribe in one click from any issue.