What are common examples of Warning messages?

What are common examples of Warning messages?

Warning messages flag potential issues that aren't currently blocking enrollment but may require attention to prevent future problems. These discrepancies should be addressed, though they don't require the same urgency as Failure messages.

Gender Mismatch
One of the most common Warning messages involves gender discrepancies between BerniePortal and carrier records.
  1. Example: BerniePortal shows an employee as female, but the carrier has them listed as male in their system.
  2. Resolution: You indicate which system has the correct information. If BerniePortal is correct, the carrier is notified to update their records. If the carrier is correct, you update the employee's profile in BerniePortal.

Name Spelling Differences
Carriers may flag discrepancies in how employee or dependent names are spelled between systems. These might include:
  1. Different spellings (e.g., "Jon" vs. "John")
  2. Middle name variations
  3. Hyphenated name differences
  4. Nickname vs. legal name issues

Dependent Relationship Discrepancies
The carrier may report that dependent relationships don't match between BerniePortal and their records. For example:
  1. A dependent listed as "spouse" in one system but "domestic partner" in another
  2. Child relationship classifications that differ

Why Warnings Still Matter
While Warning messages don't immediately block enrollment, they should still be resolved promptly because:
  1. They may indicate data quality issues that could cause problems later
  2. They could escalate to Failure messages if not addressed
  3. Accurate records prevent confusion for employees, carriers, and HR administrators
  4. Resolving them maintains clean, synchronized data across systems

Resolution Approach
  1. Most Warning messages are straightforward to resolve—you simply need to identify which system has the correct information and update accordingly.
  2. Instructions are provided in the message modal when additional steps are needed.

For information about more critical message types, see "What are common examples of Failure messages?" For general resolution guidance, see "How do I resolve carrier messages?"

    • Related Articles

    • What are common examples of Failure messages?

      Failure messages are critical issues that block a member's enrollment with the carrier and require immediate action. These represent problems serious enough that the carrier cannot process or maintain coverage until they're resolved. Date of Birth ...

    • What are the two types of carrier messages?

      Carriers send two severity types of messages through the Carrier Exchange: Failure messages and Warning messages. Understanding the difference between these message types helps you prioritize which issues need immediate attention. Failure Messages ...

    • What information do I need to configure a carrier integration?

      Configuring a carrier integration requires minimal information, but having accurate data prepared in advance will ensure a smooth activation process. Required Information Group Number: The only piece of information required to configure a carrier ...

    • Can employers resolve messages themselves?

      Yes, employers can resolve carrier messages that appear for their organization. When you activate a carrier integration for an employer, that employer automatically gains access to a Manage tab in their Benefits section. What Employers Can See ...

    • Which carriers are available through the Carrier Exchange?

      The Carrier Exchange supports a wide range of medical and non-medical carriers, powered by Ideon's network of insurance company integrations. Medical Carriers The following medical carriers are available through the Carrier Exchange: Aetna Angle ...