Metro 2 Account Type Code 75: Government Benefit Over-Payment

Specification

Code	75
Meaning	Government Benefit Over-Payment
Field	Account Type (Field 15)
Record	Base Segment
Length / position	2 chars · 84–85
Category	Government Obligations
CRRG reference	CRRG Exhibits 1 & 2 (Account Type Codes)

The narrower sibling of code 70. Where 70 covers government overpayments generally, 75 says specifically that the overpaid funds were benefit payments.
Nothing was borrowed. The obligation arises from an entitlement determination applied retroactively or from an error in the benefit calculation.
Recovery is frequently by offset against future benefit payments, which means the balance can fall every cycle without a conventional payment being made.
Does NOT mean a benefit the consumer received and was entitled to. Only the excess is a debt, and only after it is established.
Does NOT mean a fine. An overpayment recovers money the government paid out; a fine (71) is a penalty imposed.

1An agency reports a benefit overpayment established after a redetermination found the consumer was ineligible for part of a period.
2An agency reports a benefit overpayment being recovered by monthly offset against continuing benefits.
3An agency reports a benefit overpayment on an agreed cash repayment plan after benefits ended.
4An agency reports a benefit overpayment partially waived on hardship grounds with the remainder still owed.
5An agency reports a benefit overpayment fully recovered, closing the tradeline at a zero balance.
6An agency reports a benefit overpayment that stopped being recovered when benefits ended and has now gone delinquent under its cash repayment plan.

Report the established overpayment as the Original Loan Amount and the unrecovered amount as the Current Balance.
Report each offset as a payment so the payment fields and the falling balance reconcile.
Reflect a waiver by reducing the Current Balance, not by restating the established amount.
Do not furnish an overpayment that is still in an appeal or reconsideration window as a settled delinquent obligation; apply your written policy consistently across the portfolio.
Do not report the benefit program or the consumer's circumstances in any free-text field.

A file can be structurally valid and still be wrong. These are the cross-field conditions Account Type Code 75 has to satisfy.

Portfolio Type must be I (Installment).
Portfolio Type I requires Terms Duration and Scheduled Monthly Payment. Where recovery is by benefit offset, report the offset amount and its actual interval in the payment and Terms Frequency fields.
Credit Limit must be blank or zero.
Actual Payment Amount should reflect offsets applied in the cycle; a falling balance with no reported payment is an amount-logic contradiction.
Amount Past Due should be zero while recovery by offset is proceeding as agreed, even though a balance remains.
Date of First Delinquency runs from the first missed obligation under the repayment or offset arrangement, not from the date the excess benefit was paid. Anchoring the DOFD to the original benefit payment can extend the reporting window by years and is a common defect in agency portfolios.
Original Loan Amount is the established overpayment and must be greater than zero; a partial waiver reduces Current Balance and leaves the establishment amount alone.
Date Opened is the date the overpayment was established by determination, not the date the excess payment was issued.
ECOA reporting is individual to the benefit recipient. A joint ECOA code or an associated-consumer segment asserting shared liability contradicts the nature of the obligation.