The Disadvantages of Using Duplicate Document Numbers

The Disadvantages of Re-using Document Numbers

They are numerous reasons for not doing this as follows:

Typically, in most software applications, a document number is considered a Primary Key, so it should be considered “Unique” and would not be duplicated. However, there are some programs where it might be a Secondary key where multiples might be allowed, such as using a sequence Number, such as when using duplicate entries and historical tables such as Check History (e.g. checks, voids for the same checks, or manual payments, EFT transactions, etc.).

Even in situations where the programming might allow for this sort of thing, a duplication might cause other issues with software functionality, As examples.

The worst example of this that I have seen so far, is with one vendor that 21 manual payments on file using an invoice and check number of “SUPPLIES” – In this case, a better example would create the numbers would be something like “SUPMMDDYY” (e.g. SUP031518).

If you have any questions or need assistance with the creating your own document number assignment schema, please contact the CCS Retail Systems Support department.

– John

Exit mobile version