Skip to content

Run the HRA Annual Interest report and reconcile a member's balance

As an H&W Staff member, I want to run the HRA Annual Interest report for a given as-of date and confirm it matches a specific member's own HRA History ledger, so that I can verify or refute a balance discrepancy before escalating it.

Screen: Reports > H & W > HRA Annual Interest (underlying report name HRAAnnualInterest).

Steps

  1. Switch the top-nav Fund selector to H&W first.
  2. This is one of the simplest SSRS report parameter screens on this project — a single plain date field, "As at Year End date", with no checkbox-picker gotchas. It defaults to the fiscal year end (5/31 in this environment) but accepts any date.
  3. Click View Report. Columns: Last Name, First Name, Middle Name, SSN (xxx-xx-xxxx), DOB (MM/DD/YYYY), HRA Balance, Prizm ID.
  4. To reconcile a specific member: resolve their Prizm ID to a Reg# via PRIZM Query (Member entity, MemberPrizmID/RegNumber/LastName/FirstName/SSN columns — this also confirms Prizm ID is a stable PQ-queryable key).
  5. Open that member's Member > HRA History tab and compare the report's balance against the HRA History row's own Running Balance at the matching contribution period. They should match exactly.

    HRA History tab's Running Balance column

Things to watch out for

The report includes by contribution period, not post date

A late-posted payment for a period still in scope is correctly included, even though it was posted after the as-of date — the report's inclusion rule is contribution period ≤ as-of date, not post date ≤ as-of date. This matches real business behavior (dues/HRA payments routinely post late), but it's easy to get backwards from a single example, since "posted late" and "excluded" can coincide by accident on one test member. If you're verifying a "report doesn't include late postings" claim, construct an explicit test — a member whose only in-scope-period payment has a late post date — rather than inferring the rule from one observed balance. This exact misreading happened on IUOE-2822: a reviewer called a correct result "not a bug" for the right member but the wrong reason.

Not every ticket-referenced import config actually exists in this UAT environment

IUOE-2822 also called for testing a new "HRA Interest" import attribute/configuration (Prizm ID + Interest mapping). It wasn't found in either place it would be configured — Accounting > Import's "Select Import Configuration" dropdown for the relevant employer, or Maintenance > FileImportUtility's employer-to-configuration mapping grid. Don't assume a ticket's description of a delivered feature means its UAT-environment configuration was also set up — check both places before concluding the import side can't be tested, and report "not found" explicitly.

The HRA Fund Status (Forfeiture Eligibility) report doesn't net out already-forfeited balances

If a member's HRA balance includes amounts that were already forfeited, the HRA Fund Status report doesn't currently account for that — don't treat a forfeiture-eligibility figure as automatically net of forfeitures already applied. (IUOE-2758 — Phase 1 stub, same family as IUOE-2184's forfeiture scenario)

See also Look up a member's benefits and dependent history for the BenefitsHistory/H&W History tabs this report cross-checks against, and Add a new HRA record for a member for adding the transactions this report reads.