# | Property Name | Data Type | Public (Required/ Optional/ Conditional) | Choice (Required/ Optional/ Conditional) | Business Definition |
1.0 | AccountIdentifier | string | REQ'D | NOT REQ'D | LEA's load their granular or rolled set of accounts valid and mapped to valid Chart Of accounts generated as per WUFAR |
2.0 | FiscalYear | integer | REQ'D | NOT REQ'D | Fiscal year for which the COA is in effect for LEA accounting and reporting (e.g. 2020 for fiscal year 2020, the 2019-2020 school year) |
3.0 | AccountIdentifier | string | REQ'D | NOT REQ'D | valid WUFAR 18 digit account string same as COA |
4.0 | EducationOrganizationId | integer | REQ'D | NOT REQ'D | The LEA ID or the School ID |
5.0 | FiscalYear (under the chartOfAccountReference) | integer | REQ'D | NOT REQ'D | The fiscal year for the account |
6.0 | AccountName | string | OPT | NOT REQ'D | The descriptive name given to an account |
7.0 | ReportingTagDescriptor | string | OPT | NOT REQ'D | A ReportingTagDescriptor will be collection to denote the ESSA reporting, project/program tags, etc. The original purpose behind Project/Program Tags is to provide districts with flexibility if they use DPI-defined project codes for other purposes. There are only two cases where use of Project/Program Tags is required: non-DPI grants, and DPI-assigned project codes used for other local purposes.
For more information, visit https://dpi.wi.gov/sfs/wisedata-finance-using-project-codes-tags |