Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 21 Next »

(tick) Subscribe to the SSDT Newsletter by clicking here.  Your email will be added to a distribution list.             


Wave Status Update

It's hard to believe that we are officially in Wave 8 of our migration!  Waves 6 and 7 were our biggest waves and I can't thank ITC staff and districts enough for their hard work in migrating over 300 districts within the past year alone!  Such a huge accomplishment.  We are on the downhill slide, I promise, with the remaining districts scheduled in waves 8 and 9.  As ODE stated, wave 10 is to be used for emergency migrations only so we appreciate everyone's flexibility in making this happen. Our Classic software will retire in December 2022 meaning we will no longer support it nor will districts be able to process a payroll for calendar year 2023.  If you are still undecided on the Redesign or not sure which wave or when you are scheduled to migrate, please contact your ITC for further assistance. 

Wave 8 will prove to be very exciting with major new enhancements unfolding.  The Inventory application, a separate brand spanking new application, will make its production debut mid-August. (Beta release is projected for Friday, July 23rd). We have been testing, and testing (and did I say testing?) the application and I have to tell you, it's sweet!  For those loyal EIS users (wait, is there such a thing?), (wink) I think we will quickly win you over with how easy, clean and fluid the redesigned application is.  As if a new application isn't enough, the implementation of workflows within the USPS-R and USAS-R applications is right around the corner! We plan on officially releasing the production version September 22nd (with a beta release scheduled for August).  The initial release of workflows will include requisition approval in USAS-R and employee onboarding in USPS-R. 

SSDT will be presenting (in person!) both the Inventory application and Workflow system at the OEDSA conference this fall.  The conference will be held at a new venue this year (Hilton Polaris Columbus) and is scheduled for September 15th - 17th.  We're so looking forward to seeing you all again and being able to share the latest features and enhancements of state software!



It is Here! Posting a Voided or Unvoided Payment from USPS-R to USAS-R

The capability of posting a voided or unvoided payment from USPS-R to USAS-R is now available making it so much easier to make updates in both applications. After you have Voided a payroll payment in the Payments screen you will want to go to the USAS Integration tab and choose Payment Void/Unvoid Submission. Here you can see the Type (which would be Void Payment), Payment Number, Employee Last Name, Employee First Name, Employee Number, Posted to USAS (status), Timestamp for Void or Unvoid, and the USAS Posting Status:



You will click on the tab. When you do this you will get a USAS Payment Void/Unvoid Submission-Detail screen that will show you the Employee First Name, Employee Last Name, Employee Number, Payment Number, Timestamp For Void or Unvoid, Type, Username of the employee processing the void and the Payment Total Gross.

You will also see the Account Description, Account Code and the Amount you are processing the Void for.

After you verify this is the correct information you will want to click on the tab.

You will get a verification that the submission was sent to USAS successfully

You can return to the USAS Payment Void/Unvoid Submission screen by clicking on the  tab.

Here you can see that the USAS Posting Status has been changed to Pending


The same process would be followed for an Unvoided Payment as well.

After you have Unvoided a payroll payment in the Payments screen you will want to go to the USAS Integration tab and choose Payment Void/Unvoid Submission. Here you can see the Type (Unvoid Payment), Payment Number, Employee Last Name, Employee First Name, Employee Number, Posted to USAS (status), Timestamp for Void or Unvoid, and the USAS Posting Status:

You will click on the    tab. When you do this you will get a USAS Payment Void/Unvoid Submission-Detail screen that will show you the Employee First Name, Employee Last Name, Employee Number, Payment Number, Timestamp For Void or Unvoid, Type, Username of the employee processing the void and the Payment Total Gross.

You will also see the Account Description, Account Code and the Amount you are processing the Unvoid for.

After you verify this is the correct information you will want to click on the  tab.

You will get a verification that the submission was sent to USAS successfully

You can return to the USAS Payment Void/Unvoid Submission screen by clicking on the   tab.

