Before You Start
-
Confirm you have completed the FAS configuration in the following order: Configure Full Account Structure.
-
Ensure the Fund Accounting Profile – Titles tab labels match the levels you use in Account Components and Organization Chart.
-
If your site uses Full Account Format, the Translation table must be configured for the fiscal year and match your full-account mask.
The following section explains the system errors that can occur and how to resolve them.
-
Translation table (trans_acct) validation fails, or the full account won't parse
-
The segment code is missing when building the key organization
-
Payroll or HRM distribution errors (key organization / account)
"Organization not found" or "Invalid key organization"
Symptom: A transaction or budget entry rejects the organization (budget unit) with a message that the organization is not found or invalid.
Cause: The Key Organization value is not defined on the Organization Chart page for the fiscal year in use, or the user entered a value that does not match a valid key organization.
Resolution
|
Step |
Action |
|---|---|
|
1 |
On the Organization Chart page, ensure the Year is set to the correct fiscal year for the transaction or budget. |
|
2 |
Search for the Key Organization the user tried to enter. If it does not exist, either add it (using only codes already defined in Account Components) or have the user choose a valid Key Organization from the list. |
|
3 |
Confirm that Total is not selected on the Organization Chart page if the user is trying to post. Total records are for roll-up only and may not accept direct posting. |
|
4 |
If the value was entered in Full Account Format, confirm that the full string parses correctly into a Key Organization on the Organization Chart page. For more information, refer to Translation table issues. |
Prevention: Maintain a code list of valid Key Organization values by year, and train users to select the correct value from the Organization Chart page or a validated lookup.
"Account not found" or "Invalid account"
Symptom: Transaction or budget entry rejects the account (object) code.
Cause: The account code does not exist on the Account List page, or (for object segments) is not defined on the Account Components page at Level 2 for the level your implementation uses as Object.
Resolution
|
Step |
Action |
|---|---|
|
1 |
On the Account Components page, filter records by Level 2 (Object). Verify the code exists and has a title. |
|
2 |
If your implementation validates against the Account List table, open the Account List page and add or correct the Account Code and Title. Ensure the other fields are populated as required for the transaction type. Ensure the value in the Salary Charges field is not N - Not a Payroll Account if the transaction is for reporting (e.g., state) purposes, unless your processes allow it. |
|
4 |
When using Full Account Format, ensure the full account string parses so the account segment matches a valid account on the Account List or Account Components (Level 2) pages. |
Prevention: Add all required object/account codes to the Account List or Account Components (Level 2) pages before creating organizations or entering transactions.
Key organization exceeds 16 characters
Symptom: Cannot save an organization, or the system truncates or rejects the key organization.
Cause: The Key Organization field is limited to 16 characters. If the combined segment codes (with or without delimiters) exceed 16 characters, the value is invalid.
Resolution
|
Step |
Action |
|---|---|
|
1 |
Review your FAS design: segment lengths must total 16 characters or less (including any delimiters). |
|
2 |
Shorten segment lengths on the Account Components page (e.g., two-digit function instead of four digits) and ensure all codes for that level fit the new length, or reduce the number of levels used. |
|
3 |
Recreate or update the Key Organization field values on the Organization Chart page so that none exceed 16 characters. |
|
4 |
If you use Full Account Format, ensure the Translation table segment positions and lengths produce a key organization value of 16 characters or less. |
Prevention: Document segment lengths in planning and keep the total key organization length ≤ 16. Refer to Use Consistent Coding.
The Full Account Format option is disabled or grayed out
Symptom: On the Fund Accounting Profile – System Options tab, the Full Account Format option cannot be selected.
Cause: The option is controlled by the state_fullacct table. If your state is not in that table (or is not set to allow full account), the feature is disabled for your site.
New York sites: Full Account Format is not enabled by default. Before you can select the Full Account Format option, an administrator must add a record for NY to the state_fullacct table. Contact your database administrator or PowerSchool support to add this record.
Resolution
|
Step |
Action |
|---|---|
|
1 |
Confirm with your implementation or support team that Full Account Format is enabled for your state/product. |
|
2 |
If your state is supported, a record may need to be added to the state_fullacct table for your state. This is typically a database or configuration task performed by an administrator or vendor. |
|
3 |
If you do not need single-field full-account entry, you can leave Full Account Format off and enter the key organization and account separately on transaction pages. |
Prevention: Clarify state/product support for Full Account Format during implementation planning.
Translation table (trans_acct) validation fails, or the full account won't parse
Symptom: When enabling Full Account Format, the system fails to save and may display a validation error. Or, when entering a full account on a transaction, the system rejects it or splits it incorrectly.
Cause: Full Account Format requires the Translation table to be set up for the fiscal year. The table defines how the full account string is split into the key organization and account (start/end positions per segment). If the table is missing or does not match your mask, validation fails, or parsing is incorrect.
Resolution
|
Step |
Action |
|---|---|
|
1 |
Ensure the Translation table is configured for the fiscal year and ledger type(s) you use. |
|
2 |
Verify segment start/end positions match your actual full-account format (e.g., fund 1–3, function 5–8, object 10–12, account 14–17). |
|
3 |
Do not turn on Full Account Format until Titles, Account Components, Account List, Organization Chart, and the Translation table are configured. Refer to When to select the Full Account Format option. |
|
4 |
If parsing is wrong on entry, compare the full-account string to the Translation table definition and fix positions or the data. |
Prevention: Configure and test the Translation table in a test environment before enabling Full Account Format in production.
Cannot turn off Full Account Format after it was turned on
Symptom: On the Fund Accounting Profile – System Options tab, you clear Full Account Format, but the system will not save, or you receive an error.
Cause: When Use Fund Only is turned off, the system requires Full Account Format to be on. You cannot disable Full Account Format while Use Fund Only is off.
Resolution
|
Step |
Action |
|---|---|
|
1 |
If you must turn off Full Account Format, you must first turn Use Fund Only back on. This is a significant change and may affect how organizations and accounts are entered across the system. Do this only with a full understanding of the impact. |
|
2 |
In most cases, leave Full Account Format on once it is enabled and ensure the Translation table and FAS are maintained correctly. |
Prevention: Decide during planning whether to use Full Account Format or Use Fund Only; avoid toggling after go-live.
Budget or cash checking errors (warning/fatal)
Symptom: User cannot save a requisition, purchase order, or payment due to budget or cash constraints (e.g., over budget or insufficient cash).
Cause: On the Organization Chart page, the value in the Check Cash Balance or Check Budget Balance field is W - Warning or F - Fatal for that key organization record, and the transaction would exceed the budget or cash for that budget unit.
Resolution
|
Step |
Action |
|---|---|
|
1 |
Confirm the key organization and account are correct. If the transaction was intended for a different budget unit, change the organization/account. |
|
2 |
If the transaction is correct, either increase the budget (or cash) for that key organization-account combination or adjust the transaction amount. |
|
3 |
On the Organization Chart page, ensure the value in the Check Cash Balance or Check Budget Balance field is set correctly for that key organization record, as allowed by policy. |
|
4 |
Ensure the Pre-encumber Requisitions field and the encumbrance workflow are configured correctly if the error occurs at the requisition or PO stage. |
Prevention: Set budget and cash-checking levels consistently in the Organization Chart and document the policy. See Best Practices – Budget and cash checking.
Posting to a total or summary record
Symptom: The user attempts to post to a key organization configured as a Total record, but the system either denies the post or reports it incorrectly.
Cause: The Total option on the Organization Chart page indicates a roll-up/summary record. These are typically not used for direct posting. Only detail key organization values should receive transactions.
Resolution
|
Step |
Action |
|---|---|
|
1 |
On the Organization Chart page, verify that the key organization has Total selected. Do not use this option for requisitions, invoices, payroll distributions, or budget entries. |
|
2 |
Select a detail (non-total) key organization that rolls up to the desired total. |
|
3 |
If the structure is wrong, clear the Total option on the correct records or add new detail key organization values. |
Prevention: Document which key organization values are total vs. detail and train users to post only to detail organizations.
The segment code is missing when building the key organization
Symptom: When adding a key organization to the Organization Chart page, a segment (e.g., function, location) is not in the list, or the system reports the code as invalid.
Cause: That segment’s code is not defined on the Account Components page for the corresponding level (Level 1 = Function, Level 2 = Object, etc.).
Resolution
|
Step |
Action |
|---|---|
|
1 |
On the Account Components page, ensure the Level that corresponds to the missing segment (e.g., Level 1 for Function, Level 3 for Location) is selected. |
|
2 |
If the Level is incorrect, recreate the record using the Code and Title for the required value. Use consistent length and leading zeros. |
|
3 |
Return to the Organization Chart page and build the key organization using the new code. |
Prevention: Complete the Configure Account Components procedure for all levels before building the Organization Chart.
Reports show wrong or missing data
Symptom: Budget vs. actual, fund summary, or other FAS-based reports show zeros, wrong totals, or missing key organization/account breakdowns.
Resolution
|
Step |
Action |
|---|---|
|
1 |
Confirm that the report date range and fiscal year match the data. |
|
2 |
Verify that the key organization and account values on the report exist on the following pages, for that year: |
|
3 |
If using Full Account Format, ensure the Translation table is correct for the year and ledger so that posted full accounts are stored and parsed correctly. |
|
4 |
Check security views (if applicable). Users or roles may be restricted to certain organizations. Ensure the views include the key organization values you expect to see. |
|
5 |
Confirm the usage of the Total option. Reports may roll up the detail key organization to total records. If the detail data is missing, the total will be wrong. |
Prevention: Run key reports after FAS configuration and after loading budget/transactions to validate. Refer to Step 8: Verify and Document.
Payroll or HRM distribution errors (key organization/account)
Symptom: Payroll distribution or position funding fails with an organization or account error.
Cause: The key organization or account used for the distribution does not exist in the Fund Accounting setup for that year, or the account is not set up for payroll (e.g., P - Payroll is selected in the Salary Charges field on the Account List page).
Resolution
|
Step |
Action |
|---|---|
|
1 |
Verify the key organization exists on the Organization Chart page for the fiscal year that aligns with the pay period. |
|
2 |
Verify the account exists on the Account List page and that the relevant option is selected in the Salary Charges field so the account can be used for payroll distributions. |
|
3 |
If the district uses Full Account Format in the Human Resources module, ensure the full account string matches the format expected by the Fund Accounting and Translation tables. |
|
4 |
Confirm the Human Resources and Fund Accounting modules are using the same fiscal year and that organization/account codes have not been inactivated or deleted. |
Prevention: Keep a list of payroll-valid key organization-account combinations and update it whenever FAS changes.
Data load or import failures (FAS-related)
Symptom: A budget load, transaction import, or migration fails with errors referencing the key organization, account, or full account.
Resolution
|
Step |
Action |
|---|---|
|
1 |
Validate the source file. Every key organization and account in the file must exist in the target year (Organization Chart and Account List / Account Components). |
|
2 |
Check the key organization length. No value may exceed 16 characters. |
|
3 |
If the file uses full account format, ensure segment positions and lengths match the Translation table for the target year. |
|
4 |
Fix or remove invalid rows, then re-run the load, or add the missing organization/account codes first and then re-run. |
Prevention: Run validation or a small test load before the full import and document the required code lists for the load files.