Breaking news from around the world
Get the Bing + MSN extension
Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2019 release wave 2 Discover the latest updates and new features to Dynamics 365 planned through March 2020
Release overview guides and videos Release Plan | View virtual launch event
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Talent TechTalks | Upcoming TechTalks
I entered an invoice via Transactions>Purchasing>Batches but did not enter a dollar amount in the Purcahses field on the PayablesTransaction Screen. I entered all distibutions and posted the transaction.
All the distributions are in the P&L and the credit to A/P has been posted. The invoice shows in the Vendor Innquiry as HIST with a dollar amount of zero.
Now I have a historical invoice with zero dollars yet my P&L has been hit with the expense and A/P has been credited but I have no open amount to pay and clear A/P.
When I select Void Historcial Transaction this transaction does not show up.
How can I void this transaction so I can re-enter it and make a payment?
I have a client that had the very same situation last week. Unfortunately, the only way to resolve this one is to remove the record directly from the SQL tables. There is no way to correct it through the user interface. If you send me an email with the details of the transaction, I can tell you what tables you'll need to delete the record from.
Hope this helps,
I have a similar issue where our client entered a receipt against a PO and created an invoice with $0. The distributions were entered and hit the accounts. There is no way to void the invoice. How can we void this transaction? Will a return be the best way to handle this or will we have to update the tables in SQL? If this has to be fixed in SQL, can you tell me which tables?
Frank, I've also seen this at clients, of course the way you find it is you can't reconcile the account and suddenly you find the $0 amount. I know that I went into SQL and corrected the amount instead, but there should be something in Great Plains that won't allow a $0 transaction to be posted. Surprised that no one has complained in the past. I'll go put it out on Connect and see if we can get some votes on it. Or has this been fixed in 2013?
Here is where you can go vote to get this fixed:
Here's where you can vote to get this fixed if they haven't already in 2013
Thank you for responding to my post. What did you correct in SQL to fix this issue? Should I remove the invoice from the PM30200 table and the GL transactions from the GL20000 table? I see that this invoice is also referenced in POP30300 in the VNDOCNM column and in SOP30200 in the CSTPONBR column. Or should the client just make a GL adjustment for the invoice? Any advice is appreciated.
Hi Carolyn, I wish I could help you. After 3+ years, I don't even remember having the issue, let alone how I resolved it - LOL. Susan, can you help out?
Susan - the problem with not allowing $0 transactions is that sometimes you actually want to enter one for a valid reason. I find there is often a very fine line between preventing mistakes and restricting functionality.
Bonnie - another possible way to fix the issue may be to enter a non $0 AP transaction and change the GL accounts so that they net out to $0. This would fix the AP subledger without changing the GL, which is already correct.
Have you thought about removing the errant historical transaction using Utilities? You could then re-enter the document using the original document number. You can keep the transaction from posting through to GL using Posting Setup and then deleting any GL entry so that you do not double up on your income statement.
Using Utilities will ensure that all of the appropriate tables are hit because you can do it from the user interface. What do you think?
I have same issue, please guide me what are the steps to remove or resolve the above issue.
If you want to Remove (Delete) the historical transaction, use Purchasing | Utilities | Remove Transaction Entry. First, backup your database. Restrict the utility to the specific voucher, insert the restrictions, check all of the boxes and then click the 'Process' button. This is not a reversible event. It will not impact the general ledger.
After you have deleted the errant entry, go into your Posting Setup window and make sure 'Post Through' is not selected for the Payables Transaction Entry Origin. Create the entry in the correct manner in payables and post it. Go back into your Posting Setup window and reset it if you had originally selected Post Through. Open your GL General entry window and delete the journal entry transaction created by the PM module for the re-entered transaction.
Business Applications communities