From Ledgers to Market Overlaps: The Data Model Behind Items 5–7
The HSR Form's competitive picture begins in places that do not look like antitrust documents: revenue ledgers, product classifications, ownership schedules, and establishment records. This chapter follows those inputs into Items 5 through 7, with the KKR matter as the reason to care about the links. The practical goal is to understand why an apparently polished filing can still be unreliable when its codes, control map, or geographic facts do not reconcile.
Item 5 turns operating activity into comparable revenue facts
Item 5 is not a request for a single revenue total. It asks each filing person to describe dollar revenues for the most recent year using the 2017 North American Industry Classification System, or NAICS, at the six-digit industry level. For manufacturing operations in NAICS Sectors 31–33, the filer must also report products using ten-digit codes from the North American Product Classification System, or NAPCS. The two classification systems do different jobs: NAICS identifies the industry activity, while NAPCS provides a more detailed product view within manufacturing.
That distinction creates a dependency. A manufacturing filer cannot treat the ten-digit product table as an independent appendix. The PNO's guidance says the NAPCS revenue should equal the revenue reported for the associated six-digit NAICS code. The codes are listed in ascending order, and the NAPCS codes appear under the associated manufacturing NAICS code. If those amounts do not reconcile, the problem is not cosmetic. The agency would be receiving two different accounts of the same operating activity.
The overlap boxes make the reporting levels equally important but not interchangeable. If two parties overlap at a six-digit NAICS code but not at a ten-digit product code, the filer checks the overlap for the six-digit code only. If they overlap at a ten-digit NAPCS code, the filer checks both that product code and its associated six-digit NAICS code. Thus, a product-level difference does not automatically eliminate an industry-level overlap. The filing preserves both facts so the agencies can decide what the distinction means in context.
The most-recent-year rule also requires a defined time basis. The instructions say that “year” ordinarily means calendar year, or the fiscal period that most nearly corresponds when calendar-year data are unavailable. If the latest data have not been compiled, the Form permits estimates of revenues by the required codes. But an estimate is not a license to hide uncertainty. The filing must identify the basis of the estimate and mark the relevant item accordingly. For non-manufacturing codes in Item 5(a), a code with less than $1 million in revenue for the most recent year may be omitted; that limited omission should not be generalized to manufacturing data or to later overlap analysis.
Geography enters before Item 7's geographic section. The instructions ask for dollar revenues connected to operations conducted within the United States, and for products manufactured outside the United States and sold into the United States. The PNO guidance then works through different paths for those sales. A product manufactured in the United States is reported under its manufacturing code even if it is sold through another establishment. A foreign-manufactured product delivered into the United States is reported using the U.S. revenue: a sale to a controlled U.S. entity can be reported at a reasonably obtainable transfer price, while a sale to a non-controlled U.S. entity or a direct U.S. purchase uses the wholesale or retail price.