Explore

What's New?

04/16/26 - Release Notes

Features

Bugs

Chores

04/02/26 - Release Notes

Features

Payment Tracking > Add High-Risk Flag

A new member-level flag of High-Risk has been introduced

This flag can be set on the Member-level via Member Actions functionality

This flag allows users to callout specific payments as high priorities for escalation month-over-month

Future consideration will be put towards setting this flag by default at the organization level to represent teams with full risk pools as it related to premium payments and coverage

Payment Tracking > Split Member Name into First and Last

The original Member column has been split into First Name and Last Name to better match formatting on Payroll Reports and Invoices

Payment Tracking > History > Add Show/Hide Column Options

With the options to show or hide columns, the same functionality has been added to the existing Member History modal on Payment Tracking

Payment Tracking > Date Range Picker (Hackathon ‘26)

A second date picker has been added to Payment Tracking to allow for range selection

This will allow users to view multiple months of Payment Tracking information on the same page, separating PT months per row

Filters > Non-Payment Tracking pages > Set filters via URL

Following up on the previous update to Payment Tracking filters, similar functionality will apply to all other table filters on the Payments Platform

Anytime a filter or sort is applied on a table, the URL can be copied and utilized/shared with other users to maintain filter personalization

Bugs

Identified and fixed a bug related to how the system evaluates the Double Payment workflow

The workflow would be re-triggered by another System Error if occurring in a tight enough window, this has since been fixed to prevent erroneous status updates and System Errors

Fixed a bug which was causing PTs to be re-created upon card event errors on locked accounts

Since these PTs should already be removed due to the nature of inactive members, a fix has been released to ignore card events for which a PT no longer exists

Therefore, users will only be notified of card event failures for true active members with PT records

A chore has also been run to ensure that all erroneously created PTs were appropriately removed

The Member Note migration caused some Month Notes to be migrated out of order - these have since been re-migrated

An issue was identified with validation on the Last Touch Date, which was causing errors when attempting to save the status update modal

A fix has been released and validation has been improved to prohibit Last Touch Dates in the future as they must be set according to the current date or in the past

Chores

Marqeta

Implement new toolkit for deprecating resources

Highnote

Business Account Holder process

Initialize KYB

YTM logic cleanup

Member Note cleanup

03/23/26 - Release Notes

Announcements

Caution on YTM Columns

Please do not utilize these columns as a source of truth at this time

The product team’s recommendation is to hide these 3 columns via the Show/Hide column function so that they do not clutter your views

The team is working on additional features which will tie together this portion of release for a full auditing workflow improvement

Features

Payment Tracking > Add YTM Paid & Collection Columns

Three new columns have been added to PT to provide additional context for expected payment and reconciliation action, as they relate to Payroll Reports and the invoicing process

YTM Paid = Sum of Withdrawal Totals, up to the currently viewed PT month

YTM Collected = Sum of Individual Benefits Total on PR, up to the currently viewed PT month

YTM Discrepancy = YTM Collected - YTM Payments per month

YTM Collection information is currently pulled into Payments one a month - when Payroll Reports are locked

The product team is working on further updates for this feature to tie together the full workflow

Payment Tracking > Last Touch Date

A new column has been added to Payment Tracking for the member’s Last Touch Date - defined as the most recent date which FinOps has followed up on an unresolved member

The Last Touch Date can be set via the Status Change modal, and shortcuts to label Today as the Last Touch Date are available

This new field can be sorted and filtered on Payment Tracking for ease of auditing

Severe Last Touch Date values (defined by users as older than 5 days) will also be called out by red text instead of the regular black or white

Payment Tracking > Change Monthly Note to Member Note

The Monthly Note on Payment Tracking has since been transitioned to a Member-level note to contain full user context in one view, rather than tracing back context month-over-month

Existing Monthly Note content has also been migrated to the new Member Note

Payment Tracking > Prevent Transaction Auto-Assignment for past months

By default, payments will be assigned to the current pay period at the earliest, such that no new assignments should be occurring for pay periods that are in the past + kept out of user views

Transaction Log > Add Toggle for Assignable Transactions

On each transaction log in the Payments Platform at the member-level, team-level and global-level, a toggle of Show Only Assignable Transactions is now available

This toggle acts as a shortcut to apply the filters necessary for restricting the transaction log to transactions that can be assigned to Payment Tracking

Transaction Type = Withdrawal OR Deposit

Payment Type = ACH OR Card

UI/UX > Enable Opening Links in New Tab

The following components can be right clicked to open in a new tab

