States measure administrative cost as a percentage of premiums collected. The calculation includes platform fees, payment processing, print/mail, and staff oversight. Manual processes typically run 30-50% of collected premiums. Fully automated platforms achieve under 10%. The target threshold for program viability is generally 15% or less.

Published state data shows wide variation: Arkansas saw 80% delinquency (only 20% paid), Iowa exceeded 75%, Michigan was at 56%. A state using Certifi's automated platform with retail cash payments, achieved only 17% falling into 90+ day delinquency with an overall 83% collection rate including state revenue department enforcement. The difference is driven by payment method availability, automation, and enforcement mechanisms.

States with active expansion premium programs include Montana (HELP Program), Indiana (Healthy Indiana Plan), Iowa (Health and Wellness Plan), Michigan (Healthy Michigan), and Arkansas (Arkansas Works). Most operate under Section 1115 waivers. Additionally, nearly all states charge CHIP premiums for families above 150% FPL (no waiver required), and several offer Medicaid buy-in programs with premium requirements. The landscape evolves as waivers are approved or modified.

Expansion premiums: Adults 19-64 up to 138% FPL, requires 1115 waiver, typically $5-$25/month, high delinquency challenge. CHIP premiums: Children in families above 150% FPL, no waiver needed, $15-$50/month per family, billed at family level. Buy-in premiums: Individuals purchasing Medicaid coverage (working disabled, medically needy), various statutory authorities, $50-$200/month, smaller populations with more complex eligibility. All three require billing infrastructure but with different rules per population.

