Transactions disappearing before match dialog

[Jon Schewe]

However that's exactly what I want. I want the same transaction to be
listed as a possible match for multiple imported transactions because
of the overlap.

My guess is that I got it working by fixing one at a time so that
eventually each transaction was only being listed for a single imported
transaction.
I expect that this is going to be a problem for me going forward as
soon as I have 2 checks waiting to clear.

I expect it would be a problem to automatically selected the same
transaction for 2 different imported transactions. However having the
same transaction listed as a possible, but not the most likely, is a
case that should be allowed.

Perhaps the way to solve this is to instead of removing the potential
conflicting transactions, but rather to lower the score. Say
transaction 1 matches 2 imports. Pick one import to assign it to and
move it down the list for the second import. Although there are lots of
corner cases. What if there is only a single match for 2 imports and
it's the same transaction? In my case I'd like to have the option to
specify which import the transaction is associated with.

Maybe we need to do a check at the end of the match dialog, after the
user has selected transactions for each import and report an error, or
warning, when two different imports are matched against the same
transaction. Does that seem reasonable?

I don't know GTK, so coming up with such a dialog would be pretty
difficult for me.

On Sat, 2026-02-28 at 17:53 -0800, John Ralls wrote:
> I think, based on the
> comment https://github.com/Gnucash/gnucash/blob/1fda575c5b21c10bde538f593b5fb2d64b850e01/gnucash/import-export/import-main-matcher.cpp#L358
>  that it’s supposed to prevent a transaction being presented for more
> than one import. Since you have one of these checks a week I guess
> you’d have 4 in a monthly download. That might be a rare occurrence
> so that function doesn’t get exercised much.
> 
> Regards,
> John Ralls
> 
> > On Feb 28, 2026, at 15:24, Jon Schewe <jpschewe at mtu.net> wrote:
> > 
> > If I ignore the result of get_conflict_list, then I get the matches
> > that I want. That is where the desired transaction is disappearing
> > from
> > the list of possible matches.
> > 
> > Does anyone have any insight on why this function might be
> > excluding
> > transactions?
> > 
> > On Sat, 2026-02-28 at 06:40 -0600, Jon Schewe wrote:
> > > I'm trying to track down an issue where I am not presented with
> > > the
> > > transactions that I expect for some checks matching. I have a
> > > particularly difficult situation for GnuCash to match in that:
> > > 1) the checks are always the same amount
> > > 2) the checks are written a week apart
> > > 3) the checks are cashed up to 2 weeks after written
> > > 4) the back does not include the check number in the OFX file
> > > 
> > > I understand that I can double click on the match dialog and
> > > choose
> > > from all possible matches. However I'm finding that the match
> > > that I
> > > desire isn't showing up in the list.
> > > 
> > > I've added debugging to split_find_match to try and track it
> > > down. At
> > > this point I'm finding the transaction that I desire being added
> > > to
> > > the
> > > list of possible transactions in this method. The method exits
> > > with 3
> > > transactions. However when the dialog is opened I only see 2
> > > transactions. I'm always missing the one that I want.
> > > 
> > > I see the split_find_match is called from perform_matching and
> > > that
> > > it
> > > calls gnc_import_TransInfo_init_matches after all matches are
> > > found.
> > > At this point I have the correct number of transactions in
> > > match_list.
> > > However I don't know the gnucash source or gtk well enough to be
> > > able
> > > to figure out the steps between there and when the dialog that
> > > let's
> > > me
> > > pick transactions is built and displayed.
> > > 
> > > Can someone help point me to the flow of execution between these
> > > 2
> > > points?
> > > 
> > > Thank you,
> > > Jon
> > > 
> > > _______________________________________________
> > > gnucash-devel mailing list
> > > gnucash-devel at gnucash.org
> > > https://lists.gnucash.org/mailman/listinfo/gnucash-devel
> > 
> > _______________________________________________
> > gnucash-devel mailing list
> > gnucash-devel at gnucash.org
> > https://lists.gnucash.org/mailman/listinfo/gnucash-devel
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gnucash.org/pipermail/gnucash-devel/attachments/20260228/980bf829/attachment.htm>