GnuCash
Contact   Instructions
Bug 797636 - Incorrect Online account matches cannot be deleted
Summary: Incorrect Online account matches cannot be deleted
Status: RESOLVED FIXED
Alias: None
Product: GnuCash
Classification: Unclassified
Component: Import - AqBanking (show other bugs)
Version: git-maint
Hardware: PC Linux
: Normal minor
Target Milestone: ---
Assignee: import
QA Contact: import
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-03-02 10:09 EST by Peter Zimmerer
Modified: 2020-05-31 06:46 EDT (History)
4 users (show)

See Also:


Attachments

Description Peter Zimmerer 2020-03-02 10:09:45 EST
Within the Online Banking Setup tool AqBanking accounts can be matched with GnuCash accounts. If a GnuCash account has been matched with the wrong AqBanking account this match cannot be removed (easily) again.

Desired solution:

In order to allow the deletion of wrong matches it should be possible to select one or multiple matches on the "Match Online accounts with GnuCash accounts" page.
There should be a push button "Delete selected matches" on this page which removes the GnuCash account from the selected account matches.

Workaround:

There is a workaround to achieve the deletion of unwanted matches. You need a GnuCash version including PR https://github.com/Gnucash/gnucash/pull/649 as a prerequisite.

If you have a GnuCash account g1 which is erroneously matched with an AqBanking account a2 you have to decide between one of the following two cases:
1. If g1 shall be matched with a different AqBanking acccount a1 instead, you could double click on a1 and match it with g1. As a result of this action the previous match of g1 with a2 is removed.
2. If g1 shall be matched with no AqBanking account anymore you need to create a dummy GnuCash account gd, match gd with a2, and finally delete gd again.
Comment 1 Peter Zimmerer 2020-03-02 11:20:26 EST
See PR https://github.com/Gnucash/gnucash/pull/659 for an implementation of the suggested solution.
Comment 2 Bob 2020-05-31 06:46:44 EDT
Your fix PR #659 was added to maint and was in version 3.9

Note You need to log in before you can comment on or make changes to this bug.