Federal Offset Program

PART 1.0
Option to Send Transactions for Changing Obligor Name, Case ID, and Obligor Address (FOP 1487, 1488 and 1489)

• 1.1 Summary of Changes
• 1.2 Background
• 1.3 Description of Changes
• 1.4 Impact on States
• 1.5 Input Record Specifications
• 1.6 Screen Changes
• 1.7 Error Code

PART 2.0
Automate the Fee Reimbursement Report Sent to the States (FOP1490)

• 2.1 Summary of Changes
• 2.2 Background
• 2.3 Description of Changes
• 2.4 Impact on States
• 2.5 Fee Reimbursement Report

PART 3.0
Do Not Reject State Payment When Payment Amount Exceeds the Offset Amount Minus the Adjustment Amount for Prior Years (FOP 1026)

• 3.1 Summary of Changes
• 3.2 Background
• 3.3 Description of Changes
• 3.4 Impact on States

PART 4.0
Transaction Detail Enhancements - No State Impact (FOP 1165, 1491 and 1493)

• 4.1 Summary of Changes
• 4.2 Background
• 4.3 Description of Changes
• 4.4 Impact on States
• 4.5 Screen Changes

APPENDICES

1. Input Record Specifications
2. Screens
3. Fee Reimbursement Report
4. Error Code

CHARTS

• Chart A-1: Case Submission and Update Record LayoutA-2
• Chart D-1: Rejected Case Submission and Update Error Codes

• This field is required for all Transaction Types. This field must contain a valid, two-character, alphabetic state abbreviation code for the submitting State. Refer to Appendix H, "State and Territory Abbreviations; Country Codes", for a list of these codes.
• For Transaction Types 'B', 'C', 'D', 'L', 'M', 'R', 'S', 'T' and 'Z', all key fields (Submitting State Code, SSN, Case Type Indicator) must match key fields on the OCSE Case Master File in order for the transaction to be processed. If there is no match, the transaction will be rejected.

• For Transaction Type 'A' (Add/Recertify Case), the local code submitted is compared against the state's Local Code File. If the local code contains spaces or is not found, the local code for the case will be set to zeros on the OCSE Case Master File, and a local code of zeros will be submitted for the case to FMS.
• For Transaction Type 'L', if the local code submitted contains spaces, the local code for the case will be set to zeros on the OCSE Case Master File, and a local code of zeros will be submitted for the case to FMS. Otherwise, the local code that is submitted is compared against the state's Local Code File. If the local code is not found, the transaction will be rejected.
• For all other Transaction Types ('B', 'C', 'D', 'M', 'R', 'S', 'T' and 'Z'), the local code, if present, will not be updated at OCSE or FMS.

• For Transaction Type 'A' (Add/Recertify Case) the SSN is verified using an SSA-defined range check that automatically validates the area portion of the SSN (the first three positions of the SSN) against the current high digit being used for area. In addition, the group portion of the SSN (the fourth and fifth positions of the SSN) is compared against the area to ensure that the group number was issued with the particular area number. To verify the current high digits for area and group issued by SSA, refer to Chart D-3, "Useful Web Sites".
• For Transaction Types 'B', 'C', 'D', 'L', 'M', 'R', 'S', 'T' and 'Z', all key fields (Submitting State Code, SSN, and Case Type Indicator) must match key fields on the OCSE Case Master File in order for the transaction to be processed. If there is no match, the transaction will be rejected.

• For Transaction Type 'A' (Add/Recertify Case), if present, OCSE will store the field on the Case Master File without performing any edits. This field is not sent to FMS or DoS.
• For all other Transaction Types ('B', 'D', 'L', 'M', 'R', 'S', 'T' and 'Z'), the Case ID, if present, will not be updated at OCSE.

