matching transactions

[Michael Hirmke]

Hi Thomas,

[...]
>>> So my new understanding is that if this option is checked, and the
>>> import finds the (over)due  scheduled transaction, it will add the
>>> transaction and match it to the amount of the imported transaction.  If
>>> you manually add the scheduled transaction prior to the import, it will
>>> fail to match because the amounts are different.  If that is the case,
>>> then I can certainly improve the description in the handbook.
>>
>> I can certainly verify that (a few transactions are ahead during the
>> beginning of the month.

>Just did that:

>Yes, that's exactly what happens. I have a schedule over 35,59 (even split
>into expense and VAT - 29.90 and 5.69). Now the transaction is downloaded
>from the bank with an actual amount of 35.82. The match happens and the
>splits are adjusted to 30.10 and 5.72 since the auto VAT assignment with 19%
>VAT takes place. I know, 5.69 is not 19% of 29.90 but that does not matter
>here. All automatic and no manual intervention. The amount in the schedule
>is not changed, just the date of the next occurrence.

>Hope that makes sense and is understandable.

yes, it is.

Only one quesion remains: Why the behaviour for manual matching
operations is different? Perhaps through a configuration option one
could tell KMyMoney to perform manual matches even for differing
amounts? That would definitely make things easier.

>--

>Regards

>Thomas Baumgart

Thy and bye.
Michael.
-- 
Michael Hirmke