While my esteemed colleague Kevin is correct, note that you can import a list of customers to be deleted into the utility.  Export the customer list to Excel, find the ones to be deleted and delete the rest and then import the resulting file into the Delete/Change Utility. Update.

While my esteemed colleague Kevin is correct, note that you can import a list of customers to be deleted into the utility.  Export the customer list to Excel, find the ones to be deleted and delete the rest and then import the resulting file into the Delete/Change Utility. Update.

Yes, of course BigLouie is correct.  Importing a list is what I always do, but forgot to mention that. 

There are a lot of applicable fields in the table AR_DeleteChangeCustomers, so enter one row manually, then query the table to capture the hard-coded values you want to set within the VI job.  To avoid ranges, I import with the VI job set to the same csv columns for start / end customer and division.

Backups are 100% recommended.

Is this import done through Delete/Change Utility? Maybe I am just missing it but I don't see any options to import.

While looking at this further in a backup company I was wondering if this approach would work...I run a VI Job to set the status all of these bogus customer accounts to Temporary and remove using the Remove Temporary Customers Utility. Since they haven't been used and have zero balances that should work right? We do not currently use the temp customer status for any customer accounts, just the active/inactive.

Use VI to import into the table, then run the utility.

Imported the records into the AR_DeleteChangeCustomers through VI. All looks good to me. Currently running the utlility.

It was around 2500 records imported into the utility. Been running for about an hour now. Seems like a long time to me. Does that sound "normal" or no?

I usually run smaller batches.  Try 50-100 at most.