Annually, we functionally allocate all expenses through established Allocations. These allocations are refreshed by the Pools which are also updated annually. In Database View, refreshing from the pool in the Allocation and leaving all four boxes checked provided that all added GL Strings and distribution sets are brought into the pool, however the destination GL String is blank, and MUST be rekeyed before saving. Validating the GL String happens when everything is rekeyed and you go to save. If a string is inactive or invalid, it allows the ability to fix before saving and running a pre-allocation report. If you have an Allocation of 887 GL string rows, in Database, you can move through this manual keying pretty quick, as there is no lag between each line validating the legitimacy of the code - it holds until the end; in NXT, it is validating it on each row as you have keyed and you must Select (mouse click) the code, then select to override the distribution and then mouse select to the next row to key. This takes a process from database that could be about an hour (give or take) for one allocation, to 5 times or longer for the same allocation. This is also assuming you don't lose connection or have any other disruption to service leaving your work lost from the inability to save.

If there could be a similar process as Journal Entry Import, where you could import source/destination etc. into an allocation before running the pre-allocation or allocation report, this would significantly increase processing time.

If the above is not pragmatic, removing the validation function by each line and allowing the override distribution and validating at the end of keying in NXT, would match the process from Database and at least not reduce the functionality/time frame system to system.

The best option would be: to refresh from a pool and have the option to choose pre-populate destination from the source account and keep the distribution default. This would prevent any import necessity and manual keying.