Sage 100

 View Only
Expand all | Collapse all

Just determined this weekend that I can't write a

  • 1.  Just determined this weekend that I can't write a

    Posted 02-12-2018 13:35
    Just determined this weekend that I can't write a VI job for PR40. There is no data in the Data tab section. Client determined that new Sec125 cafeteria plan was set up incorrectly and needs to adjust wages subject to FICA and Medicare. Weekly payroll and 90 employees. Lots of DFDM ahead for us if I can't find a way to fix this.


  • 2.  RE: Just determined this weekend that I can't write a

    Posted 02-12-2018 13:51
    Check the Sage KB. I'm pretty sure I saw something that said information on re-writing VI jobs for the new Payroll can be found in the KB.


  • 3.  RE: Just determined this weekend that I can't write a

    Posted 02-12-2018 13:52
    Oh, sorry, did I misinterpret that this was for v2018?


  • 4.  RE: Just determined this weekend that I can't write a

    Posted 02-12-2018 13:58
    Sorry I don't have any words of wisdom that will help make the import work. I am wondering if you're not better off just entering the correct amounts through the eFiling grid rather than using DFDM, though. That should be easier to work with.


  • 5.  RE: Just determined this weekend that I can't write a

    Posted 02-12-2018 14:36
    Couldn't you do 1 payroll reversal for the full year of all wages, taxes? Then create a new Sec125 cafeteria Deduction and do 1 payroll back in putting the balance of the FICA originally W/H to Fed W/H? or I agree with @MaryJoKrueger do it in Efiling, just wouldn't be able to tie it back to Sage.


  • 6.  RE: Just determined this weekend that I can't write a

    Posted 02-12-2018 14:51
    Thanks for the ideas. Many obstacles. There are 15 deduction codes involved to accommodate gl accounts and they are running out of them now. It's already crossing months so would have to do at least two reversals. It's a weekly payroll so the window to fix is small. Yes, we can fix in Aatrix and fix PR3 and PR23 with VI but jeez.


  • 7.  RE: Just determined this weekend that I can't write a

    Posted 02-12-2018 14:55
    So is this for 2018 payroll? Sorry, but I assumed you were dealing with 2017 and it was uncovered during the W2 process. If it's 2018 payroll set up the new deduction codes with the correct flags. Then on a live payroll do a negative deduction of YTD amounts against the ""wrong"" deduction code and a positive deduction of YTD amounts against the right code. Taxes will automatically be fixed as will taxable wages. No need use DFDM or manual overrides for anything.


  • 8.  RE: Just determined this weekend that I can't write a

    Posted 02-12-2018 16:35
    +1 @MaryJoKrueger. If 2018 payroll, then this is the way to go.


  • 9.  RE: Just determined this weekend that I can't write a

    Posted 02-13-2018 00:54
    Very sorry to have not been clear. This is v2017. Not even thinking about v2018 yet. This was uncovered partially at W2 time as one set of codes had been incorrectly defined as Standard deductions instead of Cafeteria. Client was told by CPA firm to edit the 16 individual Fed and State Withholding Wages in Aatrix but no one mentioned FICA and Medicare Wages. This came up in the last few days.


  • 10.  RE: Just determined this weekend that I can't write a

    Posted 02-13-2018 03:58
    So to fix the W2s for the 2017 wages I would override the amounts in the efiling grid. I would fix the 2018 wages with a payroll run like i referenced above.


  • 11.  RE: Just determined this weekend that I can't write a

    Posted 02-13-2018 05:56
    Please send an e-mail to Luke@comstrategies.com We had the same scenario and Scott Brady at Sage provided a modified data dictionary that allowed us to import into PR40.


  • 12.  RE: Just determined this weekend that I can't write a

    Posted 02-14-2018 03:22
    Thanks @SteveEngmann for the email address. I'm not sure I understand why Sage doesn't provide VI to every file. What's especially annoying is when they define only some of the fields. Rant for the day.


  • 13.  RE: Just determined this weekend that I can't write a

    Posted 02-14-2018 09:36
    In case Luke's version of the dictionary fix is not for v2017, you can carefully make the same changes yourself after doing a backup. I would do this right on the client's system: 1) DFDM SY0DCT.SOA and find the PR.FSEFILEB001 key. Notice the ""B"" in the key. This is the 1st B record (DEPARTMENT_NO) and these are the ones that appear in the Data tab in V/I if 75,1 = D or B. Currently it's an R 2) Click Edit. Field No = 1, Starting Position = 75, Length = 1 Change the R to a B 3) Go to the next B record for EMPLOYEE_NO and do the same. 4) Repeat through the SEQUENCE_NO. You've now finished with the key fields. 5) Now edit any B records for non-key fields you want to expose. 6) After Steps 1 - 5 are complete, click on File > Run > SVCMPL > choose Select All or Payroll > Proceed 7) V/I - Import Job Maintenance. Try the Data tab now. Note better to create a new job than modify existing one. Hope it helps.


  • 14.  RE: Just determined this weekend that I can't write a

    Posted 02-15-2018 22:36
    Thanks @AlnoorCassim I'm keeping this close for future reference as I'm sure I'll need it at some point.