You should get a warning if you edit a reconciled transaction. If you aren't getting that then that probably means you accepted the warning at some point and selected don't tell me again. If you want to re-enable it then select Actions > Reset Warnings.
Colin On Fri, 11 Jan 2019 at 02:15, Matt Hanning <mth44...@gmail.com> wrote: > > Thank you for sharing your thoughts. After reading everything I believe I > have been editing the transactions which makes them show back up > un-reconciled. I will be keeping a closer eye on this and see if this has > been the problem all along. > > Thank you both for all your help and info.Matt > > > On Thu, Jan 10, 2019 at 12:30 AM D via gnucash-user < > gnucash-user@gnucash.org> wrote: > > > David's points here are all well-considered. See notes inline. > > > > On January 10, 2019, at 9:42 AM, David Cousens <davidcous...@bigpond.com> > > wrote: > > > > >Normally the only way a reconciled transaction becomes unreconciled is if > > the > > >split to the account which has been reconciled is editied, either in the > > >register for the reconciled account or in another register conatining the > > >split from the reconciled account to that registers. The splits of a > > >transaction can be edited from any register for any account which contains > > >splits to it from the transaction. In V3.4 editing details (description, > > >memo) other than the amount, date and account does not affect the > > >reconciliation flag status. You will normally get a dialogue indicating > > >that you are editing a reconciled split. > > >I think earlier versions of GnuCash may have also changed the status when > > >other splits and any information in a reconciled transaction were edited > > >were edited but I am unsure of this and when only editing specific fields > > in > > >the reconciled split triggered changing of the status was introduced. > > >The easiest way to fix this is to rerun the reconciliation process for > > >periods covering the earliest unreconciled transaction forward, checking > > >that opening balances, closing balances and transaction amounts agree with > > > > I disagree here. I think the easiest first method is to enter the *last* > > statement balance (ignoring the opening balance altogether), and see > > whether checking those earlier entries results in a zero balance. I often > > find that it does. > > > > I only go to more specificity if this one doesn't work. > > > > >the statements. GnuCash will often start the reconciliation window with > > some > > >transactions marked even if that period has not been previously reconciled > > >as it attempts to identify transactions which lead to a reconciliation. I > > > > For the record, Gnucash pre-checks only those transactions that have a > > reconcile status of "c," which usually occurs with imported transactions. > > Users can also set this status in the register themselves. > > > > >have been caught believing this in the past and I now clear (uncheck) all > > >transactions in the reconciliation window and match them individually by > > >hand. Tedious but it can pick up 2 errors cancelling each other out so > > that > > >the opening and closing balances are OK but the transactions are > > incorrect. > > >Any unreconciled transaction should show up in the reconciliation > > procedure > > >window as unchecked with any already reconciled splits being initially > > > > Again, transactions with a status "c" will be checked; reconciled items by > > definition will be excluded from the window (except insofar as they > > contribute to the opening balance figure). > > > > OP might check to see whether he accidentally re-entered transactions that > > have already been entered and reconciled, as might happen, for example when > > importing transactions from a second account (say a credit card) whose > > transaction details don't fully match the existing entry. > > > > The OP could supply further details (OS, Gnucash version, specific > > circumstances of his problem) to get better answers. Until then, we are > > speculating on a host of possibilities. > > > > David T. > > > > > > >checked which can help identify the unreconciled transactions > > >David Cousens. > > >----- > > >David Cousens > > >-- > > >Sent from: > > http://gnucash.1415818.n4.nabble.com/GnuCash-User-f1415819.html > > >_______________________________________________ > > >gnucash-user mailing list > > >gnucash-user@gnucash.org > > >To update your subscription preferences or to unsubscribe: > > >https://lists.gnucash.org/mailman/listinfo/gnucash-user > > >If you are using Nabble or Gmane, please see > > https://wiki.gnucash.org/wiki/Mailing_Lists for more information. > > >----- > > >Please remember to CC this list on all your replies. > > >You can do this by using Reply-To-List or Reply-All. > > _______________________________________________ > > gnucash-user mailing list > > gnucash-user@gnucash.org > > To update your subscription preferences or to unsubscribe: > > https://lists.gnucash.org/mailman/listinfo/gnucash-user > > If you are using Nabble or Gmane, please see > > https://wiki.gnucash.org/wiki/Mailing_Lists for more information. > > ----- > > Please remember to CC this list on all your replies. > > You can do this by using Reply-To-List or Reply-All. > _______________________________________________ > gnucash-user mailing list > gnucash-user@gnucash.org > To update your subscription preferences or to unsubscribe: > https://lists.gnucash.org/mailman/listinfo/gnucash-user > If you are using Nabble or Gmane, please see > https://wiki.gnucash.org/wiki/Mailing_Lists for more information. > ----- > Please remember to CC this list on all your replies. > You can do this by using Reply-To-List or Reply-All. _______________________________________________ gnucash-user mailing list gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user If you are using Nabble or Gmane, please see https://wiki.gnucash.org/wiki/Mailing_Lists for more information. ----- Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.