Team + Member Transaction Log

Team + Member Card Event Log

Team + Member Incoming ACH Log

Team Running Balance Log

Bugs

The Only Huntington Paid flag was incorrectly displaying False values despite a True flag - this has since been fixed

Fixed an issue with how the Reserve Used system error was behaving on System Error reassignment

Fixed Pay Period timeline

The Pay Period is now aligned on Payment Tracking as well as the platform view to display next month’s views by default when the date hits the 15th of the month

e.g. PT moves from showing April to May when the calendar hits April 15

UI now updates immediately when an account is locked

Previously, user would have to reload the page to confirm the status update despite displayed success messages

URL filter parameters caused issue with pagination, which have since been fixed

Chores

Bulk Update > Set HasPaymentsSetup for Migrated Members

03/05/26 - Release Notes

Announcements

Preset Filters on Payment Tracking has been removed in favor of personalized filters, more on this in the feature notes.

Feel free to bookmark the following links to utilize the previously available personalized filters.

Recreating original presets after removal:

⁠

Needs Paid⁠

⁠

Status = Unpaid OR Partial

Autopay Status = No OR Pending OR Hybrid

⁠

Unresolved Payments⁠

⁠

HasError = Yes

IsResolved != Yes

Filter persistence has also been removed to allow users to utilize multiple tabs of Payment Tracking

With CS entering PT, users’ views will no longer be restricted to their own teams. However, we hope the value provided by personalized filters outweighs this change. We can also explore adding a toggle in the future, similar to Unapproved Accounts.

Features

Payment Tracking > Implement Filter Personalization & Sharing