Here you can see that the USAS Posting Status has been changed to Pending

When the Void/Unvoid  file has  been Submitted to USAS-R via USAS Integration>Payment Void/Unvoid Submission. a pending transaction will show in USAS-R under Transaction>Pending File.  

When USPS-R submits a Void to USAS, the USAS-R user will have a choice to Validate for any Warning/Error messages as well as to Post or Reject the pending transaction.  If the USAS-R user Posts the Void, the user can choose the Transaction Date and a Receipt will be generated reversing the original expenditure entry by processing a Reduction of Expenditure.  The Amount Expended will be reduced on the account.   If the USAS-R user Rejects the Void, the user can enter a Rejection Reason and the file is returned to USPS-R without affecting the expenditure accounts. 

When USPS-R submits an Unvoid to USAS, the USAS-R user will again have a choice to Validate for any Warning/Error messages as well as to Post or Reject the pending Unvoid transaction.  If the USAS-R user Posts the Unvoid, the user can choose a Transaction Date and a disbursement will be generated increasing the Amount Expended on the account.    If the USAS-R user Rejects the Unvoid, the user can enter the Rejection Reason and the file is returned to USPS-R without affecting the expenditure accounts.  

If the Void/Unvoid file is Resubmitted to USAS-R, the USPS-R user will be informed that the Payment has already been submitted and require a Confirmation of OK to continue. 



Useful links:


Did You Know?

Budget amounts for 2022 that were applied from the Proposed Amounts grid prior to the FYE Close will show as the Initial Budgets as soon as the posting period for July 2021 is opened!

USAS-R gives you two options for applying full year budget amounts - temporary and permanent. If a district chooses to start with a temporary budget, a permanent budget can be applied at any time during the fiscal year to replace the temporary figures.



REDESIGN STATUS

525

Sites Live on Redesign

196

Total Wave 7 Sites

17

Participating ITCs

543

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.


Did You Know?

Mass Loading to add or update Future Pay Amounts can now be performed by using the Mass Load/Future Pay Amount option.

To add Future Pay Amount records the following fields are required on the csv file

  • id - needs to be in the load file with no value entered
  • employeeNumber
  • positionNumber
  • compensation.code

To Update Future Pay Amount records these fields are required to be on the csv:

  • id - (this is a string of characters and numbers) 838679cb-e524-45a2-bdcb-4fdb900916f3 - This column header can be found under the More option.
  • employeeNumber
  • positionNumber
  • compensation.code

To add and update Future Pay transactions in one upload, you would have to supply all the values on the current record because null values (,,) will give errors for most fields such as true, false.  Some have default values if not supplied.

If wanting to update different fields for different employees on the same load, you will need to put the old (current) values wherever you do not want it updated.  You must supply a value for most fields because a null value does not work.

See https://wiki.ssdt-ohio.org/display/uspsrdoc/Mass+Load#MassLoad-FuturePayAmount for more information on Future Pay Amount Mass Loading.



Did You Know?

Fund Changes - 200 Student Funds

The objective of GASB issued Statement No. 84, Fiduciary Activities, was to improve guidance regarding the identification & reporting of Fiduciary Funds which include funds that are managed and funded by the School District such as Trust Funds and Custodial Funds. (Funds 022, 026, and 200).

However, due to the administrative involvement in the student managed funds (200 funds), the Custodial Fund definition is not met for the Student Managed 200 funds that are now identified as a Fiduciary/Custodial Fund.  The distinction of Student Managed (200) vs District Managed (300) still exists, but as of FY22, Student Activities that are not identified as a Fiduciary Activity are required to be treated as Governmental/Special Revenue Fund.  Therefore, Districts are encouraged to review their 200 Funds to ensure they are properly classified as a 200 fund.  After the FY21 Period H Reporting is complete, the Fund Type for Fund 200 will be updated in the State software to be classified as Special Revenue fund.  Other helpful AOS GASB 84 information is available at GASB 84 (ohio auditor.gov).





  • No labels