Skip to main content
Skip table of contents

LA Transparency Portal Reports (Act 370)

Louisiana Act 370 (enacted in 2023) mandates that public school systems report detailed financial data, including budgets, audits, expenditures, and contracts, and submit it to the Louisiana Department of Treasury. Beginning FY 2024–25, semiannual reports must be submitted. This led to the launch of the School Transparency Project Portal on March 31, 2025, offering public, searchable access to K‑12 financial data statewide. It empowers citizens, educators, and policymakers to hold school systems accountable and make informed comparisons.

Menu path

From the Fund Accounting menu, select State. From the State menu, select LA Transparency Portal Reports (Act 370).

Submission period

  • For the period from July 1st to December 31st, the report must be submitted by March 31st.

  • For the period from January 1st to June 30th, the report must be submitted by September 30th.

Selection rule

Expenditure data for the fiscal year and period is selected and reported.

Prerequisite

Complete the Setup procedures.

Setup

Perform the following setup procedure before creating the LA Transparency Portal Reports (Act 370) report.

  1. On the LA Transparency Portal Reports (Act 370) page, select Setup.

  2. Refer to the Field descriptions and enter or select valid information.

  3. Select Accept.

Field descriptions

The following table describes the fields on the LA Transparency Portal Reports (Act 370) - Setup page.

Field

Description

Site Code

The unique identifier for the school site.

Site Description

The description of the school site.

Fund

The fund organization level.

  • In the Organizational Level field, select the district organization chart/accounting level for the fund.
    The Organization/Account Level must be the number representing the level on the organization chart or account as defined on the Fund Accounting Profile page. Organization levels will be one more than the organization number. For example, orgn2 = level 3. The titles of the organization levels are retrieved from the titles set up on the Titles tab of the Fund Accounting Profile page.
    The values in the drop-down are retrieved from the Titles tab of the Fund Accounting Profile page. The values also include the 1st, 2nd, and 3rd sub-accounts.

  • In the Starting Position field, enter the starting position of the organization chart/accounting level for the fund in the accounting structure.

  • In the Ending Position field, enter the ending position of the organization chart/accounting level for the fund in the accounting structure.

For more information, refer to the Fund Classifications section in the Louisiana Accounting and Uniform Governmental Handbook.

Function

The function organization level.

  • In the Organizational Level field, select the district organization chart/accounting level for the function.
    The Organization/Account Level must be the number representing the level on the organization chart or account as defined on the Fund Accounting Profile page. Organization levels will be one more than the organization number. For example, orgn2 = level 3. The titles of the organization levels are retrieved from the titles set up on the Titles tab of the Fund Accounting Profile page.
    The values in the drop-down are retrieved from the Titles tab of the Fund Accounting Profile page. The values also include the 1st, 2nd, and 3rd sub-accounts.

  • In the Starting Position field, enter the starting position of the organization chart/accounting level for the function in the accounting structure.

  • In the Ending Position field, enter the ending position of the organization chart/accounting level for the function in the accounting structure.

For more information, refer to the Function Codes section in the Louisiana Accounting and Uniform Governmental Handbook.

Object

The object organization level.

  • In the Organizational Level field, select the district organization chart/accounting level for the object.
    The Organization/Account Level must be the number representing the level on the organization chart or account as defined on the Fund Accounting Profile page. Organization levels will be one more than the organization number. For example, orgn2 = level 3. The titles of the organization levels are retrieved from the titles set up on the Titles tab of the Fund Accounting Profile page.
    The values in the drop-down are retrieved from the Titles tab of the Fund Accounting Profile page. The values also include the 1st, 2nd, and 3rd sub-accounts.

  • In the Starting Position field, enter the starting position of the organization chart/accounting level for the object in the accounting structure.

  • In the Ending Position field, enter the ending position of the organization chart/accounting level for the object in the accounting structure.

For more information, refer to the Object Codes section in the Louisiana Accounting and Uniform Governmental Handbook.

Maintain Crosswalk data

Use the LA Transparency Portal Reports (Act 370) - Crosswalk page to maintain crosswalk data for district-level data items that do not precisely match the state-level data items used by the Louisiana Department of Treasury.

