Further to the excellent advice already offered by Olly and Kruncher ...
It looks like the report has at least some lines in each 'block' of employees data - Payments and deductions.
You can therefore work with bliocks of data fields - maybe all the fields in a single block - just depends how many unique fields you may need to extract and how few lines the smallest length record has available.
So if you can make the data sample fo each append template, say, 20 lines long and you need 20 possible named non-overlapping (in terms of horizontal position on the line) fields from one or both columns of the record, you could do that with oe template. If the shortest number of lines in a record was, say, 10, you would need 2 templates.
The data sample itself is of no importance here (unless you are using a floating trap in which case all bets are off.) The number of lines simply defines the max number of rows you can fit in without overlapping the next record down the page and provides space for painting the fields you nee in their horizontal line position. Any order will do unless there are shared parts of preceding strings in the field name tags - in which case some care may be required.
If you define a field that may fall outside the number of lines in the sanmple, but before the next record starts (or any end template marker you may have set in V10), the field will still be picked up.
Does this information allow you any additional flexibility with the basic guru trap process?
V11.5 (Pro): Windows 7
V9, V10.5 (Pro): Windows 7
V8 Pro: Windows XP SP2
Earlier versions "archived" as machines died ...