Reporting Requirements

What is required of an ANA Recipient regarding reporting?

This page provides an overview of the reporting requirements for ANA Recipients. Recipients are usually expected to submit the following reports:

• Ongoing Progress Report (semi-annually, via Online Data Collection (OLDC)/GrantSolutions)
• Annual Data Report, if applicable (annually, via Online Data Collection (OLDC)/GrantSolutions)
• SF-425 Federal Financial Report-FFR (Semi Annually, Annual and Final, via Grant Solutions or Payment Management Systems)
  • If awarded in 2016 and forward submit this report online via Division of Payment Management’s Payment Management System (PMS)
  • If awarded earlier, then submit as a Grant Note in Grant Solutions, using the following naming convention: Correspondence-SF425-Q2, Q4, Annual (or) Final-YYYY
• SF-428 Tangible Personal Property Report (Final, via GrantSolutions)-submit as a Grant Note using the following naming convention: Correspondence-SF-428-Final-YYYY

Please note that reporting requirements are provided in recipients’ Notice of Award (NOA). ANA Program Specialists also provide this guidance when they conduct introductory calls, reminders during the Monthly call with the ANA Commissioner, and as part of our monthly e-mails to recipients. For the most up to date information, or if you have any questions, please contact your Program Specialist or e-mail ANAComments@acf.hhs.gov.

Ongoing Progress Report (OPR)

This is an OMB approved form used by ANA recipients to report semi-annual project progress. The submission of timely OPRs is a requirement of all grant awards and is one of the most important factors taken into consideration when deciding to continue grant funding. ANA program specialists review these reports against the approved application’s Objective Work Plan and budget and track the implementation of your project. Recipients that are late on these required reports or delayed in implementing the project will jeopardize continuation funding. Furthermore, consistent delinquency can result in actions taken by ANA, such as requiring reporting on a more frequent basis or changing the award to reimbursement rather than advance.

The GrantSolutions Grants Management Module (GMM) and Online Data Collection (OLDC) provide a convenient way for recipients to submit their Ongoing Progress Report (OPR). Recipients use the OLDC system to enter, validate, certify, submit, and retrieve information pertinent to their OPR. Note: In order to initiate the OPR, the Objective Work Plan (OWP) must first be available in the system. Please email or call your ANA point of contact with any questions.

Guidance on how to complete the OPR in the Online Data Collection System (PDF) (View disclaimer page here).

In what format should you send your OPRs?

ANA utilizes the Online Data Collection System (OLDC) through GrantSolutions (grantsolutions.gov ) for the submission of your OPR. To submit your OPR please go to GrantSolutions to access your grant file. Once you have gained access to your grant, please click on the Online Data Collection on the top horizontal tool bar.

What information is required?

Each report must provide a project status on all funded objectives, milestone activities, and outputs. The OPR must also indicate if any staff were hired for the project, project challenges and financial tracking.

Recipients must respond to ALL questions listed on the form before submitting.

When do you submit OPRs?

The OPRs are due semi-annually, 30 days after the end of each reporting period of the budget period (every three months).

Reporting Due Dates are outlined in the charts below.

Annual Data Report (ADR)

In addition to the Ongoing Progress Report, some ANA recipients are required to report project progress using the Annual Data Report (ADR) to report project data once a year and at the end of the project period.

• ADR Instructions
• Sample ADR (Please note: This Annual Data Report is a sample report)

Reporting Due Dates are outlined in the charts below.

Federal Financial Reports (FFR) SF-425

In what format should you send your financial reports?

For recipients award in 2016 and forward, please submit your financial reports via the PMS website .

If awarded earlier than 2016, recipients must use the SF-425 Form  Visit disclaimer page. The form must be signed by the Authorized Organizational Representative listed on the Notice of Award (NOA). (View disclaimer page) and uploaded as a grant note in GrantSolutions.

What information is required?

The form requires recipients to report on information, such as the federal and non-Federal share outlays, the unobligated balance, and any program income. Please view the PMS website for more information.

When do you submit FFR-SF-425s?

Semi Annual financial reports are due 30 days after the end of each reporting period of the budget period (every three months).

Annual financial reports are due 90 days after the end of the second-semi annual report of each project year.

A final SF-425 is due 90 days after the end of the project period. It must be marked as the final report in section #6 of the form. Section #9 must cover the entire project period.

Reporting Due Dates are outlined in the charts below.

SF‐428 and SF 428B Tangible Personal Property Reports

SF‐428 and SF 428B Tangible Personal Property Reports   Visit disclaimer page are fully completed if equipment (unit cost of $5,000 or more) was purchased with ANA funding during the project. 

If the project has no property to report, this report still needs to be completed and write N/A on the form.

Forms will need to be uploaded to the Notes section of GrantSolutions using the following naming conventions: SF428-Final-YYYY.

Reporting Deadlines

Reports are due 30 days after the end of each reporting period of the budget period. Annual reports are due 90 days after the end of the budget period.

For Budget Periods of July 1 to June 30 

For Budget Periods of September 30 to September 29

Failure to complete timely reports may be cause to disapprove future funding for Non-competing continuation (NCC) awards.