For each district-level data item, there are three possible crosswalk setup scenarios:

  1. One district-level data item exactly matches one state-level data item. No crosswalk entry is needed.

  2. One district-level data item maps to a different state-level data item. Add a record for that data item. For example, if the fund designated '1110' by the state is called 'R1110' by the district, you crosswalk fund R1110 to state fund 1110.

  3. Multiple district-level data items map to a single state-level data item. Add a record for each district-level data item that rolls up into the state-level data item. For example, if the district has funds 2000 and 2001, and then both roll up to the state-level fund 2000, you must add two records – one record mapping district fund 2000 to state fund 2000 and another record mapping district fund 2001 to state fund 2000.

Once used, the same district-level code can’t be used again. But the state-level code can be mapped to multiple district-level codes.

If errors are encountered while creating the report, you can correct the source data on the LA Transparency Portal Reports (Act 370) - Crosswalk page.

PowerSchool recommends that you correct the report’s source data that is retrieved from the Core application.

To maintain the crosswalk data, do the following:

  1. On the LA Transparency Portal Reports (Act 370) page, select Crosswalk.

  2. Enter the Search Criteria to find the required Crosswalk records, and then select Search.
    Refer to Search for records for more information.

    • To add a record, select Add new. Refer to Field descriptions, enter valid information, and select Accept.

    • To edit a record, select the record and select Accept. Update the information and select Accept.

    • To delete, select Delete, and then Yes.

    • To generate a report, select Print, and then select a Destination:

      • Select File to create the report in .rpt format. The default file name is la370xwalk.rpt. You can change the default file name.

      • Select Screen to download the report in .pdf format. The default file name is la370xwalk.pdf.

      • Select Excel to download the report in .xls format. Select the required Excel Options. The default file name is la370xwalk.xls.

        • Select OK.

          • Download the .rpt file from the View Files page.

          • Save the .pdf or .xls file.
            For more information about the Print option, refer to Print Reports.

Field descriptions

The following table describes the fields on the LA Transparency Portal Reports (Act 370) - Crosswalk page.

Field

Description

Data source and Valid values

Crosswalk Year

The fiscal year of the crosswalk data.

Not applicable

Crosswalk Type

The type of crosswalk.

Valid values:

  • Fund

  • Function

  • Object

PowerSchool ERP Code

The local code used in the application.

Select the Lookup icon to search for and select a fund, function, or account.

The records on the Fund/Function/Account Search page are retrieved from the Organization Chart page.

State Code

The corresponding state code defined by the Louisiana Department of Treasury.

For a list of valid values, refer to the Louisiana Accounting and Uniform Governmental Handbook.

Copy

Use the LA Transparency Portal Reports (Act 370) - Crosswalk - Copy page to copy crosswalk data from one year to another. You must perform this procedure when transitioning to a new fiscal year.

  1. On the LA Transparency Portal Reports (Act 370) - Crosswalk page, select Copy.

  2. Select the Fiscal Year to Copy From and Fiscal Year to Copy To.

  3. Select Accept and then Yes.

If data for the selected Fiscal Year to Copy To exists, you must purge the crosswalk data before using the Copy option.

Purge

Use the LA Transparency Portal Reports (Act 370) - Crosswalk - Purge page to purge the crosswalk data if data for the selected Fiscal Year to Copy To exists. After purging the data, you can use the Copy option.

  1. On the LA Transparency Portal Reports (Act 370) - Crosswalk page, select Purge.

  2. Select the Fiscal Year.

  3. Select Accept, and then Yes.

Maintain Descriptions data

Use the LA Transparency Portal Reports (Act 370) - Descriptions page to maintain Louisiana state code descriptions.

If errors are encountered while creating the report, you can correct the source data on the LA Transparency Portal Reports (Act 370) - Descriptions page.

PowerSchool recommends that you correct the report’s source data that is retrieved from the Core application.

