01. System Assigned Reject Codes.

1. A receipt distributing to arrears with a processing Type of LOT, WAG, OWA, REG, IFC, STO, or UIB suspends under the SADR reject code when the case has an Open Administrative Review status.
1. An Open Administrative Review Status is:
1. The ADRD (Administrative Review Detail) screen is in Open status.
2. The Administrative review was requested by the NCP.
1. The Review Requested By field on ADRD will display NCP.
2. Only arrears amounts will suspend under SADR.  Any distribution to current support in the receipt’s SRD month will release automatically before the arrears amount is routed to suspense.
3. Upon completion of the Administrative Review, the case worker conducting the administrative review updates the ADRD screen with the date the review is completed.  The suspended receipts will release through overnight batch processing when on the ADRD screen:
1. The Status Code equals ARC (Admin Review Completed).

1. Payments with a Processing Type of REG, IFC, STO, or BND will suspend under the SALL reject code when the Payor is an NCP in more than one case, and that NCP does not designate which case to post the payment to.  An IRS and FAO payment will also suspend under the SALL Reject Code when the NCP has multiple HLCI numbers.  The IRS or FAO payment will then post to the first case associated to the first HLCI identified to the NCP's SSN.
1. Case Worklist Item F0001 (Susp Item (SALL); Allocate NCP Payment) is added to the case when a payment with a REG, IFC, STO or BND Processing Type suspends under SALL.  
2. The Case Worklist Item is manually purged after the payment is allocated.
3. CAAL Narrative F0785 (IRS/FAO payment could not be posted to NCP multi cases) is added to the case when an IRS or FAO payment suspends under SALL.  The CAAL Narrative is added to the case that the payment posted to
4. Upon identification of this code, and the payment is not an IRS or FAO, the obligor must be contacted to ensure that the payment is posted to the correct case.
1. When the obligor has been contacted previously, and there is a pattern of consistency to the allocation of payments, add CAAL Narrative M3918 (Comments to DCSS Staff) detailing the contact with the obligor or the historic allocation history.
2. When the payment is an IRS or FAO, review the certification balances on the cases for the NCP and allocate the payment.
5. A PAAR (Payment Adjustment) request is added when it’s determined how to allocate the payment. 

3. A receipt (other than IRS or DOR) suspends under the SBKR reject code when a BADE (Bankruptcy Detail) screen displays that the NCP is under an active Chapter 11, 12, or 13 bankruptcy status.  Any current support amount due in the receipt’s SRD month will distribute and disburse.  Any distribution to arrears will suspend.
1. Receipts do not suspend when the NCP is under Chapter 7 bankruptcy status.
2. Case Worklist Item F0002 (Suspense Item (SBKR); NCP is Bankrupt) is assigned to the caseworker.  The worklist item is manually purged after the receipt is allocated.
3. When the BADE End Date is less than today’s date, the receipt will automatically release from suspense and distribute to the case.
4. It is the Attorney General’s responsibility to complete and maintain the BADE screen status.

4. A receipt suspends under the SCLS reject code when the case is in Closed Status.  Case Worklist Item F0003 (Susp Item (SCLS) Pmt on a Closed Case) is assigned to the caseworker.  This worklist item is manually purged after the receipt is distributed or refunded.
1. When the current support obligation is still due and it is an Arizona order, notify the SDU PIE Unit to move the receipt to the Non IV-D case.
1. When the Non IV-D case needs to be opened on ATLAS, send the FCSE0001 F0410 001 (Notification of Change of Case Status: IV-D/Non IV-D) form to the court in the county where the order was entered.
2. Notify the SDU with a SURE request stating the Non IV-D case number in the Comments field.
2. When itappears that the payment may have been posted in error to the wrong case, notify the SDU PIE Unit research the payment.
1. Add CAAL Narrative F0037 (AZ payment Error) to the case.  Write the Payment ID or Check Number of the receipt that needs to be researched.  Briefly explain why you think that it was posted to the wrong case.
2. CAAL Narrative F0038 (AZ Payment error – caseworker notified) is added by the PIE Unit when they begin their research.  CAAL Narrative F0039 (AZ Payment Error Resolved) is added by the PIE Unit when the issue is resolved.
3. When the support obligation has ended the payment is refunded.
1. Refund to the NCP when the NCP is the source of the payment.
2. Refund to the other jurisdiction when they are the source of the payment.  Notify the other jurisdiction that the case is closed.

