Skip to main content

Billing Code Editing Flow Release Notes

Agency Admins can now edit existing billing codes, even after those codes have been used in billing records.

Updated over 2 months ago

🧩 Overview

Agency Admins can now edit existing billing codes, including updating configuration settings, names, modifiers, and groups—even after those codes have been used in billing records. This feature is designed to support compliance with state-regulated billing changes, such as new rates, modifiers, or naming conventions.

The goals of this release are:

  • Provide flexibility to update billing codes when regulations change

  • Maintain historical accuracy where required (e.g., rate updates not retroactive)

  • Ensure changes are communicated clearly with a preview of client and budget impact

  • Prevent unintended application of changes to historical records where not allowed

šŸ‘„ Impacted Users

This release impacts Administrators. Mainly those who are responsible for billing within their Agency. Bug fixes should be unnoticed by users as fixes were made to ensure current functionality works as expected.

✨ New Features and Feature Enhancements

šŸŽØ UI/UX Improvements

  • Updated design for creating new billing codes

  • Cleaner layout and more intuitive field groupings for both creation and editing

  • Visual cues for retroactive-editable fields vs. non-editable fields

āœ… Editable Fields

Admins can now edit the following in an existing billing code:

  • Billing Code Name

  • Display Name

  • Group

  • Modifiers

  • Billing Code Configuration settings (e.g., rate, rounding rules)

  • State

  • Place of Service

  • Description

  • EVV required toggle

  • Split at Midnight toggle

āš ļø Unit Type is NOT editable once a billing code has been created.

When the code name, modifiers, rate, and unit value of a billing code is edited, any budget linked to that code will automatically be split. This means:

  • The original budget is archived.

  • A new budget is created with the updated billing code.

  • The new budget keeps all the same details as the original—except for the specific changes made to the billing code.

Example:

You have a billing code with a day rate of $60, and a client budget using that code that runs from July 4, 2025 to February 3, 2026.

If you update the billing code’s rate to $65, effective August 6, 2025, here’s what happens:

  • The original budget (at $60/day) is archived, covering July 4, 2025 to August 5, 2025.

  • A new budget (at $65/day) is created, covering August 6, 2025 to February 3, 2026.

You’ll see the updated budget with the new rate in the client’s profile, and the archived version will remain visible in the archived budgets section for historical reference.

šŸ”€ Retroactive vs. Non-Retroactive Behavior

Field Edited

Retroactive Allowed?

Notes

Name / Group / Modifier

āœ… Optional

Controlled via toggle

Billing Configuration (rate, rounding, etc.)

āŒ Not allowed

Always applies to future records only

Unit Type

āŒ Not editable

Hard-locked

🧠 New Behavior: Apply Changes Toggle

On the final confirmation modal during an edit, the admin will see:

Toggle: ā€œApply changes to only new billing recordsā€

  • Default: ON

  • Applies only to name, group, and modifier updates

  • If turned OFF, updates apply retroactively to all historical billing records

āš ļø If configuration settings are edited and the admin tries to toggle OFF, they will see a blocking notification stating:

"You edited billing configuration, which cannot be applied to historical records."

šŸ“Š Preview: Pending Changes Summary

Regardless of the toggle state, the user will see a Pending Changes section with:

  • Original settings

  • What has changed

  • Updated settings

  • List of affected clients and budgets (if applicable)

This gives admins visibility before confirming changes.


šŸŽØ UI/UX Improvements

  • Updated design for creating new billing codes

  • Cleaner layout and more intuitive field groupings for both creation and editing

  • Visual cues for retroactive-editable fields vs. non-editable fields

✨Feature Set and Affected Other Feature Areas

  • Outline what feature area this specific feature is a part of and if any, outline other feature areas this feature touches

šŸ› Issues and Bug Fixes

  • Any bug fixes that were a part of the release of this feature

Did this answer your question?