To maintain the description data, do the following:

  1. On the LA Transparency Portal Reports (Act 370) page, select Descriptions.

  2. Enter the Search Criteria to find the required Description records, and then select Search.
    Refer to Search for records for more information.

    • To add a record, select Add new. Refer to Field descriptions, enter valid information, and select Accept.

    • To edit a record, select the record and select Accept. Update the information and select Accept.

    • To delete, select Delete, and then Yes.

    • To generate a report, select Print, and then select a Destination:

      • Select File to create the report in .rpt format. The default file name is la370xwalk.rpt. You can change the default file name.

      • Select Screen to download the report in .pdf format. The default file name is la370xwalk.pdf.

      • Select Excel to download the report in .xls format. Select the required Excel Options. The default file name is la370xwalk.xls.

        • Select OK.

          • Download the .rpt file from the View Files page.

          • Save the .pdf or .xls file.
            For more information about the Print option, refer to Print Reports.

Field descriptions

The following table describes the fields on the LA Transparency Portal Reports (Act 370) - Descriptions page.

Field

Description

Data source and Valid values

Fiscal Year

The fiscal year of the description data.

Not applicable

Description Type

The type of description.

Valid values:

  • Fund

  • Function

  • Object

State Code

The corresponding state code defined by the Louisiana Department of Treasury.

For a list of valid values, refer to the Louisiana Accounting and Uniform Governmental Handbook.

Title

The title of the state code defined by the Louisiana Department of Treasury.

For a list of valid values, refer to the Louisiana Accounting and Uniform Governmental Handbook.

Description

The description of the state code defined by the Louisiana Department of Treasury.

Not applicable

Import

Use the File Import and Data Selection - Import L.A.U.G.H. Descriptions page to import description data from the Louisiana Accounting and Uniform Governmental Handbook (L.A.U.G.H.). The import file is in .csv format and stored on your computer.

Use the Import Wizard

The Import option launches the import wizard that will take you step by step through:

  • Loading the file.

  • Mapping the columns in the file to the fields in the database table.

  • Mapping static columns required by the Import option, but not defined in the file.

  • Saving the mapping that was created to be used for future file imports.

  • Generating a list of warnings and error messages found during the data validation.

Import file requirements

Your ability to import a file depends on the following:

  • The data in the file's fields must comply with the field requirements for description records. For example, the system cannot import the file if a field requires numeric data and the import file contains characters.

  • The import file must be in Comma Separated (CSV) format.

  • The import file's extension must be *.csv.

  • You must have the appropriate security resource to access the Import item.

Create the import file

For information about the recommended import file layout and data mapping, refer to Import Descriptions - File Layout and Data Mapping.

