How should a furnisher report an account that is in forbearance, and when should forbearance reporting transition to deferment logic?
Forbearance is one of the most operationally complex reporting scenarios in Metro 2 because it sits between two other concepts: temporary payment relief (where the payment schedule is informally adjusted) and formal deferment (where payments are postponed to a defined future date). Forbearance typically involves a written or documented agreement between the servicer and the consumer that temporarily reduces, suspends, or modifies the payment obligation during a hardship period. Metro 2 provides specific field logic and a dedicated Special Comment Code to communicate forbearance status to consumer reporting agencies and data users.
Definitions and context (what “forbearance” means in Metro 2)
In Metro 2, forbearance is generally characterized by:
- A documented agreement between the furnisher and consumer.
- A temporary modification to payment terms (not a permanent loan modification).
- The account remains open and active (not closed, not transferred).
- There may or may not be a payment due during the forbearance period, depending on the specific agreement terms.
Metro 2 communicates forbearance through:
- Special Comment Code CP (“Account in Forbearance”) to indicate the account is currently in a forbearance arrangement.
- Account Status (Field 17A) that reflects the account’s condition relative to what is contractually or programmatically due during the forbearance period.
- K4 Segment with Specialized Payment Indicator = 02 when the forbearance includes a deferred payment structure (payments formally postponed to a future start date).
Step-by-step reporting standards
1) When forbearance begins
- Special Comment (Field 19): report “CP” (Account in Forbearance).
- Account Status: report based on whether the consumer is meeting the forbearance terms. If the terms require no payment (or a reduced payment) and the consumer is compliant, report Account Status 11 (Current).
- Scheduled Monthly Payment Amount (Field 15): report the payment amount actually due under the forbearance agreement. If no payment is due during forbearance, zero fill.
- Current Balance (Field 21): continue reporting the outstanding balance as of the Date of Account Information. The balance does not disappear because the account is in forbearance.
- Amount Past Due (Field 22): if the consumer is meeting the forbearance terms and the account is being treated as current, report zero. If the forbearance agreement does not cure the prior delinquency (and the consumer remains past due under the modified terms), report the applicable amount.
2) During the forbearance period (ongoing months)
- Continue reporting Special Comment CP each month as long as the forbearance is active.
- Continue reporting Account Status based on performance relative to the forbearance terms.
- Payment History Profile (PHP): increment based on the prior month’s Account Status as reported. If you reported Account Status 11 last month, the PHP position for that month should reflect “0” (current). If you reported a delinquent status, the PHP should reflect the corresponding delinquency level.
- Do not suppress or freeze reporting during the forbearance period. The account should continue to be reported with current balances and payment information each cycle.
3) When forbearance includes deferred payments (K4 Segment required)
If the forbearance agreement specifies that payments are deferred to a defined future start date:
- Report the K4 Segment with Specialized Payment Indicator = 02 and the Deferred Payment Start Date (the date the first payment will be due after forbearance ends).
- Terms Frequency (Field 14): change to “D” (Deferred) if the forbearance arrangement suspends all payments and defers them.
- Scheduled Monthly Payment Amount: zero fill (consistent with deferment logic).
- Continue reporting Special Comment CP alongside the K4 Segment.
This combination (CP + K4 with deferred indicator) tells consumer reporting agencies that the account is both in forbearance and has a defined payment resumption date.
4) When forbearance ends and normal payments resume
- Remove Special Comment CP: report a blank Special Comment (or transition to another applicable comment if one exists).
- Remove the K4 Segment if it was being reported for deferment during forbearance.
- Terms Frequency: return to the standard frequency (for example, “M” for Monthly).
- Scheduled Monthly Payment Amount: return to the standard contractual payment amount.
- Account Status: report based on whether the consumer makes the first post-forbearance payment on time.
- PHP: the forbearance months remain as-reported in the trailing positions. Do not retroactively change them.
5) When the consumer does not comply with forbearance terms
If the consumer fails to meet the obligations of the forbearance agreement (for example, a reduced payment was required and was not made):
- Report the Account Status that reflects the actual delinquency level relative to what was due.
- Continue reporting Special Comment CP as long as the forbearance agreement is still active (even if the consumer is not complying).
- Progress Amount Past Due and PHP based on the actual delinquency.
Key distinction: forbearance vs. deferment vs. loan modification
| Concept | Metro 2 Indicator | Payment Due? | K4 Required? |
| Forbearance (reduced payment) | Special Comment CP | Yes (reduced) | No |
| Forbearance (no payment, deferred) | Special Comment CP + K4 (Indicator 02) | No | Yes |
| Formal deferment (no forbearance context) | Terms Frequency “D” + K4 (Indicator 02) | No | Yes |
| Loan modification (permanent) | Special Comment CN or CO | Yes (new terms) | No (unless balloon) |
If a forbearance transitions into a permanent loan modification, the furnisher should stop reporting CP and begin reporting the applicable modification comment (CN for federal government plan, CO for non-federal modification) with updated contractual terms.
Compliance requirements (FCRA alignment)
Under the FCRA, furnishers must report information that accurately reflects the terms of and liability for the account, as well as the consumer’s performance. Forbearance reporting pitfalls include:
- Reporting delinquency when no payment is due under the forbearance terms. If the agreement suspends payments and the consumer is compliant, reporting delinquency progression is inaccurate.
- Failing to report Special Comment CP. Without it, data users cannot distinguish a forbearance from a standard delinquency or from a permanent modification.
- Omitting the K4 Segment when payments are deferred. Without the deferred payment start date, consumer reporting agencies and data users cannot determine when the consumer’s payment obligation resumes.
- Retroactively altering PHP after forbearance ends. Metro 2 guidance is clear that accurately reported history should not be rewritten.
Impact on consumers
Forbearance is typically granted to consumers in hardship. Accurate forbearance reporting protects consumers from delinquency escalation during months where no (or reduced) payment is required. It also provides transparency to future creditors evaluating the tradeline: the CP comment and K4 Segment together explain why the account may show zero-payment months without delinquency. Misreporting during forbearance is a frequent trigger for disputes and can undermine the consumer’s ability to access credit during or after the hardship period.
Conclusion
Forbearance reporting in Metro 2 relies on three coordinated signals: (1) Special Comment CP to flag the forbearance arrangement, (2) Account Status and payment fields that reflect what is actually due under the forbearance terms, and (3) the K4 Segment when the forbearance includes deferred payments with a defined resumption date. When forbearance ends, remove CP and the K4 Segment, resume normal payment logic, and leave the forbearance-period PHP intact.