Question About Limited Account Code Ranges for Clients/Suppliers?

[perfectpitchconcepts]

Howdy,

First off, thanks for such a great package! I've been playing around with it for a week or so and really like what I'm seeing on many levels :)

As for my question, I'm running into an issue trying to migrate some records from an existing company into a fresh install. The company has data going back 10+ years, and there are a LOT of small transactions with various clients and suppliers. In other systems I've seen, the clients and suppliers were sort of broken out into their own tables (or they seemed to be based on the UI of those systems at least), but I understand that in this package the idea is that each of these should have a unique "account" object (based on the example accounts in the documentation, that is):

• Clients = Account::RECEIVABLE
• Suppliers = Account::PAYABLE

The issue I'm running into has to do with the limited ranges of the account code system where Account::RECEIVABLE types have a limited range of 500 - 1999 and Account::PAYABLE types have a limited range of 2400 - 2999. The package seems to just do a quick count of existing accounts in each type and +1 when adding a new account into the system.

But what happens in situations where a business may have thousands of clients/suppliers from over a decade of operations? It seems like at some point the system will start creating new clients that spill into the 2000 - 2099 Account::NON_CURRENT_LIABILITY range, and new suppliers that spill into the 3000 - 3999 Account::EQUITY range, right? This would obviously happen sooner than later when dealing with large imports, but seems like it would be a potential issue for any business.

Of course, I realize that I may be approaching this incorrectly... because it definitely feels like I'm missing something obvious here? Apologies if so! Perhaps the idea isn't actually that each customer/client/supplier should have their own account after all? Or is it a matter of adjusting the ranges of the account codes? Any guidance or advice would be much appreciated here!

Thanks again for building and—maybe even more importantly—continuing to maintain such a fantastic package!