At this moment, document dates from sub ledgers are not carried over to General Ledger Transaction Date, rather it is showing Posting date from sub-ledgers. This has defeated the purpose of viewing GL Transaction Lisitng report which it does not tell the user of this reports, when was the actual document date. For example: i would like to know why this month (period) 7 transactions are so high, but looking at the transaction date (document date from subledgers, in 5.4). We know that this is a backlog transactions from June.
by: Disa W. | over a year ago | Financial Management
Comments
3 years overdue!!
Good idea
Document date used to be carried over to the GL Transaction Report, but not anymore. The Posting Date is now used since V5.5. See KB Article 26540. The Posting Date may not have anything to do with the Document Date (and are usually not the same - particularly with A/P). Going to Posting Date in the GL Transaction Report is a backwards move by Sage and needs to be rethought (and fixed ASAP). I need a GL Transaction Report showing the date of the transaction, not when I got around to posting it in the G/L. This is a SERIOUS problem.
Caused a major problem for one of my units that moved from Oracle to Accpac. 5.4 used to have this feature. Needds to fixed as a product update to 5.6
I really don't get why Sage can't see this as a major accounting flaw.
Please can Document date be made avaliable in GL Integration!
Yes please!
Another vote for the inclusion of this functionality.
Feature will be helpful. Yes please!
Make it so. This is such an obvious feature for accountants to have that it should not have changed without polling the clients and partners in the first place.
I agree with the other comments. Transferring the posting date instead of the document date causes auditing issues for many companies. I understand the posting date is needed to properly revalue transaction for multicurrency users. An option in the GL Integration to select either the document date or the posting date to transfer to the GL would give the end user the choice and should be an easy change since the GL Integration function already exist.
As I've alreay discussed with the Sage team, this change has caused a MAJOR issue for a client that depends on G/L transaction reporting that goes out to multiple managers at multiple sites and they need to see the original document date. In my client's case, they are already using the G/L ref and desc fields, but having the added G/L integration option would be better than nothing. Ideally it would be best to have a seperate field. I've been told that no changes are in the works now because it is not high up on the priority level. Please vote for this idea if you agree the priority needs to be moved up. Thanks!
I agree whole heartedly with the above comments. If only one date can be sent to the ledger, why not give users the option to override the fiscal year/period. This will accomplish the same objective.
Yes it worked this way before. It was better in the subledger when you changed the fiscal period rather than using a posting date. IE benefits company sends the invoice for the following month on the 28th of the month. The invoice date for August would be July 28. In 5.5 the invoice date was July 28 and you just posted it to the corresponding fiscal period that the cost should apply to. Now you have to use a posting date of August 1 which is also how it shows in the GL. This was a step backwards.
Should be a selectable option in each subledger.
Agreed. An option for this would be ideal.
Should be an option for each specific subledger.
At least another field should have been added to the database instead of changing the behaviour of an existing one.
I definitely agree. This is causing quite a difficult time for my clients with their auditors and also with Gov't tax auditors. This does not follow GAAP at all. Also as above invoices that get entered in the beginning of the month for the prior month. Managers and sales people who rely on transactional reporting, have a hard time trying to tell them if they are meeting their budgets or not. They are starting to go back to using their spreadsheets to track this. They are not happy about this at all. Add another field or have it as an option to pick up either date.
This is a major "flaw" that has come from programmers and obviously not from accountants. If there is/was a need to send the posting date to the GL from the subledgers then this should have been added as a new field to the GL and the original document date kept. When the new Posting Date field was introduced I asked why it was added and what would it be used for. I never did receive a reasonable answer to this question.
All clients view the GL Transaction Listing and identify subledger transactions which may be posted to the wrong fiscal period by comparing the GL transaction date with the fiscal period. However this can no longer be done and instead this has caused huge issues for a number of clients. This new "feature" has made it almost impossible to track down differences between the subledger aged reports and the GL control account balances. I have had to write several reports and give them to clients for free just so they are able to balance things.............a complete waste of my time and clients time when it was so easy before.
BTW - this does not follow GAAP any longer and makes any auditing extremely difficult. Just try explaining this to the accountants who audit and they literally roll their eyes and groan.
Add back the document date field to the GL and if you want keep the posting date.
I have to also agree with everyone else's comments. This was a backwards move by Sage that needn't have been done because there was no problem in the old system that needed to be solved by makig this change.
I am hoping that Sage admits this was a problem, corrects it by returning the old functionality, and move on.
With all due respect, the whole idea of going to transacion date field (instead of the origianl Year-Period field) as a way of determining the fiscal period to post the transaction into was unneeded... this was a solution to a problem that didn't exist. What was wrong with simply selecting the yaer-period? Having to now select a transacion date is much more confusing, and I have had to explain to every 5.6 upgradde "now, instead of putting in the year-peruiod yu want to post to, you need to put in the last day of the month that correlates to the year-period you want to post to."
How does that improve anything? It just makes it more confusing. And now we've lost the transaction date in the GL, which is a disaster and totally dimishes Accpac's reputation as having on of the best GL's around. This is a serious deficiency.
PLEASE SAGE - Go back to the old method of having a transaction date, and a Year-Period for evey subledger transaction. And go back to sending the transation date to the GL, and the Year-Period. It worked fine before, but this new change has made it a worse product. Thanks fcr listening.
Ken A.
Agree the doc date is very useful in GL.
Just add the extra date field in the GL - keep the posting date where it is in the GL , have a new posting date field, show on key reports / allow it to be used for selections.
Just add the extra date field in the GL
Please add the transaction date from the subledgers back to the GL transaction listing report. The GL transaction listing report, which was perhaps the most useful GL report, must now be supplemented by subledger inquiries to see what actually transpired. I suggest this change should be fixed in a 5.6 patch/minor update. This is our biggest disappointment with the 5.6 version and offsets any positive feelings from enhancements over version 5.4.
This 'innovation' was very poorly implemented by Sage. Overwriting the original Document Date from the sub-ledger is absolutely pointless and makes our custom reporting a nightmare as we can no longer report on GL Transactions using the original document date. Other systems I have used keep both dates and allow reporting by Document Date or by Posting Date. We also have had to revert to manually creating spreadsheets to satisfy requirements for our Auditors. This is very time consuming for us and very frustrating as we previously had Crystal Reports etc which gave us these figures quickly. It's definitely a step backwards for us....
I can't believe something as critical as this has not been promoted to Planned.
It is clear that Sage is NOT listening. Many votes, many motivations and even the GAAP angle is being ignored.
Our accounting firm is using Accpac ERP to do the bookkeeping for 400+ clients that are in the agriculture industry. These businesses report on a cash basis only and for this reason we require the ability to override the posting year/period in the AP and AR modules so we can see the transaction date in the general ledger and not the posting date. The only other option is to start a new batch for each day of the month in which a transaction takes place. This makes data entry much too labour intensive. It also poses a greater issue at the year end when cheques are clearing in the 1st period of the new year that were written in the 12th period of the prior year. Obviously, we cannot have these items posting back to the prior year when that year is closed and ready for tax work. A fix for this is urgently needed, and not in the next version but in the form of a patch or a hotfix!
Agree that this was a backwards move -- can't imagine how it helps anyone but someone obviously wanted it. Even the ability to include transaction date as text in GL integration from the subledgers would be helpful
This feature in it's present form is quite helpful to us. We follow the posting date as our accounting date and happy that same is appearing in GL Transaction History/Listing.
This feature is very much helpful to implement a strict period cut-off and closure process. Once we close a period (month) and report the financial for that period we should not post anything to any date pertaining to the closed/reported period.
An example of the scenario:
We closed the period on 30-Nov.
On 2-Dec, we received a supplier invoice pertaining to 29-Nov (time taken by postal service).
As we have closed November we need to book it on 2-Dec, that is the day we have received and accounting. At the same time we need to capture supplier invoice date also. So we capture supplier invoice date in "Transaction Date" field and 2-Dec in "Posting Date".
Both AR Customer Transactions and AP Vendor Transactions reports are designed to list the transactions on Transaction Date basis. So we have developed two macros to print AR Customer Transactions and AP Vendor Transactions based on "Posting Date" basis. These reports reconcile with GL Transaction Listing report for a given period.
I can't believe something as critical as this has not been promoted to Planned.
It is clear that Sage is NOT listening. Many votes, many motivations and even the GAAP angle is being ignored.
COME ON SAGE -- get this sorted, it is a huge nuisance factor... We need to be able to see the transaction date in the GL
I don't understand why this isn't obvious. if there is somebody who doesn't want it, then make it a set-up option. Why does something with this many votes not get done?
Please sort this out !
Yes please, this would be awesome!!
Yes, Sage MUST fix this error ASAP!
maybe we need to start a petition on www.change.org to get Sage to notice. :-)
I have asked Sage directly, will post updates here
Good news, I asked Sage directly, their comment on 21 Feb 2014 :
"It is being considered for 2015 release"
Can anyone assist me? My AR GL is more than the sub-ledger. I have checked the receipts and they are posted in the correct period. How can this be fixed?
Hi Jodiann, please either review with your Sage consultant or goto the general Sage forums
Document date
Transaction date
Fiscal period
These are all different things and no accounting software should make any assumptions about the relationship between the three. When I opened ticket 8004097819 with support, they referred me to this website.