The answer depends on the billing infrastructure, not the premium amount. A $17/month premium is viable at 7% administrative cost (Montana's result with Certifi). A $50/month premium is not viable at 60% administrative cost (common with manual processes). States that conclude "premiums aren't worth collecting" are typically making a statement about their billing technology, not the program concept. Purpose-built automation makes programs viable that manual processes cannot sustain.

Three factors converge: premiums are small ($10-$30/month), making the cost-per-transaction ratio unfavorable; a large portion of the population is unbanked, limiting electronic payment options; and eligibility changes frequently, creating retroactive adjustments. When you add 40-50% delinquency rates and the cost of manual check processing, many programs spend more to collect than they receive. The solution is automation combined with payment method diversity.

Three proven strategies: expand payment methods (retail cash at Dollar General, Walmart, and similar stores reaches unbanked members who cannot pay electronically), automate delinquency escalation (rules-based reminders at 30/60/90 days with automatic notice generation), and drive recurring payment enrollment (members on auto-pay rarely become delinquent). One client combined all three and achieved 83% overall collection with only 17% reaching 90+ day delinquency.

Retail cash payment is the primary solution. Members receive a payment barcode and present it at participating retail locations (Dollar General, Walmart, Walgreens, 7-Eleven, Family Dollar, CVS). Payment posts electronically within 24 hours. This serves rural populations without bank access and members who prefer cash transactions. Additional options include money orders via lockbox, stored-value (prepaid) cards, and prepaid debit cards that function without a traditional bank account.

The minimum set: ACH (one-time and recurring), credit/debit cards (including prepaid), retail cash at national retail networks, checks via bank lockbox automation, and stored-value cards. Beyond acceptance, the system should support binder payments at enrollment, saved payment methods, recurring payment subscriptions, and credit incentives for electronic payment enrollment. States that omit retail cash from their RFP requirements risk excluding 20-35% of their population from convenient payment.

Disenrollment follows a due process sequence: grace period (typically 60-90 days), written notice at multiple intervals, opportunity to cure (accept payment up to the effective date), appeal rights notification, and finally disenrollment communication to the enrollment system. The billing platform must enforce this timeline automatically, prevent premature disenrollment, and cancel pending actions when payment arrives. Federal law and waiver terms govern the specific requirements per state.

The automation stack includes: scheduled invoice generation from enrollment data, multi-channel delivery (electronic + print fulfillment), automatic payment posting from all channels, rules-based delinquency with auto-generated notices, recurring payment processing with retry logic, automated reporting to MMIS and state finance systems, and automated balance transfers to revenue departments. Together, these reduce the billing operation, cutting administrative costs.

Three procurement paths: competitive RFP (most common, 6-18 month timeline), NASPO ValuePoint or state cooperative contracts (pre-negotiated, faster procurement), and MMIS modular procurement (premium billing as a standalone module qualifying for enhanced federal matching). CMS modularity guidance supports best-of-breed procurement for specific functions like billing.

Essential RFP sections: population support (which programs, premium amounts, billing frequency), payment methods (specify retail cash explicitly), delinquency management (configurable events, notice generation, enforcement), MMIS integration (data standards, interface frequency), member portal (online payments, recurring enrollment), invoicing (electronic + paper, multilingual), fees/credits (incentives, late fees, waiver-specific credits), reporting (CMS metrics, collection rates), security (PCI, HIPAA), and implementation timeline. Common gaps: omitting retail cash requirements and the cost-per-dollar-collected evaluation criterion.

The billing system operates as a modular component with configurable interfaces. Inbound: enrollment data (demographics, coverage, premiums, effective dates) via web services, ANSI X.12 834, or proprietary files. Outbound: payment data to accounts receivable, delinquency/disenrollment events to eligibility, financial reporting to state finance, and delinquent balances to state treasury. The platform does not require MMIS core modification and integrates through standard interface patterns.

Custom MMIS builds cost $5-15M+, take 18-36 months, require ongoing state-funded maintenance teams, and lack the domain-specific depth of a purpose-built platform. Dedicated SaaS solutions cost a fraction, deploy in 90 to 180 days, include all maintenance, and bring proven collection optimization from prior state deployments. The MMIS vendor is a generalist; the billing vendor is a specialist. CMS modularity guidance supports using best-of-breed solutions for specific functions rather than asking one vendor to build everything.

Purpose-built SaaS: 90-180 days covering configuration, integration development, testing, and go-live. Custom MMIS build: 18-36 months. The 90-day timeline is achievable because the core platform (billing engine, payment processing, delinquency management, member portal) already exists in production. Implementation focuses on state-specific configuration and interface development using proven patterns from prior deployments.

Yes. A well-architected billing platform is MMIS-agnostic. It receives enrollment data through configurable interfaces (REST APIs, 834 transactions, or proprietary files) and returns payment/status data through the same layer. It works with legacy mainframe MMIS, modern API-based environments, hybrid architectures, and any vendor's platform (Deloitte, Accenture, IBM, CNSI, Conduent). Typically, no MMIS core modification is required.

The justification is straightforward: the platform must cost less than the premiums it collects. Supporting arguments include net revenue calculation (collected minus admin cost), cost avoidance versus manual operations (automated platforms save 70-80% versus manual), collection rate improvement (moving from 50% to 80% collection generates far more incremental revenue than the platform costs), and federal matching eligibility. If the platform enables a program that would otherwise be abandoned, all collected premiums represent incremental revenue.

Custom build: $5-15M+ initial development, 18-36 months, $1-3M annual maintenance, $50K-$500K per change request, state owns all risk. Purpose-built SaaS: Minimal or no upfront cost, 90-180 day implementation, predictable operational expense, maintenance included, vendor owns platform risk. The hidden cost of custom builds is what makes them particularly expensive: security patches, regulatory updates, staff turnover, and the opportunity cost of IT resources permanently tied to billing.

Sum all costs over 5 years: platform fees, payment processing, print/mail, staff oversight, IT maintenance, and (for custom builds) development team, infrastructure, and change requests. Divide by total premiums collected over the same period. The result is your administrative cost ratio. Target: under 0.10 (10 cents per dollar collected). Manual processes typically land at 0.30-0.50. Automated platforms achieve 0.07-0.10.

This is the single most important metric for program viability. Formula: total annual billing cost ÷ total annual premiums collected. At $0.07-$0.10, the program is clearly viable. At $0.30-$0.50 (manual processes), the program may cost more to operate than it generates. For a 25,000-member program with $17/month premiums, the difference between $0.07 and $0.40 per dollar collected is roughly $1.6M annually in administrative waste.

Automation eliminates manual labor at every stage: invoice generation (zero staff), electronic delivery (50-70% cost reduction vs. all-paper), payment posting (automatic from most channels), delinquency management (rules engine replaces manual tracking), and reporting (real-time vs. spreadsheet compilation). A program requiring 5-10 FTEs manually runs with less oversight when automated. At $80-120K per FTE, that is $400K-$1M+ in annual savings before accounting for error reduction and improved collection rates.

ROI comes from two sources: higher collection rates (moving from 50% to 80% on a 25,000-member, $17/month program adds $1.5M in annual revenue) and lower administrative costs (automation saves $500K-$1M vs. manual). Combined, a purpose-built platform can generate $2M+ in incremental annual value versus manual operations. Even at $500K/year platform cost, first-year ROI exceeds 300%. For many states, the real ROI is program survival: without efficient billing, the program is abandoned entirely.

The framework includes Section 1916 (baseline premium authority with income-based limits), Section 1916A (expanded authority via State Plan Amendment), Section 1115 waivers (most expansion premium programs operate here), and 42 CFR Part 447 (implementing regulations). Key constraints: aggregate cost-sharing cannot exceed 5% of household income, emergency services cannot be denied for non-payment, and disenrollment requires adequate notice and due process. CHIP has broader premium authority than traditional Medicaid above 150% FPL. Note, however, that the OBBBA appears to disallow premium for the Medicaid expansion population effective Oct. 1, 2028.

Waivers define the specific rules the billing system must enforce: premium amounts by income band, grace periods and enforcement mechanisms, incentive credits (healthy behaviors, community engagement, electronic payment), reporting requirements, and evaluation terms. No two state waivers are identical, so the billing platform must be configurable enough to accommodate each state's specific terms without custom development for every variation.

Waiver reporting may include: collection rates (% of billed premiums collected), delinquency rates by threshold (30/60/90+ days), disenrollment rates for non-payment, administrative cost ratios, payment method distribution, and incentive utilization rates. The billing system must generate these metrics automatically from transaction data. Manual compilation from spreadsheets is error-prone and unsustainable. CMS uses this data to evaluate whether the premium program meets its stated objectives without creating coverage barriers.

Three vendor categories: purpose-built billing platforms (designed for insurance premium collection complexity, including Medicaid-specific challenges), MMIS vendors offering custom modules (Deloitte, Accenture, IBM, CNSI, Conduent building billing as custom development), and general payment platforms (transaction processing without billing logic or delinquency management). Evaluation criteria should include: Medicaid deployment experience, demonstrated collection rates, retail cash capability, MMIS integration track record, CMS certification experience, implementation timeline, and total cost of ownership.

The billing system must process eligibility changes (income shifts, pregnancy, age changes, exemption qualifications) by recalculating premiums retroactively, generating credits for overpayments, pro-rating mid-month changes, cancelling pending delinquency events when premium status ends, and maintaining a full audit trail. These changes arrive from the enrollment system and must be reflected in billing within the current cycle. Member-level accounting architecture handles this without manual reconciliation.