1. A receipt (except for IRS and DOR tax offsets) suspends under the SCOB reject code when during the disbursement process an out of balance or illogical CP Ledger/Case Program code condition exists and ATLAS cannot determine how to disburse the payment. 
2. There are several situations where this might happen.  The more prominent conditions are:
1. The CP Ledger arrears do not agree with the case program code.
2. When a receipt distributes to an IDI debt arrears, it must also disburse to the CP Ledger arrears.  The CP Ledger arrears that it disburses to must agree with the receipt’s SRD month case program code algorithm.

Note: When a child on one of the CP’s cases is a Benefit Cap child, the Benefit Cap Unpaid support amount is included in the total Unpaid Monthly balance, and the Benefit Cap arrears are part of the Never Arrears balance.

1. When there aren’t any CP Ledger arrears balances that agree with the case program code algorithm, the receipt suspends under SCOB.  As an example, if the receipt distributed to arrears on a CAI case, but only Never Assigned arrears exist, it suspends under SCOB.
2. The following procedures help determine and correct the out of balance condition.
1. Do a CP Ledger calculation to ensure that the CP Ledger balances are correct.
2. When corrections to the CP Ledger need to be made, add a DEHA request to do a ‘net zero’ adjustment to correct the balances.  The beginning month of the DEHA request must be equal to the suspended receipt’s SRD month.
3. When the CP Ledger balances need to be increased or decreased, but the debt balances do not, notify the Help Desk to correct the appropriate CP Ledger balances.
4. When the Case Program code is incorrect, add a DEHA request to move the CP Ledger balances immediately after the program code is corrected.  The CP Ledger arrears must agree with the new case program code.
2. The total Unpaid Monthly Accrual amount from all of the IDI debts doesn’t equal the Unpaid Monthly balance on the CP Ledger.
3. There are two unpaid monthly amounts that must equal each other on ATLAS, the NCP Debt and CP Ledger unpaid monthly amount.
1. When the amount distributed to the NCP Unpaid Monthly Amount is greater or lesser than the CP Ledger Unpaid Monthly balance, the entire receipt will suspend under SCOB.

Note: The balance in the Unpaid Monthly Accrual field on Panel One of the DEHA screen is the unpaid monthly accrual balance for the displayed debt.  The balance in the Current field on Panel Two of the DEHA screen is the sum of the unpaid monthly CP Ledger accrual balances from all of the cases that the CP is involved with.

2. Add the total Unpaid Monthly Amount balances from all of the IDI Debt Type CCH and CSP Obligations from DEHA (if the receipt has a prior month SRD) or DEDN if the SRD is in the current month.  The IDI debts from all of the CP’s suffixes must be added together.  This total is compared to the Current field amount on Panel Two of DEHA.
3. When the total Unpaid Monthly balances on all of the IDI Debt type CCH and CSP obligations from all of the CP’s cases does not equal the Current field amount from Panel Two of DEHA, notify the Help Desk to correct the Current field amount to match the total of the NCP’s debt unpaid monthly amount.
4. The Benefit Cap Unpaid amount on DEHA is included in the Unpaid Monthly DEHA balance.  Out of balance problems are often due to the Benefit Cap Unpaid amount being incorrect.
3. The NCP’s arrears are less than or greater than the CP Ledger arrears.
1. This out of balance SCOB condition occurs when a receipt distributes to the IDI Debt arrears and they are not equal to the CP Ledger Account balances.  This out of balance condition can be from principal interest, principal arrears, or both.
2. When the receipt’s SRD is in the current month, sum the debt balances by viewing each IDI Debt Type’s DEDN screen.
1. You must look at all of the CP’s suffixes when adding the debt arrears.
3. When the receipt’s SRD in a prior month, display the DEHA record from each of the IDI Debt Type debts from that SRD month.
4. Compare the sum of the arrears to the CP Ledger balance on CPAS for the SRD month.
1. Do a CP Ledger calculation to ensure that the CP Ledger Account balances are correct. 
2. When the CP Ledger balances are wrong, notify the Help Desk to correct the CP Ledger with the amount needed to correct the out of balance condition.

