DI 52130.020 Office of Personnel Management (OPM) Data Exchange Alerts
SSA’s Master Beneficiary Record (MBR) is matched periodically against OPM records. Alerts are sent to the processing center (PC) when the MBR contradicts the OPM data or the system cannot determine if the MBR information is correct.
NOTE: The Modernized Claims System Earnings Computation (MCS EC) system also interfaces with OPM. See DI 52155.040 - Processing Initial Claims with Federal PDB for the initial claims interface.
A. OPM/Public Disability Benefit (PDB) data exchange alerts – Due process
OPM/PDB data alerts, especially alert codes A and B, can result in /PDBoverpayments and/or reductions to ongoing benefits. Therefore, it is important to remember that OPM alerts are third party reports. Give the individual due process per GN 03001.025 prior to taking any reduction or overpayment action due to OPM/PDB alerts. For due process notices, see NL00703.511-NL 00703.513.
B. Processing OPM/PDB data exchange alerts
The alerts provide valuable information to SSA, but do not always provide all of the information needed to process the case correctly. For instance, the system cannot compute the 85 percent covered service exception. Always develop for pension amounts or covered service whenever there is an apparent discrepancy.
Format of the Alert
The top line shows the run date and the month and year of the data match. Immediately below that line is the SSA Claim Number and the alert code. The table below defines each alert code and the action required.
OPM is paying a non-covered pension, but no offset is on the MBR.
Develop to determine if either of exception tests in DI 52130.001 A is met. Impose offset if applicable. These alerts generally result in large overpayments. Consider administrative finality per GN 04030.080 and give due process prior to taking any action.
Offset is on MBR but offset adjustment may be necessary.
Develop pension amounts per DI 52130.001 for any period not already proven. Provide due process notice of any adverse adjustment and adjust offset accordingly.
The one-day covered service exception test in DI 52130.001 A 1 b is met, but PDB offset is on MBR. (DIB onset is 03/01/1981 to 04/30/1986, MOET is 09/1981 or later and the CSCOVIND = Y)
Remove offset, delete PDB data and adjust the CSPDB indicator per DI 52130.025. Code C cases most often result in underpayments.
CSPDB Code Required.
CSPDB indicator missing or blank.
NOTE: This alert code is no longer used.
DIB onset is 05/01/1986 or later and the CSCOVIND = Y. (There is some covered service but the system cannot determine if offset should apply.)
Develop to determine if the 85 percent covered service exception test in DI 52130.001 is met. Impose or remove offset accordingly. Code the correct CSPDB indicator per DI 52130.025 if not already on the MBR.
NOTE: The alerts will always require some type of corrective action unless an intervening action has resloved the discrepancy.
The table below defines other fields on the OPM alert:
Name of CSRS Annuitant. (Last, First, Middle)
DOB: mm yyyy
Annuitant’s date of birth.
SSN: (no dashes)
OPM claim number
Covered service indicator.
Y = pension based on at least some covered service.
N = pension based on all non-covered service.
CSAWDTE: mm dd yyyy
Date of entitlement to CSRS pension.
CSAMT: $ 9999.99
Most current pension amount.
CSAMTEFFDT: mm dd yyyy
Date the most current pension amount is effective.
Four digit field showing the number of years followed by the number of months of service.
Showed the CSRS payment history from 1981 through date of alert. An asterisk indicates that the payment information was possibly inaccurate.
NOTE: This field is no longer shown on the alerts.