Page tree
Skip to end of metadata
Go to start of metadata

Unanet Administrators can use the Time Period Setup screen to create and maintain the set of time periods that will be available for each user in their person profile.

The time period specified in each user's profile is used to generate multiple time periods as users enter new timesheets throughout the year. Each Timesheet User is associated with a time period. 
Time periods define the period of time in which a timesheet begins and ends. Consider how you enter your time today; you are likely using an automated system or paper timesheets. The days displayed on the timesheet will typically line up with one of the time periods that Unanet supports, e.g., weekly, bi-weekly.

It is important that the time period in Unanet lines up with your pay period. For example, if you pay your employees every two weeks, either a weekly or bi-weekly time period should be configured. If your pay periods begin on the 1st and 16th date of the month or are monthly, you should configure a semi-monthly time period or a monthly time period. (Monthly is generally less desirable for two reasons: 1) with a month date range, people have the ability to delay putting time in for longer, and will tend to forget what they did and 2) the monthly time period can stretch across the screen longer than is feasible to navigate and scroll.)

Best Practices:

  • Unanet recommends aligning the time period with the pay period, or within an equivalent subset of a payroll period (i.e., monthly payroll and semi-monthly timesheet periods). There may be trade-offs when time periods are set in a way that do not align with payroll periods. Additionally, the Billing cycle and Labor Cost Post process should be considered. Timesheets must be approved and LOCKED/EXTRACTED prior to being available for T&M and CP billing and for labor cost posting.
Pay PeriodOptions for Unanet Time Period when Dilution is on
BiweeklyWeekly or Biweekly
MonthlySemimonthly or Monthly
  • Define time periods so the begin date of the period corresponds to the desired start day of the timesheets. If you want the timesheets to start on Sundays, make sure the begin date is a Sunday.
  • Define time periods so historical time will be covered by the time period definition. If you are going to import time all the way back to Jan 1, 2005, make sure the begin date is set back as early as Jan 1, 2005.
  • ALLOW ADJ. should be left to the default setting of BLANK. If time adjustments are allowed periodically, Admin users can enable this to allow adjustments for a specific time period only by editing the Time Periods screen. 
  • MAX FUTURE PERIODS: This value determines how many time periods may be created into the future. This function can be used if a client wants to restrict employees in logging time (e.g., PTO) for a given number of future periods from the current time period. We typically recommend allowing future periods to be created for one to three months in the future. Note that this is typically used so that PTO can be charged into the short term future, while worked projects are typically prevented from having charges applied via leaving turned off a project setting called Allow Future Charges.
  • Cut Off Date: May be used if you are changing from one time reporting period to another at some date in the future. May also be used if you need to cut off your last full week in the year and prevent people from creating new weeks until you have had the opportunity to create "stub" timesheets. (For example, Dec. 29-31)
  • If you are on a bi-weekly payroll and need the ability to report by bi-weekly period, you may want to use the solution outlined on this page: KC - Quick Topic (SUCCESS PACKAGE) - Bi-weekly Time periods and Fiscal weeks

Navigate to Admin > Setup > Time > Time Period Setup > +Time Period.

Additional Information

Help Docs - Time Period Setup

KC - Quick Topic - Considerations in the alignment of timesheets and payroll periods

Quick Topic (Success Package) - Timesheet periods and Fiscal weeks

Write a comment…