1245 results found

1. Time Off decimal entry restrict to .00 or .50

   We would like to restrict the time off entry to be entered in decimal increments of whole decimal(.00) or half decimal (.50)increments. We no longer allow any other option of decimal incremens.

   33 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Time Off  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   Planned  ·  AdminAshley Prinsen (Product Owner - Business Suite, Skyward SMS 2.0) responded

   Plan to complete in the October Release.

2. Update PSERS reporting for Sabbatical leave

   Need Skyward to update PSERS state reporting correctly for Sabbatical leave.
   We were given a solution in SKYWARD to create correction contributions but not a way (except with a manual change in state reporting) to report the wages as described below.
   From PSERS Manual

   During the period of the leave the member must be paid 50% or more of their contracted salary. The

   employer reports the actual amount paid to the member as well as the unpaid portion (totaling 100% of

   contracted salary) each month. Members are considered to be in regular daily attendance during the

   period of the leave and service is reported accordingly. The employer and member pay contributions on

   100% of the contracted salary.

   Reporting Requirements

   The employee (member) should be reported to PSERS as follows:

   Work Status = SABTLC - Sabbatical Leave (Contributing) When submitting the Contract

   Record the Work Status Start Date should be equal to the first day of Sabbatical Leave. After

   submitting the SABTLC Contract Record your Work Report should reflect the same Work

   Status.

   Wages should be equal to the employee's full contract salary. Wages should be reported in

   the following fields.

   Wages paid to the employee should be reported in the BASE field.

   Wages representing the unpaid portion of the full contract salary should be

   reported in the URCC field.

   Days or Hours should be reported based on the time that would have been rendered had the

   school employee not been on leave.

   If the school employee was employed with a Wage Type of Per Diem or Salaried

   Days should be reported based on the number of days the employee would have

   worked.

   If the school employee was employed with a Wage Type of Hourly Hours should be

   reported based on the number of hours the employee would have worked.

   Member Contributions should be paid by the school employee to the employer and remitted

   and reported by the employer based on the employee's Member Contribution Rate

   multiplied by the employee's full contract salary.

   Employer Contributions should be paid and remitted based on the Employer Contribution

   Rate in effect for the fiscal year(s) of the Sabbatical Leave multiplied by the employee's full

   contract salary.
   Maybe create a field that would hold the salary amount that needs to override the regular salary amount when the employee is on sabbatical.

   Need Skyward to update PSERS state reporting correctly for Sabbatical leave.
   We were given a solution in SKYWARD to create correction contributions but not a way (except with a manual change in state reporting) to report the wages as described below.
   From PSERS Manual

   During the period of the leave the member must be paid 50% or more of their contracted salary. The

   employer reports the actual amount paid to the member as well as the unpaid portion (totaling 100% of

   contracted salary) each month. Members are considered to be in regular daily attendance during the

   period of the leave… more

   44 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  State Reporting  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   Deferred  ·  AdminAshley Prinsen (Product Owner - Business Suite, Skyward SMS 2.0) responded

   Thank you for submitting this request to the Ideas Portal. In reviewing this request with our State Reporting and Compliance Department, while our current process involves a small portion for manual verification, we are compliant with the PSERS reporting manual specifications.

3. This report sorting rules should be able to be mod

   This reports is setup to sort by social security number which is sometimes the way I like to see it but it would be helpful to also have the option to sort it by vendor name as well.

   Having different options on sorting will allow users to be more efficient.

   32 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Reporting  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   Tell us More  ·  AdminAshley Prinsen (Product Owner - Business Suite, Skyward SMS 2.0) responded

   Thank you for submitting this idea. We’d like to see more support from the Skyward User community before we consider it for development.

   Thank you!

4. Allow JE for SBAA to work like regular JE

   Allow a Journal Entry for SBAA to post or pre date transactions greater than 90 days.

   For Journal entry for SBAA to behave like a regular Journal entry allowing it to be predated more then 90 days.

   33 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Account  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   Deferred  ·  AdminAshley Prinsen (Product Owner - Business Suite, Skyward SMS 2.0) responded

   Thank you for submitting this request to the Ideas Portal. At this time we are not considering the ability to pre or post date transaction greater than 90 days.

5. District needs widgets to be forced, not suggested

   Widgets need to be forced upon users not merely suggested. This functionality used to be in Skyward but was subsequently removed.

   Included in this use selection parameters to identify who to assign the widget to.

   83 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   2 comments  ·  Dashboard  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   Deferred  ·  AdminAshley Prinsen (Product Owner - Business Suite, Skyward SMS 2.0) responded

   Thank you for this idea request and participating in voting.

   We suggest using the “Force Widget Suggestions” This process will re-suggest the widget to all users that are currently not using the widget.

   While this option will not force widgets on users, there are technical difficulties that would delay this enhancement. We are taking this request into consideration and working on a Qmlativ solution. At this time we will no longer be considering this enhancement for SMS 2.0.

   Thank you!