First, let's be brutally honest. Your problem is a design flaw. If you accepted data with neither fixed width nor fixed delimiters, you ASKED for trouble - and got it. If there is no way to get the data back in some other format that supports a more orderly programmed approach, I'll be blunt. You are in trouble.
I'm going on a flight of logic here, so if I spin, crash, and burn somewhere, don't say I didn't warn you it could happen.
I assume that you believe this data set would be suitable in a table, which means you have SOME knowledge of the structure, even if not complete knowledge. You must work "backwards" here. Let's look at your data.
52-60-600 -726.00 Apr 28, 2007 GJ008403 BENEFITS PREMIUM ACCRUAL FOR APRIL 2(Rev) GJ00 316113 Y C49226
Those fields look predictable in format except for that mess in the middle. Take what you know about the fields and parse this thing out. For instance, you probably expect one field to be nnn-nn-nnn. Look for that. Next, you expect a number that could be signed. Then a date with a predictable format of MMM dd, yyyy
Next comes the messy one. So work from the OTHER end and scan backwards. Did you expect a field with a letter and several numbers? Pull that out from the rear. What about a single alphabetic character? Pull that out. Maybe now a 6-digit number? (Remember, working backwards.) OK, how about 2 alphas and 2 digits?
Now you have worked backwards from the tail to find the things you expect and forwards from the head of the line for things you can predict in format. Whatever is in between those two known items is your wild field that defies analysis.