Basic (01-01)

VB 02507.025 Unrestricted Reopening — Similar Fault

A. INTRODUCTION

When fraud cannot be established (i.e., there is not a preponderance of evidence showing both knowledge and intent to defraud), we can reopen determinations in SVB cases at any time if there is “similar fault.” (See VB 02507.010A.6. for a definition of similar fault.)

For reopening under similar fault, we must establish by a preponderance of evidence that the claimant, beneficiary or other person knowingly did something wrong. However, we do not have to establish intent to defraud.

NOTE: Similar fault determinations are made only with regard to reopening initial determinations under administrative finality provisions. In criminal matters and matters concerning earnings record correction under the statute of limitations, there is no provision for a finding of similar fault.

B. PROCEDURE

1. When to Develop Similar Fault

The FO has the authority to decide whether to initiate similar fault development in SVB cases. Consider developing similar fault when:

  • A case of suspected fraud has been referred to OIFD and a determination has been made by that office that fraud does not exist because there is no intent to defraud; or

  • OIFD gives no reason for a determination that fraud does not exist; or

  • The case was not referred to OIFD for a potential fraud violation, but it meets all the criteria in VB 02507.025B.2.

2. Criteria to Establish Similar Fault

A similar fault finding must be supported by a preponderance of evidence as defined in GN 04020.010A.6. Such a finding may be appropriate under the following conditions:

  • The issue or event relating to the similar fault decision is material and will create a new or additional overpayment; and

  • If other benefit income is involved, there is a wide discrepancy between the new information and the information reported.

    NOTE: The term “wide discrepancy” cannot be defined in terms of money amount. It is a matter of judgement. It depends on how recently the other benefit was received, how long it was unreported or under-reported, as well as the amount and frequency, etc.

  • The SVB beneficiary knowingly completed an incorrect or incomplete report, knowingly concealed events or changes, or knowingly neglected to report events or changes that affect payment; and

  • The event (e.g., deportation of the SVB beneficiary, change in other benefit income, return to the United States, etc.) can and will be verified;

  • After verification, there is no doubt that the event or change applies to the SVB recipient.

CAUTION: Before initiating or continuing similar fault development, review VB 02507.025B.7. and VB 02507.025B.8. for situations where such development should be avoided or stopped. Also, in developing for similar fault, take into account any physical, mental, educational or linguistic limitation (including lack of facility with English) which would bring into question the individual's knowledge of the suspected wrongdoing.

3. Documentation

Prepare Form SSA-553 (Special Determination) in cases where similar fault has been developed. List the specific evidence available to support the determination that similar fault exists or does not exist.

4. Notification

  1. a. 

    Notify the beneficiary of the revised determination (see VB 02507.050) and that similar fault exists.

  2. b. 

    Include in the notice a discussion of the evidence used to make that determination.

  3. c. 

    The beneficiary must also be advised of his/her appeal rights. (See VB 02507.050.)

5. Overpayments

  1. a. 

    If similar fault is established and fraud does not exist, we:

    • Make the similar fault determination; then

    • Develop and recover the entire overpayment;

  2. b. 

    The overpayment notice should cover the entire overpayment period.

6. Waiver

  1. a. 

    If similar fault on the part of the recipient is established, the overpaid beneficiary should be found at fault for waiver purposes.

  2. b. 

    If similar fault is found on the part of an individual other than the beneficiary, the beneficiary can still be found without fault for waiver purposes.

7. Excluding Similar Fault Development

In some SVB cases, similar fault development requires excess effort on the part of SSA for a small payoff or imposes undue hardship on the beneficiary. In those cases, similar fault development should not be started, or if started, it should be stopped. Examples of cases where similar fault should not be initiated include (but are not limited to) those in which:

  • The SVB beneficiary is dead;

  • The beneficiary is 75 years or older and is in poor health;

  • The overpayment resulted solely from failure to report a cost-of-living increase in an “other benefit.” (See VB 00205.100 ff.)

NOTE: Documentation is not required in the above cases.

8. Curtailing Development of Similar Fault

If already begun, similar fault development should be stopped in the following situations:

  • The SVB beneficiary died;

  • After reasonable efforts have been made to develop a preponderance of the evidence that similar fault exists, evidence is insufficient to establish it and the incorrect payment on the record is less than the current monthly SVB benefit payable under the law;

  • Negligence or error by SSA employees significantly contributed to the incorrect payment;

  • The file contains a determination (initial or appealed) favorable to the beneficiary on the issue involved in the similar fault.

  • The law or policy has changed so that the event or change would no longer cause excess payments.

NOTE: Complete a report of contact showing reasons for curtailing development in the above cases.

9. Reference

SI 04070.020E. (Exhibit). The flowchart for similar fault development in SSI cases can also be followed for SVB cases. If you use the chart for SVB cases, substitute references to SI 04070.020E. and SI 04070.020 with references to VB 02507.025B.7. and VB 02507.025B.8. respectively.

 


To Link to this section - Use this URL:
http://policy.ssa.gov/poms.nsf/lnx/1402507025
VB 02507.025 - Unrestricted Reopening — Similar Fault - 07/05/2005
Batch run: 09/12/2023
Rev:07/05/2005