Error: A currency to convert from is required to retrieve exchange rate information.

While posting Pending Invoices in AX 2012, there are cases when this error message is shown and the posting is cancelled.

What is more annoying than the error is that the infolog is very cryptic and reads:

Error: Exception has been thrown by the target of an invocation. A currency to convert from is required to retrieve exchange rate information.

More often than not, the currencies and exchange rates are available in the system and other related configurations for multi - currency transactions are set. This issue was common in the Feature pack, but is sometimes observed in R2 as well.

There is no known KB or hotfix available for this and no defined cause for its occurrence. It is as random as can be and will pop up when least expected.

Although no permanent fix is available, it can be sorted, until further occurrence. And considering it is rare to encounter this issue, one can ensure the client that the issue is fixed for good.

Caution: Please try in test environment before applying to Live instance. Take necessary backups before performing the activity in Live.

Resolution:

Make note of the Purchase Order number for which the Pending Invoice posting is causing the error.

Delete Pending Invoices and matching history for the related Purchase Order:

Accounts Payable >> Common >> Vendor Invoices >> Pending Vendor Invoices

Accounts Payable >> Inquiries >> History >> Approval Journal history and matching details

Sometimes, even after deleting the pending invoices, the issue persists. Then the details must be deleted from the DB as in some cases there are multiple records at the table which may or may not reflect on the form.

Note: the erroneous records have a status: Waiting in the table. DO NOT, in any case delete any records with status: Executed

For this:

- Note the PO and Invoice details

- Go to VendInvoiceInfoTable

- Filter by PO number/ pending invoice number

- Select all available records, that have a status other than Executed and delete.

This is an alternate solution and has to be applied with discretion. It may not always solve the issue and deleting records from the Table must only be done by experts after taking all necessary precautions.

Any other solutions, do leave comments below :)