Notice of Maintenance on October 9th. Click here for further details.
SAGE 300 ERROR Document currency differs from tax reporting.
Why is the document currency not updating and I have set the tax reporting currency to a currency other than the functional currency.
When I select the vendor when creating the AP Invoice, the document currency is not updating to the tax reporting currency. It still remains as the default functional currency.
Hi Ian Nyingi the Vendor Account Set currency will drive the Document Currency. For example in the screenshot below, this is a Canadian Dollar company. When I opened a blank Invoice Batch, the currency displayed as CAD by default. As soon as I typed in vendor 1350 (A USD Vendor) the Currency for the Document immediately changed to USD. So check the Vendor your entering is setup for USD like the below by checking the Account Set the Vendor is allocated is in USD:
The next part sounds like its OK but just to double-check, Tax Currency by default will be driven by your Vendor's Tax Group:
Hope that helps - let me know if I've misinterpreted your question 
Good luck!...Tim.
Hello, I had configured the Account sets correctly as shown below.
Hi Ian Nyingi Please also check the Processing tab for the Vendor. Please ensure the Currency code is correct - can you check the Processing tab then try entering an invoice again? Depending on the original Account Set when the Vendor was created the Currency Code could differ to the current Account Set. Good luck!
Hello. I think I have figured it out. The user had imported the vendors using an excel template and they keyed in the wrong currency codes for vendors. Below is an Vendor export template.
I have updated the vendor currency as shown below.
UPDATE APVEN SET CURNCODE = 'USD' WHERE IDACCTSET = 'LOCUSD'
It has worked.
Hi Ian Nyingi nice work identifying and resolving the issue. Just a note that fixing issues in SQL is generally OK (and sometimes required) but if you can resolve a problem through the GUI or via import I always recommended it as making changes through SQL bypass the controls and input sanitization and can sometimes result in other required areas of the system not being updated at the same time. Again in this case its a simple SQL statement and the record being changed is straight forward but it's something worth keeping in mind . Thanks again for the update.
Hello,
I tried to import using the correct Excel template, but it did not update the currency codes. Additionally, when I look at my vendor processing view, if the currency was set to the default functional currency, it is difficult to update it as I don't have the view or the icon to do so.
The first screen shot is before the update. 
After the update. 
