You’re offline. This is a read only version of the page.
45
Hi Experts,
I research Posting definitions in https://technet.microsoft.com/en-us/library/hh242107.aspx, https://technet.microsoft.com/en-us/library/hh227607.aspx , ...
I setup Posting definitions for Purchase order as follow:
( 15210000: material account,33110000: vendor account).
then, I created PO and Invoice PO is error:
Can you help me fix this error ? Give me a example about setting up and running it.
Thanks in advance
Best regards,
Hoa
*This post is locked for comments
Hello Kristi,
In your case number 2 you mention only invoices. Does it work for PO receipt as well and how ? I’ve tried confirming the PO and it works fine, but not with the recept.
Many thanks
Hi Canh Hoa Le,
Posting definitions are an alternative(=) to posting profiles
docs.microsoft.com/.../about-posting-definitions
Hi Canh
I face this error before and the reason was that I didn't create posting definition for AP so AX couldn't post the vendor invoice. U have to create more than one posting definition ONE for purchase order AND one for each Vendor group.
Kindly check the link below:-
Hi Xanh Hoa,
The provided Link (technet.microsoft.com/.../hh412236.aspx) by Ludwig Reinhard is queit comprehensive and can help i this case.
You have also an alternative to create profile on Vendor posting profiles (AP > Setup > Vendor posting profiles) with required values on each fields (i.e. Account code, Account/Group number, and etc,) and then invoice the PO.
Regards, Alireza
Please see this site for examples, including the account names. There is a scenario specifically for purchase order encumbrance.
[quote user="Kristi Weekley"]Any accounting entries created on the PO will be reversed when you post the vendor invoice[/quote]
Normally what would be the accounting entries in this case , i mean account names ?
Lally,
Any accounting entries created on the PO will be reversed when you post the vendor invoice. BUT.....you need to make sure that the customer even wants to post to encumbrance for the PO. That is typically only used for public sector. If you don't want to encumber (which is basically recording the budget amount reserved in GL), then you won't setup the posting definitions for the PO.
The accounting entries for the vendor invoice are NOT reversed. Again, I only mentioned that posting definition could be used to include additional ledger account but that is only for very specific scenarios, typically in public sector for fund accounting. Most organizations that are NOT public sector will never do this. They will only have one Generated entry, which the AP ledger account.
I'm not aware of a manual, but the link that Ludwig referenced above has a lot of good examples. Please remember that these examples are written from a public sector perspective, so you have to evaluate YOUR business requirements when you setup your posting definitions.
Here's another link (which also has additional pages about PD): technet.microsoft.com/.../hh242680.aspx
Kristi
Good to see that MS team helping helping to give the explanation.
As you said that The posting definition you defined was specifically for the POs posting, and NOT the PO invo?ice posting.
In this case system posts amounts to ledgers , then when these ledger entries will be reversed ?
For the vendor invoice this would be your AP ledger account. In public sector organizations, they may even have an additional two ledger accounts (posting an additional DR/CR for the same amount) in the Generated entries.
When these accounts will be reversed ?
Does any manual available with detailed explanation that how this functionality can implement to clients ?
Hoa,
Posting definitions is an alternative to the posting profiles, and is only available for documents that have implemented the source document/accounting framework. When defining the posting definitions, there are two basic scenarios:
1 - Documents that MAY post to GL - Today in AX this includes the purchase requisition and the purchase order. For most organizations, these documents don't post to GL, but if you are a public sector organization, then you can enable posting of pre-encumbrance (Purch Req) and encumbrance (purch order). When you define the posting definitions for these documents, you have to define BOTH the DR and CR in the Generated entries section. This is because the PR and PO don't post to the actual asset/expense ledger account on the Accounting distributions, but instead is just used as input for how to encumber the amount of the purchase. The posting definition you defined was specifically for the POs posting, and NOT the PO invoice posting. This is why it is failing. You are missing the posting definition setup for the vendor invoice. See my next point for this.
2 - Documents that always post to GL - This includes all your other typical documents, such as invoices that must always post to GL. When you define the posting definitions for these documents, half of the accounting entry will be the ledger account on the accounting distributions (the asset/expense). This ledger account(s) becomes your match criteria in the posting definitions. You need to then define what the generated entry will be, which is the other half of your accounting entry. For the vendor invoice this would be your AP ledger account. In public sector organizations, they may even have an additional two ledger accounts (posting an additional DR/CR for the same amount) in the Generated entries.
Based on this I hope you understand that you need to define a posting definitions specifically for the vendor invoice, NOT the purchase order.
Thanks
Kristi
Hello Hoa,
It Looks as if you miss a second line in the generated entries section.
You can find some example for comparison here.
technet.microsoft.com/.../hh412236.aspx
Hope this helps,
Ludwig
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,134
Super User 2024 Season 2
#2
Martin Dráb
229,928
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (