What are some examples of possible reporting due dates?

After the initial registration deadline of March 1, 2015, entities will have some flexibility to select a date that most easily accommodates the entities’ workloads to comply with the requirement to update information reported on the portal every year on or before December 1. 


Uploading on the Deadline

Here is an example for an entity with a fiscal year-end of September 30, 2015, who completes their annual audit on June 15, 2016, including a timeline for submitting information to the portal that would satisfy the requirements:

  • September 30, 2015: Fiscal year ends
  • December 1, 2015: This is the deadline for updating registry information. The following information should be available:
    • Any changes to the administrative information of the entity.
    • The most recently adopted budget should be for the fiscal year ending September 30, 2016.
    • An unaudited budget to actual comparison should be available for the fiscal year ended September 30, 2015.
    • The amount of bonds and other debt outstanding, the average length of terms, and the average interest rate of all debt obligations should be available from the audited financial statements for the fiscal year ended September 30, 2014.
  • June 15, 2016: The audit of fiscal year 2015 is completed and can be uploaded to the portal.
  • September 30, 2016: The fiscal year ends and the cycle begins again.

Uploading Before the Deadline

Reporting does not have to be on December 1 each year. The requirements state that the information must be updated on or before December 1 each year, which allows local governing entities to update their information on a schedule that is convenient for them.

Many local governing entities may find it most convenient to update the portal information once per year when they upload their audit reports. Using the same information as in the previous example, a local governing entity may choose a different timeline that would also satisfy the requirements:

  • September 30, 2015: Fiscal year ends.
  • December 1, 2015: The deadline for updating registry information. If your initial registry information has been entered by March 1, 2015, and the information is still accurate, then your 2015 reporting requirements have been satisfied.
  • June 15, 2016: The audit of fiscal year 2015 is completed and can be uploaded to the portal. The following information should also be available for reporting to meet the December 1, 2016 reporting requirement:
    • Any changes to the administrative information of the entity.
    • The most recent adopted budget for the fiscal year ending September 30, 2016.
    • The most recent fiscal year end is September 30, 2015, and the audit report should contain audited budget to actual amounts. The requirements are for unaudited amounts, but many entities may be more comfortable reporting audited amounts which also satisfy the requirements.
    • The amount of bonds and other debt outstanding, the average length of terms, and the average interest rate of all debt obligations should be available from the audited financial statements for the fiscal year ended September 30, 2015.
  • September 30, 2016: The fiscal year ends and the cycle begins again.

Show All Answers

1. Why are we creating a registry portal?
2. What is required under Idaho Code 67-450B and C?
3. Why was additional legislation introduced in the 2014 legislative session?
4. What are the new requirements in House Bill Number 560 codified in Idaho Code Section 67-450E?
5. What are local governing entities required to do?
6. What will be on the registry portal?
7. What are some examples of possible reporting due dates?
8. How are the Legislative Services Office and counties affected?
9. What penalties are in place for noncompliance with the requirements included in Idaho Code Section 67-450E?
10. What items are needed prior to registering an entity?