Sage 100

 View Only
Expand all | Collapse all

UG from 4.4 to 2016.3 - customer now says that ACH

  • 1.  UG from 4.4 to 2016.3 - customer now says that ACH

    Posted 02-03-2017 11:10
    UG from 4.4 to 2016.3 - customer now says that ACH created and posted in AP since the upgrade do not transfer to BR like they did before. The integration is turned on and the registers appears to have all been posted. I do see there is an option under AP - Setup - ACH to post in detail which is UNCHECKED (customer does not want the detail only total). Does not seem as if anything from ACH has posted into BR. Anyone else seen anything similar when the option NOT to post ACH in detail to BR is selected? Update: Logged in with Sage, they could not duplicate. We fiddled and ultimately took case # 8005905335. Brett suggested click/unclick the post in detail option. I found another company in the customers system and looked via DFDM and found that if their PostBankRecInDetailACH$ was = [] then no ACH goes to BR. Solution is DFDM this field to either Y or N or check/uncheck in options as Brett suggested.


  • 2.  RE: UG from 4.4 to 2016.3 - customer now says that ACH

    Posted 02-03-2017 11:16
    I think you may need to just toggle it on and then off to reset the setting.


  • 3.  RE: UG from 4.4 to 2016.3 - customer now says that ACH

    Posted 02-03-2017 11:23
    They have one batch that had both checks and ACH - the checks post to BR. The ACH does not.


  • 4.  RE: UG from 4.4 to 2016.3 - customer now says that ACH

    Posted 02-03-2017 11:24
    right


  • 5.  RE: UG from 4.4 to 2016.3 - customer now says that ACH

    Posted 02-03-2017 11:25
    Did they look under the Deposits tab in BR? I think one way posts it as an adjustment, and the other as a check...


  • 6.  RE: UG from 4.4 to 2016.3 - customer now says that ACH

    Posted 02-03-2017 11:26
    Yes


  • 7.  RE: UG from 4.4 to 2016.3 - customer now says that ACH

    Posted 02-03-2017 11:38
    On the phone with Sage - taking a case # as this appears to be a bug. Sage is trying to push back saying that in order to integrate you must check off the ""post to bank reconciliation in detail"". Thankfully the help file says otherwise.... They shifted me to another tech who tried the same but I persuaded them that it the help file said otherwise. They say they can't duplicate so now they are looking again.


  • 8.  RE: UG from 4.4 to 2016.3 - customer now says that ACH

    Posted 02-03-2017 12:00
    @WayneSchulz, I'm a little confused. Did you try what I suggested? That worked last week for one of our Consultants.


  • 9.  RE: UG from 4.4 to 2016.3 - customer now says that ACH

    Posted 02-03-2017 12:01
    No - Sage is on now. I can hear the customer next questions ""so do we have to go click every option ...


  • 10.  RE: UG from 4.4 to 2016.3 - customer now says that ACH

    Posted 02-03-2017 12:01
    Or maybe I wasn't exactly clear. I was suggesting you toggle on/off the 'ACH Post in Detail' setting.


  • 11.  RE: UG from 4.4 to 2016.3 - customer now says that ACH

    Posted 02-03-2017 12:03
    Well tell them to try that first. :)


  • 12.  RE: UG from 4.4 to 2016.3 - customer now says that ACH

    Posted 02-03-2017 12:05
    And if there's other settings they have to do that for, you'll of course offer to do that for them ""no charge"". lol. Only other situation I heard of that's similar is in P/O and S/O which was previously discussed in SC.


  • 13.  RE: UG from 4.4 to 2016.3 - customer now says that ACH

    Posted 02-03-2017 12:15
    Copied to a test company and could not duplicate so unsure what's happening.


  • 14.  RE: UG from 4.4 to 2016.3 - customer now says that ACH

    Posted 02-03-2017 12:54
    Appears that if AP_Optionis..M4T field PostBankRecInDetailACH$=[] that no ACH posts to BR. If you set it to N either by DFDM or check/uncheck then ACH post to BR. All other postings to GL and AP seemed ok. This just impacted BR.