Back to admin

Reason to Charge Code Mapping

Manage the governed link between business adjustment reasons and the charge codes they are officially allowed to apply to. This screen is designed as a scalable mapping console, not a one-row-at-a-time maintenance grid.

Mapped rows

6

Total stored reason-to-charge mappings

Filtered rows

6

Rows matching the current filters

Charge codes

150

Active charge codes in the catalog

Unmapped codes

144

Charge codes without any explicit mapping yet

Reset

Mappings overview

Browse the explicit mappings that already exist between charge codes and adjustment reasons.

Charge codeReasonCategoryReviewEffective

DATA_OVERAGE

Data Overage

Wireless Consumer

OVERAGE_RELIEF

Extra Data Charge Credit

USAGEDirect2026-08-14

INTL_DAY_PASS

International Day Pass

International

ROAMING_DISPUTE

International Roaming Dispute

ROAMINGReview2026-08-14

INTL_PAYGO

International Pay-As-You-Go

International

ROAMING_DISPUTE

International Roaming Dispute

ROAMINGReview2026-08-14

AUTO_PAY_DISCOUNT

AutoPay Discount

Wireless Consumer

MISSING_AUTOPAY_DISCOUNT

Missing AutoPay Discount

CREDITReview2026-08-14

ACTIVATION_FEE

Activation Fee

Wireless Consumer

FEE_WAIVER

One-Time Fee Waiver

ONE_TIMEReview2026-08-14

UPGRADE_FEE

Upgrade Fee

Wireless Consumer

FEE_WAIVER

One-Time Fee Waiver

ONE_TIMEReview2026-08-14

Bulk mapping

Map one reason to many codes

The scalable way to manage hundreds of charge codes is to assign mappings by reason, category, domain, or filtered result set instead of editing one row at a time.

Preview mode will be the next step here: show which charge codes would be mapped before applying changes to the database.

Why this matters

  • Use mappings as the governed permission layer between reasons and charge codes.
  • Let Rule Mgmt suggest likely codes, but only allow officially mapped combinations.
  • Use this screen for curated defaults and bulk assignments, not just row-by-row edits.