- Created by Michelle Drewes , last modified by Amanda Folkman on Sep 09, 2022
You are viewing an old version of this page. View the current version.
Compare with Current View Page History
« Previous Version 25 Next »
Subscribe to the SSDT Newsletter by clicking here. Your email will be added to a distribution list.
USAS-R: Improving Current Processes
The recent USAS-R Release updates have included some exciting updates that are aimed to improve current processes. Releases are scheduled every two weeks and include regular Improvements, Bug Fixes, New Features, and Internal changes. A full list of Release Notes can be found here: USAS-R Release Notes
In this article, two of the recent updates will be highlighted in further detail. These improvements were completed based on user feedback that we received directly from district and ITCs!
Improving the Expenditure Process
On July 30th, Release 8.52.0 included performance improvements to the expenditure process due to refactoring Purchase Orders. There were additional areas identified where processes can be improved and those will be addressed in future as well. This update is particularly relevant for districts when processing large purchase orders. Often, the purchase orders created from the Pending Transactions for benefits are very large so this will also improve this part of the process.
Pending Transaction → PO: 28-52%
Often, the purchase orders created from the Pending Transactions for benefits are very large so this will also improve this part of the process. The pending transactions include Employer Distribution and Employer Retirement Share transactions. These are populated in the Transaction > Pending Transactions page from USPS-R. This improvement is specific to the step where the pending transactions are posted from this grid to create the purchase order.
PO → AP Invoice: 38-64%
In order to pay on a purchase order, the invoice must be created. This step specifically covers when the purchase order is invoiced to fill items on the purchase order and saving the transaction to create the invoice in the AP Invoice grid.
Payable → Disbursement: 18-35%
When you are ready to create the disbursements, the transactions appear in the Payables grid to represent any AP Invoices that have been filled but not yet paid. Payables can be selected and then "Posted" as disbursements/checks in this step. This step also updates the amounts from encumbered (filled) to expended.
A full list of Release Notes can be found here: USAS-R Release Notes
Vendor Repair Update
The PO Repair tool is a powerful function that was added last year. This feature is similar to VERINV in the Classic USAS software. PO Repair allows you to update a purchase order date, vendor, and/or item account codes even after it has been invoiced. This tool will also update any invoices that have been issued against the purchase order.
There are some rules that apply to the PO Repair process to maintain appropriate information for reports. The PO must be outstanding, have no payments posted against it, and it must be in an open posting period for most changes. However, we received feedback to request that the Vendor Repair can be used without reopening a posting period. Since this change doesn't specifically impact report totals, this update made that request a reality!
The Repair option can be found by viewing the purchase order and clicking on the icon. Navigate to the Vendor tab of the window that pops up and simply select the new vendor and click Update! The Repair option will work its magic and then provide you with a results window and a report to print for your records.
For more information on the PO Repair option please see the Purchase Order Documentation in the SSDT Wiki or the PO Repair article in the August 2021 Newsletter.
Article #2
Wrapping up STRS Advance for another Fiscal Year!!
To make sure that you processed out of the STRS Advance correctly, after the last pay, go to System/Configuration/STRS Advance Configuration. If the Amount Paid Back is equal or greater than the Advance Amount, then the district would have come out of advance and the advance flag on the configuration will be un-checked. When the advance flag on the configuration is unchecked, then the amount paid back will always display zero. If the Amount Paid Back is less than the Advance Amount after the last pay, then the advance flag on the configuration will not be un-checked and the Amount Paid Back will continue to show on the configuration record.
If the Advance Mode flag is unchecked and the Advance Amount and Amount Paid Back fields are 0.00 and you are wanting to see the total Amount Paid Back, to verify that you did not overpay, you can check the 'Advance Mode' box, refresh the screen or (close it and re-open) and the value will be displayed in the Amount Paid Back field.
*NOTE -You will want to remember to un-check the Advance Mode box before you move on to your next payroll.
If you have overpaid or underpaid you will want to create a report that will assist in finding the employee(s) that may have had different amounts reported to STRS for the fiscal year advance in comparison to what was truly paid during the advance.
- You will want to go to Reports/STRS Reporting/Check STRS Advance. You will enter in the dates of advance processing for fiscal year 2022. (Example Start Date 7/1/21 (stop date of first pay in advance) to End Date 9/15/22 (stop date of last pay in advance). A report named Check STRS Advance Report is created. You will then go out to the Utilities/File Archive/2022 Fiscal Year Reports/STRS Advance Positions Report and click the to create the advance positions report for fiscal year 2022.
- After each report is created you will then want to compare the two, checking employee by employee and find anyone who’s amount paid during the advance on the Check STRS Advance Report does not match the STRS Advance Positions Report. Once all discrepancies are found the total should be what you are off between the Advance Amount and Amount Paid Back figures.
- You will need to contact STRS and inform them about the discrepancies you found for the fiscal year advance for the employee(s). After the corrections have been filed with STRS for over withholding or under withholding you will then need to be taken out of the Advance. You will go back to System/Configuration/STRS Advance Configuration and uncheck the flag and click on . This will update the Advance Amount and Amount Paid Back fields to 0.00.
- You will then go out to Core/Compensations/Contract Compensations and pull the STRS Advance property into the grid. Filter the grid for any records that are STRS Advance true. This will pull up any records still set as advance on the compensation record.
- Go to the Mass Change tab and import this Mass Change script SSDT_STRS_ADVANCED_FALSE. Click on the Execution Mode bubble and click Click Go back to the grid and filter for STRS Advance true. There should be no records reflecting the STRS Advance flag at this point.
*NOTE- If you have compensations that are not out of advance, there is a field on the bottom of the Payroll Report--Payroll Item Strs Advancement: that shows how much is going toward the advance.
Useful links:
- SSDT Wiki
- August Release Recap
- Newsletters Home Page
- SSDT Redesign Documentation
- Inventory Documentation
- Redesign Implementation Details
- Redesign Recorded Demos
- SSDT YouTube Channel
A new look to New Contract Grid!
Now have the option to add More column headings to the New Contract Grid! Can now see Old and New Contract Info on the grid. By using the More, you can select Old Compensation and New Compensation headers, to create a report for verification:
For more information on creating a Report, click here.
Benefit Obligation Reports
The Benefit Obligation By Accounts and Employee reports can now be ran by CSV or PDF format.
REDESIGN STATUS | |
---|---|
619 Sites Live on Redesign | 121 Total Wave 8 Sites |
17 Participating ITCs | 649 Total Districts Participating |
Please view the Current List of Districts & Status to see a comprehensive list of school districts along with their ITC, implementation status and the wave they are scheduled to migrate from Classic to Redesign.
The following terminology is used to determine where in the implementation process the entity is currently at:
Implementing: The ITC is running test imports and balancing reports on the entity. The district and ITC are working to schedule dates to begin dual processing and go live.
Paralleling: The entity is inputting all production transactions into both Classic and Redesign.
Live: The entity is using Redesign for production processing; no parallel processing is being performed; Classic is available in 'read-only' mode.
Topic #3
- DYK: OEDSA “Celebrating Sunset” reminder Michelle
- No labels