Re: Sage 50 Premium With Payroll Torrent
Lucho Bizier
Hi I am trying to make changes to posted time in Sage 300CRE payroll. The payroll month for the time I am trying to change has already been closed. The entry is an intercompany change entry. Will the change still be accepted seeing that the payroll month has already been closed? Also any suggestions on the best way to change this time to another division (given you can only reallocate time to a different job?)
The best practice to correct GL accounts on a Payroll check is to void the check, make the corrections, and post it again. More information can be found in knowledgebase article 46227 How can I edit or change the General Ledger account used for Payroll entries?
Thanks for this information. In voiding the check and reissuing the check in a prior month (say Feb 2021) that has already been closed will this be able to post to JC & the GL? The prior month is still in the current year. I know Payroll is sensitive when making an entry to a prior closed period.
Posting to JC and GL should not be a problem. However, I'm concerned about the Subject-To amounts getting out of sorts when you backdate and reissue. I'm not familiar with intercompany or divisions, but I think you may consider using a current payroll period, issuing a new check where the bad data is entered exactly as it was before, only as a negative, and on the same new check, entering the correct data the way you intend it to be. Process the new check which should have net pay of zero. Because we cannot control Subject-To amounts, it seems to me the best solution. Otherwise, you may have to use the painful PR Tool of Recalculate Subject-To.
If anyone can offer suggestions on this I would greatly appreciate it. We issue payroll at our company bi-weekly. After payroll has been processed (we use an outside payroll company), I then come into sage and enter all the employees hours and job cost their time to the various jobs and work orders (we have the service module - but its the same thing as just posting it to a job if you don't have that). The issue I am running into is that we cannot see the labor until after two weeks. That is a serious lag for us when we want to review work orders that are completed in just one day. Does anyone have any better way of posting payroll to the various jobs or job costing their payroll? I thought that maybe the daily payroll would help, but again, it doesn't actually job cost anything. Nothing actually gets job costed until I hit the final compute. Help??
I tried calling support and she recommended making sure we input the hours the employee is supposed to work when we enter the work order but again that doesn't help us. We want to track how much time they actually are spending out there and see which jobs we are making or losing money, etc. So seeing the real costs.
If you use Daily Payroll, you can run the 6-1-12-31 report and get Accrued Payroll based on the unposted payroll hours. Also, the 6-1-3-41 report shows the Payroll only detail with accrued payroll. This only works for Job Costing and not Work Order only reporting. Support is correct. If you aren't using Jobs, then you should record actual payroll hours on the work order and import them into payroll. That way you can easily reconcile payroll hours charged on a work order to the payroll hours paid to the employee.
This still doesn't help me though because we want to see the costs for the work orders. (So if you look at a work order, and view - service order costs. Or by running various reports.) We are having issues with employees spending more time then they are supposed to out on the work orders. We can't put in the actual hours after the work order has already been posted/invoiced. So basically we have to do it from the payroll section. Support understood what I was asking but she didn't know of a good solution. I was hoping someone else would. We don't want to see a report of the employees hours, we just want to be able to look at different reports in the service module and see the labor hours spent on the job. But didn't want to have to wait until payroll is posted because there is a 2 week lag or more. Thank you so much though and hopefully someone has a good method for handling this situation!
You state that they are spending more "time" than they are supposed to on the work orders. So you already know the "time" they are spending, just not the burdened cost. You can probably write a work order report that will add the burden, but the "time" seems to really be the issue.
If you are saying that they are turning in more hours on their timecards than what they reported on the work order for billing, then tell them from now on they only get paid for what they report on the work orders. If you enter their time there before you bill it, then import their time. When they only have 24 hours imported but claim they are working 40, show them what got imported and short pay them that week. It will only happen once. You should also look into GPS systems for tracking their whereabouts. I know some companies have discovered their technicians were at home or elsewhere when they claim to be at the work site.
We are having the same issue - our payroll is bi-weekly so we can't see accurate job profit reports until the final compute. Our Consultant told us that the Service Module would fix this, so we paid for the Service Module - only to find that it just records total hours - it doesn't differentiate between regular and overtime (???)... so that doesn't help us at all.
I just ran it on the Sample Company and it pulled an estimated labor cost value based on the technician's time put on the work order. #72 is editable so you could add a burden rate using a calculated field.
If I enter within a workorder just to see the reports then I will still have to go back and re-enter everything into payroll - since when the Workorder is imported there is no differentiation between regular and overtime hours.
If I make invoices using T&M billing (to ensure that the time gets tracked and marked as billed), then we have to wait the full two weeks until the final compute is done before we can create the invoice.
From the start of the integration process through the actual utilization of the software, it's been a very positive experience. The platform itself is very versatile to handle many or our client's complex payroll processes. The customer service is top notch. Overall we've had a very positive experience with isolved and would highly recommend it.
When I ask questions, I not only get a speedy and thorough response, I also receive a personal walk-through of the procedures involved to ensure I understand them. This excellent customer service is above and beyond that offered by any other company with whom I've worked.
Payroll formulas and updates are not included with the software. If you just installed Sage 50, most payroll taxes will not calculateautomatically for you during payroll entry. (In some cases, payroll taxamounts will be inaccurate or zero.) To calculate these taxes in Sage 50 and to stay current with regulatory changes, you should subscribe to Sage Business Care, and install the latest tax update (see how below).
If you have the latest update installed,the first four digits of the version represent the current payrolltax year (for example, 20110101 represents version 0101 forpayroll tax year 2011). If the first four digits of the versiondo not match your current payroll year, you should install the latesttax update.
If your tax version is 19000101,a generic set of payroll formulas is installed on your system. These formulas are suppliedwith previous installations of Sage 50. During payroll entry, these formulas will not calculate accurate payroll tax amounts. (Most calculatedamounts will be zero.) Sage 50 does not provide formulaswith each version of the product that it ships. For up-to-date formulas, subscribe to Sage Business Care.
Through pay period ending 12-3-21 (checks issued 12-8-21) my payroll stubs reflect the same gross and year to date figures. I don't know if this anything to do with it, but on 12-13 I did my year end closing so the open periods I have are 2021 and 2022. I just ran payroll for week ending 12-10 and while my YTD figures are accurate the gross YTD figures are all over the place. I've double checked quarterly earning reports, tax liability reports, etc. and the figures appear to be ok. Can someone please explain this?
I've never had a case where this didn't work until there are other issues in your system complicating this. I would suggest that you either reach out to Sage support (if you are current), or our company offers paid support assistance for this and any other Sage 50 issue. Please reach out to us if interested in working with us, 800-780-0700 or 954-961-0600
We had the same issue beginning 01-01-2022. We noticed after we ran the first payroll of the year, that our balance sheet didn't balance, but just by a few cents. As of 08/31, the balance sheet difference had grown to $0.18. We compared the payroll reports to the G/L and everything was fine. By exporting the YTD check register to Excel and formatting the data to 3 decimal places, we saw that for each paycheck, gross pay wasn't rounding to 2 places. The sum of the YTD third-decimal amount totaled our balance sheet difference of $0.18. Today we ran the integrity check, suggested by termerins above from pcosupport.com, and resolved the issue. Great job, termerins!
If you have closed the general ledger for that fiscal year, Sage 100 Contractor displays a message stating that you cannot directly void the ledger transaction for this payroll record. There is no general ledger record to void in the current year.
To verify that the reversal has been posted, go to the payroll record and verify that the status has changed to 5-Void. At the bottom left corner of the payroll record click Go to Transaction and verify that the 1-3 Journal Transaction is correct.
If I recall, the automatic backup function caused us the same issues you state when they automatically enabled it during an update a couple of years ago. I am surprised you've not had the issue before?
We disabled the function altogether as our server is backed up daily so we have the data files anyway.
We didn't see the point in keeping it going with the performance issues we were having