You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 5
Next »
Data Properties:
Click here to view all data properties under the /localAccounts endpoint:
# | 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 | chartOfAccountReference.AccountIdentifier | string | REQ'D | NOT REQ'D | valid WUFAR 18 digit account string same as COA |
3.0 | educationOrganizationId | integer | REQ'D | NOT REQ'D | The LEA ID or the School ID |
4.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) |
5.0 | AccountName | string | OPT | NOT REQ'D | The descriptive name given to an account |
6.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 |
Use Cases:
Click here to view all the use cases pertaining to the /localAccounts endpoint:
# | Use Case Title | Use Case Description | What to Submit/retrieve |
---|
1.0 | Sending local accounts at the school-level | 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: accountIdentifier: 10E200120110000141 fiscalYear: 2020 chartOfAccountReference: accountIdentifier: 10E000100110000000 educationOrganizationId: 48856 fiscalYear: 2020 educationOrganizationReference: educationOrganizationId: 2730 |
---|
| 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: accountIdentifier: 10E800230251100000 fiscalYear: 2020 chartOfAccountReference: accountIdentifier: 10E000230251100000 educationOrganizationId: 48856 fiscalYear: 2020 educationOrganizationReference: educationOrganizationId: 6826 |
---|
| 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: Fund-Type-Location-Object or Source-Function-Program/Project] 10-E-001-165-110020-000 / 2nd grade licensed teacher salary 10-E-001-175-110020-000 / 3rd grade classroom teacher salary
| POST on /localAccount: accountIdentifier: 10E100165110020000 fiscalYear: 2020 chartOfAccountReference: accountIdentifier: 10E000100110000000 educationOrganizationId: 48856 fiscalYear: 2020 educationOrganizationReference: educationOrganizationId: 2730 |
---|
| | | |
---|
JSON Sample:
Click here to view view the JSON sample for posting the /localAccounts endpoint:
{
"chartOfAccountReference": {
"accountIdentifier": "80B000000939900000",
"educationOrganizationId": 48856,
"fiscalYear": 2020,
},
"educationOrganizationReference": {
"educationOrganizationId": 7533,
},
"accountIdentifier": "50B000111456000000",
"fiscalYear": 2020,
"accountName": "TEST Finance API",
"reportingTags": [{
"reportingTagDescriptor": "uri://dpi.wi.gov/reportingTagDescriptor#S"
}],
}
0 Comments