Sage 100

Now that v2018 PU3 and v2018 PR PU 2 have been released, what are the reported issues in PR/TC/JC that are still outstanding? The ADV/Prem issue when printing checks/direct deposits, then the check register is in Beta. What other potential stoppers are unresolved?

I haven't done any yet but think that I will have a few coming up. Very generally, the issues that I've seen are largely related to the pre-conversion steps. I believe @PhilMcIntosh reported one where the history wasn't retained if the company source data wasn't flagged for it prior to conversion. Within the next month I will probably pull together a type of internal guide to follow for these updates. Luckily I only have about a half-dozen as most of mine fled for paid payroll processors long ago.

Oregon taxes, Workers' Comp calcs, forms printing balance of benefits (sick/vacation/etc). Seems like there is another State tax issue too, think it's Washington state and a new tax that was enacted.

also the check/direct deposit issue has a hot fix.

Issue: Timecard: Speed issue, concerns about ability to purge transactions - https://90minds-com.socialcast.com/messages/38857052?ref=stream

Is the check/direct deposit an official hot fix or is it still in beta? @SueBennett ??

Issue: Some customers asking for reports in portrait vs new landscape layout - https://90minds-com.socialcast.com/messages/38966554?ref=stream

Issue: Sage 100 2018 Adv may stop when checks print - https://90minds-com.socialcast.com/messages/search?utf8=%E2%9C%93&q=hotfix&sort=recent

Info: How to import to Payroll 2018 and higher - https://support.na.sage.com/selfservice/viewdocument.do?noCount=true&externalId=86747&sliceId=1&isLoadPublishedVer=&docType=kc&docTypeID=DT_Article&stateId=36482&cmd=displayKC&dialogID=1439204&ViewedDocsListHelper=com.kanisa.apps.common.BaseViewedDocsListHelperImpl&openedFromSearchResults=true

Info: How to display personally identifiable information in Crystal - https://support.na.sage.com/selfservice/viewdocument.do?noCount=true&externalId=88325&sliceId=1&isLoadPublishedVer=&docType=kc&docTypeID=DT_Article&stateId=36484&cmd=displayKC&dialogID=1439308&ViewedDocsListHelper=com.kanisa.apps.common.BaseViewedDocsListHelperImpl&openedFromSearchResults=true and list of PII files - https://90minds-com.socialcast.com/messages/37563069/comments/9250706?ref=stream

Info: BOI may be required to pull Payroll 2018+ PII data (ODBC won't work) - https://support.na.sage.com/selfservice/viewdocument.do?noCount=true&externalId=89390&sliceId=1&isLoadPublishedVer=&docType=kc&docTypeID=DT_Article&stateId=36485&cmd=displayKC&dialogID=1439445&ViewedDocsListHelper=com.kanisa.apps.common.BaseViewedDocsListHelperImpl&openedFromSearchResults=true

Info: All payroll tax computation is done in the cloud so be sure that the customer can reach this site - https://support.na.sage.com/selfservice/viewdocument.do?noCount=true&externalId=86024&sliceId=1&isLoadPublishedVer=&docType=kc&docTypeID=DT_Article&stateId=36490&cmd=displayKC&dialogID=1439657&ViewedDocsListHelper=com.kanisa.apps.common.BaseViewedDocsListHelperImpl&openedFromSearchResults=true

@MoiraGoggin - Can you get a list of open issues from Linda Cade that they are working on. BTW, for Iowa, users are looking for the rounding SIT to the nearest dollar for withholding.

@JeffSchwenk - I don't know if the check/direct deposit printing is a beta or not - I just know it has worked for us everywhere we've installed it. (We only have one site ""live"" on Payroll 2018 - all of the other are still in ""testing"" mode - thank goodness.) The engineer I spoke with said they would put the programming in the next PU, but I don't know if they will release a hot fix before then or not. And I think I've mentioned this before: The Sage Techs don't seem to be talking to Engineering. I think if anyone calls about the DD Stub Printing or the Check Printing issues, the Sage Support desk would say ""Yes, we know that is an issue but we're not sure when a fix will be out.

@MoiraGoggin - when you say ""Oregon Taxes"" - do you mean that Sage is not coming up with a fix for the new Oregon Statewide Transit Tax for any version other than 2018? Because another really big issue with Oregon and V2018 is that the new tax profiles only have one GL Account for withholdings from Employee paychecks, and we need at least 2: One for the Statewide Tax and one for the Worker's Benefit Fund withholding....

@SueBennett - Life is normal at Sage...... Must say if the resellers ran their businesses like Sage is running theirs, it would quickly be lights out for us!

I know - and how incredibly sad is that? I miss the days when the folks at State of the Art actually cared about the customer and weren't just after more money.

@SueBennett see attached - it does not look as if Sage is planning a fix for any pre 2018 releases despite those versions being ""supported"". I have already voiced my displeasure to Sage on this though I am by now much more realistic in how far that will ever go.

@WayneSchultz -That's why we wrote the work-around blog posted on our website. But here's the humorous thing: if clients DO upgrade to 2018, then can have the Transit Tax calculate automatially, however there's no way to account for it in the General Ledger (either that, or we can't account for Worker's Benefit Fund). So we're damned if we do upgrade them and damned if we don't. Just...damn....

IMO, Sage should have linked to your workaround instead of suggesting that upgrade was the only option

@BarbaraGoldstein has the scoop on how to modify the payroll check form to display OR STT instead of SDI.

No @SueBennett that's not what I meant it was a list of open issue that I recalled. @JeffSchwenk I'll ask.

I created a formula to replace the Tax Desc field in the Deductions subreports in the check stubs. ""If {PR_32CrystalLine.TaxDescription} = ""OR State DI"" then ""OR State TT"" else {PR_32CrystalLine.TaxDescription}

Issue: Certified Payroll Reports not in same format as 2017 or earlier

I had issued this case in April that was supposed to have been fixed v2.18.2. Customer told me yesterday it did not get fixed. - submitted 04.23.18, I (Kelly) was able to reproduce in the PR company in v2018.2. Enter two people from dept 00 no tips, two people from dept 01 with tips and two people from dept DD, one with tips one without. On the audit report the tips break down correctly. On the employers expense summary report there are tips calculated across all depts. Did not test posting, but believe it is correct. Checked case 04.27.18 and it was in progress. on 6/4 this was posted to case - Called and left message for Kelly noting that there are a number of fixes for the employers expense summary included in the 2.18.2 scheduled to be released at the end of the month.

Issue: Unlike with prior upgrades you do NOT appear to be able to shortcut to the final data conversion by copy/paste the MAS_XXX and then run conversion. It appears if you have payroll on 2018 then you have to go through the Sage migration for the final conversion. https://90minds-com.socialcast.com/messages/39051909?ref=stream

We have the following information on what files to save for reconvert: http://www.evernote.com/l/AQ6rwolxcORLsqSFC4dMbr7rKKeSWIaDs3Y/

Here is the KB I report in April. Finally wrote up and fix is supposed to be released in Sept with 2.18.3

Better late than never? Now if they only do what they promised..... Is it just me or are others confused when they see a reference of 2.18.3 and automatically think that it is about Sage v2018 PU and NOT the PR PU? Just thinking out loud...