The bill directs the Director of the Bureau of Justice Statistics to establish a Corporate Crime Database by adding a new section to the Omnibus Crime Control and Safe Streets Act. It defines corporate offenses and enforcement actions, and requires the collection, aggregation, and publication of enforcement data on a public internet database.
The aim is to standardize reporting across federal agencies and provide researchers, policymakers, and the public with a searchable record of corporate enforcement actions and outcomes.
Key mechanics include: a broad definition of corporate offenses, a detailed data schema (entity names, employers, parent companies, offense type, statutes, enforcing agency, outcomes, and unique identifiers), and a timetable that starts with guidance within 180 days and a public database within one year. The bill also requires annual reporting to Congress on data trends and policy implications, and it adds a Council provision to improve data collection and standardization across agencies.
At a Glance
What It Does
Establishes a Corporate Crime Database by adding Section 305 to the Omnibus Crime Control and Safe Streets Act. The Director must collect, aggregate, and analyze enforcement actions related to corporate offenses and publish a public, searchable database.
Who It Affects
Federal enforcement agencies that carry out corporate offense actions, the Bureau (BJS) that maintains the database, and members of the public and researchers who access the published data.
Why It Matters
Sets a standardized, transparent view of corporate enforcement actions and outcomes, enabling monitoring of trends, outcomes, and potential gaps in enforcement accountability.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
The Corporate Crime Database Act of 2025 directs the Director of the Bureau of Justice Statistics to create a centralized database of corporate offenses and related enforcement actions. The definitions section clarifies what counts as a corporate offense and what constitutes an enforcement action, including settlements and non-prosecution agreements tied to federal actions.
The database is designed to collect information from multiple federal agencies, including the entity involved, its employers and parent companies, the specific offense or alleged offense, the violated statutes, the enforcing agency, the action’s outcome, and an assigned unique identifier for each party.
Implementation requirements drive interagency cooperation. The Director must issue guidance within 180 days to outline which agencies submit data, what data fields are needed, and the submission cadence.
Agencies identified in that guidance must cooperate and provide the requested information. The data gathered will be published on the Bureau’s website within one year and updated whenever new information is collected, ensuring the public has access to current enforcement data.A legislative report to Congress is required annually after the database is published.
Reports describe what data are collected and analyzed, assess potential impacts on victims and the public, and offer recommendations to improve monitoring, response, and deterrence of corporate offenses. A separate amendment to the Chief Data Officer Council directs agencies to improve data collection, sharing, and standardization to support this section’s goals.
The Five Things You Need to Know
The bill defines corporate offenses to cover actions by a business entity or individuals in occupational roles, plus other offenses the Director deems corporate offenses.
The database must include: entity and employer information, parent company relationships, offense type, statutes, enforcing agency, outcomes, and a unique identifier.
A guidance process within 180 days requires federal agencies to submit data, and cooperation is mandatory for data collection.
Within 1 year, the database is to be published online in a searchable, downloadable format and then updated with every new enforcement action.
The Act requires annual Congressional reporting on data collected, recidivism analysis, and policy recommendations to improve monitoring and deterrence.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Definitions for corporate offenses and related terms
This section creates the glossary used throughout the database. It defines a 'business entity' and a 'corporate offense' as offenses by a business entity or by an individual in an occupational role for a business entity, plus any other offenses the Director designates as corporate offenses. It also defines 'enforcement action' to cover concluded agency actions, settlements, and related dispositions, and it clarifies who is the 'Director' for purposes of the database.
Establishment of the Corporate Crime Database
Beginning not later than one year after enactment, the Director must collect, aggregate, and analyze enforcement actions concerning corporate offenses and publish a public database on the Bureau’s website. This creates a centralized repository intended to illuminate enforcement activity across agencies.
Information included on each enforcement action
The database must capture nine categories of data for each action: the entity and any identified individuals, the employer and parent company, the specific offense or alleged offense, the statutes violated, the enforcing federal agency, the action’s outcome, a unique identifier, and any additional director-approved information necessary to carry out the section.
Information collection by the Director
The Director must issue guidance within 180 days outlining which federal agencies submit data, what data must be provided, and the timing and frequency of submissions. Agencies identified in the guidance must comply and submit the required information in accordance with that guidance.
Publication details of the database
Not later than one year after enactment, the Director must publish the database in a searchable and downloadable format on the Bureau’s website. The information must be updated whenever new data are collected to keep the database current and accessible to the public.
Congressional reporting on the database
Within one year after publication and annually thereafter, the Director must report to Congress on the data collected and analyzed, the impact on victims and the public, and policy recommendations to strengthen monitoring, response, and deterrence of corporate offenses.
Chief Data Officer Council amendment
The amendment adds a subparagraph to require the Chief Data Officer Council to identify ways federal agencies can improve the collection, digitization, tabulation, sharing, and publishing of data under Section 305, and to standardize processes to support the corporate crime database goals.
This bill is one of many.
Codify tracks hundreds of bills on Justice across all five countries.
Explore Justice in Codify Search →Who Benefits and Who Bears the Cost
Every bill creates winners and losers. Here's who stands to gain and who bears the cost.
Who Benefits
- Federal enforcement agencies (e.g., DOJ and other agencies bringing enforcement actions) gain standardized data to monitor activity, coordinate actions, and assess outcomes.
- The Director of the Bureau of Justice Statistics and the Bureau itself benefit from a defined mandate and public-facing data platform that enhances transparency and accountability.
- Researchers, academics, and policy analysts gain a rich dataset for empirical studies on corporate offenses, enforcement patterns, and recidivism trends.
- The public and victims of corporate offenses gain access to a transparent, searchable record of enforcement actions and outcomes.
Who Bears the Cost
- Federal agencies required to submit data incur administrative and operational costs to collect, format, and transmit information per the Director’s guidance.
- The Bureau of Justice Statistics bears ongoing data processing, publication, and maintenance costs to support the database and its updates.
- The federal budget and taxpayers bear the funding burden for establishing and sustaining the database over time.
- Businesses named in enforcement actions may experience reputational impact due to public disclosure within the database.
Key Issues
The Core Tension
The central dilemma is balancing maximum transparency and the public’s right to know with the need for accurate, consistent data and protection against mischaracterization or harm to individuals and entities. Standardizing data across multiple agencies can improve comparability but may constrain agency discretion and create incentives to adjust reporting. The policy seeks to deter corporate offenses while relying on robust internal processes and data sharing, but it raises questions about data quality, privacy, and the potential chilling effects on enforcement.
The bill creates a centralized data system that relies on interagency cooperation and consistent data standards. The quality, completeness, and timeliness of the information depend on how well agencies implement the guidance and submit data.
Because the database aggregates enforcement actions across agencies and includes details about entities and individuals, there are potential privacy, confidentiality, and reputational concerns that require careful handling and clear definitions. The bill does not specify data minimization or privacy protections beyond what agencies already apply, and the broad definition of 'corporate offense' could raise questions about scope and accuracy if agencies interpret terms differently.
In addition, while the database aims to deter wrongdoing and improve oversight, the trade-offs between transparency and the risk of misinterpretation or unintended consequences for participants remain a central issue.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.