Try Microsoft Edge
A fast and secure browser that's designed for Windows 10
I have enabled Using posting definition Under General ledger parameters.
I created Posting definition PO1 for module Purchasing and attached it in Transaction posting definitions.
When I posted Purchase order I was able to hit the accounts setup under Posting definition. But when I posted the invoice system is throwing an error Voucher do not balance.
Further, I went and created a posting definition PO2 for module Accounts payable. And attached this in Transaction posting definition for vendor invoice. But I am still getting the same error i.e. Voucher do not balance.
Please suggest. Or please let me know if I can refer any document for Posting definition related to vendor invoice.
I think posting definition does not work with invoice journal only with "free-text" vendor invoice. I didn't find any documentation about it, but it simply doesn't work.
Probably you need to set up vendor posting profile because invoice journal will use account from it.
Can somebody confirm this conclusion?
Can the OP share what is the business scenario that requires him to use posting definitions?
We are trying to setup budgetary accounting where each cost account defines separate liability account.
Posting definition would be great setup for us, but it doesn't work in the forms we need.
Do you have any other suggestion?
Did anyone get the solution :(
well.. seems it doesn't work you will need to involve developers :)
We used vendor journal for user data inset form, then we transfer data into the vendor tax invoice and post it. This way, we are using vendor journal wich is more familiar for users and vendor tax invoice form for posting, because only there posting definitions for vendor work.
So, posting definitions for vendors only work in one forme - vendor tax invoice.
I can share setup if you need it, but it's the same you mentioned above.
In a conversation with the Microsoft R&D team they indicated their strategic plan is to continue and add functionality to the "Vendor Invoice" form, which the "Invoice Journal" form is more or less going to be deprecated eventually.
So for companies implementing it makes sense to focus on implementing using the Vendor Invoice form.
Posting definition only works with documents that are based on source document framework. For the list of documents, you can use the transaction posting definitions. It does not work with invoice journal which is based on journal framework.
Please share the error message details, which will help us understand which specific account setup is missing.
yes, we figure it out already because it just didn't work, but thank you for answer.
AX provide no error, it just doesn't post on the account in posting definition, it uses only account in posting profile.
We fixed it on two different ways:
1. for vendor journals we used invoice journal as the insert form for users, but before posting we transfered all data in vendor invoice form and posted it from there.
2. for general journal we tricked AX on some specific journal types that we opened that we are using transaction posting type on which posting defition works (we need it for customer payment when we import it from bank statement in general journal).
I hope it would help :)
You need to create a new posting definition(say Purchase) for that and select module Accounts Payable,
In match criteria select Ledger account where you book your purchase expenses,
and in generated entries select ledger account of sundry creditors or any other ledger account you want to credit against purchases like Project account.
Then click on Related Information Button on the top, go to Accounts payable tab-Vendor Invoice, and create new line there with item code and account code all or as per your requirements, and select posting definition as 'Purchase' that you created.
Then try to post your invoice.
But your Inventory Posting setup should be complete as ledger account of purchase expense will be picked from there.
yes - this is standard procedure but it doesn't work for journals.
Only for vendor invoice form if we talk about AP module.