DBA auto signs the next inv#--- right?   WRONG!!!
It skipped number 114384 on April 10, 2003  and I think I know why.
 
In Dec 1997 a customer sent us a payment on ch# 114384.   The check had an overpay.  DBA references the overpay as the check #.  That check# appeared as a credit on the statement (The credit/check# was iin the same column as the unpaid  invoice #s) in Dec 1997.  
So when DBA was automatically assigning inv #s  it skipped 114384.
 
I printed the INV listing by number--no dates--.there was no 114384,
I search all released SO thinking we missed posting one--no 114384.
I looked at unreleased Sos to see if one had 114384 in the top right corner--nope.
 
I searched  MAINTAIN DATABASE and found 114384 ONLY in BKARINVT-B.
It looks something like this:
ACME mfg      114383    4/09/2003
Sam mfg   114384   12/15/1997
BILLS mfg      114383    4/10/2003
 
I can find  114384 in  AR-R as a check # and then as credit # (because it was an overpay)  The dates assoc.w/114384 are all Dec 1997.
 
Am I on the right track?
 
Laura
 
 

Is this a problem with the                           INTERNAL  REVENUE SERVICE?
 
I remember years ago that sequential numbering was important in invoicing and checks.  Of course that was when we used our fingers and an abacus. I know things change....but I don't like having a # unaccounted for.
 
Laura

The IRS does not care if you use your invoice or check numbers sequentially.   They prefer their ducks in a row for audit purposes, but as long as your back up documentation is easy to find they do not care.
 
Jeanette Zimmerman
Lowery & Company Inc.