Import file

  1. On the LA Transparency Portal Reports (Act 370) - Descriptions page, select Import.

  2. To locate the file you want to import from your computer or network, select Click to upload a file beside the File to Import field.

  3. Select the file, and select Open to display the path and file name in the File to Import field.

  4. Select Load.

  5. In the Import File Data section, select the line to use for Column Titles and select Set Column Titles. The selected data appears in the section's column headings.
    If you selected the incorrect line, select Reset Column Titles to reinstate it in the list, then repeat the step with the correct line selected.

  6. Once the column titles are set, select the lines to import from the file.

    • To select a range of lines, hold down the Shift key, select the first line in the range, and then select the last line.

    • To select multiple lines individually, hold down the Ctrl key and select each line.

    • To select all lines, select Select All.

  7. After selecting the lines, select Next.

  8. On the Define Column Mapping page:
    Select a mapping in the Saved Import Mapping field.
    or
    Tab into the Table Field column for the first Import File Column, and select the file column from the database table to map to the column listed in the Import File Column field on the left. Refer to Import Descriptions - File Layout and Data Mapping for information about column data mapping.
    The Field Description column defaults to the column's user-friendly name and cannot be changed. Map the remaining fields accordingly.

  9. Select Next.

    • If the data in the file does not meet the requirements of the database table, the Import Errors page will display. You cannot proceed until either the file or the mapping is corrected.

    • If there are no errors but some required fields from the database are not mapped, the Static Column Value Mapping page displays. Complete Steps 10-11.

    • If there are no errors and all required fields are mapped, proceed to Step 12.

  10. On the Static Column Value Mapping page, the required fields from the database table that were not mapped on the Define Column Mapping page will display. Add values as needed. To add other fields that have not been mapped, select Append Row.

  11. Once the static mapping is complete, select Next.

  12. On the Save Import Mapping page, enter a unique name to identify the mapping, and then:

    1. In the Mapping Name field, enter a unique mapping name. The Owner field displays the user name of the person importing the file. You cannot update this field.

    2. You can select the Public option to allow others to use the mapping file or the Restricted option to prevent others from changing it.

    3. Select the required Save Options:

      • Select Create new mapping to create a new mapping file under the name assigned.

      • Select Update existing mapping to save changes to an existing mapping file. This option is unavailable when creating a new mapping file or when changing the file is restricted.

      • Select Do not save mapping only to use the mapping for the current file.

      The ability to add and update an import mapping on the Save Import Mapping page depends on the assigned security resources.

  13. Select Finish to exit the Import wizard.

  14. From the Confirmation box, select one of the following:

    • Select Update/Add to update description records. Existing records are updated if they match the import file. Otherwise, the record from the import file is added.

    • Select Replace to replace description records. This option requires a complete description import file.

    • Select Cancel to abort the import.

  15. After the file is imported, the Import Status page displays if any errors or warnings are encountered during data validation. The page lists the errors and warning messages.

    • From the Display Results field, select one of the following:

      • Warnings Only

      • Errors Only

      • Warnings/Errors Only

      • Show All

    • The Line # column lists the line numbers in the import file to find the data requiring correction.

    • The Summary Information section displays the number of Errors, Warnings, and Successes. At this point, you can:

      • Select Print to print the listing of errors.

      • Select Import on the Action Bar to import any successes. If there are no successes, this item will not display.

      • Select Back to exit, correct the file, and re-run the import procedure.

  16. If there are no errors or you selected the Import option in the last step, a Confirmation box will display. Select Yes to import the file and generate a final Confirmation. Select OK.

Field descriptions

The import wizard consists of the following pages:

File Import And Data Selection page

Use this page to initiate the Import wizard and select the file and records to import.

The following table describes the fields on the File Import And Data Selection page.

Field

Description

File to Import

Location and name of the file on your computer or network server.

Line #

Identifies the line in the file to be imported.

Column 1 - Column 100

Identifies the column headings for the import file.

Define Column Mapping page

Use this page to map the columns in the file to be imported to the fields in the database table.

The following table describes the fields on the Define Column Mapping page.

Field

Description

Saved Import Mapping

Lists the mapping you created or mappings set to public.

After a saved mapping is selected, the table field mapping defaults to the Column Mapping section of the page.

Import File Column

Lists the Column Titles set on the File to Import Data Selection page.

Table Field

Lists the table and field names from the database table.

Select the field you want to map to the Import File Column.

Field Description

The user-friendly name for the value in the Table Field column.

This field is display-only.

Import Errors page

Use this page to view a list of errors when the data in the file does not match the fields' requirements in the database table.

The following table describes the fields on the Import Errors page.

Field

Description

Line #

Identifies the line in the file to be imported.

Import File Column

Lists the Column Titles set on the File to Import Data Selection page.

Table Field

Lists the table and field names from the database table.

Value

Displays the data in the field generating the error.

Error Message

Error message explaining why the value does not meet the database's requirements.

Static Column Mapping page

Use this page to statically map required fields in the database table to a value. The values apply to all lines of the imported file.

The following table describes the fields on the Static Column Mapping page.

Field

Description

Table Field

Lists the table and field names from the database table that have not been mapped on the Define Column Mapping page.

Required fields will default in this field. Non-required fields can be added by selecting Append Row.

Field Description

The user-friendly name for the value in the Table Field column.

This field is display-only.

Value

Displays the value used for all rows in the import file.

Save Import Mapping page

Use this page to save the mapping and enter related settings.

The following table describes the fields on the Save Import Mapping page.

Field

Description

Mapping Name

Accepts a unique name for identifying the mapping.

The limit is 38 characters.

Owner

Identifies the user who created the mapping.

When a user updates the mapping, the user's ID, date, and time are displayed beside this field.

This field is display-only.

Public

Indicates whether all users can access the mapping.

