I've been using MD without the setting for separate tax date for a couple of years. But I've just enabled it, solely for the sake of one annual fund distribution payment which needs to be reported in the previous year's tax return.
It's a good feature, but I'm already finding it's behaviour rather annoying and efficiency-reducing - and on reflection the problem may be a spin-off from a relatively new enhancement. (Am I right that the the way the date of a new transaction defaults to the date of the last transaction entered, is a newish feature.. ??)
Well anyway, now that I've enabled tax date, every new transaction is created with a tax date, which defaults to the same date as the default actual date. However that becomes a problem if the last transaction I entered has a different date from the one I want for the one I'm now entering. If I then change the actual date for the new transaction, the tax date stays the same as the date of the previous transaction! So I have to do an extra step of manually changing the tax date to match the revised actual date, so that I don't end up with an unwanted tax date in the register.
(Is this making sense? I think I'm starting to sound like a government bureaucrat... ) My suggestion: Changing the actual date should be automatically mirrored in the tax date field (but not vice-versa!). That way, you'll only end up with a separate tax date saved in the register if you actually want that - but you won't need to manually fix that.
