Tsheet Posting Schedule

[Anon Anon]

We are thinking about running our posting job hourly. Currently we run it every hour only on Monday then a couple of times Tues and Wed.We've heard that  many Clarity users post very frequently throughout the week.What are the PROs/CONs of a higher frequency?Thanks  

[Deactivated User]

For PROs you could argue that hourly posting 247will keep the project data updated with timesheets andless data to process in each runallow to invoice the work performed earlier  For CONs you could litsconstant monitoring of the posting job,   errors, invalid transactions and no real date limit when the timesheet should be actually submittedhow frequently are the approvers going to approve the timesheetsare the projects in a comparable state in regards to reporting at any day of the year if the time is reported in user selected mannercan the project managers see the project status from the actuals and pending actuals anywayis the invoicing done by the hour or by the monthly fiscal periods in accountingis the time reporting period one hour or one week and how many times a time reporting period you submit your timesheets  If there is a say weekly deadline for the timesheets to be a) submitted and b) approved what exactly is hourly posting going to be posting  Martti K.  

[Anon Anon]

Its really a BUSINESS decision, not a Clarity decision how often you post timesheets...  My business decision is that we want the actuals data on the plans as soon as we can, and we want to send the posted time data to another corporate system as soon as we can...  So we post every half-hour and we auto-approve all timesheets*; so a user submitting their timesheet should automatically get their time onto the plan within a 1/2 hour with no other intervention at all.   * - Of course we then need to cope with "adjusted timesheets", (but thats not so bad)  --  So you really need to start with the BUSINESS to determine how often you post!

[Anon Anon]

Dave and martink,thanks for the quick replies.  We were thinking more from a performance improvement standpoint initially(posting and slicing more often but hopefully smaller bites means quicker throughput).Also the higher frequency means closer to real-time data.  However, with all good things comes a price. Those who manage by the time reports may find it a challenge to have the report data be so volatile.  I'll see if we can get the Business to accept/understand this.  Thanks again.

[Deactivated User]

Dave:  Please educate me. Your time reporting period can't be half an hour it has to be at least a day. If that is the case or if it is even longer then it sounds as if there will be a large number of timesheet postings before the users actually submit their timesheets which is likely to be at the end of the time reporting period or are they expexted to submit their timesheets partly filled or more than once.  Second education: if the frequency of posting is based on business need how exactly is the business value of posting that frequently compared to weekly calculated?  With regards  Martti K.

[Anon Anon]

Our time reporting period is the standard "weekly" one, but we allow (in fact encourage) timesheets to be completed in advance of the period end (especially at month-end) - and we want that data available on plans (and on an interfaced-to corporate system) as soon as we can after the resource has entered their timesheet.  Therefore timesheeting can happen at any point in the week (although it is heavily loaded to Friday afternoons), therefore we post timesheets throughout the week (and this also spreads the timselice load throughout the week).  If you only post once a week (at the end of the period), what do you do with people who have missed entering their timesheet?   Do you fill it in for them?   Do you chase them BEFORE you run post?   Do you an extra post after they have filled it in (but this will also pick up any other next-week timesheets in the system?).   I don't have any of those issues (but I do have a load of other issues, liking coping with adjustments....)  I can perfectly understand if the business model is built around a strictly defined drop-dead time in the weekly cycle and the business has processes in to enforce that cycle.... its just that I don't....     It would be a challenge to introduce those processes for us; we process >3000 timesheets weekly across an organisation with a number of different existing business practices.....  So it just all depnds on what the business wants!     ....and my business wanted time on plans (and the interfaced corporate system) as soon as possible, so thats what we do!   :-)    

[Deactivated User]

Thanks Dave,  I do understandtime on   the interfaced corporate system as soon as possiblebut just wondering again what is the proportion of the timesheets posted in each posting.  You could encourage people to post timesheets if it ware basis of billing and pay.Yes, there are always people who do not post in time.With human approval you delegate the kicking and in the worst case the mangers have to fill in the timesheets for their subordinates,which reduces the final count of missing timesheets.If you wait an hour after the approval deadline before posting you allow for the better late than never.You could also have a second unannounced posting next morning.This time limited posting would require admin to monitor and take action only for a few hours of the week.You could do that with more frequent posting by just looking at the results once a week, but defats the purpose.  Martti K.

[Slovak]

My question is why? Is your company running the finanancial piece this much as well? If not then why post. You can run into a lot of errors wiht invaild transactions, financials being closed. etc.

We post time every Thursday. I process over 5000 transactions a week.

I would check with your company's accountng team and find out what they requrie. I cannot beleive they require time more then once a week.