The mapping will appear in the Saved Import Mapping field of the Define Column Mapping page.

If this option is not selected, only the owner can access the mapping.

Restricted

Indicates whether all users except the owner are prevented from updating the mapping.

If this option is not selected, all users can update the mapping.

Save Options

Indicates how the mapping should be saved.

Options:

  • Create new mapping
    Creates a new mapping file under the name assigned.

  • Update existing mapping
    Saves changes to an existing mapping file. It is not available when creating a new mapping file, or changing it is restricted.

  • Do not save mapping
    Only use the mapping for the current import file.

Import Status page

Use this page to view errors and warning messages generated while validating the import's data.

The following table describes the fields on the Import Status page.

Field

Description

Number of Errors

Displays the count of errors found during validation that will prevent the data from being imported.

This field is display-only.

Number of Warnings

Displays the count of warnings found during the data validation. Warnings will not prevent the data from being imported.

This field is display-only.

The Number of Successes field displays the count of successes found during the data validation.

This field is display-only.

Display Results

Allows you to specify the records to display in the page's list and the Import Status report.

Options:

  • Show Errors Only
    Only shows the errors preventing lines from being imported.

  • Show Warnings Only
    Only shows the warning messages.

  • Show Errors/Warnings Only (default)
    Shows errors and warning messages.

  • Show All
    Shows errors, warning messages, and successes.

Indicator

Displays symbols for identifying warnings, errors, and successes.

Line #

Identifies the lines in the file to be imported.

Status

Displays the errors and warning messages generated during data validation.

Also displays successes if Show All is selected in the Display Results section.

Purge

Use the LA Transparency Portal Reports (Act 370) - Descriptions - Purge page to purge the description data for a selected year.

  1. On the LA Transparency Portal Reports (Act 370) - Descriptions page, select Purge.

  2. Select the Fiscal Year.

  3. Select Accept, and then Yes.

Create file

Use the LA Transparency Portal Reports (Act 370) page to specify the report criteria and create the report file.

  1. On the LA Transparency Portal Reports (Act 370) page, refer to the Field descriptions and enter or select the report and additional criteria.

  2. Select Accept.

  3. If errors are found, select the Destination for the error log:

    • Select File to save the error log in .rpt format. In the File Name field, enter a path and file name.

    • Select Screen to save the error log in .pdf format.

    • Select Excel to save the error log in .xls format. Select the required Excel Options.

  4. Select OK.

  5. Review the error report, make the necessary corrections, and then repeat this procedure.

  6. If no errors are found, proceed to step 7.

  7. Select OK and save the file.

  8. Navigate to the folder containing the report file.

  9. Inspect the file. Refer to Maintain Crosswalk data and Maintain Descriptions data, and update the data if necessary.

  10. Repeat these steps until all the required data is included.

The default file name is la370.xlsx.

For information about the report’s file layout, refer to LA Transparency Portal Reports (Act 370) - File Layout and Data Mapping.

Follow the state's submission procedures.

Field descriptions

The following table describes the fields on the LA Transparency Portal Reports (Act 370) page.

Field

Description

Fiscal Year

The fiscal year of the expenditure data to be reported.

Period

The period within the fiscal year to be reported.

Transaction Codes

The transaction codes to include in the report.

Leave this field blank to include all transaction codes.

State Code Formatting

The format for the state code data.

Excluded Funds

The fund codes to exclude from the report.

Enter the excluded fund codes as a pipe-delimited list. You can use wildcards (* or ?) and character ranges such as [0-9] or [A-Z].

Excluded Functions

The function codes to exclude from the report.

Enter the excluded function codes as a pipe-delimited list. You can use wildcards (* or ?) and character ranges such as [0-9] or [A-Z].

Excluded Objects

The object codes to exclude from the report.

Enter the excluded object codes as a pipe-delimited list. You can use wildcards (* or ?) and character ranges such as [0-9] or [A-Z].

Excluded Transaction Descriptions

The transaction description codes to exclude from the report.

Enter the excluded transaction description codes as a pipe-delimited list. You can use wildcards (* or ?) and character ranges such as [0-9] or [A-Z].

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.