The response from all three of the Support Forum team members is basically saying "We don't fix it as of now". And the Paycom integration in question is with The Standard which is on the Support forum Team so we should be fine moving forward.
------------------------------
Michael J Grudgings
Business Architect, Data Standards | LL Global, Inc.
300 Day Hill Road, Windsor, CT, 06095
t: (860) 298-3850 |
mgrudgings@limra.com------------------------------
Original Message:
Sent: 11-06-2023 15:58
From: Jacquelynn Payne
Subject: Ampersand values on LDExBEM 1.3
We have a project right now that is requesting an ampersand in the Group Name, ie 'M&M Mouse Ventures'. This, of course, prints on the file as 'M&M Mouse Ventures'. The ampersand issue has previously been addressed in regards to 'AD&D' and is accepted in that context. However, my team would like to confirm that when an ampersand is requested in any other fields including in the <GroupName>, that it's acceptable that it is sent with the error printing, instead of requiring us to push back for updated coding supplements from the carrier partner.
#LDEx-BEM
------------------------------
Jacquelynn Payne | HCM Carrier Liaison | She/Her
Paycom
7501 W. Memorial Road | Oklahoma City, OK 73142
800.580.4505 ext. 13836
Jacquelynn.payne@paycomonline.com
------------------------------