Generating a unique transaction number

[foxylady337]

On Mon, 2011-05-09 at 02:01 -0700, Maf. King [via GnuCash] wrote:
> On Monday 09 May 2011 08:37:02 foxylady337 wrote: 
> > Good to know I'm not unique! 
> > 
> > Seriously, though, if there's no intrinsic support for a transaction
> number 
> > within GNUCash, how do other users manage to organise and file all
> the 
> > unnumbered vouchers that comprise the vast bulk of day-to-day
> activity in 
> > my domestic accounts? 
> > 
> 
> Hi, 
> 
> I file the accomanying paperwork for credit card transactions etc,
> firstly by 
> account and then by date, and then group to match statements when they
> arrive. 
> 
> At the end of a financial year, I'll have upto 12 bundles of reciepts
> etc. 
> (paperclipped together) for each card I've used during the year, and
> each 
> bundle will be in the same order that items appear on the statement,
> which 
> corresponds roughly to the date order in GC. 
> 
> Don't really see how having an extra "system number" to identify a
> reciept 
> really adds useful info over date/retailer/total.  I would say that it
> would 
> be highly unlikely for me that 2 txns would duplicate those 3 pieces
> of info 
> exactly, but YMMV of course (and whatever the Tax authorities
> stipulate, but 
> you did say domestic!) 
> 
> HTH, 
> Maf.   
> 
> _______________________________________________ 
> gnucash-user mailing list 
> [hidden email] 
> https://lists.gnucash.org/mailman/listinfo/gnucash-user
> ----- 
> Please remember to CC this list on all your replies. 
> You can do this by using Reply-To-List or Reply-All. 
> 
> 
> 
> ______________________________________________________________________
> If you reply to this email, your message will be added to the
> discussion below:
> http://gnucash.1415818.n4.nabble.com/Generating-a-unique-transaction-number-tp3478309p3508733.html 
> To unsubscribe from Generating a unique transaction number, click
> here. 


OK, but your method seems to involve a lot of extra paper handling.

I know my age makes me resistant to change - I've been using the method
I described for > 15 years, and the method I adopted was prompted by the
book-keeping program I was using - but...

Vouchers for shop purchases, returned items, on-line purchases etc come
in a variety of shapes and sizes, don't reach me in date order and are
paid for using several different credit and debit cards.

When I come to enter a batch of vouchers, I simply take the one from the
top of the pile first, and work my way to the bottom, numbering them
sequentially. I then clip them into manageable bundles with a stapler
and file them away. Unless I need to send something back, or deal with
an error, I don't need to touch these vouchers again. If I need to
recover one, I can search for the relevant transaction using GNUCash,
and get straight to the voucher using the unique transaction number.

There's no need to get the vouchers out again for reconciliation with
the bank or credit card statement, as the transactions have all been
recorded through GNUCash already - unless an error is picked up, of
course.




--
View this message in context: http://gnucash.1415818.n4.nabble.com/Generating-a-unique-transaction-number-tp3478309p3509073.html
Sent from the GnuCash - User mailing list archive at Nabble.com.