Reconciling questions

[Derek Atkins]

Hi,

It's POSSIBLE that there's a fencepost error; that the 3/17/08
reconcile date didn't think that the 3/17/08 transaction was in the
current period.

Did the same thing happen later?  That the transaction date of the
cleared-but-not-reconciled transaction and the reconcile date were
the same?

If so...  Reconcile 1 day later (but use the same ending balance).
Does that get the transaction to convert from 'c' to 'y'?

-derek

Quoting Tim Zakharov <tzakharov at charter.net>:

> Okay, I was going by memory on my last post.  Now I'm in front of my
> computer and see that this was actually a March statement, not April.
>
> So, the posted date was 3/17/08 and the date I entered in Gnucash was
> also 3/17/08.  Incidentally, I split this transaction into three
> categories (groceries, clothing, holiday) as we purchased a variety of
> items from a single store.  Perhaps I did something during the split
> that caused this?
>
> Currently, this transaction is reconciled, as I described in my last
> post.  It was reconciled as part of the May statement.  That means I
> hadn't resolved this as I was reconciling April, so it rolled over as
> the first unreconciled transaction as I was reconciling the May
> statement.
>
> I am using version 2.2.4.  This is the version in the Ubuntu Hardy
> repositories.  I installed from Synaptic; I did not compile myself.
>
> As I look at my checking account in Gnucash, I see that 5/16/08 deposit
> that did not reconcile (shows the "c" instead of "y") even though I saw
> it in the reconcile window and ticked the checkbox next to it.  How do I
> reconcile a single transaction...is it possible?
>
> I have a feeling this is not a bug, but somehow related to a mistake I
> made while splitting that original 3/17 transaction.  How I think this
> happened, I can't say.  I just would like that 5/16 transaction to have
> a "y" next to it.
>
> Any more ideas?
>
> Thanks for your time.
>
> On Fri, 2008-05-23 at 15:56 -0400, Derek Atkins wrote:
>> Hi,
>>
>> What was the posted date of the $91.14 transaction?
>> What was the date you entered for the April reconciliation?
>> What version of GnuCash are you using?
>>
>> I've never seen this behavior myself.   There is absolutely no
>> requirements that you pre-clear a transaction prior to reconciliation,
>> and indeed I rarely do that myself.  Generally I click on the transactions
>> in the reconcile window, and I've never seen this behavior.
>>
>> -derek
>>
>> Quoting tzakharov at charter.net:
>>
>> > I'm sorry, I don't think I made myself clear.  I never tried to
>> > reconcile a future transaction.  What led you to believe I meant that?
>> >
>> > Let me provide a little more detail.  First, I input all my
>> > transactions from Jan to present prior to doing any reconciling (this
>> > is why I'm reconciling older transactions right now). In my April
>> > statement was a transaction for $91.14.  Somehow, during the
>> > reconciliation process, this single transaction did not get marked as
>> > reconciled, even though I manually ticked the check box next to the
>> > transaction while reconciling, and even though the balances zeroed
>> > out while reconciling.  Perhaps this is because I manually ticked the
>> > box?  I'm not sure why (maybe I forgot to clear it before
>> > reconciling), but this was the ONLY transaction that did not
>> > automatically have a tick in the check box.  Anyhow, after I finished
>> > reconciling that month, I noticed the $91.14 transaction still had a
>> > "c" instead of a "y" like all the other transactions in that
>> > statement period.
>> >
>> > In May's statement (it ended May 21, maybe this is where you got
>> > confused?), when I started to reconcile, the $91.14 transaction
>> > showed up on the first line.  After going through the May statement,
>> > again I got the balances to zero out with the correct ending balance
>> > (the starting balance was $91.14 more than my May statement because
>> > of that one transaction).  But when I finished reconciling the May
>> > statement, there was once again one transaction that was not
>> > reconciled even though it was part of the May statement and I ticked
>> > the checkbox while reconciling.  This time it was a deposit for my
>> > salary, and it happened to be the last transaction on my May
>> > statement.  Could the fact that I had the $91.14 transaction tacked
>> > on to the front of the May statement have pushed the last transaction
>> > off?
>> >
>> > I hope this makes more sense.
>> >
>> > Thanks.
>> > ---- Derek Atkins <warlord at MIT.EDU> wrote:
>> >> Hi,
>> >>
>> >> Quoting timzak <tzakharov at charter.net>:
>> >>
>> >> >
>> >> > Thanks for the reply.  I decided to go ahead and reconcile 
>> against my bank
>> >> > statements.  All went well until March or April's statement (can't
>> >> remember
>> >> > which as the date of the transaction in question is right on 
>> the border).
>> >> > Basically, there was a single transaction that didn't get automatically
>> >> > selected during the reconcile process, I think because it was a split
>> >> > transaction and I forgot to set it as cleared.  So in the 
>> Reconcile menu,
>> >> > this transaction was unchecked.  I checked it, and the reconcile
>> >> process got
>> >> > balanced to zero (as it should).  However, when I finished
>> >> reconciling, that
>> >> > transaction only showed a "c", not a "y" like it should if it had been
>> >> > reconciled.  I wasn't sure what happened, and could not figure out
>> >> how to go
>> >> > back and reconcile just the one transaction, so I moved on to the next
>> >> > month's statement and saw that the transaction in question showed
>> >> up in the
>> >> > next statement's reconciliation window.  Again, I went through each
>> >> > transaction, noting that they all had checks next to them.  
>> When I got to
>> >> > the end, I noticed one deposit of salary that was not checked, and the
>> >> > balance was off by that same amount.  So I put a check next to
>> >> that deposit
>> >> > (it was the last transaction on that month's statement), and saw the
>> >> > balances get to zero (balanced the month).  Everything looked 
>> great, so I
>> >> > applied the reconciliation.  This time I noticed that the original
>> >> > transaction that didn't get reconciled, was now reconciled.  Yay!
>> >> However,
>> >> > now this last deposit that I had to manually check in the 
>> reconcile window
>> >> > does not show as reconciled!  It has a "c" instead of a "y" 
>> just like the
>> >> > original one I mentioned.  It appears now that I have to wait til next
>> >> > month's statement and tack this one onto next months to reconcile it,
>> >> > leaving me to wonder if there will be another transaction that
>> >> this happens
>> >> > with, leaving me in some weird endless loop.  Does this sound
>> >> familiar?  Do
>> >> > you have any way to help me?  Am I making any sense?
>> >> > javascript:Nabble.smiley('anim_confused.gif',':confused:')
>> >> >
>> >> > Thanks.
>> >>
>> >> I'm afraid it does not sound familiar, but it also doesn't sound all
>> >> that surprising..   How can a transaction that happened in the future
>> >> get reconciled?  E.g., if you took money out of an ATM on May 23rd,
>> >> how could it show up on a statement dated May 22nd?
>> >>
>> >> To me it sounds like you're entering in the incorrect statement
>> >> date, or your marking your transaction dates incorrectly.
>> >>
>> >> > Please remember to CC this list on all your replies.
>> >> > You can do this by using Reply-To-List or Reply-All.
>> >>
>> >> -derek
>> >> --
>> >>        Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
>> >>        Member, MIT Student Information Processing Board  (SIPB)
>> >>        URL: http://web.mit.edu/warlord/    PP-ASEL-IA     N1NWH
>> >>        warlord at MIT.EDU                        PGP key available
>> >>
>> >
>> >
>>
>>
>>
>
>



-- 
       Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
       Member, MIT Student Information Processing Board  (SIPB)
       URL: http://web.mit.edu/warlord/    PP-ASEL-IA     N1NWH
       warlord at MIT.EDU                        PGP key available