Bug 424180 - Payment from scheduled transactions incorrectly allocated when using similar accounts
Summary: Payment from scheduled transactions incorrectly allocated when using similar ...
Status: RESOLVED WORKSFORME
Alias: None
Product: kmymoney
Classification: Applications
Component: database (show other bugs)
Version: 5.1.0
Platform: Debian stable Linux
: NOR major
Target Milestone: ---
Assignee: KMyMoney Devel Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-07-14 07:56 UTC by Shane
Modified: 2021-01-04 04:33 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Shane 2020-07-14 07:56:35 UTC
SUMMARY
Payments allocated against wrong accounts when using scheduled transactions (with splits) from two similar accounts on different dates.


STEPS TO REPRODUCE
1. Enter scheduled transaction from account 1 (50 High Street) on any date (usually first of month)
2. Enter scheduled transaction from account 2 (52 High Street) on subsequent date (usually one day later)
3. Save and exit

OBSERVED RESULT
Payments from 50 High Street are allocated against 52 High Street. Splits are also incorrectly recorded so that it appears that two payments have been received from account 2 (52 High Street) each month, and nothing received from account 1 (50 High Street).


EXPECTED RESULT
Payments and splits from account 1 (50 High Street) should be allocated correctly instead of being allocated against account 2 (52 High Street).



SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Comment 1 Thomas Baumgart 2020-12-05 09:29:51 UTC
I don't fully understand this problem, mainly because some (maybe important) details are unclear to me. What I understand is:

- you have to (very similar) schedules
- you have two payments

My questions:

- is "5x High Street" the payee or a category?
- account1 and account2 are two asset (e.g. checking) accounts?
- How do the splits look like of those two schedules?
- Which options are activated for the specific schedules?
- Which global schedule options are active?
- When do the schedules get entered? Do you do this manually or do you have the KMyMoney automatic entry turned on?
- Do you use any form of transaction import (either online or via file)?

It would be super cool, if you can provide a small sample file that shows the problem, attach it to the problem report and describe the steps you take to reproduce the problem with this file here.
Comment 2 Shane 2020-12-05 09:54:29 UTC
Thanks for your reply.

I will try and replicate the error in a sample file and send it separately.

Meanwhile to answer your queries:
Account1 (labelled 50 High St) and Account2 (labelled 52 High St) are payees 

Both accounts have identical splits where the income from each account is directed into a Landlord account (95%) and an Agency fees account (5%)

Both transactions are scheduled for the first of each month, but only entered manually as they are received.

There is no other transaction importing used.
Comment 3 Bug Janitor Service 2020-12-20 04:34:29 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Bug Janitor Service 2021-01-04 04:33:59 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!