1. A receipt suspends under the SDBT reject code when all of the debts on the case are in an Inactive Status.
1. Review on the CAAL (Case Activity List) and DEDR (Debt Deactivation) screens and the case file record why the debts were inactivated.
1. When the debts are inactive because the support obligation has ended and the case is going to be closed, refund the payment to the obligor.
2. When the payments are from another jurisdiction, refund the payment to that jurisdiction.  Notify the other jurisdiction that the case is being closed.
2. When the debts are inactive because the CP has withdrawn from IV-D services but the support obligation still exists, review if there is a Non IV-D case.
1. When a Non IV-D case exists, notify the SDU PIE Unit with a SURE request to move the money to the Non IV-D case.
2. A Non IV-D case is set up when the support obligation still exists and the underlying order is an Arizona order.

1. A receipt suspends under the SDNO reject code when no debts exist on the case.
1. Obtain all court orders from the CP, the Clerk of Court (check the Non IV-D ATLAS system to see if a court order exists), or the initiating jurisdiction.
1. When a payment is posted to an Intake case and an ATLAS Non IV-D case exists for the same case participants, release the money from suspense by copying the Non IV-D court order information to the IV-D SUOD screen and set up a debt for the current support amount.  Calculate arrears upon receipt of the actual order.
2. When the CP provides court order information but there is no copy of the order available, contact the appropriate Clerk of Court and verify the information given by the CP.  Set up a debt for current support only to release the payment from suspense. Calculate arrears upon receipt of the court order.
3. When the payment was received after the court order sign date, add a PAAR (Payment Adjustment) request to change the SRD to match the effective date of the accruing DEDN child support debt.
2. When the payment has a WAG Processing Type, and no order exists, logon to iDOC Store to research if the payment was posted in error. If payment posted in error, submit a PIE request to the SDU PIE Unit via GearUp.
1. Add the F0037 (AZ Payment Error) CAAL Narrative. State which receipt is being researched.
3. When an order does not exist, the payment Processing Type is REG, and the receipt is posted to the correct case, set up a Voluntary Debt with an effective date equal to the first day of the month of the payment’s SRD.

1. A payment posted to a case with a Payment Type of FAS (Financial Asset Seizure) will be held in Suspense for 15 calendar days under the SFAS suspense reject code.
1. FAS payments are those received from financial institutions from Financial Asset Seizure Enforcement actions.
2. The payments are automatically released from suspense to distribute to the case after 15 calendar days.
3. The Financial Institution Data Match Team (FIDM) can release SFAS receipts before or after 15 calendar days when appropriate.
1. The FIDM Team is the only entity that can manually release SFAS receipts.
2. The FIDM Team changes the release date on SFAS receipts by modifying the Release Date field on the SULI screen.
3. Activity Code E9493 (FIDM Payment Release Date Change) is added to the case when the FIDM Team changes the FAS Payment Release Date.

1. A receipt suspends under the SFTO reject code when there is an accruing monthly support obligation but the unpaid support and arrears balance in the current month is zero.
2. The SFTO receipts are evaluated daily to determine if the receipt can distribute to the unpaid support amount or arrears.
3. If the debts are changed to non-accruing with no arrears balances, the SFTO receipt will change to the SROP suspense status.

1. A receipt suspends under the SFTR reject code when a “Y” is entered in the Seasonal Employment field of the NCJD (NCP Job Detail) screen and the amount of the receipt is greater than the current monthly amount.
1. The receipt will be distributed by ATLAS the following month.

