CMS waiver terms define the specific rules a state's premium billing program must follow. These vary significantly by state and create direct requirements for the billing system:

• Premium amounts and schedules. Waivers specify maximum premium amounts by income band, billing frequency (monthly, quarterly), and whether premiums are flat or income-based. The billing system must calculate and apply the correct premium for each member based on their eligibility category.
• Grace periods and enforcement. Waivers define how long a member can remain enrolled without paying and what happens after the grace period expires. Some waivers prohibit disenrollment entirely (requiring alternative enforcement like benefit lockouts). Others allow disenrollment after 60 or 90 days.
• Incentives and credits. Many waivers include provisions for premium credits tied to healthy behaviors (completing health risk assessments, participating in wellness programs, maintaining employment). The billing system must track and apply these credits.
• Reporting requirements. Waivers typically require states to report collection rates, delinquency rates, disenrollment rates, and program costs to CMS at defined intervals. The billing system must generate this data.
• Evaluation requirements. 1115 waivers include evaluation terms. States must demonstrate that the premium program meets its stated objectives (cost offset, personal responsibility, etc.) without creating barriers to coverage.

Waiver terms often require states to provide adequate notice and opportunity to cure before disenrolling a member for non-payment. The specific requirements may include:

1. Advance written notice. Members must receive written notice before any adverse action. Most waivers require notice at least 30 days before disenrollment takes effect. The notice should clearly state the reason, the amount owed, how to pay, and the consequences of non-payment.
2. Plain language and accessibility. Notices should be written in plain language at an appropriate reading level. Many states require notices in multiple languages based on the population served. Notices must be accessible to members with disabilities.
3. Opportunity to cure. Members should have a clear, accessible path to bring their account current. This means the billing system must accept payment up to and including the disenrollment effective date, and must automatically cancel the disenrollment if payment is received.
4. Appeal rights. Members should be informed of their right to appeal the disenrollment decision through the state's process.
5. Multiple notice attempts. Best practice (and some waiver requirements) call for escalating notices at multiple intervals (e.g., 30 days past due, 60 days, final notice at 90 days) before disenrollment.

The billing system must:

• Generate compliant notices automatically at configurable intervals
• Support custom notice language per population type
• Automatically cancel disenrollment events when payment is received
• Communicate disenrollment events to the enrollment system only after all due process requirements are satisfied

States operating premium programs under 1115 waivers or State Plan Amendments must report program performance to CMS. The specific reporting requirements vary by waiver but typically include:

• Collection rates. Percentage of billed premiums actually collected, reported monthly or quarterly. This is the primary measure of program effectiveness.
• Delinquency rates. Percentage of members past due at various thresholds (30, 60, 90+ days). Tracks the health of the collection process.
• Disenrollment rates. Number and percentage of members disenrolled for non-payment. CMS monitors this to ensure premiums are not creating barriers to coverage.
• Administrative cost ratios. Cost of operating the billing program relative to premiums collected. Demonstrates program efficiency.
• Payment method distribution. How members are paying (electronic, cash, check). Informs program design decisions.
• Incentive utilization. If the waiver includes premium credits for healthy behaviors, states may need to report participation rates and credit amounts.

The billing system must generate these metrics automatically from transaction data. Manual compilation of CMS reports from spreadsheets is error-prone and unsustainable at scale.

The vendor landscape for state Medicaid premium billing includes three categories:

1. Purpose-built premium billing platforms. Vendors whose core product is premium billing and payment collection. These platforms are designed specifically for the complexity of insurance premium billing, including the unique challenges of Medicaid populations (small premiums, unbanked members, high delinquency, retail cash payment needs).

2. MMIS vendors offering custom billing modules. Large system integrators (Deloitte, Accenture, IBM, CNSI, Conduent) that build custom billing functionality as part of broader MMIS contracts. These are custom development projects, not configurable products, and carry significantly higher cost and implementation timelines.

3. General payment platforms. Payment processing companies that handle transaction processing but lack the billing logic, delinquency management, invoicing, and program-specific configuration required for Medicaid premium programs.

When evaluating vendors, state technology teams should assess:

• Medicaid-specific experience. Has the vendor deployed premium billing for a state Medicaid program? Do they understand the population, the economics, and the compliance requirements?
• Collection rate outcomes. What collection rates have they achieved in production? What is the total cost of billing as a percentage of collected premiums?
• Payment method breadth. Do they support retail cash payments for unbanked populations? This is a critical differentiator for Medicaid programs.
• Configurability. Can the platform adapt to state-specific waiver terms without custom development?
• MMIS integration experience. Has the vendor integrated with state MMIS environments? Do they support standard interfaces (834, web services)?
• CMS certification experience. Has the vendor been through the CMS certification process for a state Medicaid module?
• Implementation timeline. How quickly can the platform be production-ready?
• Total cost of ownership. What is the ongoing cost relative to a custom build?

Medicaid beneficiaries frequently move between eligibility categories that require premiums and categories that do not. Common scenarios include:

• Income changes that move a member above or below the premium threshold
• Pregnancy (which often exempts members from premiums)
• Age changes (children aging into or out of CHIP)
• Qualifying for a premium exemption (Native American status, veteran status, student status)
• Moving between Medicaid expansion and traditional Medicaid categories

The billing system must handle these transitions accurately:

• Retroactive adjustments. When eligibility changes are reported retroactively (which is common), the billing system must recalculate premiums for affected periods, generate credits for overpayments, and adjust future invoices accordingly.
• Real-time eligibility updates. The system must process eligibility changes from the enrollment system promptly and stop or start billing within the current billing cycle.
• Pro-rated premiums. When a member's premium status changes mid-month, the system must calculate pro-rated amounts based on the effective date of the change.
• Delinquency reset. When a member transitions from premium to non-premium status, any pending delinquency events must be cancelled and the account closed or zeroed appropriately.
• Audit trail. All eligibility-driven changes must be tracked with full audit history for CMS reporting and dispute resolution.