To provide Reconciliation reports between sub-ledgers module and GL for easier reconciliation of balances in the events that subledgers balances does not tally with GL control account balances.
by: AFON S. | over a year ago | General Enhancements
by: AFON S. | over a year ago | General Enhancements
To provide Reconciliation reports between sub-ledgers module and GL for easier reconciliation of balances in the events that subledgers balances does not tally with GL control account balances.
by: AFON S. | over a year ago | General Enhancements
Comments
agreed
With the exception of Payables Clearing, all the necessary reports are there.
I agree with Rebekah, the standard reports are fine.
Except for PJC WIP report, which is terrible.
I agree reconciliation of clearing and control accounts is really big big task for users
I voted for this, but it would be better if the subledger balances could never get out of agreement with the control accounts in the first place. Having accounting software that doesn't enforce this is like keeping a dog but having to do your own barking.
> it would be better if the subledger balances could never get out of agreement with the control accounts in the first place.
you can already set up "control accounts' to not allow errant posting.
but user can still post a transaction to the AR_control from AR module.
i agree with shamprasad R
go to http://www.hwmtech.biz for an excellent solution!!!
Having these reconciliation reports is a good idea, however I agree with Jim R and Geo F that it is more important that Accpac has the ability to prevent manual postings to Control Accounts (idea 893).
Needs more than reports - needs tools. There are already various third party tools with on-screen recs, drill downs and identification of missing parent or child entries. Sage would be best to grab the best one and OEM it ( only if it is written in the SDK - please!).
Viola - instant new cool feature everybody will love.
Why a tool William? If so then would maintenance and correction thereof be be done in the background or directly in the database itself? From my past exposure in correcting these errors is that they emanate primarily from user input therefore the correction enables the user to understand the cause / reason for the error occuring. Also the corection is always an accounting process or procedure and hardly a technical one. This would scare off users into believing that Sage 300 ERP has programatic flaws which would make them lose their faith in Sage 300 ERP techinical abilities and flow processes?
Tool would not allow new entries, only dynamic investigation of them. A report is flat and difficult to work with, an on screen tool that shows summaries then can expand to one area and its associated entries is a lot more powerful. And of course it would have related reports.
I agree corrections needs to be done using normal processes.
Accountants buy ERP systems, or are strong influences. And accountants need to place a lot of focus on reconciliations. QED.
Hi William, please have a look at our application RecIT! and comment thereon? If you like I could forward you some sample reports.
Hi Andre, please sell it to Sage :)
For over a year ago read over 4 years ago
This idea is now well over 5 years old
This comment posted 8 March 2016
Hey Sage, Apple was probably still $17 a share when this idea was created. ANY feedback ? Email me if its too embarrassing to publicly discuss.
Posted by William on the 22 Jan 2020 - just for transparency of age, which this ideas forum prefers to keep in the dark.