Worldsoft Documentation Search

How to resolve problems listed in the Budget Audit

Invalid Begin/End Fiscal Year Dates For Version
Data Management -> Code Table Maintenance -> Salary Budget Version.
This message indicates that the beginning or end dates for a particular version do not appear correct. If the begin and end dates are set correctly, this error may indicate that the salary download date is after the beginning of the year. This is not actually an issue, but the audit attempts to bring attention to this as it is rare for the download to occur after the year being budgeted.

 

The Salary Profile Has Missing Or Extra Hours/Vacation Groups.  Both Hours/Vacation Must Exist Only Once Per Profile.
Data Management -> Code Table Maintenance -> Profile Master.
The ‘Standard FTE’ or ‘Vacation’ designation must only occur once within the erroneous profile.

 

No Schedules For Worksheet With Staff
Budget Manager -> Salary Budget, Worksheet tab.
Indicates that a worksheet has staff attached but has not been budgeted.

 

Salary Master and Worksheet Cost Centres Do Not Align (Mapping Errors)
Budget Manager -> Salary Budget, Salary tab
Staff are attached to a worksheet that have a different cost centre than the worksheet. Load the worksheet, then change the Cost Centre in the C: Salary tab for the listed staff.

 

Missing Role Value For Employee Organization
Data Management -> Code Table Maintenance -> Group Roles.
The system does not know how to define hours for a particular employee organization, entry needs to be made on the lower table.

 

Allocation Referenced But Not Defined For That Year
Budget Manager -> Allocation.
An allocation code has been assigned to a record but has no definition for the current year. Create the allocation values for the allocation code.

 

Salary Master Allocation Is Set To Not Coded
Budget Manager -> Allocation, Salary tab
The salary record has an allocation code of ‘Not Coded’. If allocation is not in use for the record it should be left blank.

 

Production Type Is Not Coded For Employee Class
Data Management -> Code Table Maintenance -> Employee Class Types.
All employee class types should have a proper Production Code, not ‘Not Coded’.

 

Salary Master Employee Organization Set To Not Coded
Salary Master Employee Type Set To Not Coded
Salary Master Employee Classification Set To Not Coded

Budget Manager -> Salary Budget, Salary tab
The indicated field is set to ‘Not Coded’ on the salary record. Edit the record with the correction. If you set the filter to ‘All Salary Records’ you can then set the column filters to see all records with a ‘NOTCODED’ value.

 

Salary Master Salary Grid Type Set To Not Coded
Correction location varies depending on fix.
The employee record has no pay grid. This can be fixed by either using:
1) Salary Grid Override checkbox in Budget Manager -> Salary Budget, Salary tab and manually setting a grid
2) Heading to Data Management -> Code Table Maintenance -> Salary Grid/Cross Reference and setting up the appropriate Class/Pay Level combination mapping.

 

Salary Master Step Plan Type Set To Not Coded
Correction location varies depending on fix.
The salary record has no step plan. This can be fixed by either using:
1) Budget Manager -> Salary Budget, Salary tab, use the Step Plan Override checkbox in the salary module and manually set a step plan
2) Data Management -> Code Table Maintenance -> Step Plan and set the employee type/org/class (optional) in the assignment tab of the correct plan.

 

Salary Master Vacation Plan Set To Not Coded
Correction location varies depending on fix.
The salary record has no Vacation plan. This can be fixed by either using:
1) Budget Manager -> Salary Budget, Salary tab, use the Vacation Plan Override checkbox in the salary module and manually set a Vacation plan
2) Data Management -> Code Table Maintenance -> Vacation Plan and set the employee type/org/class in the assignment tab of the correct plan.

 

Missing Salary Grid Previous References
Data Management -> Code Table Maintenance -> Salary Grid.
Indicates that there is only one effective date for a given grid code, meaning the system cannot calculate step and grid increases. Corrected by creating an earlier grid entry.

 

Salary Master Missing Step Plan Details
Data Management -> Code Table Maintenance -> Step Plan.
The salary master record has been assigned a step plan that doesn’t have any details defined in the dictionary. Provide plan details to correct.

 

Salary Master DL Step Exceeds Max Salary Grid Step
Budget Manager -> Salary Budget, Salary tab.
The employee’s downloaded step is higher than the number of steps in a grid. If the DLStep is not decreased the employee will be receiving a pay rate of $0/hour. This can be corrected by either:
1) Fixing the grid assigned to the employee
2) Decrease the Download Step to be within the assigned grid plan.

 

Salary Master Missing Benefits
Correction location varies depending on fix.
The salary record has earnings but no benefits. Either :
1) Add benefits to the record directly in the Salary tab
2) Use Budget Manager -> Salary Budget Utilities -> Utilities by Budget Version, Worksheet, and Cost Centre -> Add Default Benefits (From Similar Record)

 

Salary Master Missing Download Step
Budget Manager -> Salary Budget, Salary tab
The salary record has no download step. Fill in DLStep on the salary record. Even if you intend to use an Hourly Rate Override, the system expects a value in Download Step.

 

Missing Distribution For Salary Earnings
Correction location varies depending on fix.
Earnings have no defined distribution code relationship and, as such, the system doesn’t know how to distribute them throughout the fiscal year. Either:
1) Easiest fix is to run Budget Manager -> Salary Budget Utilities -> B: Page 2 -> Add Default Distribution, selecting the Distribution from the dropdown and pressing ‘Add Default Distributions’.
2) Manually enter by heading to Budget Manager -> Distribution and Assignments -> C: Salary Assignments.

 

