Bloomberg Terminal

The Bloomberg Terminal is a subscription-based professional financial-information platform that combines market data, news, research, analytics, communication, and trading-workflow tools. It helps users find and analyze information, but a Terminal screen is not automatically the original source, an executable market price, or proof that a transaction occurred.

Access depends on the subscriber’s products, exchange entitlements, data licenses, permissions, and integrations. Two users can therefore see different fields, delays, research, or execution capabilities.

Key Takeaways

• The Terminal integrates information and workflow; it is not itself a stock exchange or universal source of record.
• Data can come from exchanges, issuers, regulators, contributors, models, Bloomberg calculations, or third parties.
• A field should be recorded with its security identifier, source, timestamp, currency, unit, and methodology.
• Quotes, evaluated prices, consensus estimates, and executed prices answer different questions.
• Trading and order-management functions require specific connections and permissions; viewing a security does not imply execution access.
• Contract terms govern data use, exports, derived data, sharing, and redistribution.

What the Terminal Provides

Bloomberg’s official Terminal product page describes coverage across markets, companies, industries, and asset classes, together with data, analytics, research, news, collaboration, portfolio tools, and execution workflows.

The exact product set changes over time. Users should consult their current agreement and enabled services rather than assuming that every advertised capability is included in every subscription.

Data Screen vs. Source Record

A Terminal can make a source easier to find without replacing it. For a material decision, identify which layer produced the number:

1. Primary record: exchange message, issuer filing, regulator publication, prospectus, contract, or economic release.
2. Vendor normalization: identifiers, field mapping, currency conversion, corporate-action adjustment, or standardized financial statement.
3. Contributor or estimate: broker quote, analyst forecast, consensus, evaluated price, or third-party research.
4. User analysis: custom formula, spreadsheet link, screen, chart, filter, portfolio rule, or scenario.

The layers can be useful together, but they are not equally authoritative. A normalized revenue field may differ from the filed line item because the vendor maps classifications or adjusts periods. A consensus figure is an aggregation of forecasts, not reported company performance.

Worked Example: Reviewing a Bond Screen

Assume an analyst uses the Terminal to compare two corporate bonds. One screen shows a yield of 5.42% for Bond A and 5.58% for Bond B. It would be premature to conclude that Bond B offers 16 basis points of additional compensation.

The analyst should first verify:

• the issuer, exact security, ISIN or other identifier, coupon, maturity, and currency;
• whether the price is a live executable quote, delayed trade, composite, evaluated price, or user input;
• the yield convention, settlement date, day-count basis, call assumption, and accrued interest treatment;
• trade size, bid or ask side, market depth, and timestamp;
• credit rating source, seniority, guarantees, covenants, and current filings; and
• whether either bond is callable, putable, convertible, illiquid, or in default.

After aligning those inputs, the analyst can calculate a comparable spread or yield measure and retain the screen or export with the source details. The Terminal accelerates the workflow; it does not remove the need to define the instrument and calculation.

Terminal, Data Feed, Spreadsheet, and Venue

Common Mistakes

• Copying a screen value without its field definition, source, currency, unit, or timestamp.
• Treating an indicative quote or evaluated price as a completed transaction.
• Comparing securities whose yields, maturities, currencies, or settlement conventions differ.
• Treating consensus estimates as audited or filed results.
• Using a ticker without confirming the venue and security identifier.
• Assuming a spreadsheet refresh corrected stale formulas, overrides, or broken links.
• Sharing screenshots or exports without checking contractual licensing and compliance rules.
• Describing a proprietary score or model output as an objective fact.

How to Evaluate Terminal Evidence

For each decision-relevant figure, record:

• the security or entity and a stable identifier;
• the function, field, dataset, contributor, or primary source;
• the observation and retrieval timestamps;
• currency, scale, units, price side, and market status;
• methodology, adjustment, and calculation conventions;
• any user override, custom formula, or spreadsheet transformation; and
• the document, order, fill, or ledger record used for independent confirmation.

Critical legal, tax, accounting, regulatory, and transaction conclusions should be checked against the governing document or authority source. Data-provider access does not replace professional judgment or advice.

Related Terms

• Market Data: Quotes, trades, reference fields, and other observations whose source and timing must be identified.
• Ticker Symbol: Short market identifier that is incomplete without venue and instrument context.
• Bloomberg: The financial-information and media company that provides the Terminal.
• S&P Capital IQ: Financial-data and research platform with overlapping but separately licensed datasets and workflows.
• Investment Banking: One professional context in which market, issuer, and transaction data are analyzed.

FAQs

This page is educational and does not endorse a data provider or provide investment, trading, legal, tax, accounting, or compliance advice.