A Chapter 12 or Chapter 13 filing triggers reporting obligations that require careful alignment between account-level fields (status, balances, payment amount, history) and consumer-level fields (bankruptcy indicators and ECOA relationship codes). Inaccurate reporting can increase disputes, create rework through e-OSCAR processes, and expose a furnisher to compliance risk under the Fair Credit Reporting Act (FCRA), including the duty to furnish accurate information and to investigate disputes.
Definitions and context
Chapter 12 and Chapter 13 cases typically involve a repayment plan and an automatic stay. The stay can impact more than the filing consumer. In some co-borrower scenarios, the non-filer can be protected through plan completion, which changes how (and whether) the non-filer should be updated during the plan period.
Key Metro 2 concepts used in these scenarios include:
- Consumer Information Indicator (CII): used to reflect a bankruptcy petition and later resolution (completion/discharge, removal).
- ECOA Code: used to define each consumer’s relationship to the account; can also be used to terminate a consumer’s association without deleting account history.
- Payment History Profile (PHP): must remain logically consistent; it should not be rewritten after the fact to “clean up” plan months.
Step-by-step reporting standards
1) Month the petition is filed
- Report the appropriate bankruptcy petition CII on the filer’s consumer segment.
- Report account-level fields “as of” the Date of Account Information for that reporting period (status, balances, payment amount).
2) Months during the plan or while protected by the stay
- Continue reporting the petition CII (or allow it to persist per your reporting method).
- PHP handling: for months where the consumer is protected by the stay and traditional delinquency progression is not appropriate, the PHP should reflect those months consistently (commonly using the “D” concept for “no payment history reported/available this month” during protected periods, depending on the scenario and your internal compliance approach). Avoid retroactive removal of accurate prior history.
3) When a non-filer is protected by the stay (joint/co-debtor scenario)
If the non-filer is protected through plan completion, the non-filer is typically terminated from ongoing reporting during the protected period:
- Report ECOA Code T (Terminated) for the non-filer (in the segment where that non-filer is reported).
- Do not continue to report that non-filer in subsequent periods until the plan reaches a point where re-reporting is appropriate.
This is a critical control to prevent the appearance that the non-filer is accruing new negative (or positive) monthly updates while legally protected and operationally not being serviced in the same way.
4) Plan completion outcomes
- Plan completed, no further obligation: report the appropriate “completed/discharged” CII for the filer, and then discontinue reporting the filer as required by your Metro 2 workflow for that scenario.
- Plan completed, account continues (common for secured debts): report a removal CII to clear the petition indicator so that ongoing, post-plan performance can be reported normally going forward.
5) Plan dismissed or withdrawn
- Report the appropriate removal CII to clear the petition indicator.
- Resume standard reporting logic going forward. Importantly, do not “erase” protected-period PHP entries if they were accurate for the periods reported.
Compliance requirements
Under FCRA Section 623, furnishers have duties to provide accurate information, correct and update information, and conduct reasonable investigations of disputes. In Chapter 12/13 contexts, common dispute triggers include:
- Non-filer being updated monthly despite stay protection
- Improper delinquency progression during plan months
- Inconsistent balances or payment amounts relative to plan terms
- Inaccurate bankruptcy indicators (wrong consumer, wrong lifecycle stage)
Your procedures should ensure the reporting reflects verifiable records and consistent Metro 2 logic across account-level and consumer-level fields.
Impact on consumers
Bankruptcy reporting affects a consumer’s access to housing, credit, employment screening, and insurance pricing in many markets. Inaccurate reporting during plan months can create the appearance of new delinquency, duplicate harm already addressed by the plan, or confuse users of the report about whether the consumer is performing under court supervision.
Conclusion
Accurate Chapter 12/13 reporting is primarily about consistency: match consumer-level bankruptcy indicators to the correct person, control non-filer participation when protected by the stay, and keep payment history coherent without retroactive rewrites. Strong internal controls and documented decision rules reduce disputes and support defensible FCRA compliance.