Say there are 2 invoices for a customer. First invoice of value 100 and is due for payment. Second invoice for value 150 and is not due for payment. Customer makes a payment for 100 pertaining to first invoice. User incorrectly applies it to the second invoice. Customer ledger entry pertaining to second invoice shows remaining amount as 50. At this point in time if customer statement is printed, the system correctly shows that first invoice as unpaid but the fact is different. How to rectify this? It is also possible that the user actually applied the payment to the correct invoice but later on the bank reported that the cheque has bounced, how to handle this when cheque printing is not used?
Hi Rajiv, Reapplication of entries is not possible in Standard Navision Attain. Once an application is done, the same is confirmed as final. This is a common shortcoming which is yet to be added as a standard feature in the Attain functionality. However the only workaround for this is to post necessary rectification journals for both the invoices and payments to recorrect the situation as desired. However there are some add-ons available which provide this functionality.
Hi Another idea would be: Use a dataport to export the involved customer ledeger entries. Change the fields (Open, Closed by Entry No.,Closed at Date,Closed by Amount) with an editor. Import the records with the same dataport. It works [8D]. bye André
Thanks Rohit and Andre I think dataport option is not bad if it can serve the purpose. However have you also used in scenarios where a payment was applied to multiple entries. I am going to try it out and will post the outcome. Remaining amount field will also require changes.
Hi Rajiv,
quote:
Originally posted by rajiv_tyagi
… However have you also used in scenarios where a payment was applied to multiple entries. …
No I haven’t done it yet with multiple entries. But I think there shouldn’t be any problem as long as you take care with the amounts.
quote:
… Remaining amount field will also require changes. …
YEP. You are right. Please note: IMHO you shouldn’t publish this method to a wider range of people. You change posted records. This could be a violation of security rules e.g. by the auditors etc. [;)]. bye André
Hi Andre I tried and it works but life is not that simple with Attain, now you also have Detailed customer ledger entries with entry type Application. So when entries are applied additional entries are created in detailed cutomer ledger entries.
quote:
Originally posted by rajiv_tyagi
Hi Andre I tried and it works but life is not that simple with Attain, now you also have Detailed customer ledger entries with entry type Application. So when entries are applied additional entries are created in detailed cutomer ledger entries.
Hi Rajiv You are so right[:(]! Regarding the additional entries: I must confess I made similar changes long time ago. Sorry for forgetting these entries. bye André
Maybe the void payment function from SimCrest will do the trick for you, it voids the payment (like the check bounced) and reopens the applied documents again. http://www.simcrest.com/Simcrest1/SimCrestproducttemplate1.asp?ProductID=Void%20Pay
And maybe somebody also forgot about the application entries table… where you’re also having to change the things… By default: 1) Never use dataports for exporting/importing ledger entries… specially on Attain… you’ll mess up your data easily and you’ll get in trouble when doing an audit. 2) Always try using standard ways first: for doing such thing, you can always credit the payment and set a new payment to the invoice where you didn’t apply properly. Regards,
Hi Alfonso
quote:
Originally posted by apertierra
And maybe somebody also forgot about the application entries table… where you’re also having to change the things… By default: 1) Never use dataports for exporting/importing ledger entries… specially on Attain… you’ll mess up your data easily and you’ll get in trouble when doing an audit. 2) Always try using standard ways first: for doing such thing, you can always credit the payment and set a new payment to the invoice where you didn’t apply properly. Regards,
- I can’t agree with your ‘NEVER’. Your are right you should try to avoid it. But during the daily work with an ERP system it could happen that you need such ‘work arounds’. I call this “work at the heart of the system”. Then you have to know what you are doing. This is the reason why I write a Note in my posting above. Of course you shouldn’t tell such ways to the auditors [;)]. 2)How can I remove an applied payment from a customer record? bye André