• For Transaction Types 'A' (Add Case) and 'B' (Name Change), the entire last name is stored on the OCSE Case Master File after the last name passes the edit check above.
• For Transaction Types 'C', 'D', 'L', 'M', 'R', 'S', 'T' and 'Z', the first 4 characters submitted must match the first four characters that are stored on the OCSE Case Master File or the first four characters of a Transaction Type 'B' (Name Change) transaction for the same case in the same process. If there is no match, the transaction will be rejected.
• For Transaction Type 'A' (Recertify Case), if the last name does not match against the OCSE Case Master File, the name is processed as a name change.

• For Transaction Types 'A' (Add Case) and 'B' (Name Change), the entire first name is stored on the OCSE Case Master File after the first character passes the edit check above.
• For Transaction Type 'A' (Recertify Case), the first character must pass the edit above. The obligor first name is not matched against the first name stored on the OCSE Case Master File; the entire first name is stored on the OCSE Case Master File.
• For all other Transaction Types ('C', 'D', 'L', 'M', 'R', 'S', 'T' and 'Z'), the obligor first name, if present, will not be updated at OCSE or FMS.

• For Transaction Type 'A' (Add/Recertify Case), the arrearage amount is the current amount owed by the obligor. If the arrearage amount is less than $25, the Add Case transaction will be rejected.
• For Transaction Type 'D', this field is not required. However, the existing arrearage amount will be zeroed out.
• For Transaction Type 'M', the arrearage amount is the current amount owed by the obligor. If the arrearage amount is equal to zero, the case will be flagged as deleted.
• For Transaction Type 'S', this field functions as the Accumulated Payment Amount Field, and is referred to by that name. The accumulated payment amount is the accumulated State Payment Amount for the processing year.
• For all other Transaction Types ('B', 'C', 'L', 'R', 'T' and 'Z'), the arrearage amount, if present, will not be updated at OCSE or FMS.

• This field is required for all Transaction Types. This field must contain one of the following valid case type codes:
  A TANF
  N Non-TANF
• For Transaction Types 'B', 'C', 'D', 'L', 'M', 'R', 'S', 'T' and 'Z', all key fields (Submitting State Code, SSN, and Case Type Indicator) must match key fields on the OCSE Case Master File in order for the transaction to be processed. If there is no match, the transaction will be rejected.

• For Transaction Type 'T', This field must contain a valid, two-character, alphabetic State abbreviation code for the transfer State. Refer to Appendix H, "State and Territory Abbreviations; Country Codes", for a list of these codes.
• For all other Transaction Types ('A', 'B', 'C', 'D', 'L', 'M', 'S', 'Z' and 'R'), this field, if present, will not be updated at OCSE.

• For Transaction Type 'T', this field should contain a three-position, alphanumeric local code for the transfer state. If present, this field is stored on the OCSE Case Master File.
• For all other Transaction Types ('A', 'B', 'C', 'D', 'L', 'M', 'R', 'S' and 'Z'), this field, if present, will not be updated at OCSE.

• For Transaction Type 'S', this field must be in the format of CCYY, and must contain the year the tax refund or administrative payment was offset. The date must fall within the previous seven years of the current year.
• For all other Transaction Types ('A', 'B', 'C', 'D', 'L', 'M', 'R', 'T' and 'Z'), this field, if present, will not be updated at OCSE.

• For Transaction Types 'A' (Add Case) and 'Z' (Address Change), this field contains the first address line of the obligor's mailing address. If this line is blank, the Obligor Address Line2 Field will be checked for an address (refer to Part 3, "Federal Offset Program Pre-Offset Notices", for information regarding address processing).
• For Transaction Type 'Z' (Address Change), Obligor Address Line 1, Obligor Address Line 2, Obligor City, Obligor State, and Obligor Zip Code cannot all be spaces.
• For Transaction Type 'A' (Recertify Case), this field is not required. If present, the address currently stored at OCSE will be updated with the submitted address.
• For all other Transaction Types ('B', 'C', 'D', 'L', 'M', 'S', 'R' and 'T'), the address, if present, will not be updated at OCSE or FMS.