Missing Distribution Code Table Entries
Budget Manager -> Distribution and Assignments.
A referenced distribution code has no default GL/PP distributions or has no GL/PP distributions specific to the budget year. Create the appropriate period percentages to correct.

 

Has Benefits But No Earnings.  Will Cause Distribution Imbalance (Simply Incomplete)
Budget Manager -> Salary Budget
The employee record has benefit codes but is not scheduled/budgeted for any earnings. This is occasionally deliberate. Consider deleting or disconnecting the salary record.

 

Single Employee Hours Exceeds 3000 Hours
Budget Manager -> Salary Budget Review (to see split positions) OR Budget Manager -> Salary Budget, Schedule tab
An employee is budgeted as working more than 3000 hours in a budget year. If this has happened because of backfill scheduling consider adding additional vacant staff to represent the necessary headcount for relief.

 

Invalid Worksheet Item Begin / End Dates
Budget Manager -> Salary Budget, Schedule tab
The Beginning and Ending dates in the B: Schedule tab are outside of the range of the fiscal year and need to be corrected.

 

GL Distribution Not Balanced – Earning Types
GL Distribution Not Balanced – Earning Details
GL Distribution Not Balanced – Benefit Types
GL Distribution Not Balanced – Benefit Details

The amounts distributed to the GL periods is not totaling to the amount budgeted. This can sometimes occur due to rounding problems, you may need to increase the number of decimals you’re budgeting to as a correction. On newer versions (1.7.0.3+) this should not be a persistent error; contact support if this continually appears.

 

PP Distribution Not Balanced – Benefit Types
PP Distribution Not Balanced – Benefit Details
PP Distribution Not Balanced – Earning Types
PP Distribution Not Balanced – Earning Details

The amounts distributed to the pay periods is not totaling to the amount budgeted. This can sometimes occur due to rounding problems, you may need to increase the number of decimals you’re budgeting to as a correction. On newer versions (1.7.0.3+) this should not be a persistent error; contact support if this continually appears.

 

Benefit Detail Formula Has Self-Reference – Redefine Otherwise Numbers Keep Changing
Earning Detail Formula Has Self-Reference – Redefine Otherwise Numbers Keep Changing

Data Management -> Code Table Maintenance -> Earning Benefit Types.
Indicates there’s a circular reference – the code in question uses the same Accumulator Group than it contributes to in the Counts Towards tab. You may need to set up a new accumulator group for the code if removing the code from Counts Towards is not an option.

 

There are no Earning/Benefit Details Records For The Earning/Benefit Code
Data Management -> Code Table Maintenance -> Earning Benefit Types.
The earning or benefit code is in use but no calculation information is available. If it should not be budgeted, use Budget Manager -> Salary Budget Utilities -> C: Page 3 to remove the entries from the entire budget.

 

No corresponding match between Earning Details to Salary Master
No corresponding match between Benefit Details to Salary Master

Data Management -> Code Table Maintenance -> Earning Benefit Types.
The system cannot find a match between the salary records Class/Code/Type combination and the earning/benefit code’s definition. A new detail line will need to be set up that will provide a match.

 

The Earning/Benefit Detail Does Not Match Its Corresponding Type (Mismatch)
Data Management -> Code Table Maintenance -> Earning Benefit Types.
The earning/benefit code has been defined in Data Management -> Code Table Maintenance -> Earning Benefit Types as the opposite type of where it is being used in the Salary Module. Either the type needs to be changed in the code table or it needs to be called differently in the budget. There are options available in the top grid to report an earning or benefit as its opposite type.

 

No corresponding match between Earning/Benefit Details to Secondary Accounts
Data Management -> Code Table Maintenance -> Earning Benefit Types.
The Secondary Code assignment is missing for the given production type.

 

Two Or More Download Rates For Same Employee And Employee Class
Budget Manager -> Salary Budget, Salary tab
The employee in question exists in multiple places in the budget with the same employee class but shows different download rates among the locations. Meant as a warning.

 

Salary Grid assigned to multiple Employee Organizations
The salary grid shows up on employees belonging to multiple organization. Important only when looking at using the Salary Grid code table to increase/decrease rates by org.

 

Salary Master DL Step Exceeds Max in Step Plan
Budget Manager -> Salary Budget, salary tab
The employee’s DLStep is higher than the step plan’s maximum step. Employee will not receive any increases. Either change the step plan assignment, lower the DLStep, or leave it as is.

 

Salary Master not matched in salary grid cross reference (class type & pay level if used)
Data Management -> Code Table Maintenance -> Salary Grid Cross Reference.
The system does not have an entry that matches the Employee Class and/or Pay Level of the employee. Add the reference to the code table.

 

Cost Centre coded to other than BUDGET — invalid account type
Data Management -> Code Table Maintenance -> Cost Centres.
The cost centre is being used in the operating budget but does not have an account type of ‘Budget’.

 

Manual salary entry NOT tagged as ‘G’ (GL) sourced account
Data Management -> Code Table Maintenance -> Secondary Accounts.
The system expects that any secondary accounts listed as ‘Salary’ will not be used by entry lines in Budget Manager -> GL Budget. It is recommended you create an equivalent account in Data Management -> Code Table Maintenance -> Secondary Accounts with a suffix of ‘G’ and use that for adjustments.

 

Group Role detail hours mis-matched with yearly earned hours
Worksheet item detail weeks mis-matched with yearly earned weeks
Profile hours mis-matched with yearly earned hours

The system is comparing the hours defined against the typical range of 1950 – 1965. Your site may have organizations that fall outside of this range, which means this warning can be ignored.