Corporate Crime Database Act of 2026
- Sponsor
- Sen. Durbin, Richard J. [D-IL]
- Committees
- Judiciary Committee (primary)
- Last action
- Mar 16, 2026
Bottom line
This bill aims to enhance transparency and data availability regarding corporate crime and enforcement by establishing a centralized, public database at the Bureau of Justice Statistics.
What it actually does
This bill directs the Director of the Bureau of Justice Statistics (BJS) to establish and maintain a public database of corporate offenses and related enforcement actions taken by federal agencies. It mandates that federal agencies collect and submit relevant information to BJS, including historical data, and requires BJS to publish the database online in an accessible format and submit annual analytical reports to Congress.
Proponents argue
Proponents argue that increased transparency regarding corporate offenses and enforcement actions is crucial for public accountability, informed policymaking, and deterring corporate misconduct. A centralized database would allow researchers, policymakers, and the public to better understand patterns of corporate crime, recidivism, and the effectiveness of enforcement efforts, leading to a more just and equitable system.
Opponents contend
Potential opponents might raise concerns about the significant administrative burden on federal agencies to collect and submit this detailed and potentially historical data, as well as the associated costs of establishing and maintaining such a comprehensive database. They may also express concerns about potential privacy implications for individuals identified in enforcement actions or the risk of public misinterpretation of complex legal outcomes, especially for alleged violations.
The bill is concise and can be read and understood quickly, allowing ample time for detailed consideration of its implications.
Section 2(a), adding Section 305(b) to the Omnibus Crime Control and Safe Streets Act of 1968
Mandate for Bureau of Justice Statistics to Establish Database
This provision directs the Director of the Bureau of Justice Statistics (BJS) to establish a public database on its website within one year of the bill's enactment. This database will collect, aggregate, and analyze information regarding enforcement actions taken by federal agencies concerning corporate offenses, making this data publicly available.
Supporters argue
Supporters argue this is the core mechanism for achieving greater transparency and accountability for corporate crime, providing a much-needed centralized resource for data that is currently fragmented or inaccessible across various federal agencies.
Critics contend
Opponents might argue that creating a new, comprehensive database is an unnecessary expansion of government bureaucracy and could be costly, potentially duplicating efforts already undertaken by individual agencies or leading to inefficiencies.
Tradeoffs
This provision balances the public's right to information and the need for comprehensive data on corporate misconduct against potential administrative costs and the inherent complexity of integrating data from numerous, diverse federal agencies.
Section 2(a), adding Section 305(a) to the Omnibus Crime Control and Safe Streets Act of 1968
Definitions for Database Scope
This section defines key terms for the database. A 'corporate offense' includes violations or alleged violations of federal law by a business entity or an individual in their occupational role, plus any other violations determined by the BJS Director. An 'enforcement action' is broadly defined to include concluded administrative, civil, or criminal actions, as well as declinations, settlements, deferred prosecution agreements, or non-prosecution agreements.
Section 2(a), adding Section 305(c) to the Omnibus Crime Control and Safe Streets Act of 1968
Required Data Elements for the Database
This provision specifies the detailed information that must be included for each enforcement action in the database. This includes identifying information for business entities, individuals, their employers, and parent companies; the type of offense, relevant statutes/regulations violated, the federal agency involved, the outcome of the enforcement action (including all relevant documentation), and a unique identifier for each entity.
Section 2(a), adding Section 305(d) to the Omnibus Crime Control and Safe Streets Act of 1968
Federal Agency Data Submission Requirements
This section mandates that BJS establish guidance for federal agencies on how, when, and with what frequency to submit information on corporate offenses. It also requires identified federal agencies to cooperate and submit the specified information. Crucially, the database must include information on enforcement actions taken *before, on, or after* the date of enactment, to the extent available, ensuring historical depth.
Section 2(a), adding Section 305(e) and (f) to the Omnibus Crime Control and Safe Streets Act of 1968
Public Accessibility and Annual Congressional Reports
This provision requires the database to be published on the BJS website within one year, in a format that is searchable, downloadable, and publicly accessible, and to be updated regularly. Additionally, BJS must submit annual reports to Congress, including analysis of recidivism, offenses, enforcement actions, estimated impact on victims and the public, and recommendations for legislative or administrative improvements.
Section 2(b)
Role of Chief Data Officer Council in Data Improvement
This section amends title 44, United States Code, to add a new function for the Chief Data Officer Council. The Council will be tasked with identifying ways federal agencies can improve the collection, digitalization, tabulation, sharing, and publishing of information related to corporate offenses under this Act, and standardize these processes across the government.
Requires the database to include information on corporate enforcement actions taken by federal agencies *before, on, or after* the date of enactment, to the extent information is available.
Section 2(a), adding Section 305(d)(3)
Why it matters:This is standard legislative practice for ensuring comprehensive historical data, rather than being evasive. It ensures the database has historical depth, which is crucial for trend analysis.
Case for: Supporters argue that historical data is essential for understanding long-term trends, identifying repeat offenders, and assessing the cumulative impact of corporate crime and enforcement, providing a more robust analytical foundation for policy decisions.
Case against: Critics might point to the significant administrative burden and technical challenges for federal agencies to compile and standardize historical data, especially if older records are not digitized or are stored in disparate systems, potentially leading to high costs, delays, or incomplete data for past actions.
Estimated impact: Significantly expands the scope and utility of the database by providing a historical context for corporate offenses and enforcement, enabling longitudinal studies and better recidivism tracking, but also increases the initial implementation burden on agencies.
Amends existing law (title 44, United States Code) to add a new duty for the Chief Data Officer Council: to identify ways federal agencies can improve and standardize the collection, digitalization, tabulation, sharing, and publishing of corporate offense information under this Act.
Section 2(b)
Why it matters:This is standard legislative practice for making technical adjustments to related statutes to ensure smooth implementation and inter-agency coordination, rather than being evasive. It's a mechanism to support the main objective.
Case for: Proponents argue that leveraging the expertise of the Chief Data Officer Council is crucial for ensuring inter-agency coordination, data quality, and standardization, which are vital for the long-term success and utility of the corporate crime database and efficient government operations.
Case against: No specific opposition is typically raised against provisions aimed at improving data management and standardization, as these are generally seen as good governance practices that enhance efficiency and effectiveness across government.
Estimated impact: Facilitates more efficient and consistent data collection and reporting across federal agencies, improving the overall quality, comparability, and utility of the corporate crime database by promoting best practices and coordination.