Page Comparison

#

Property Name

Data Type

Public (Required/ Optional/ Conditional)

Choice (Required/ Optional/ Conditional)

Business Definition

1.0

accountIdentifierAccountIdentifier

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

34.0

educationOrganizationIdEducationOrganizationId

integer

REQ'D

NOT REQ'D

The LEA ID or the School ID

45.0

FiscalYear (under the chartOfAccountReference)

integer

REQ'D

NOT REQ'D

Fiscal The 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)

the account

6.0

AccountName

string

OPT

NOT REQ'D

The descriptive name given to an account

67.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

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:
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:

• [Fund-Type-Location-Object or Source-Function-Program/Project]

• 10-E-000-100-110000-000 / Salaries

  • AccountType remains same as DPI 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

Sending the LEA locat accoutn 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:

• [Fund-Type-Location-Object or Source-Function-Program/Project]

• 10-R-000-100-000000-000 / State Equalization Aid

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:

• Fund-Type-Location-Object or Source-Function-Program/Project]

• 10-R-800-621-500000-000 / State Aid Equalization account

POST on /localAccount:
accountIdentifier: 10R800621500000000
fiscalYear: 2020
chartOfAccountReference:
accountIdentifier: 10R000621000000000
educationOrganizationId: 48856
fiscalYear: 2020
educationOrganizationReference:
educationOrganizationId: 1302

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:

• 10-E-800-581-221250-400

• Essa: Exclusion

• ProjectProgram: FedPerkins
  

POST on /localAccount:
accountIdentifier: 10E800581221250400
accountName: Instructional Technology Hardware
fiscalYear: 2020
chartOfAccountReference:
accountIdentifier: 10E000581221250000
educationOrganizationId: 48856
fiscalYear: 2020
educationOrganizationReference:
educationOrganizationId: 3166
reportingTags:
reportingTagDescriptor: uri://dpi.wi.gov/reportingTagDescriptor#ProjectProgram
tagValue: FedCharters
reportingTagDescriptor: uri://dpi.wi.gov/reportingTagDescriptor#Essa
tagValue: Exclusion