Sage 100

 View Only
  • 1.  V2013 PR issue (but it can actually be ANY version

    Posted 12-19-2014 14:36
      |   view attached
    V2013 PR issue (but it can actually be ANY version. Client is trying to cut a manual check that includes a PRE-Tax NEGATIVE deduction. Issue is that FICA wages and taxes are handled properly but the MEDICARE portion is completely ignored, thus screwing up the employee record, the GL accrual and the 941 calc (and probably other buckets). I personal think this is a bug because the FICA is handled properly but not the Medicare. Any one else noticed this?? I would turn it in, but what is the use?


  • 2.  RE: V2013 PR issue (but it can actually be ANY version

    Posted 12-19-2014 14:59
    Just a thought but has the employee reached the Medicare limit?


  • 3.  RE: V2013 PR issue (but it can actually be ANY version

    Posted 12-19-2014 15:19
    Good thought but there is no max limit on Medicare....


  • 4.  RE: V2013 PR issue (but it can actually be ANY version

    Posted 12-19-2014 22:08
    Looks like the deduction is set as a cafeteria plan. Have you tried another deduction type?


  • 5.  RE: V2013 PR issue (but it can actually be ANY version

    Posted 12-20-2014 07:23
    I believe the same issue exists with the pension type. Need to verify on Monday


  • 6.  RE: V2013 PR issue (but it can actually be ANY version

    Posted 12-23-2014 07:32
    Client contacted support - Their first attempt - ""They say I am missing qtr 3 tax table update. They are going to send to me to install"". This should be interesting....


  • 7.  RE: V2013 PR issue (but it can actually be ANY version

    Posted 12-23-2014 10:41
    And the solution from Support via the client - Well I just got off the 1.5 hour phone call with support they don't know why it is doing that but they went behind the scenes into the data files and changed things so everything would balance out. Now my only problem is I might have one more to do and I obviously can't go into all the places she did to make changes so I will call back if necessary. At least they had a workaround for me