Why Is My Allowance Showing an Incorrect Value (e.g., $1 or $0) and How Can I Resolve It?
Allowance discrepancies, such as seeing $1 or $0 instead of the expected amount, can occur for several reasons. Below, we explain why these discrepancies happen and how to address them.
Possible Reasons for an Incorrect Allowance Display
Coverage tier issues: The allowance amount displayed may vary depending on the coverage tier assigned to the employee. For instance, employees in the single coverage tier may see a lower allowance (e.g., $300/month), while those in the couple or family tier may see the full $500/month allowance.
1. $1 Allowance Due to Class Assignment
One common reason for an employee seeing a $1 allowance is an issue with their class assignment. Employees must be assigned to the appropriate class that reflects their actual allowance. Incorrect or default class assignments often result in the $1 value showing erroneously.
During enrollment, employees may see a placeholder amount (e.g., $1) on their notice. This placeholder is temporary and will update automatically after the employee uploads their proof of coverage (POC) to the Take Command platform. Once the POC is approved, the placeholder will be replaced with the actual allowance amount tied to the employee’s health plan.
How to Resolve: If you believe this is the issue, contact your employer or the admin responsible for class assignments. Admins can update the class assignments by: - Navigating to the Employee Roster in the Admin Portal. - Finding the relevant employee. - Clicking the three dots next to their name and selecting "Edit." - Updating the employee’s classification to the correct one for the intended benefits.
Verify your coverage tier with your employer to ensure it aligns with the correct allowance amount. Adjustments to your tier must be made by your employer to reflect the accurate allowance.
2. $1 Allowance Due to Temporary Display Issues
In some cases, a $1 allowance may display temporarily due to platform shopping restrictions. For example, when shopping must be conducted through a state Marketplace instead of directly via the portal, this placeholder value might show until enrollment is complete.
Additionally, the allowance will update automatically after the employee submits and receives approval for their proof of coverage (POC). This ensures that the displayed amount reflects the correct allowance tied to the employee’s health plan.
How to Resolve: After completing the proper enrollment path (e.g., submitting your plan details), the portal will update to reflect the correct allowance based on your class and plan year.
Notices will also update to reflect the correct allowance amount after the POC submission and approval process is completed.
3. $0 Allowance During Checkout
If you see $0 for your allowance, it may be because HRA funds are not applied directly at the time of checkout. Instead, you must first pay the premium out of pocket. Once your plan is approved, your allowance amount is reported to your employer, enabling reimbursement as per HRA rules.
How to Resolve: Submit your premium payment as required and ensure plan approval to unlock reimbursement. Contact your employer or review your reimbursement guidelines for additional details.
If your allowance amount does not match the expected value (e.g., $500/month), confirm your coverage tier with your employer. Coverage tiers directly impact the allowance amount, and adjustments must be made by the employer.
Understanding Your Allowance on the Dashboard
On your Take Command dashboard, you will find two key terms:
Monthly Allowance: This is the fixed reimbursement amount allocated to you each month for eligible expenses.
Current Year Allowance: This represents the accumulated unclaimed allowance for the year to date. It is calculated by subtracting your total claims from the unlocked year-to-date allowance, reflecting how much you can still claim.
Summary and Additional Notes
When your allowance does not display as expected, it is often tied to class assignment issues, temporary platform constraints, or timing related to initial payment and reimbursement. Admins play a critical role in resolving most class-related issues, while users should ensure they follow the correct enrollment and payment steps. For further assistance, contact your employer or refer to the Take Command support team for clarification.
Additionally, coverage tier verification is crucial as it directly impacts the allowance amount. Employees should confirm their tier with their employer to ensure the displayed allowance is accurate. Unused ICHRA allowances are not payable to employees. Instead, they remain with the employer. Unclaimed amounts can roll over month-to-month within the plan year, allowing employees to submit eligible expenses later. At the end of the plan year, the employer may choose to carry over remaining balances to the next year or reset them to zero, depending on the plan design.
Accessing and Using ICHRA-Related Documents
Locating the ICHRA Employee Notice
Employees can download their ICHRA Employee Notice from the Take Command portal under the Documents tab. Look for the item labeled “Employee Personal Notice.” If the notice was sent by email but the attachment is not visible, check the employee’s portal for their personal employment/eligibility notice. In some email clients, the attachment may appear as a link beneath the sender’s signature.
Using the ICHRA Employee Notice for Enrollment
The ICHRA Employee Notice is not sent to insurance carriers (e.g., BCBS) with your application. Instead, it is a separate document for employees to use when applying for coverage. If the carrier requests proof of a qualifying life event, download the notice from the portal and provide it to them.
Addressing Discrepancies in Dates or Amounts
The start date listed on the ICHRA Employee Notice often reflects the employer’s plan year start date (e.g., January 1), which aligns with compliance requirements. This date does not necessarily indicate the employee’s personal eligibility or the date they were informed of the benefit.