Not automatically, no.  The way it works is there is a “last account number used” field in the master corporate record (table is GLTRLR) that is incremented by 1 every time the system needs an account number to store data, whether an actual member, or a possible member account where the application is still in process.  This is done to prevent the same account number from being assigned to more than one record. 

As an example, the process used for creating new memberships (Tool #3) gets the last account base used from GLTRLR then increments it by 1, or by whatever the CU has configured for the increment. Then it runs these verifications:
  • Account base cannot be 0.
  • Account base cannot be between 999999000 and 999999999
  • Unless the allow number over 6 digits flag is set to Yes, account base cannot be over 999999
  • Account number can’t start with the Corp ID if multi corp processing is on (Note: multi-corp processing is no longer supported for member accounts.)
  • Account base cannot be in MASTER or MEMBER1
  • If account base is in MSHIST a warning is given to the user about reusing an account number
If any of those checks fail, the account base is incremented again and the program runs the same checks. That process is repeated until a valid account number is found. The last account # used can be changed if needed (via the corporate ID record, Tool #1784), to force the system to start over again at a lower number. 

A different, slightly less complex program (CRUD00020M) is used for any online process (such as MOP/MAP). It gets the last account base used from GLTRLR then increments it by 1, or by whatever the CU has configured for the increment, then runs these verifications:
  • If account base is > 999999999 then it loops and starts over at 1
  • Account base cannot be in MASTER, if it is program increments the account base and checks again
  • Account base cannot be in MSHIST, if it is program increments the account base and checks again