Salesforce Dictionary - Free Salesforce GlossarySalesforce Dictionary
Full Company Information entry
How-to guide

How to audit Company Information for an established org

The pattern: audit annually rather than edit. Most Company Information settings should not change after go-live; the audit confirms the original choices still match reality and surfaces usage signals (license, storage) that drive procurement and data lifecycle decisions.

By Dipojjal Chakrabarti · Founder & Editor, Salesforce DictionaryLast updated May 18, 2026

The pattern: audit annually rather than edit. Most Company Information settings should not change after go-live; the audit confirms the original choices still match reality and surfaces usage signals (license, storage) that drive procurement and data lifecycle decisions.

  1. Schedule the annual Company Information review

    Add to the admin calendar. Once per year is sufficient for most orgs; faster cadence for high-growth orgs hitting license or storage limits.

  2. Confirm default time zone matches the org's primary operating region

    The default cascades to scheduled jobs and system-context automation. Misalignment is the most common Company Information mistake.

  3. Verify default currency and multi-currency status

    For multinational orgs, multi-currency should be enabled. For single-currency orgs, the default should match the corporate currency. Changes are heavy; verify rather than edit.

  4. Confirm fiscal year configuration matches finance

    Standard for calendar-year orgs, custom for non-calendar. Coordinate with the finance team before any change; mid-year changes cause report disruptions.

  5. Review license usage against allocations

    Approaching cap on Salesforce User license, Customer Community license, or Permission Set Licenses signals procurement need. Catch the trend before the cap.

  6. Review storage usage and trigger cleanup if over 70 percent

    Data storage growth is gradual but compounds. Cleanup at 70 percent prevents the urgent 95 percent panic.

  7. Document the Organization ID for support and integration use

    The 15-character Organization ID is the unique identifier used in support tickets, federation IDs, and integration debugging. Save it where the support and integration teams can find it.

Default time zoneremember

The org's reference time zone. Cascades to scheduled jobs and system-context automation.

Default currencyremember

The corporate currency. Conversion base for multi-currency orgs.

Multi-currencyremember

One-way toggle that enables per-record currency selection. Enable deliberately.

Fiscal yearremember

Standard (calendar) or custom (non-calendar). Custom is one-way once enabled.

Default locale and languageremember

Date and number formats, default UI language. Per-user override available.

Gotchas
  • Default time zone mismatch is the most common Company Information mistake. Set to the org's primary operating region, not the admin's location.
  • Multi-currency and custom fiscal year are one-way toggles. Enable deliberately; reverting requires Salesforce engagement and is operationally heavy.
  • Changing the default currency post-go-live recomputes conversions across historical data. Plan the change as a major event.
  • License caps surprise teams that do not monitor. Check usage quarterly; procurement lead time can be weeks.
  • Data storage growth is gradual. The 95 percent panic is the symptom of skipped quarterly reviews; the 70 percent trigger prevents it.

See the full Company Information entry

Company Information includes the definition, worked example, deep dive, related terms, and a quiz.