Sage News and Discussion

Sage 100 ERP 2013 (V5) Pre-Release Guide -- looks like it confirms plans to do away with PC Charge. They also indicate that FRX is no longer supported through I don't know if that means it won't be compatible with the next release. We strongly recommend that customers running on older releases switch to Sage Payment Solutions for their Credit Card Processing and obtain a Sage Payment Solutions merchant account prior to upgrading to Sage 100 ERP 2013. Without a Sage Payment Solutions merchant account, integrated credit card processing cannot occur.

Love these comments on the last page of the PDF. Business Partners and customers have a voice in our roadmap and in features and functionality that will be incorporated into future Sage 100 ERP releases. Please use your voice on the feedback and request site www.Sage100ERP.com/Sage100ERPFeedback. Sign up, view ideas already submitted, suggest new ideas, collaborate on suggested enhancements, andmost importantlyvote on the ideas that you value. It takes just a few minutes to participate. 6561 Irvine Center Drive Irvine, CA 92618-2301 800.854.3415 www.Sage100ERP.com What is the Idea web site for???? Oh wait..... Click on the link referenced and where does it take you?????? The OLD Idea website!!!!!!!

Looks as if Sage plans to shut off AP and PR form printing (traditional) after 2013. Filings for tax year 2014 look as if they will require Aatrix (which is keyed to a customer support plan / ID number).

Makes sense from a programming support standpoint. I am highly recommending to all of my clients to switch to Aatrix forms this year. Much better looking (printed) plus easier to align/print. From Sage's standpoint, this will force all of the lagards to get back/stay on support.

I wonder how they are going to widen the AP invoice number and still stay compatible with JC/WO?

Probably some type of key that is the same size? Create a new 20 character field that is on the form - hash it down to current number of characters.

Or they might make it an option - 7 or 20. The downside is it won't work with the legacy modules.

They did it with the AR customer # . Same issues. (it was 7 and it is now 20)

Someone at Summit made the comment that FRx would not work with version 5.

Erika I think but can't swear to it.

Can wait for 5.0 beta.

Beta? No such thing any more. Early adopters now...... Most ""bugs"" discovered won't be fixed until PU 1.

@JeffSchwenk - Thanks for sending me here - I do not know why I missed this thread!

Stuff happens!!!!! Don't forget to check out the ongoing dialogue thread of the webinar. Some interesting comments at the tail end there also.