• For Transaction Types 'A' (Add Case) and 'Z' (Address Change), this field may contain the second address line for the obligor. On an Add Case, if OCSE sends the Pre-Offset Notices and no address information is submitted in either address line, OCSE will attempt to obtain an address (refer to Part 3, "Federal Offset Program Pre-Offset Notices", for information regarding address processing).
• For Transaction Type 'Z' (Address Change), Obligor Address Line 1, Obligor Address Line 2, Obligor City, Obligor State, and Obligor Zip Code cannot all be spaces.
• For Transaction Type 'A' (Recertify Case), this field is not required. If an address is present, the address currently stored at OCSE will be updated with the submitted address.
• For all other Transaction Types ('B', 'C', 'D', 'L', 'M', 'S', 'R' and 'T'), the address, if present, will not be updated at OCSE or FMS.

• For Transaction Types 'A' (Add Case) and 'Z' (Address Change), this field contains the city of the obligor's mailing address (refer to Part 3, "Federal Offset Program Pre-Offset Notices", for information regarding address processing).
• For Transaction Type 'Z' (Address Change), Obligor Address Line 1, Obligor Address Line 2, Obligor City, Obligor State, and Obligor Zip Code cannot all be spaces.
• For Transaction Type 'A' (Recertify Case), this field is not required. If an address is present, the address currently stored at OCSE will be updated with the submitted address.
• For all other Transaction Types ('B', 'C', 'D', 'L', 'M', 'S', 'R' and 'T'), the address, if present, will not be updated at OCSE or FMS.

• For Transaction Types 'A' (Add Case) and 'Z' (Address Change), this field contains a two-character, alphabetic State abbreviation code for the State of the obligor's mailing address (refer to Part 3, "Federal Offset Program Pre-Offset Notices", for information regarding address processing).
• For Transaction Type 'Z' (Address Change), Obligor Address Line 1, Obligor Address Line 2, Obligor City, Obligor State, and Obligor Zip Code cannot all be spaces.
• For Transaction Type 'A' (Recertify Case), this field is not required. If an address is present, the address currently stored at OCSE will be updated with the submitted address.
• For all other Transaction Types ('B', 'C', 'D', 'L', 'M', 'S', 'R' and 'T'), the address, if present, will not be updated at OCSE or FMS.

• For Transaction Types 'A' (Add Case) and 'Z' (Address Change), this field contains a 5 or 9 digit zip code (refer to Part 3, "Federal Offset Program Pre-Offset Notices", for information regarding address processing).
• For Transaction Type 'Z' (Address Change), Obligor Address Line 1, Obligor Address Line 2, Obligor City, Obligor State, and Obligor Zip Code cannot all be spaces.
• For Transaction Type 'A' (Recertify Case), this field is not required. If an address is present, the address currently stored at OCSE will be updated with the submitted address.
• For all other Transaction Types ('B', 'C', 'D', 'L', 'M', 'S', 'R' and 'T'), the address, if present, will not be updated at OCSE or FMS.

• For all other Transaction Types ('B', 'C', 'D', 'L', 'M', 'S', 'R', 'T' and 'Z'), the date issued, if present, will not be updated at OCSE or FMS.

• For Transaction Types 'A' (Add/Recertify Case) and 'R', this field is optional. If setting more than one exclusion indicator, the indicators must be separated with a comma or space (e.g., RET, PAS, FIN, or RET PAS FIN). Valid exclusion indicators are:
  ADM Exclude all Administrative Offsets (RET, SAL, VEN)
  RET Exclude Federal Retirement Offset
  VEN Exclude Vendor Payment/Miscellaneous Offset
  SAL Exclude Federal Salary Offset (not yet activated)
  TAX Exclude Tax Refund Offset
  PAS Exclude Passport Denial
  FIN Exclude Multistate Financial Institution Data Match
  Space Remove all existing exclusion indicators
• For all other Transaction Types ('B', 'C', 'D', 'L', 'M', 'S', 'T' and 'Z'), this field, if present, will not be updated at OCSE or FMS.