How should a furnisher report an account when a consumer’s regular payments are temporarily postponed through a payment holiday, skip-a-pay program, or similar short-term relief arrangement?
Temporary payment relief programs have become a standard tool for servicers and creditors managing consumer hardship, seasonal flexibility, or disaster recovery. Under Metro 2, these arrangements require careful handling because the payment fields, Account Status, and Payment History Profile must all remain internally consistent during and after the relief period. Misreporting during these windows is a common source of consumer disputes and regulatory scrutiny, particularly when consumers are told “no payment is due” but their credit report reflects delinquency progression.
Definitions and context (what “temporary relief” means in Metro 2)
A temporary payment relief program generally means:
- The consumer’s regular payment obligation is reduced or suspended for a defined period.
- The underlying account remains open and active.
- The contract may or may not be formally modified (a key distinction for Metro 2 field logic).
Metro 2 does not use the phrase “payment holiday” as a formal field value. Instead, the reporting framework handles these scenarios through a combination of:
- Scheduled Monthly Payment Amount (Field 15): reflects what is actually due during the relief period.
- Account Status (Field 17A): reflects the account’s condition relative to what is contractually or programmatically due.
- Payment History Profile (Field 18): must remain logically consistent with the Account Status reported month to month.
- Terms Frequency (Field 14): may change to “D” (Deferred) if the arrangement qualifies as a formal deferment.
Step-by-step reporting standards
1) When relief begins and no payment is due
- Scheduled Monthly Payment Amount: report the amount actually due during the relief period. If no payment is required, zero fill this field.
- Account Status: if no payment is due and the consumer is meeting the terms of the arrangement, report Account Status 11 (Current).
- PHP: for the prior month’s position in the Payment History Profile, increment based on the Account Status that was reported in that prior period (standard PHP logic). For months where no payment is due and the account is current, some furnishers use “D” (no payment history reported/available this month) to represent the relief period, while others report “0” (current). Your internal policy should govern which approach you use, and it must be applied consistently.
2) When relief begins and a reduced payment is due
- Scheduled Monthly Payment Amount: report the reduced amount that is actually due during the relief period.
- Account Status: report based on whether the consumer meets the reduced obligation. If the consumer pays the reduced amount on time, report Account Status 11 (Current).
- PHP: increment normally based on the prior month’s Account Status.
3) During the relief period (ongoing months)
- Continue reporting Scheduled Monthly Payment Amount as what is due (zero or reduced, depending on the arrangement).
- Continue reporting Account Status based on the consumer’s performance relative to the current obligation.
- Do not allow delinquency to progress if the consumer is meeting the terms of the relief agreement.
4) When the relief period ends and normal payments resume
- Scheduled Monthly Payment Amount: return to the standard contractual payment amount.
- Account Status: report based on whether the consumer meets the resumed payment obligation.
- Critical rule: do not retroactively change PHP entries for the relief months after the plan concludes. Those months were reported accurately based on the conditions in effect at the time.
What to do when a consumer was delinquent before entering relief
This is the most compliance-sensitive scenario. If the consumer was already past due before the relief arrangement began:
- The Date of First Delinquency (DOFD) should reflect the original first delinquency that led to the current status. It should not be reset simply because the consumer entered a relief program.
- During the relief period, if no payment is required and the account is being treated as current under the program terms, report Account Status 11. However, the DOFD from before the arrangement should be zero filled only if the account is genuinely brought current (meaning the pre-relief delinquency has been resolved, not merely paused).
- Your compliance and legal teams should document the specific conditions under which your organization considers a pre-existing delinquency “cured” by entry into a relief program versus merely “paused.”
Compliance requirements (FCRA and Metro 2 alignment)
Under the FCRA, furnishers must report information that is accurate and consistent with their records. Key compliance considerations for temporary relief include:
- Do not report delinquency during a period where no payment is due. If the relief agreement removes the payment obligation for a defined period, reporting delinquency progression during that window is inaccurate.
- Do not retroactively rewrite PHP. Metro 2 guidance specifically warns against updating Payment History Profile entries for relief months after the plan ends.
- Do not use disaster indicators as a substitute for proper relief reporting. If disaster-related relief is granted, the disaster Special Comment (AW) may be reported as optional context, but it does not replace the mechanics of accurate payment field and status reporting.
- Document the arrangement. Defensible reporting requires that your records support the terms of the relief program, including start date, end date, payment amount during relief, and any conditions.
Impact on consumers
Consumers who enter relief programs in good faith expect their credit reporting to reflect compliance with the arrangement. When furnishers report delinquency during a zero-payment window, the result is predictable: disputes, escalations, and potential regulatory attention. Conversely, overly generous reporting (for example, reporting “current” and zero-filling DOFD when a pre-existing delinquency was never actually resolved) can create accuracy concerns in the other direction.
Conclusion
Temporary payment relief reporting in Metro 2 comes down to three principles: (1) report Scheduled Monthly Payment Amount as what is actually due during the relief period, (2) report Account Status based on performance relative to that obligation, and (3) do not retroactively alter the Payment History Profile after the relief window closes. Consistency, documentation, and alignment between your servicing records and your Metro 2 output are the foundation of defensible compliance.