Employer Registration Reporting

The following may assist people to avoid "unwanted data" when reporting from Employers to their linked (via Employer Identifier/EDRS) Registrations ...

There is a reporting category within TERMS – Employer Registrations – that will extract Employers and their corresponding Registrations. This can be via a designed report or an export.

The link between the Employer and the “Employee Registrations” is made using the Employer Identifier code (was EDRS, which is still the internal name within TERMS). As the majority of Registrations probably do not have an Employer Identifier (i.e. non-Employment based provision) then if you have an Employer with a missing Employer Identifier then your SQL server will probably hook onto all the Registrations without an Employer Identifier.

In English this means that you will get out all of your Employer Registrations, but you may well get all other Registrations if one or more Employer is missing an Employer Identifier. Each and every Employer without an Employer Identified (EDRS) will pick up every Registration without an Employer Identifier – this can obviously cause problems.

To give you an example.

You have 5 Employers

• Emp 1, EDRS 11111111
• Emp 2, EDRS 22222222
• Emp 3, EDRS 33333333
• Emp 4, no EDRS – i.e. “blank”
• Emp 5, no EDRS – i.e. “blank”

You have 2000 Registrations

• 5 are marked as EDRS 11111111
• 10 are marked as EDRS 22222222
• 15 are marked as EDRS 333333333
• 1970 do not have an EDRS (they are non-employer Registrations)

Running a report/export will result in the following

• 5 lines for Emp 1 with each of the Registrations marked as EDRS 11111111
• 10 lines for Emp2 with each of the Registrations marked as EDRS 22222222
• 15 lines for Emp3 with each of the Registrations marked as EDRS 33333333
• 1970 lines for Emp4 with each of the Registrations marked as a blank EDRS
• 1970 lines for Emp5 with each of the Registrations marked as a blank EDRS

Total of 3970 lines as Emp4 and Emp5 have both latched onto the same Registrations.

There are two ways around this when reporting or exporting

1. Ensure that all your Employers have an Employer Identifier/EDRS – so that they cannot link onto the “blank” registrations
2. Filter out any Employers with a missing Employer Identifier/EDRS when running the report or export

The supplied sample report has a built in filter vREM:EDRSID<>'' which means that this problem doesn’t occur. If exporting then ensure the same is used along with your other filters (it is called “Employer Registration Service ID” on screen) to ensure that you have “does not equal” in Type of Filter and ‘’ in the Value to Filter.


Add Feedback