It is quite likely I don’t understand the interface/system Lupos is anticipating. My concern was requests have been made for sequence numbers for many things such as:
Receipt, payments, purchase invoice sequence number, payslips, bank transaction, general ledger transaction.
Different users have expressed different requirements. Some want a global reference number. Others want different sequence numbers for different functions. Others prefer user entered data.
I had assumed each user would want their system to consistently implement their chosen behaviour. To achieve consistent behaviour it need to be a set up parameter (as well as administrator setting) not data entry setting. As it is being retrofitted to existing user databases, some consideration should be given to management of the transition (default to old behaviour for existing databases, when activated define if retroactively generate numbers or just new numbers or user selectable). How flexible the sequencing system is, is a program design decision and well beyond me, however thinking about the likely range of requirement early on is likely to result in more efficient use programmer time.