Company Information
Company Information is the Salesforce Setup page that holds the org's identity and global configuration: organization name, primary contact, default time zone, currency, locale, language, fiscal year settings, edition, user license counts, used storage, API request counts, and the Organization ID.
Definition
Company Information is the Salesforce Setup page that holds the org's identity and global configuration: organization name, primary contact, default time zone, currency, locale, language, fiscal year settings, edition, user license counts, used storage, API request counts, and the Organization ID. It is the org's identity card; the values here cascade to nearly every other feature (currency defaults on Opportunities, time zone defaults on scheduled jobs, fiscal year boundaries on reports and forecasts).
Company Information is one of the least-edited Setup pages but holds some of the most consequential settings. Changing the default currency, the time zone, the fiscal year start, or the multi-currency toggle is rare but high-impact when it happens; the change ripples through historical data, reports, dashboards, and any automation that depends on date or currency math. Most orgs configure this page at go-live and never revisit; the maintenance audit is more about confirming the values still match reality than about active editing.
Why Company Information holds the highest-leverage one-time settings in the org
Where Company Information lives and what it contains
Setup, Company Settings, Company Information. The page shows organization identity (name, primary contact, division), regional settings (default time zone, currency, locale, language), fiscal year configuration (start month, custom vs standard fiscal year), edition and license counts (Sales Cloud Enterprise, Service Cloud Unlimited, plus add-ons), storage usage (data storage, file storage), API usage (requests in the last 24 hours), and the Organization ID (the unique identifier for the org used in support tickets and integrations).
Default time zone and the cascading effect
The default time zone in Company Information drives time-sensitive behavior across the platform: scheduled Apex jobs use it as their reference time zone, reports group time-based fields by it, Business Hours interpret schedules in it. Individual users can override their personal time zone preference, but the org-wide default applies to anything that runs in system context (scheduled jobs, Flow on schedule, batch jobs). Setting the default to the wrong time zone is the kind of issue that produces "the report is off by 12 hours" tickets weeks after go-live.
Default currency and the multi-currency decision
The default currency is the corporate currency, the base for all conversions when multi-currency is enabled. Multi-currency is a separate org-wide setting that enables per-record currency selection and exchange rates; once enabled, it cannot be disabled. The default currency is the conversion base, used in roll-up summaries and forecasting. Most US orgs default to USD; multinational orgs default to USD or EUR and enable multi-currency for regional deals. Changing the default currency post-go-live is significant; existing records keep their currency values and conversions recompute against the new base.
Fiscal year configuration: standard vs custom
Fiscal year tells Salesforce when the year starts and how to group quarterly reporting. Standard fiscal year uses calendar quarters (Q1 = Jan-Mar). Custom fiscal year supports non-calendar fiscal years (Q1 starts in April, August, October, etc.) and even 4-5-4 retail calendars. Most orgs use standard; retail, government, and academic orgs often need custom. Enabling custom fiscal year is one-way; once on, it cannot be reverted to standard. Plan deliberately at go-live and document the configuration; mid-life changes are operationally heavy.
Locale, language, and the user-experience cascade
Default locale drives date format (MM/DD/YYYY vs DD/MM/YYYY), number format (1,000.00 vs 1.000,00), name format (First Last vs Last First). Default language drives the platform UI language for users who have not personally selected one. Individual users override per their preference. The defaults matter for users who never customize, which on most orgs is a significant fraction. Multinational orgs often default to en_US for the platform language plus a tolerant locale and let regional users override.
License counts, edition, and the usage signal
The User Licenses section shows total and used counts per license type (Salesforce, Salesforce Platform, Customer Community Plus, etc.). Approaching the cap on a license type is a procurement signal; the org needs to buy more or deactivate unused users. The Permission Set Licenses section shows the same for the granular permission set licenses. Reading this page quarterly catches license-creep before it becomes an emergency procurement situation. The Organization ID near the top is the unique identifier used in Salesforce support tickets and integrations; copy it from here when needed.
Storage usage and the cleanup signal
Data Storage and File Storage usage show how close the org is to its storage allocation. Data Storage counts records (per-object allocation; standard objects use varying amounts). File Storage counts uploaded files and attachments. Approaching the cap triggers cleanup decisions: archive old data, delete unused files, evaluate Big Objects for cold storage. Most orgs hit storage caps from accumulated activity records and attachments rather than from primary business records. The page is the visibility surface; the cleanup work happens through data archival projects.
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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
The org's reference time zone. Cascades to scheduled jobs and system-context automation.
The corporate currency. Conversion base for multi-currency orgs.
One-way toggle that enables per-record currency selection. Enable deliberately.
Standard (calendar) or custom (non-calendar). Custom is one-way once enabled.
Date and number formats, default UI language. Per-user override available.
- 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.
Trust & references
Cross-checked against the following references.
- Company Information referenceSalesforce
- Administrator overviewSalesforce
Straight from the source - Salesforce's reference material on Company Information.
- Company InformationSalesforce Help
- Fiscal YearSalesforce Help
- Multiple CurrenciesSalesforce Help
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. What is the primary benefit of Company Information for Salesforce administrators?
Q2. Why is understanding Company Information important for Salesforce admins?
Q3. In which area of Salesforce would you typically find Company Information?
Discussion
Loading discussion…