Health plans that limit their premium billing platform to one or two payment channels leave money on the table. The populations health plans serve are not financially the same. Some members set up ACH auto-pay without prompting, others pay by card when a grace period notice arrives, and a subset have no reliable banking access at all. William™, Certifi’s purpose-built health plan billing platform, supports the full spectrum of payment methods that modern health plan operations require. That includes ACH and lockbox, retail cash, and government subsidies. Collection rate improvement requires meeting members and employers where they are, not where it is convenient to collect.
This post covers each major payment channel, including how it works, the populations it serves, the processing economics, and what health plans should require from their billing software for effective support.
ACH and Electronic Funds Transfer
How it works
ACH (Automated Clearing House) and EFT (Electronic Funds Transfer) are the same underlying mechanism: a direct bank-to-bank transfer initiated through the ACH network. For premium billing, ACH is used in two modes. In pull ACH, the health plan’s billing system initiates the transfer from the member’s or employer’s bank account on a scheduled date. In push ACH, the payer initiates the transfer themselves through their bank’s bill pay system, which delivers the funds to the health plan’s account as an inbound payment.
Pull ACH is the preferred mode for recurring premium collection because the health plan controls the timing. Push ACH requires the payer to initiate each payment, which introduces the same human execution risk as any manual payment method.
Which populations does it serve?
ACH is the baseline payment method for all market segments. It is the lowest-cost payment method to process, the easiest to automate, and the most reliable for collecting recurring premiums. Employer groups billing large monthly premiums almost universally pay via ACH. ACA marketplace members with a stable income and a bank account are strong candidates for auto-pay. Medicare Advantage members without Social Security withholding commonly pay via ACH.
Any billing platform that does not support ACH as a primary payment channel is not viable for health plans to use when scaling.
Processing economics
ACH transactions carry the lowest per-transaction cost of any electronic payment method. The typical cost is well under a dollar per transaction with no percentage-of-payment fee. This makes ACH the most cost-effective channel for large premium payments and the natural choice for recurring auto-pay programs.
What should billing software support?
- Auto-pay enrollment: Members should be able to enroll in ACH auto-pay through the member payment portal. Self-service auto-pay enrollment serves as the best method to improve collection rates.
- Payment method management: Members must be able to update bank account information when accounts change — a common event that, if not handled via self-service, generates unnecessary member service contacts and missed payments.
- NSF and return handling: Returned ACH payments (insufficient funds, closed accounts, etc.) should be automated. The billing system can reverse the payment entry, generate a return notice to the member, and re-queue the account for delinquency tracking without manual intervention.
- NACHA compliance: ACH processing must comply with NACHA rules. Billing platforms should have NACHA-compliant ACH processing built in.
Lockbox Processing
How it works
A lockbox is a bank-operated payment processing service that receives physical checks on behalf of the health plan, deposits them, and delivers electronic remittance data to the billing system. Members and employers mail checks to a dedicated bank-owned P.O. box rather than to the health plan’s offices. The bank opens the mail, scans the checks, deposits the funds, and sends a remittance file to the billing system. The file contains the payment amount, check number, and any accompanying remittance information.
Without lockbox integration, check processing is entirely manual. Staff open envelopes, read check amounts and member identifiers, enter payment data into the billing system, and deposit checks at the bank by hand. Any significant volume leads to an expensive and error-prone process.
Which populations does it serve?
Check volume persists in two populations: employer groups that pay large consolidated invoices by check as a matter of accounts payable policy, and individual market members who prefer paper-based payment. For Medicare Advantage plans, check volume from members can be meaningful because many MA members are accustomed to paying bills by mail.
The goal is not to encourage check payments. It is to process them as efficiently as possible while actively offering electronic alternatives. Lockbox processing reduces the cost of handling checks that arrive regardless of the electronic channels offered.
AI-assisted payment matching
The primary operational challenge with lockbox payments is matching incoming payments to the correct member or employer account. Checks frequently arrive without adequate identifying information. A member may write their name but not their member ID, or an employer may include a remittance stub that does not match the current invoice.
AI-assisted payment matching reads check images, searches for likely account matches based on payment amount, name, and any available identifiers, and presents matched recommendations for staff review rather than requiring staff to perform the search manually. Health plans using AI-assisted lockbox matching report productivity improvements of 4x or more compared to fully manual check processing. That results in the same volume of checks being processed in a quarter of the staff time.
What should billing software support?
- Bank lockbox integration: The billing system must receive lockbox remittance files from the bank in standard formats (typically a flat file format produced by the bank) and process them automatically. For AI-assisted payment matching, plans should request that check images should also be sent to the billing system. This usually incurs an additional fee, but is well worth it for the efficiency gain.
- Suspense queue management: Payments that cannot be automatically matched arrive in a suspense queue for manual review. The suspense queue should display the payment details, the check image if available, and suggested account matches. It should be reviewable and clearable within the billing system without requiring a separate tool.
- AI-assisted matching: Purpose-built billing platforms should offer AI-assisted payment matching that reduces the manual work required to clear the suspense queue.
Credit and Debit Card
How it works
Health plan premium billing card payments are typically rare. Some health plans offer one-time payments or recurring card auto-pay. However, this is less common because the processing fee scales with the premium amount, making it more expensive than ACH for large payments.
Which populations does it serve?
For Medicare Advantage and other low-premium products, the processing fee may represent a meaningful percentage of the monthly premium. A 2.5% card processing fee on a $35 monthly premium is $0.88 per transaction. That is manageable, but worth evaluating against the collection rate improvement the channel provides for a given population.
Processing economics
Card processing fees typically run between 2% and 3% of the transaction amount and could include a small per-transaction fee. For one-time catch-up payments during a grace period, the cost may be justified by the collection outcome. A member who pays a $300 balance by card costs the plan approximately $7.50 in processing fees and avoids the revenue loss, member churn cost, and disenrollment administrative burden of a termination.
For recurring auto-pay on high-premium employer group accounts, ACH is almost always more cost-effective.
What should billing software support?
- PCI-compliant card processing: Card processing must comply with PCI DSS requirements. The billing platform should handle card data through a PCI-compliant payment gateway and should not store raw card numbers in its database. Look for platforms that use tokenization, where the card is stored as a token by the payment processor rather than as a card number in the billing system.
- Mobile-responsive payment portal: A significant share of card payments happens on mobile devices when members respond to delinquency notices. A payment portal that is not mobile-responsive will experience abandonment from members attempting to pay by phone.
- Immediate payment confirmation: Members who pay by card to resolve a delinquency need immediate confirmation that their coverage is intact. The billing system should post the payment, update the member’s paid through date, and email payment confirmation.
Payroll Deduction
How it works
Payroll deduction is the payment mechanism for employer-sponsored coverage: the employee’s premium contribution is withheld from their paycheck by the employer and remitted to the health plan on a regular schedule, typically semi-monthly or monthly. The health plan’s billing system receives a payroll deduction file from the employer or their payroll processor, reconciles the amounts received against the expected premium for each enrolled employee, and identifies discrepancies.
Payroll deduction is also the primary payment mechanism for voluntary benefits products. An employer offering voluntary life, disability, or supplemental health coverage collects employee payroll deductions and remits them to the benefit carrier or administrator.
Reconciliation requirements
Payroll deduction reconciliation is operationally demanding because the amounts received do not always match the expected premium exactly. Common discrepancies include employees who changed enrollment after the preparation of the payroll deduction file, new hires starting a mid-cycle deduction, terminated employees whose deduction happened for a pay period after termination, and rounding differences between the employer’s payroll calculation and the health plan’s premium records.
The billing system must be able to receive the payroll deduction file, match payments to individual employee accounts, and identify employees whose deduction amounts do not match their premiums.
What should billing software support?
- Standard payroll file formats: Payroll deduction files come from multiple payroll systems in varying formats. The billing system should support standard payroll remittance file formats and be able to ingest employer-specific file layouts without custom development for each employer.
- Employee-level payment allocation: The billing system must allocate the employer’s total payroll remittance to individual employee premium accounts and post individual payment credits, not just apply a lump sum to the group account.
Retail Cash Payment
How it works
Retail cash payment allows members to pay their health insurance premium in cash at a participating retail location. Typical locations include national pharmacy chains (CVS, Walgreens, Rite Aid) or mass retailers (Dollar General, Family Dollar, Walmart). The member receives a barcode on their paper invoice or in the member payment portal, presents the barcode at the retail payment terminal, pays cash, and the transaction is electronically reported to the health plan’s billing system through a retail payment network.
From the health plan’s perspective, retail cash payments are fully electronic. They arrive as electronic remittance data, not as physical cash. The billing system receives the payment through the retail payment network’s API or file feed, matches it to the member account, and posts it. The ‘cash’ designation refers to the member’s payment experience at the retail counter, not to the health plan’s accounting process.
When retail cash makes sense
Retail cash is a niche channel that delivers clear ROI in specific situations and negative ROI in others.
It makes sense for Medicare Advantage plans serving members with fixed incomes who may be more comfortable with in-person, cash-based transactions than online payment. For unbanked or underbanked MA members, retail cash may be the most accessible payment option available, and MA premiums are typically low enough that per-transaction processing costs are manageable.
It makes sense for CHIP and low-income ACA marketplace populations where underbanked members represent a meaningful share of enrollment. Offering retail cash reduces the share of members who face a coverage termination simply because they cannot access the electronic payment methods the plan offers.
It does not make sense for commercial employer group billing or individual market plans with higher premiums because employers and individuals will not carry that amount of cash to a retail site.
Implementation requirements
Retail cash payment requires a native integration between the billing platform and a retail payment network. Health plans cannot enable retail cash unilaterally by adding a barcode to their invoices. The billing software must support the retail payment network’s API, handle the remittance data feed, and generate compliant barcodes.
Government Subsidy and Capitation Payment Matching
APTC payment matching for ACA marketplace plans
Health plans participating in ACA exchanges receive monthly Advance Premium Tax Credit (APTC) payments from the federal or state exchange on behalf of subsidy-eligible members. These payments arrive as a lump sum covering the aggregate APTC for all enrolled members in that payment cycle. The billing system must disaggregate this payment, match each portion to the correct individual member account, credit the member’s net premium obligation accordingly, and flag any discrepancies where the APTC received does not match the expected amount based on the plan’s enrollment records.
APTC discrepancies arise frequently. They happen because enrollment changes, income changes, and exchange eligibility updates do not always synchronize perfectly between the exchange’s records and the health plan’s enrollment system. Retroactive eligibility changes may arrive after the monthly APTC payment has already been processed. That requires the billing system to create retroactive adjustment entries that are reconcilable in future payment cycles.
Medicaid capitation payment reconciliation
Medicaid managed care organizations receive capitated payments from state Medicaid agencies based on enrolled members. Each month’s capitation payment must be reconciled against the plan’s current enrollment roster to confirm that the payment reflects the correct number of enrolled members at the correct capitation rate for each eligibility category.
Retroactive enrollment adjustments, like members added or removed from the roster after the payment period, require corresponding capitation adjustments in future payment cycles. The billing system must track these adjustments, maintain an accurate reconciliation between capitation received and capitation owed based on actual enrollment, and support the reporting required by state Medicaid agencies.
What should billing software support?
- Exchange payment file integration: The billing system must receive and process APTC payment files from the federal exchange and any state-based exchanges in the standard file formats each exchange produces.
- Member-level payment disaggregation: Plans must automatically break down aggregate subsidy payments by individual member accounts.
- Capitation reconciliation reporting: For Medicaid MCOs, the billing system must support capitation reconciliation with reporting that aligns with state agency requirements.
Choosing the Right Payment Mix for Your Population
No single payment channel serves all populations. Health plans that offer only one or two channels will experience lower collection rates compared to plans that meet members and employers across the full spectrum of payment preferences. Here is a quick reference for which channels are most important by market segment:
| Market Segment | Priority Payment Channels |
|---|---|
| ACA Marketplace (with APTC) | ACH auto-pay, credit/debit card, lockbox for check payers, APTC matching, retail cash for underbanked |
| ACA Marketplace (without APTC) | ACH auto-pay, lockbox for check payers |
| Medicare Advantage | ACH, Social Security withholding, retail cash, lockbox for check payers |
| Medicaid / CHIP | Retail cash, ACH, lockbox for check payers, |
| Commercial Employer Group | ACH, lockbox for check-paying groups, payroll deduction |
Frequently Asked Questions
What payment methods should health plan premium billing software support?
A purpose-built health plan billing platform should support ACH and EFT for recurring premium collection, credit and debit card for one-time and catch-up payments, lockbox processing with AI-assisted payment matching for check volume, payroll deduction for employer-sponsored and voluntary benefits programs, retail cash payment for underbanked populations in Medicare Advantage and CHIP programs, and automated government subsidy and capitation payment matching for ACA and Medicaid plans. Each channel serves a distinct population and collection scenario. A platform that supports only ACH and card will underperform on collection rates across the full membership.
How does lockbox processing work for health plan premium billing?
A lockbox service operated by the health plan’s bank receives check payments by mail. It then deposits the funds, scans the checks, and delivers remittance data electronically to the billing system. The billing system matches each payment to a member or employer account. This is mostly automated, although a manual review queue exists for exceptions. AI-assisted payment matching improves matching productivity substantially compared to manual check processing. It can read check images and suggest likely account matches based on payment amount, name, and any available identifiers.
When should health plans offer retail cash payment for premiums?
Retail cash payment makes sense for Medicare Advantage plans serving unbanked or underbanked members. It can also be a good choice for low-income ACA marketplace and CHIP populations where underbanked members represent a share of enrollment.
What is AI-assisted payment matching, and how does it improve billing operations?
AI-assisted payment matching leverages machine learning to read incoming payment data and check images. It then recommends the most likely member or employer account match for each payment. Rather than requiring billing staff to manually search for the account corresponding to each unmatched payment, the system presents a ranked list of probable matches that staff can confirm or override. Health plans using AI-assisted matching report processing check volumes 4 times faster than manual matching with lower error rates.
What does NACHA compliance require for ACH premium billing?
NACHA compliance for recurring ACH premium debits requires written or electronic authorization from the member or employer before initiating debit transactions, specific authorization language that meets NACHA standards, a process for handling return codes when ACH transactions are rejected, prenote verification for new bank accounts, and record retention of authorization records. The billing platform should manage NACHA compliance requirements natively.
Related Knowledge Center Resources
For deeper coverage of related topics:
Premium Billing for Health Plans: Questions Answered
How to Improve Premium Collection Rates
Certifi’s health insurance premium billing and payment solutions help healthcare payers improve member satisfaction while reducing administrative costs.
