<strong>Federal</strong> <strong>Award</strong> <strong>Findings</strong>, <strong>Questioned</strong> <strong>Costs</strong> <strong>and</strong> <strong>Corrective</strong> <strong>Action</strong> <strong>Plan</strong>(Reformatted from FY 2009 Single Audit Report)In addition, DBME is revising the screening <strong>and</strong> processing of the federal tax information to improve theeffectiveness of the information <strong>and</strong> make the process more efficient. DBME expects to implement the newprocess by December 2010.09-112TANF Cluster:CFDA No.: 93.558 Temporary Assistance for Needy Families, #s G0802AZTANF <strong>and</strong> G0902AZTANFU.S. Department of Health <strong>and</strong> Human Services<strong>Award</strong> Period: October 1, 2007 through September 30, 2008October 1, 2008 through September 30, 2009Reporting<strong>Questioned</strong> Cost: N/AFindingCriteria: In accordance with 45 CFR §§265.7(b)(1) <strong>and</strong> 265.7(b)(3), the data reported on the quarterly TANF DataReport must be complete <strong>and</strong> accurately reflect information available in case records, financial records, <strong>and</strong>automated data systems. In addition, in accordance with 45 CFR §265.9(c)(5), the average monthly total numberor the total number of eligible families served for which maintenance of effort (MOE) expenditures are claimed atfiscal year-end must be reported on the Annual Report on State Maintenance-of-Effort Programs.Condition <strong>and</strong> context: The Department of Economic Security did not accurately prepare its quarterly TANF DataReports <strong>and</strong> Annual Report on State Maintenance-of-Effort Programs. Specifically, the Division of Benefits <strong>and</strong>Medical Eligibility’s Family Assistance Administration did not accurately report child care <strong>and</strong> work participationdata on the TANF Data Report. While performing test work, auditors noted for 4 of 24 items tested, the child caredata reported did not agree to the child care information tracking system. In addition, the Division of Business <strong>and</strong>Finance’s Policy <strong>and</strong> <strong>Plan</strong>ning Administration did not include 5,396 families in the total number of familiesserved under the TANF program with MOE expenditures reported on the Annual Report on State Maintenanceof-EffortPrograms during fiscal year 2009 for the Jobs Program line item.Effect: Incorrect data was submitted to the federal government. This finding is a significant deficiency in internalcontrol over compliance <strong>and</strong> noncompliance with the Cluster’s reporting requirements.Cause: The Family Assistance Administration did not extract updated child care data before compiling the TANFData Report. In addition, the Policy <strong>and</strong> <strong>Plan</strong>ning Administration did not have procedures to perform reviews onits Annual Report on State Maintenance-of-Effort Programs.Recommendation: The Family Assistance Administration should extract updated child care data to correspondwith the TANF Data Report submission dates. In addition, the Policy <strong>and</strong> <strong>Plan</strong>ning Administration should requiresupervisors to review reports <strong>and</strong> underlying data prior to submission of the Annual Report on State Maintenanceof-EffortPrograms.Agency Response: ConcurContact persons: Leona Hodges, DBME Deputy Assistant Director, (602) 542-7596 <strong>and</strong> Kathy Waite, Policy& <strong>Plan</strong>ning Administration Administrator, (602)-542-3882Anticipated completion date: Various, for anticipated completion dates see corrective action plan belowAgency <strong>Corrective</strong> <strong>Action</strong> <strong>Plan</strong>: To ensure Temporary Assistance to Needy Families (TANF) Data Reports areprepared accurately, the Division of Benefits <strong>and</strong> Medical Eligibility (DBME) identified the programming errorthat resulted in the incorrect childcare data. DBME will initiate a program change to correct this coding issue byDecember 2010.16
<strong>Federal</strong> <strong>Award</strong> <strong>Findings</strong>, <strong>Questioned</strong> <strong>Costs</strong> <strong>and</strong> <strong>Corrective</strong> <strong>Action</strong> <strong>Plan</strong>(Reformatted from FY 2009 Single Audit Report)The Policy <strong>and</strong> <strong>Plan</strong>ning Administration (PPA) receives client count information from the various Departmentprograms utilizing TANF funds <strong>and</strong> inputs the data into the final report format for submittal to Health <strong>and</strong> HumanServices, Administration for Children <strong>and</strong> Families (HHS/ACF). PPA will ensure all programs that submit datafor the report are provided an opportunity to review the final report prior to submission to HHS/ACF. The reviewprocess will utilize a final sign-off by the designated responsible person in each program area. By doing so, eachprogram area will ensure that the numbers being used in the report are accurate. This corrective action will beeffective with completion of the 2010 Annual TANF Maintenance of Effort (MOE) Report (ACF 204), onDecember 31, 2010. PPA will submit a corrected ACF 204, Attachment B, to HHS/ACF no later than July 1,2010.09-113CFDA No.: 93.563 Child Support Enforcement, #s G0804AZ4004 <strong>and</strong> G0904AZ400493.563 ARRA—Child Support Enforcement, #G0904AZ4002U.S. Department of Health <strong>and</strong> Human Services<strong>Award</strong> Period: October 1, 2007 through September 30, 2008October 1, 2008 through September 30, 2009Special Tests <strong>and</strong> Provisions<strong>Questioned</strong> Cost: N/AFindingCriteria: In accordance with 45 CFR §§302.33, 303.2(b), 303.4(d), <strong>and</strong> 303.7(b)(2), the Department of EconomicSecurity is required to establish support obligations, process interstate cases, <strong>and</strong> open a case within specific timeframes.Condition <strong>and</strong> context: The Department of Economic Security, Division of Child Support Enforcement, did notalways follow its internal control policies <strong>and</strong> procedures to ensure compliance with special tests <strong>and</strong> provisionsrequirements for establishing support obligations, processing interstate cases, <strong>and</strong> establishing new cases. For 3 of53 cases tested, the Division did not refer the noncustodial parent to the Office of the Attorney General or pursueother actions to establish a child support order within 90 days after it located the noncustodial parent. Specifically,one case was never referred to the Office of the Attorney General, one case was referred after 245 days, <strong>and</strong> onecase was initially referred in 41 days but was returned for missing information <strong>and</strong> the missing information wasnot provided until 81 days later. In addition, for 1 of 10 cases tested, the Division never referred an interstate IV-D case to the applicable state’s interstate central registry for action after it determined the noncustodial parent wasin a different state. Finally, for 6 of 77 cases tested, the Division failed to establish new cases within 20 days afterreceiving a case referral or an application. Specifically, the Division took between 24 <strong>and</strong> 155 days to completethis process.Effect: Failure to meet the time frames specified by the federal regulations could result in delays in providingfinancial support to the custodial parents. This finding is a material weakness in internal control over compliance<strong>and</strong> material noncompliance with the Child Support Enforcement <strong>and</strong> ARRA—Child Support Enforcementprogram’s special tests <strong>and</strong> provisions requirements.Cause: The Division did not always follow its policies <strong>and</strong> procedures to check work lists to ensure that caseswere processed within the specified time frames.Recommendation: The Division should ensure that case workers check the work lists on a regular basis or developother means to notify the case worker of critical due dates.This finding was similar to a prior-year finding.17
- Page 1 and 2: Federal Award Findings, Questioned
- Page 3 and 4: Federal Award Findings, Questioned
- Page 5 and 6: Federal Award Findings, Questioned
- Page 7 and 8: Federal Award Findings, Questioned
- Page 9 and 10: Federal Award Findings, Questioned
- Page 11 and 12: Federal Award Findings, Questioned
- Page 13 and 14: Federal Award Findings, Questioned
- Page 15: Federal Award Findings, Questioned
- Page 19 and 20: Federal Award Findings, Questioned
- Page 21 and 22: Federal Award Findings, Questioned
- Page 23 and 24: Federal Award Findings, Questioned
- Page 25 and 26: Federal Award Findings, Questioned
- Page 27 and 28: Federal Award Findings, Questioned
- Page 29 and 30: Federal Award Findings, Questioned
- Page 31 and 32: Federal Award Findings, Questioned
- Page 33 and 34: Federal Award Findings, Questioned
- Page 35 and 36: Federal Award Findings, Questioned
- Page 37 and 38: Federal Award Findings, Questioned
- Page 39 and 40: Federal Award Findings, Questioned
- Page 41: Federal Award Findings, Questioned