[moneytalks] Re: void/cancel
- From: dan ceppa <goddanc1redmond@xxxxxxxxx>
- To: moneytalks@xxxxxxxxxxxxx
- Date: Sat, 9 Dec 2006 12:11:44 -0800 (PST)
It should also sort on check number. I haven't tried a reconciliation yet, but
one sorts the checks in numerical order when going through the hard copy.
As to duplicate check numbers, it definitely was not on purpose. I ran into
the problem
after voiding a check. And, the program should not accept duplicate check
numbers in the first place. Worse, it offers check numbers automatically that
create additional duplication.
One situation is if you go shopping and handwrite a couple 3 checks. On
returning how you enter the vchecks. However, you skip one and enter an
earlier check number after you entered the others. After that check is
entered, newer checks added will start with that number+1 rather than the
actual last check+1 that was used.
The check number field needs to be made unique. One problem though would be
in handling online transactions that are debited directly from the checking
account.
The sort date on all registers is the date of the transaction. So if
you move a transaction's date, the associated check number will move up or down
in the list of transactions in your register. For what it's worth, I don't'
have checks in sequencial numeric order and it's not a problem for me.
If you find keeping check numbers in order is useful to you, then just make
sure to date your checks in date order accordingly.
Just curious, why would you want duplicated check numbers in the program when
you wouldn't want to send out two checks with the same number? And if you've
mis printed a given check, wouldn't it be easier to just void it and print out
a new one thus creating a new check?
----- Original Message -----
From: dan ceppa
To: moneytalks@xxxxxxxxxxxxx
Sent: Friday, December 08, 2006 4:43 PM
Subject: [moneytalks] Re: void/cancel
Some of this depends on why a check is bveing voided. If the check is
completely no good, that works. However, there arde the cases where a check
gets mis-printed. In that case, all that should be necessary is to re-print
the check and change the check.
BUT---- That messes up the check numbering system. I've been able to both
input duplicate check numbers as well as get the program itself to generate a
duplicate check number.
When there is a check which I choose to void for whatever reason, I created
a payer name of Void. In the debit field, I made it $0.00. In the item field,
I entered the check number which I voided. I used the category name of Void,
and didn't choose to use a subcategory in this case. In the memo field
sometimes I write where the check was supposed to go to or most usually, I
leave this field blank. But since the memo field is a free-flowing type of
field, one can write whatever they want in their that would be meaningful to
them.
Now whenever I run across an instance where I need to void a check, I just type
in the first few letters of the word void while entering a new transaction. I
then arrow down to have the program locate that payer, and the category field
is automatically filled in as void. I make sure to put the correct check
number in the Item field and save the record.
Of course, if I have already written out the check I make sure to clear that
record too with the delete key while focused on that record.
The memo idea is good, but it is also helpfull to keep most of the info in the
register. A Void Field would be nice to have.
---------------------------------
Cheap Talk? Check out Yahoo! Messenger's low PC-to-Phone call rates.
---------------------------------
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.5.432 / Virus Database: 268.15.15/580 - Release Date: 12/8/2006
12:53 PM
---------------------------------
Access over 1 million songs - Yahoo! Music Unlimited.
Other related posts:
