[Kmymoney-devel] Consistency Check for opening dates

[aga]

On 22/10/15 19:47, Jack wrote:
> On 2015.10.22 05:28, Thomas Baumgart wrote:
>> On Wednesday 21 October 2015 21:08:36 Christian Dávid wrote:
>> >
>> > for a while now I receive such consistency check errors:
>> >
>> >   * Transaction 'T000000000000000112' has a post date '⟨date⟩'
>> before one of
>> > the referenced account's opening date.
>> >     Referenced accounts: ⟨account name⟩
>> >     The post date was not updated to '⟨date from above +3 days⟩'.
>> > […]
>> > Finished: 0 problems corrected. 2 problems still present.
>> >
>>> I think this error is not useful for the user. Mainly because the
>>> long id is shown – to normal users this is the only place to meet
>>> this id, so it is absolutely useless. We should change that (I can do
>>> that).
>>
>> Not really, because in case you copy that long id to the search bar
>> above the ledger in the said account KMyMoney selects exactly that
>> transaction. I am not sure if we have another means to identify a
>> transaction within a ledger other than showing all details which would
>> swamp the report and confuse the user even more.
>>
>>> However, I wanted to ask if we should stick to this message? KMyMoney
>>> can handle this situation very well, so why should we care?
>>
>> We left this situation as one that needs to be handled by the user
>> manually. All the ones that can be handled automatically are handled
>> by KMyMoney already.
>>
>>> Is there a way to show this message only if you start the check
>>> manually (Tool -> Consistency Check)?
>>
>> Simple answer: no.
>> The solution: fix the problem in the data
>>
>> It would be extremely useful to know how you ended up there, as this
>> scenario should not happen in the first place. I think that all the
>> manual entry methods do not allow to enter transactions before the
>> opening date of an account, so I expect the source to be one of the
>> import handlers.
>>
> I just discovered how this might happen, and as Thomas suspects, it's
> from an import.  I just did an OFX import, which included a dividend
> transaction from 08 Oct.  KMM apparently set the opening date of the
> account to today instead of the date of the transaction.  On doing a
> save, the consistency checker corrected the opening date by setting it
> to the transaction date.  Since it was a dividend transaction, there was
> no price to be imorted.  (I have no idea how I got a dividend on a stock
> I don't seem to own, but that's another story.)

It is possible to get a dividend on a stock which you've disposed of 
fairly recently, depending on the sell date wrt. the dividend 
declaration date.
>
> As additional information, however, I just cleaned up a bunch of such
> errors, and for many of them, it WAS a buy transaction, so I don't know
> why a price wasn't entered in those cases.  I have created an anonymous
> file that still shows some of those errors, but I'm not sure it will be
> useful to find out why a price didn't get set from the transaction,
> since they are all from somewhat older imports.
>

How old are the transactions?  Originally, I found that prices for 
manually entered buy/sell transactions were not recorded/retained.  I 
fixed that (or rather I thought I had, but I can't trace the fix.  It 
may have been in KMM2.)  Anyway, it certainly is working now.

Allan