11 code 025 status check
Status Code Check - Code 025
Note: Prior to performing this edit, the MI28 program will check three date fields (the liability, end-of-liability, and reactivation dates). If the liability and end-of-liability dates are identical, and the reactivation date is blank, or earlier than this date (which produces a Code 024 error), then the account is assumed to have been added in error, so the status code is set to a ‘2’. If the EOL date is equal to the reactivation date, then an inactivation is assumed to be incorrect, so the status is set to ‘1’. When the EOL date is set to the first date of the quarter, and all employment and wages are zero/missing for the quarter, then the status code is changed to a ‘2’ here as well, as long as the reactivation date is either missing or earlier than the EOL date.
This edit checks the processed and prior quarter’s status code fields for valid values. These include ‘1’ (active), ‘2’ (inactive), and ‘9’ (pending future activation). If any other value shows in the status code field, the account is flagged for the respective quarter. Invalid status codes should be a physical impossibility for the EXPO system, since there is no means available (on-line or batch) within the system for applying an invalid status code.
Note: An establishment with an invalid status code is eligible for all edit processing, whereas those with a non-active (‘2’ or ‘9’) status may skip over many if not most of the standard micro edits due to their inactivity.
This is a crucial edit, which will prevent the edit flag from being set until the status code has been set to a legitimate value. The status code will be underscored in the edit exception report, or auxiliary edit report, in program ES2UT23. This is a “gross” error condition, if the employer is large enough. BLS classification: A.1.3 or B.1.4, depending on size of establishment. EXPO “G” code: A025 or B025.
Related Links
