What HSR Compliance Really Requires
The KKR enforcement matter and the current DOJ and FTC materials answer the title's question in the same direction: HSR compliance is the alignment of a transaction's legal scope, its supporting evidence, its business data, its certification, and its submission record. The useful final judgment is not whether a team can complete a PDF. It is whether a reviewer could follow the filing from the deal that triggered it to the evidence that supports it, and whether the package remained current and usable when it reached the agencies.
Compliance is alignment across the whole evidence chain
A filing becomes reliable when its parts continue to describe the same transaction. That sounds simple, but each part comes from a different source of truth. The transaction team knows what the parties intend to acquire. The legal analysis identifies the filing persons, the acquisition structure, the applicable statutory row, and the effective date. Finance and operating teams know how revenue was generated and classified. Deal participants and advisers hold analyses and reports. The signatories connect the final package to a good-faith representation. The submission record shows what was actually transmitted.
The HSR materials do not call this an “alignment model”; that phrase is a useful synthesis. Its value is causal. Scope determines whose documents and business activity are relevant. The document search determines which analyses and reports can support the competitive account. Item 5 converts operating activity into NAICS and, for manufacturing, NAPCS revenue facts. Items 6 and 7 use those facts to test ownership relationships, associates, overlaps, and geography. The certification represents the package, while the filing channel and retained records preserve the version that agencies could inspect. A defect at one layer can change the meaning of a later layer.
For example, a wrong acquisition perimeter can make a revenue table look complete while excluding the assets actually being acquired or including an unrelated business. A correct perimeter paired with a poor document search can leave the filing without the analysis that explains how the parties viewed competition. A sound revenue table can still produce an incomplete overlap picture if minority holdings or relevant associates are absent. A substantively correct package can become difficult to review if its files are not searchable, if attachments cannot be connected to the Form, or if the team cannot establish which version was transmitted.
That is why “accepted” and “accurate” are different words. The Form Tip Sheet says its missing-mandatory-items list is only a guide and leaves responsibility for a complete and accurate filing with the filing party. The electronic-submission guidance requires separate searchable files, descriptive conventions, first-page identification, and no password protection, permission restrictions, zip files, or malware. Those controls make the package usable and traceable. They do not decide whether the UPE was correct, whether an Item 4 document was responsive, whether a revenue code was appropriate, or whether an associate belonged in the analysis.
The same distinction applies to the signature. An affidavit and certification are not substitutes for the work beneath them. The instructions require attestations tied to good faith and, depending on transaction type, to an executed agreement or other transaction posture. They permit estimates when exact answers cannot be supplied, but require a source or basis and a visible “est.” qualification. A signature can make those judgments accountable; it cannot make an unsupported number exact or transform a silent omission into a disclosed limitation.
The complete relationship looks like this:
The loop matters because compliance is not frozen at the moment a team first fills a field.