Printing out FULL decimal places on investment reports (please help!)
Microfiche
Member ✭✭
I asked this question once before - but did not get a useful answer.
https://community.quicken.com/discussion/comment/20000542#Comment_20000542
You can NOT change the number of decimal places that will show in reports for exchange rates - it seems to have been hard coded for 2 decimal places for some bizarre reason.
Printing out the exchange rates from currency list is useless as the rate can be overridden in a transaction (and in my case often is)
All I want to do it to check the exchange rates in my investment transactions by exporting them out somehow - but 2 decimal places is useless in forex.
Anyone?
https://community.quicken.com/discussion/comment/20000542#Comment_20000542
You can NOT change the number of decimal places that will show in reports for exchange rates - it seems to have been hard coded for 2 decimal places for some bizarre reason.
Printing out the exchange rates from currency list is useless as the rate can be overridden in a transaction (and in my case often is)
All I want to do it to check the exchange rates in my investment transactions by exporting them out somehow - but 2 decimal places is useless in forex.
Anyone?
Using Quicken since sometime before the beta test of Quicken 6 for Windows in 1996... 
Tagged:
0
This discussion has been closed.
Comments
I'm wondering in your case is the security of a currency other than what the account is?
In the US version the security has to be setup as the same currency as the account it will be used in. As in the above account is set to CAD and when I created a new security it created it in USD, which is my default currency, and then wouldn't let me enter it into the register. I had to go to the security list and change it to CAD before I could use it in that account.
Given this restriction there is in fact no exchange rate because the account where the cash is coming from and the security are both in the same currency.
I'm guessing that the Canadian version is more flexible and as such the printing problem would only come up in the Canadian version.
For tax purposes, in Canada we need to report gains and losses in Canadian dollars, based on the settlement date of the transaction. In order to do that properly, you need to enter the exact exchange rate (in this case USDCAD) on that date so that when you run your capital gains report, Quicken can calculate the costs and proceeds using that exchange rate (there is an option to use the transaction exchange rate in the Canadian version of the report)
So I have a bunch of transactions in a USD account entered with exchange rate x.xxxx and I want to check to ensure that I didn't enter one incorrectly. The exchange rate is entered at 4 or more decimal places - required with higher dollar transactions for accuracy. Seeing 2 decimal places in the report or export is useless.
That is suppose to go directory to the development team.
The more you can get attention on the problem the more likely it will get fixed.
There is the possibility that Windows is doing something in the background. Did you check this conversation - but this is not specifically about exchange rates but worth checking?
https://community.quicken.com/discussion/comment/20104222#Comment_20104222
Those extra decimal places are essential.
My gut feeling is that they go into the ether, but I suppose I have only lost 5 minutes of my life!
In my case running Canadian 2020, I have Australian formats and AUD home currency, so my US security accounts have exchange rate USD back to AUD. weird for most I know but this should not matter. Then when I hit Ctrl+P I get this printout with no FEX rates on it?! Is yours the investment register, or some kind of linked cheque account (which I have never used BTW).
It only shows up in investment accounts.
1. Run the report as you would in your home currency. Then export it to Excel label the share price column with the currency used eg. AUD. Ensure "Transaction currency" is ticked so you don't get the most recent average FEX Rate. Delete the column that holds the FEX rate that is exported, just keep prices/amounts.
2. On the same report customise on the first tab change the reported currency to the one your shares are in eg. USD. Ensure "transaction currency" is again ticked. Export the report again to excel and same again delete the FEX Rate column it exports.
3. In Excel ensure they are sorted the same way then cut/paste the new column of prices this time in US$ from the second file, next to the **** in the first file. Then add a column in Excel to the right and calculate the FEX rate again in full decimal places.
You have to add a new column and new amounts for each other currency you are trying to extract of course. Rates should turn out to be very close to those in each transaction, although there will always be small differences? But you have to do it outside of Quicken.
David
None of the investment companies I have ever dealt with track the CAD ACB of foreign securities according to CRA rules, which require that you record each transaction in CAD using the exchange rate on the settlement date of related transactions. The investment company I am with currently is the closest to the rules so far, but they use trade date rather than settled date. Particularly this year, a few days can make a huge difference on large trades. Most companies just track in the foreign currency and then give you a report that converts all the values using the current exchange rate - which is useless.
So when I enter transactions in my foreign currency investment accounts, I enter the USDCAD rate based on the Bank of Canada rate for that day. At the end of the period, I would like to run a report to compare those entries to a daily Bank of Canada rate chart to ensure I didn't typo anything. Without a report, I am stuck manually scrolling through each transaction and visually comparing to a printed out sheet of rates.
Yes, there are workarounds that "sort of" work - and that is what I have been doing. But none of them are as exact and as easy as this method should be...