Filters can now be saved via bookmarking (Cmd + D on Mac // Ctrl + D on Windows). Saved filters can then be accessed by loading the stored bookmark.

Filters can also be shared with team members by linking the respective Payment Tracking URL.

While persistence has been removed if users navigate away from Payment Tracking, reloading the page to fetch updated data does persist the user’s active filters.

With this change, users are recommended to keep a main Payment Tracking tab open in their workflow, such that main filters are retained while further drilling down can be done via opening bookmarked filters or other Payment platform pages in separate tabs.

Users are able to open filters from hyperlinks or by copy/pasting filter links into their browser

Copy/pasting seems more stable as testers have reported possible hanging when opening a filter link directly (from Slack, hyperlink, etc.), but this is fixed by simply reloading the page once it opens in the browser

Payment Tracking > Allow Sorting by Carrier

Using the sort button on the carrier column now sorts alphabetically

If there are multiple carriers, the sort respects the member’s first listed carrier

The column can also be sorted reverse alphabetically by clicking the sort button again

Payment Tracking > Implement Default Sort

On initial load, Payment Tracking will now be sorted by Team, then by Member Name

If the user navigates away from PT and back, this default sort is also applied

Payment Tracking > Retain Review Status on Assigned Transaction

When a member is in a review status defined as the below, and a transaction is assigned to the month at the same time:

The status will remain in the given review status

A System Info of Transaction Assigned in Review will be applied to notify the user

Review Statuses are defined as:

Fin-Review

Adv-Review

CS-Review

Payment Tracking > Exporter > Add New Fields

The following fields have been added to the Payment Tracking Exporter:

System Info

System Error

User Note

User ID

Payment Tracking > Reinstate Info on Card Unlock

When a member’s debit card is unlocked, the member’s Payment Trackings will also be refreshed from the Core Platform.

Users will see a success message if the member’s Payment Trackings were refreshed

Otherwise, users will receive an error message, which will direct them to the Core Platform to utilize the existing Resend to Payments functionality on plan cards.

Payment Tracking > Set HasError with Card Event

When a member experiences a card event failure, the corresponding Payment Tracking month will be marked with an error based on the assignment timeline.

A System Error of Card Event Failure will be set

The existing card event failure reason of Digital Wallet Not Enabled has been ignored as this error code has been deemed a non-factor in user experience

This exclusion could not be tested concretely due to the lack of availability for this particular error code in Treasury Prime’s testing environment. All other available card event errors were tested.

Tables > Allow Users to Show and Hide Columns

A Columns button has been added to table headers next to the existing Filters and Density options

This button will allow users to hide or show columns on various tables as they see fit, such as Payment Tracking, Transaction Logs, etc.

Teams Overview > Show FinOps Team Owner

With FinOps Owner using the Core Platform as its source of truth, a label for FinOps Owner has been added on each Team Overview page for visibility.

Teams > Add Banking Integration Setting

When creating a new team in the Payments app, a new setting for Bank will be available to select Highnote or TreasuryPrime-BSB.

This feature is not intended to be used yet, it is in preparation for our bank migration.

Bugs

Fixes for Submitted to Paid validation

Manual Payment system info is now properly saved on attempted edit to Submitted

Users are notified via toast message that status was recently updated to Paid

A fix has been released for a bug that was causing team to stay the same despite swapping payment information to another member account was not a complete action.

PT Exporter has been fixed to show the correct Owner Name

The Last Modified By user was incorrectly shown instead

Added logic to catch cases that caused Autopay Statuses not to propagate to Payment Tracking, due to being saved via database script rather than user interaction

Chores

Money Movement > Ambetter & Anthem Balances

Money Movement > BCBS of MN

Bulk Update > Update Anthem AP to Expected from Carrier List

Bulk Update > Update Anthem AP from Joseph’s List

Bulk Update > Update Ambetter AP from Transaction History + Carrier List

Bulk Update > Update PTs to Fin-Review-Resolved

Tech Debt

Opening transaction logs in new tabs

More efficient saving of data

02/19/26 - Release Notes

Announcements

The functionality to update FinOps Owner/Org Representative from the payments platform is no longer available - this must be done through the core platform.

Updates made to member and team names from the core platform will also reflect in the payments platform moving forward.

Features

Selected Plan Flow > Revise Delete Logic for User Edits in History

The original update to selected plan delete logic for Payment Tracking added consideration for any edits in the history by a non-service user, which caused Payment Trackings to not get deleted when they should have.

This logic has since been updated in a 2/7/26 hotfix to ignore deletion given ANY the following criteria in the PT month:

Has an assigned transaction

Contains content in the user note

Is in a status other than Unpaid

Payment Tracking > Open Member Transaction Log & Team Transaction Log in New Tab

When clicking the Member Transaction Log or Team Transaction Log buttons in Payment Tracking, users will now be sent to a new tab in order to preserve their Payment Tracking view in the original tab.

PT > Validation When User Marks Already Paid PT as Submitted

Since manual payments can sometimes process faster than users can return to Payment Tracking to mark a row Submitted + log the confirmation, validation has been added to the status.

With this update - anytime a user attempts to change a status to Submitted, the system will check for the following and return an error if both are true:

Does the month have an assigned transaction?

Was the month’s status changed to Paid in the last 5 minutes? (Can be identified via the history modal)

Simply waiting the 5 minutes will allow users to mark a row Submitted if it was recently flipped to Paid, but this should mainly serve as a flag for users to indicate that their previously submitted payment has already processed.

How often does this happen as this could affect users’ manual payment statistics?

PT > Export Functionality

Users can now export their current view of Payment Tracking (in CSV format) based on the applied filters via the Actions button in the top right.

The applied filters will also be displayed in the export file for ease of visibility.

The size limit on Payment Tracking exports is 10,000 rows, so batch sizes exceeding this will need to be split by using filters.

Currently, the available columns are as follows:

Team Name

RH Member ID

Member Name

Current Balance

Expected Premium

Withdrawal Total

Last Withdrawal Date

Status

Has Error?

Carriers

Auto Pay Status

Is Resolved?

Owner Name

Number of Plans

Only Huntington Paid

Additional columns will be added in a future iteration, so please provide feedback as necessary to escalate column needs.

Payment Tracking > Callout for Inactive Payment Accounts

There is now a red icon callout for locked debit cards as well as closed checking accounts displayed on Payment Tracking to help users identify non-active payment accounts at a glance.

Bugs

Pagination does not get next pages on Teams page

PT > Double Payment Calulation Ignores Refunds

PT > Additional Filters > Glitching with Multiple Tabs

PT > History Modal > Paid Displaying as Unpaid

PT > Visual Flickering and Loading Bug

Searching Members on Team causes numerous API calls

Chores

Bulk Update > Send Mismatched FinOps Owners to Core

Bulk Update > Update BCBS MN Member Ids

Bulk Update > Change AP Status for Moda + Wellmark Members

Bulk Update > Mark Premium Mismatches as IsResolved

Bulk Update > AP Status for Remaining Pendings

02/05/26 - Release Notes

Features

Payment Tracking > Filters > Allow Null Search on Carriers

This update aims to aid users with auditing stale Payment Tracking rows or bad data in the form of missing carrier information

New filter options have been added to Carriers:

IsNull - filters only for rows where the Carrier field is empty or not set

IsNotNull filters only for rows where the Carrier field has been set explicitly

Payment Tracking > Enhance History Modal to Display Active vs. Resolved Errors

The existing history modal has been improved upon with added visibility into System Errors as well as when each error was resolved

When clicking the Show History button on the View Member Info modal, the current data will be highlighted in yellow, and any new + unresolved System Errors will cause IsResolved to change back from Yes to No for FinOps visibility

In the below example, the member’s Reserve Used System Error had been resolved on 1/21/26 but a new Reserve Used error was flagged one minute later, which set IsResolved back to No

⁠

⁠

Payment Tracking > Add Resend to PT button from Plan Card

A new Action button has been added to plan cards of Resend to Payments to manually refresh all Payment Tracking for the particular member based on the plan card which is refreshed

This can be used in situations when scripts have been run or database updates have been made that may not have been caught by ServiceBus to propogate updates to Payment Tracking

Should prevent users from having to edit the plan card directly - simplifying the action as well as reducing risk of bad data from arbritrary user edits

Payment Tracking > UI/UX > Change Not Set to Dash

We received feedback that a mass of Not Set on Payment Tracking can be strenuous on user eyes

Any of those fields now simply display as a - in Payment Tracking, which should simplify views

Bugs

Selected Plan Deletes > Plan Card Termination setting values to Null

In implementing logic to prevent deletions in PT, a bug was discovered that would null or “zero out” a given user’s PT monthly values if they were slated for deletion but were prevented by the new logic

A fix has since been deployed to ensure PT rows that are slated for deletion but avoided via logic:

Should retain any monthly infos in undeleted PT months

Should have a Plan Card Not Active System Info added

Core > Plan Cards with early end dates set will dissappear from UI

Particularly during OE, there were many cases or missing or phantom plan cards due to the system removing plan cards from the UI (but not deleting) which had coverage end dates < coverage start dates

This caused issues in sycning other microservices with the correct plan with plan cards being the source of truth

Validation has been added to plan cards such that a plan card can no longer be saved if a user attempt to set the coverage end date as prior to the coverage start date

Payment Tracking > Unable to filter for any new System Infos

Member Paid, Credit, No Coverage, Plan Card Not Active

A fix has been released which will allow users to filter for the new System Infos in Payment Tracking as expected

Chores

Account Management > Swapping HoldCo and Campbell St. Accounts

Account Management > Member Name Changes

Account Management > Ignite & JHG Consolidation

Bulk Update > Raush CReek Autopay Statuses

01/28/26 - Hotfix

Features

Payment Tracking > Logic for Delete Events

Logic has been added to PT such that a plan card delete event will be ignored in PT if any of the following conditiona are met for the PT month that is attempted to be deleted:

Has been edited by a user other than the ServiceUser in its history

Has an assigned transaction

Contains content in the user note

Is in a status other than Unpaid

If a PT month is slated for deletion via plan card event, but is not deleted due to the above mechanism, a new System Info of Plan Card Not Active will be added to that month

Bugs

Locking Accounts > Removal mechanism not respecting user-selected PTs

A fix has been released for the issue where the locked account mechanism was not deleting the appropriate PT months despite user selection being made on the modal

⁠

01/22/26 - Release Notes - January 22, 2026

Features

Payment Tracking > Review IsResolved > Add Dropdown for System Infos

When a member has an error flagged and is placed in a review status by a user, the user is then able to mark the error Resolved to remove the member from their error queue

Building on this, users will now be able to add a System info when Resolving a member based on the following options:

Member Paid

Credit

No Coverage

In addition, new System Errors will now change a member’s IsResolved status back to No if it has been set to Yes by a user

Payment Tracking > Show Modification History

When accessing the View Member Info modal, a new button option will be shown to Show History

This new modal reveals the payment tracking history for a given member in the month that the user is viewing

Payment Tracking > Removal Selection on Account Locking

When locking a member’s debit card, users will now be displayed a modal to select which months to remove from Payment Tracking. The status and note content for each PT month is displayed for user visibility.

If no months are selected and debit card locking is finalized, no PT months will be removed by this mechanism.

This portion of the feature is not currently working as intended - a fix is in progress as of 01/23/26

A fix has been released as of 01/28/26.

When a debit card is unlocked after having been locked, a similar selection modal will be displayed to allow users to select PT records for manual creation.

Bugs

Null Input Error from Global Search

Chores

Update 302 autopay statuses for happy path auto enrollments

User-requested name changes

Want to print your doc?
This is not the way.

Try clicking the ··· in the right corner or using a keyboard shortcut (

CtrlP

) instead.