Currently, when data is added or updated, the results only flow downstream. This can cause building differences that become locked in after two years. As well, numbers can vary report by report (even within the same module - e.g. open invoices as compared to aged invoices). Any accounting system worth its weight needs to be able to withstand the abuse of the most disinterested accounting clerk. But with Sage 300 CRE, it's far too easy to make database errors even with a full education in its use. When I used to use Sage 50 (Simply Accounting), while I understand it was a far simpler setup, it integrated better with itself. For instance, when a GL entry was made to cash, it was added to the bank rec. That doesn't happen with Sage 300 CRE because Cash Management is upstream from the GL. You shouldn't have to manually reconcile modules to the GL each month. It really should be setup in such a way that these errors can't or very infrequently happen. As it stands, I've been finding several entries every month dating back as far as our records go (over 15 years).
by: Zach P. | over a year ago | 7 General Enhancements
Comments
Completely agree! While Sage has some great features better than less sophisticated systems this is a huge area where Sage CRE 300 can improve. Our previous software allowed us to post from one module to another and vice versa, updating all key tables either way. I would add to your notes that a GL entry should post to CM and also likely the AP vendor tables (for interest expense for example). Although each module should be able to interact with the others, two other key areas I'd say in this product that should integrate better with each other are AR and AP with one another for refund processing and also Service Management with (from) all modules (PR, AP, AR, JC).