Applying pmt entries: you are not allowed to apply + post...

ajmalsherif
Member Posts: 111
Hi
I am sure this has come up before but i couldn't find any thing when i did a search...
I have a vendor pmt on account which is then followed by a couple of invoices- however when i start by applying the payment and then try to apply the PI (F9) - i get the message:
"You are not allowed to apply and post an entry to an entry with an earlier posting date.
Instead post payment XXX and then apply to the PI yyy"(i can see the open payment but i cant post it.
Is there a work around suitable for a busy accounts department or is there a fix for this (we are on V4 SP1)?
Thanks in advance for any suggestions.
I am sure this has come up before but i couldn't find any thing when i did a search...
I have a vendor pmt on account which is then followed by a couple of invoices- however when i start by applying the payment and then try to apply the PI (F9) - i get the message:
"You are not allowed to apply and post an entry to an entry with an earlier posting date.
Instead post payment XXX and then apply to the PI yyy"(i can see the open payment but i cant post it.
Is there a work around suitable for a busy accounts department or is there a fix for this (we are on V4 SP1)?
Thanks in advance for any suggestions.
0
Comments
-
I think this means someone has already made a manual application through the vendor ledger entries. Go to the vendor ledger entries for this vendor, find the PI you are trying to post, go to Functions-> Apply Entries. In the 'Applies-to ID' column there should be someone's username. Either select Application->Post Application, or remove the application so it can be posted through a journal.0
-
They haven't been applied -there is no name in Applies to ID0
-
Oh, then either make the posting date of the payment after the date of the PI, or post the payment by itself and make the manaual application from the vendor ledger entries.0
-
Thanks - what i have done is 'Reverse Transaction' for the payment and then re-posted it with a date of the last PI - which is similar to your suggestion.
Just seems a bit daft that we have to do this0 -
If I recalled correctly this "feature" was introduced in version 4 & created a lot of prepayment problems. Until now nobody seems to know why this "feature" was introduced...
Maybe someone here can enlighten meNAV - Norton Anti Virus
ERP Consultant (not just Navision) & Navision challenger0
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 116 Navision DOS
- 851 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 617 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 320 Dynamics CRM
- 111 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 990 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 35 Design Patterns (General & Best Practices)
- 1 Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1.1K General Chat
- 1.6K Website
- 83 Testing
- 1.2K Download section
- 23 How Tos section
- 252 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions