This is a pretty big one. 
I learned yesterday that when I change the date of a transaction, the exchange rate doesn’t always get updated. I’d estimate it fails >50% of the time.
I had to manually delete and re-enter about 30 transactions yesterday after I realised this. The bigger issue is that there’s no visual feedback when the update succeeds or not, so I have no way of knowing except to know what the current exchange rate is and assume it must be different for any other day.
What sort of transactions are you referring to? Are this transactions on the bank? Are you using a date picker or directly entering the date?
It’s odd that it would happen intermittently like this.
I noticed this on adding payments to invoices. At first I thought it was that I was typing the date instead of using the date picker. However, further testing showed that it didn’t matter. I was copying data from our old system so I was repeatedly entering a lot of EUR transactions. Tried in two browser, intermittent failures in both.
I suspect it’s not browser related, do you recall what date range these invoices covered? It may be that for some earlier periods we did not have exchange rate data, but this I believe would need to go back some way.
Did you create the invoice first then go back and edit the dates? Just trying to identify some steps so we can reproduce the problem.
Invoices were all after 1 Oct 2016. Process was create invoice in EUR, go to invoices list, click chip payment icon, enter date, tab, click save. I was doing these pretty fast, and I usually use the keyboard so there wasn’t a huge delay between changing the date and coming out of the field. Then I started entering dates with the date picker instead, and that didn’t seem to make much difference. I’ll try it again with the browser console open, I’m doing more data entry today, oh yay!
Sorry just one more detail… were these invoices paid into a EUR account or a GBP account?
Hmm, you raise an interesting question. On many of them, it looks like I may have been incredibly stupid. Most of them were paid in EUR into an EUR account. So the exchange rate really didn’t matter. DOH!
However, some of them were in USD paid into a GBP account. I saw the same issue on them. They all had different dates but all had the same exchange rate.
When a payment is lodged to a foreign currency invoice but received into a GBP bank account QuickFile will present two boxes so you can explicitly set the amounts in say USD and GBP, the exchange rate is then inferred from these two figures.
Right now changing the date doesn’t alter the GBP amount and therefore does not modify the exchange rate. It has been suggested in the past for the GBP amount to update on date modification, we can certainly do this but I believe it should only happen if the GBP amount has not been manually overridden by the user.
It works this way as in the case of GBP transactions often there is a very specific amount received in the bank that must be matched to the penny.
OK, so the rate gets locked as soon as there’s a number entered. Hmm. I was doing this late at night, so I missed the fact that I was recording EUR payments into an EUR account, and so the exchange rate may not have mattered there.
But I was also recording USD payments into an EUR account, via a “virtual” account in the middle. In that case, the exchange rate doesn’t necessarily matter, depends on how currency gains / losses are calculated behind the scenes, but there was no bank transaction to get the exact numbers from.
Bottom line, this seems like a pretty minor issue given that it only applies to a very specific edge case.
I’ve reclassified as a “Support” post for now. Our development team will take a closer look next week. I think it would benefit from dynamically binding the rate & GBP amount on date modification (on the proviso the user hasn’t edited it first), it will probably help in a few cases such as the one you described.
@QFMathew Just to clarify, it does that now. When I change the date, the rate gets updated. But that was intermittently failing for me. In a quick test right now, it’s updating every time, so perhaps it was a temporary issue, or maybe there’s some intermittent issue.