1. A receipt suspends under the SINC reject code when one of the following conditions exist on the case.
1. The receipt distributes to an accruing IDI Debt Type with a **O case program code.
1. An accruing IDI Debt Type can only distribute money when the case program code is **I.
2. When the SRD of the receipt is a prior month, you must look at the case program code for that month.
1. When the accruing debt is an IDI Debt Type in the SRD month, but the case program is **O today, the receipt will suspend under SINC.
3. Complete the following steps before changing the case program code from **I to **O to avoid SINC situations.
1. Release from suspense all receipts with an SRD prior to the effective case program change date.
2. Perform debt maintenance on all IDI Debt Types so that only state assigned arrears are left.  This must be done for all months on and after the case program change date through the current month.
3. Change the case program code to **O.
4. Set up ODO debts including not assigned arrears moved from the IDI debt.  The effective date of the ODO debts must be the same month as the **O case program change date.
2. The receipt distributes to an accruing ODO Debt Type with a **I case program code.
1. An accruing ODO Debt Type can only distribute money when the case program code is **O.
2. When the SRD of the receipt is a prior month, you must review the case program code for that month.
1. When the accruing debt is an ODO Debt Type in the SRD month, but the case program is **I today, the receipt will suspend under SINC.
3. Complete the following steps before changing the case program code from **O to **I to avoid SINC situations.
1. Release from suspense all receipts with an SRD prior to the effective case program change date.
2. Change the case program code to **O.
3. Add a new accruing IDI Debt.
3. The receipt distributes to an ODO debt and there is no Open INCM record.
1. On the INCM screen the Intrst Case Nbr (Interstate case Number) field must display the other state’s case number, and the Status field must display “O” for Open.
4. The receipt distributes to an ODO debt and the Open INCM record doesn’t match the State and Jurisdiction FIPS Code numbers (the first five digits of the FIPS code) on the DEDN screen.
1. On Panel Two of DEDN, the Pay to Jurisdiction & Address FIPS State and County field values must match the INCM screen State and County FIPS code values.
5. The receipt distributes to an ODO debt but INCM record doesn’t have an Intergovernmental Case number.
1. The case worker must obtain the correct case number and update the Intergovernmental Case Nbr field of the INCM screen with that case number.
2. When the case number is not available, enter the obligor’s social security number in the Intergovernmental Case Nbr field.  Do not enter dashes or other special characters.
6. When the SINC conditions are corrected, add a SURE request to release the receipt from suspense.

1. Payments received with a payment status of Identified (I), Refunded (R), Non-sufficient funds-NSF (N), or Previously Unidentified (P) will be evaluated according to the SLCK process.
2. A payment of $2, 500.00 or greater suspends under the SLCK suspense code if the payment type is one of the following:
1. Business Check (BCH)
2. Personal Check (PCH)
3. Electronic Funds Transfer (EFT)
4. Pay by Phone ACH Account (PBA)
5. Pay by Phone Credit Card (PBC)
6. Point of Sale ACH Account (POA)
7. Point of Sale Credit Card (POC)
8. Travelers Check (TCH)
9. Web Credit ACH Account (WBA)
10. Web Credit Card (WBC)
3. A payment of $2,500.00 or greater will not suspend under the SLCK process if in the past 60 days three or more payments have posted to the case from the same payer with the same payment type and amount. The payments cannot be identified as a NSF check or refunded. These monies are released immediately.
4. IRS and DOR incoming payments do not suspend under the SLCK code. These payments are available immediately.
5. The system will auto release the payment after it has been holding for 10 business days. 5 business days if the payment type is EFT.
6. The SDU staff review payments suspended under the SLCK code daily to determine if there are any “guaranteed” form of payments holding to determine if they can be immediately released as long as there are no other payment issues causing concern.
7. If a payment needs to be considered for early release, a request needs to be sent to SDU-Suspense at [email protected] with the following subject: Please Review For Early Release SLCK CS#0000000000-00. Upon SDU approval, payments will release with a SURE request.

1. A receipt suspends under the SRDS reject code when a programming error was unable to release the payment.
1. SRDS suspended receipts are often caused by a PAAR (Payment Adjustment) error.
2. SRDS receipts are released by the System’s and Automation Help Desk. Advise the Help Desk of any actions that might have been taken prior to the receipt suspending under SRDS”

1. A receipt suspends under the SROP reject code when the support debts are not accruing and there is no principal or interest arrears balance for the support debts in the current month.
2. To determine how to process the SROP receipts, the debts are reviewed to see if balances exist in the current month, if the debt should be accruing, or if the receipts should be refunded.
1. Use the DRU on-line calculator to calculate the obligation’s arrears balance to see if an error exists in the debt arrears balance.
1. When a calculation of the case results in a determination that a balance exists on the debt(s), correct the debt balance with a DEHA request.  When the arrears amounts are corrected, the receipt will move to the SFTO suspense status and will distribute to the current month balances the following day.
2. When the court order is a foreign order, contact the other state to obtain an arrears balance.
2. Determine if the debt should be accruing.
1. Review the emancipation dates of the children on the case to determine if the debt should be accruing.  If the children have not emancipated, review the court orders to determine if an order had stopped the monthly obligation.
3. Overpayment Processing.
1. When a review of the case results in a determination that all of the debts have been paid and that the debt should not be accruing, the payment can be deemed a true overpayment and can be refunded.

