Skip to main content

HRA Admin Portal: Why an employee on my roster is not showing a reimbursement amount

This article is for employers and administrators using Take Command who are reviewing employee reimbursement amounts in the HRA Admin Portal or reimbursement reports.

Written by Support

An employee may show $0 or no reimbursement amount on your roster when they have not yet submitted eligible claims, have not completed onboarding (including proof of coverage review), are in a non-participating status, or have already been included in a prior reimbursement statement for the selected time period.

Why is an employee showing no reimbursement amount?

An employee will show $0 or no reimbursement amount when there is nothing currently owed to them for the selected reporting period.

This typically happens for one of the following reasons:

1. The employee has not completed onboarding

If onboarding is not complete, reimbursements cannot be processed.

This includes situations where:

  • The employee has not logged in

  • Proof of Coverage has not been submitted

  • Submitted documentation is still under review

In these cases, the employee’s HRA status may show as:

  • No Proof of Coverage

  • Reviewing Coverage

Until onboarding is complete, no reimbursement amount will appear.

2. The employee has not submitted any eligible claims

Employees must submit reimbursement requests—coverage alone does not trigger payment.

An employee may show $0 if:

  • They have submitted proof of coverage but no reimbursement claims

  • They have not entered any premium or medical expense claims

  • Their recurring premium claim has not been created or activated

Claims must exist before reimbursement amounts appear in reports.

3. The reimbursement was already included in a prior statement

Reimbursement statements are time-bound and only reflect activity for a specific period.

An employee may show $0 if:

  • Their reimbursement was already paid in a previous statement

  • Their recurring premium was processed earlier in the month

  • The selected report range does not include their activity

Each statement is a snapshot, not a full year-to-date summary.

4. The employee is not currently participating

Employees who are not actively enrolled in the HRA will not show reimbursement amounts.

This includes:

  • Employees who waived coverage

  • Employees marked as not participating

  • Employees who are not eligible for the selected benefit period

Non-participating employees will show $0 by design.

5. The employee is ineligible or not active in the HRA

In some cases, the employee may be excluded from reimbursement due to eligibility status.

Examples include:

  • Ineligible owner classification

  • Terminated employees

  • Employees not assigned to an active benefit class

  • Employees outside the current plan year

These employees will not generate reimbursement amounts.

How can I verify what is happening for an employee?

To troubleshoot an employee showing $0:

  1. Go to the Employee Roster

  2. Check their HRA Status:

    • Active → eligible for reimbursement processing

    • No Proof of Coverage → onboarding incomplete

    • Not Participating → waived coverage

    • Reviewing Coverage → pending approval

    • Ineligible Owner → excluded from benefits

  3. Click into the employee record

  4. Review submitted claims and reimbursement history

  5. Cross-check with the Reimbursement Summary Report for the correct date range

Why does onboarding status matter for reimbursement?

Reimbursements cannot be processed until:

  • Proof of Coverage is submitted

  • Coverage is reviewed and approved

  • The employee is marked Active

Without this step, the system will not generate reimbursement amounts.

Why might a valid employee still show $0?

Even active employees may show $0 when:

  • They have a $0 claim balance for the selected month

  • Their allowance has not been used yet

  • Their reimbursement is scheduled for a future statement cycle

  • Their premium has not been set up as a recurring claim

This is normal in early onboarding or low-claim months.

Did this answer your question?