Versions Compared

Old Version 4

changes.mady.by.user Muriel Marable (Unlicensed)

Saved on

compared with

New Version 5

changes.mady.by.user Muriel Marable (Unlicensed)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Contents

Table of Contents

Summary

With the Data Standard v4.0-a release, a number of changes were introduced to the Finance Domain. The new Finance API is aligned with common accounting standards and reporting standards in the K–12 education space. The primary sources include:

...

Building on the example above, the following listing shows a hypothetical school district's mapping to an SEA's account for teacher salaries. In this example, the LEA is mapping its fine-grained account for Language Arts - Literature teacher salaries to the SEA's more general account for regular curriculum teacher salaries.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16

{
  "id": "336108d6468f43408388221bde5c639c",
  "accountIdentifier": "LEA16-10-100-122300",
  "chartOfAccountReference": {
    "accountIdentifier": "10-100-120000",
    "educationOrganizationId": 1,
    "fiscalYear": 2020
  },
  "educationOrganizationReference": {
    "educationOrganizationId": 16
  },
  "accountName": "Regular Curriculum - Language Arts - Literature",
  "reportingTags": [
    { "reportingTagDescriptor": "uri://state-agency-example.edu#LEA-Superintendent-Report" }
  ]
}

Items of note from this example:

  • Similar to the SEA example, this LEA has reflected its account dimensions in the accountIdentifier, prefixed by an identifier for the district (LEA16-10-100-122300). Same deal as the SEA: the API doesn't require or enforce any particular pattern, it's up to the SEA and its LEAs to define a convention that works best for their environment.
  • Platforms implementing this API (including the Ed-Fi ODS / API) will require a valid chartOfAccountReference from the LEA. This ensures every LEA account maps to exactly one SEA account.