Vendor Doing as Business Name

Human-readable name of the vendor's operating or trade business name in the IDV record. This is the label used to identify the business under which the vendor is conducting business, and it may differ from the legal entity name or legal registration name.

Family: IDV
Category: Vendor Header
Data Type: string
Semantic Type: label
Mapping: flattened_fpds_xml_field
AI Confidence: high

Variable Overview

FPDS Query Variable
content__IDV__vendor__vendorHeader__vendorDoingAsBusinessName
Title
Vendor Doing as Business Name
FPDS Path
IDV/vendor/vendorHeader/vendorDoingAsBusinessName
Description
Human-readable name of the vendor's operating or trade business name in the IDV record. This is the label used to identify the business under which the vendor is conducting business, and it may differ from the legal entity name or legal registration name.
Business Meaning
This field helps analysts recognize the contractor as it appears in procurement records, especially when the legal name and operating name differ. It is useful for vendor normalization, market concentration analysis, and matching awards to publicly known brand or trade names.
Example Value
CES/WAY INTERNATIONAL INCORPORATED
Observed Non-Null Count
272,457

FPDS Compare

FPDS Query Variable
content__IDV__vendor__vendorHeader__vendorDoingAsBusinessName
FPDS XML Path
IDV/vendor/vendorHeader/vendorDoingAsBusinessName
Mapping Type
flattened_fpds_xml_field
Comparison Summary
FPDS Query flattens the original nested FPDS XML path 'IDV/vendor/vendorHeader/vendorDoingAsBusinessName' into the SQL-ready variable 'content__IDV__vendor__vendorHeader__vendorDoingAsBusinessName'.

Use Cases

  • Dictionary lookup and field explanation
  • SQL filtering and grouping
  • Analytical reporting and reusable query building
  • Contractor profiling and competitor analysis

Common Usage

  • Display the vendor's trade or operating name in reports
  • Support vendor matching when legal and doing-business names differ
  • Review name variations during entity cleanup and normalization

Common Mistakes

  • Using the field as a unique key for vendor joins
  • Assuming it always matches the legal entity name

Query Guidance

Select and group by this field only when you want the visible vendor name. For entity-level analysis, join on vendor identifiers and use this field as a label; if multiple name fields exist, inspect both legal and doing-business values to resolve abbreviations or alternate spellings.

SQL Examples

Preview values

SELECT
    content__IDV__vendor__vendorHeader__vendorDoingAsBusinessName AS vendor_doing_as_business_name
FROM fpds.data
WHERE content__IDV__vendor__vendorHeader__vendorDoingAsBusinessName IS NOT NULL
LIMIT 25

Top values

SELECT
    content__IDV__vendor__vendorHeader__vendorDoingAsBusinessName AS value,
    count() AS record_count
FROM fpds.data
WHERE content__IDV__vendor__vendorHeader__vendorDoingAsBusinessName IS NOT NULL
GROUP BY value
ORDER BY record_count DESC
LIMIT 25

Each dictionary item includes SQL-ready examples generated alongside the variable metadata, allowing immediate use in FPDS Query for filtering, aggregation, and analysis.