WI DPI WISEdata Ed-Fi Docs
/localAccounts
Jaidaa Shafaei
Data Properties:
# | 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. |
Use Cases:
# | Use Case Title | Use Case Description | What to Submit/retrieve |
|---|
# | Use Case Title | Use Case Description | What to Submit/retrieve |
|---|---|---|---|
1.0 | Sending local accounts at the school-level | LEAs may submit local accounts that exactly map to the rolled up DPI chart of accounts when they don’t submit granular-level chart of accounts. DPI expects LEAs to submit Actuals and Budgets to the Local Account which is referenced to the DPI chart of account. For the local accounts chosen to be submitted at the school-level, the educationOrganizationId would be the 'School ID', and the school-level local account would roll up to DPI WUFAR chart of accounts on /localAccounts | POST on /localAccount: |
2.0 | Sending local accounts at the district-level | For the local accounts chosen to be submitted at the district-level, the educationOrganizationId would be the 'LEA ID', and the location code is 000 in that 18 digit string | POST on /localAccount: |
3.0 | Sening the LEA local account more granular than the DPI chart of accounts | The Object or Source can be submitted at more granular level than DPI chart of account. Example : DPI CHART OF ACCOUNT:
LOCAL ACCOUNT:
| POST on /localAccount: |
4.0 | Sending the LEA local account with any Function beginning with 5 | Local accounts with Function beginning with 5 should be mapped to 000000. Example : DPI CHART OF ACCOUNT:
WUFAR defines function 500000 as “district-wide” that is still used by some districts in revenue accounts. In order to validate local account functions are consistent with reporting accounts, we need to make sure that any 5xxxxx function is mapped to reporting function 000000. LOCAL ACCOUNT:
| POST on /localAccount: |
5.0 | Sending reporting tag for local accounts | LEAs should be able to submit the local account identifier with an ESSA tag as Exclusion or ProjectProject tag along with associated Project dimension. See this document for more samples. Example: LOCAL ACCOUNT:
| POST on /localAccount: |
JSON Sample:
{
"chartOfAccountReference": {
"accountIdentifier": "80B000000939900000",
"educationOrganizationId": 48856,
"fiscalYear": 2023,
},
"educationOrganizationReference": {
"educationOrganizationId": 7533,
},
"accountIdentifier": "50B000111456000000",
"fiscalYear": 2020,
"accountName": "TEST Finance API",
"reportingTags": [{
"reportingTagDescriptor": "uri://dpi.wi.gov/reportingTagDescriptor#S"
}],
}
Wisconsin Department of Public Instruction