1. A receipt suspends under the SRPC reject code when the receipt’s SRD is prior to the case open date.
1. When the case was previously closed in error, and there is an existing support obligation, notify the Help Desk to change the case open date.
1. Policy must add a CAAL Narrative approving the change to the case open date.
2. When the case open date is changed, a new debt will need to be added based on the order with an effective date equal to the first day of the month of the payment’s SRD.
2. When the case was opened because of a IV-A interface, the case open date must equal the date that the CP assigned their support rights.
3. When the payment was received after the court order sign date, add a PAAR (Payment Adjustment) request to change the SRD to match the effective date of the accruing DEDN child support debt.

1. A receipt suspends under the SUOP reject code when the UI payment amount is greater than the submitted amount.
1. The UI submitted amount is displayed on the UIHD screen.
2. The SUOP suspense receipts are researched and released by the SDU FiRST Team.

1. Payments suspend under the SLEA suspense code when the case is logged into the AGO or when AG staff determine that only current support amounts should distribute to the case.   Payments for arrears suspend under SLEA when panel two of the CAAS screen is completed as follows.
1. The Legal intake field must have a date entered.
2. The Hold Payments field is blank or displays a C.
3. The Legal Out Date field is blank.
2. Amounts for current are distributed to the case.
3. Payments are released from the SLEA suspense code when a date is entered in the Legal Out Date field on panel two of the CAAS screen by AG staff or when AG staff change the Hold Payments field on panel two to A or N.
1. AG staff must notify the Debt Team if debt work is needed or if they should release the payments from suspense.
2. When AG staff change the Hold Payments field from C or blank to N,  ATLAS will automatically move the receipts to the SLED suspense code without needing a SURE request.  
3. When AG staff change the Hold Payments field from C or blank to A,  ATLAS will automatically move the receipts to the SLEC suspense code without needing a SURE request.  
4. When a date is entered in the CAAS Legal Out Date field, receipts held under SLEA will move overnight to the SLED suspense code by ATLAS.
4. CAAL Narrative M5187 (CAAS Hold Payment Field Modified) is added to the case automatically by ATLAS when the Hold Payments field value is changed.

1. Payments suspend under the SLEC suspense code when AG staff determine that the entire amount of the receipt should be suspended.  Payments for current and arrears suspend under SLEC when panel two of the CAAS screen is completed as follows.
1. The Legal Intake must have a date entered.
2. The Hold Payments field displays an A.
3. The Legal Out Date is blank.
2. Amounts for current and arrears suspend under SLEC.
3. Payments are released from the SLEC suspense code when a date is entered in the Legal Out Date field on panel two of the CAAS screen by AG staff or when the Hold Payments field on panel two is changed to C or N.
1. AG staff should notify the Debt Team if debt work is needed.
2. When AG staff change the Hold Payments field from A to C, ATLAS will automatically move the amount of the receipt for arrears to the SLEA suspense code without needing a SURE request.
3. When AG staff change the Hold Payments field from A to N, ATLAS will automatically move the amount of the receipts for arrears to the SLED suspense code without needing a SURE request.
4. When a date is entered in the CAAS Legal Out Date field, receipts held under SLEA will move overnight to the SLED suspense code by ATLAS.  
4. CAAL Narrative M5187 (CAAS Hold Payment Field Modified) is added to the case automatically by ATLAS when the Hold Payments field value is changed..

1. Payments held under the SLEA or SLEC suspense code move to the SLED suspense code by ATLAS when a date is entered on the Legal Out Date field on panel two of the CAAS screen.
1. The Debt worker must review to see if debt work is needed on the case.
2. The Debt worker must add a SURE request to release a payment from the SLED suspense code.
3. The SURE Request will require an AUD Request Reason.