INSURANCE & PAYERS
A Payer Name Is Not a Billing Rule.
The same insurance brand can administer different products, networks, benefits, and payment arrangements. Billing Horizon organizes payer follow-up around the plan and service involved, not just the name on the insurance card.
We connect eligibility, authorization, claim responses, and payment review so the next action has a defined reason and an accountable owner.
Five details. One working context.
Resolve the context before deciding the route.
Payer Environments
Different Payment Systems. Different Billing Questions.
A payer workflow begins by identifying who administers the benefit, which rules apply, and where the claim or inquiry should be sent.
01 / FEDERAL
Original Medicare
Review the applicable Medicare Administrative Contractor, national or local coverage guidance, enrollment, and coding edits. An active Medicare record does not establish medical necessity for every service.
02 / PLAN ADMINISTERED
Medicare Advantage
Identify the member’s actual plan, network, referral requirements, and utilization management process. The claim route and administrative requirements differ from Original Medicare.
03 / STATE & MANAGED CARE
Medicaid & CHIP
Distinguish state fee-for-service from managed care and identify any separately administered benefits. The state program, plan, and provider enrollment context all matter.
04 / EMPLOYER & INDIVIDUAL
Commercial & Marketplace Plans
Check the product, benefit design, network, and applicable contract. An administrator’s brand does not tell you whether the employer’s plan is fully insured or self-funded.
05 / PROGRAM SPECIFIC
TRICARE & Other Government Programs
Confirm the program, region or administrator, provider status, and service requirements. Keep program-specific referrals and claim instructions separate from commercial workflows.
06 / RESPONSIBLE PARTY
Workers’ Compensation & Liability
Establish the injury-related carrier, claim information, and jurisdiction before treating the visit as a routine health plan claim. The responsible payer may depend on the service’s relationship to the injury.
Primary coverage needs its own review.
CMS requires Medicare billers to determine whether another payer has primary responsibility. Employment, other coverage, and injury-related information can change the billing order; Medicare should not automatically be placed first.
INSURANCE BRANDS & PLAN ADMINISTRATORS
The Name Is the Starting Point.
Billing work may involve national insurers, regional Blue plans, managed care organizations, and third-party administrators. We establish the member’s product and billing destination before applying a payer workflow.
Representative payer environments, not a list of partnerships or participating networks. Service scope and access are confirmed for your practice.
UnitedHealthcare
Aetna
Cigna Healthcare
Blue Cross Blue Shield Plans
Humana
Elevance Health / Anthem Plans
Molina Healthcare
Centene / Ambetter Plans
Oscar Health
Kaiser PermanenteUnitedHealthcare
Regional plans & other administrators
Tell us which plans matter to your practice. A payer not shown here can be part of the initial workflow discussion.
POLICY CONTEXT / REVIEWED OCTOBER 4, 2026
A Current Rule Still Needs the Right Scope.
Effective dates alone are not enough. Payer type, service category, state, and exceptions determine whether a policy belongs in your workflow.
CMS-0057-F / NON-DRUG AUTHORIZATION
Separate decision deadlines from API readiness.
72 hours
Expedited requests
7 calendar days
Standard requests
The 2026 decision-timeframe requirements apply to impacted Medicare Advantage, Medicaid, and CHIP payers for non-drug items and services. They do not apply to QHP issuers on federally facilitated exchanges under this rule. Applicable extension provisions still need review.
Specific denial reasons are required for impacted payers, including those QHP issuers. API compliance dates generally begin in 2027 and vary by payer type; an operational deadline does not mean every electronic connection is available today.
UNITEDHEALTHCARE / MEDICARE ADVANTAGE
A referral requirement is not universal.
Beginning in 2026, most UnitedHealthcare Medicare Advantage HMO and HMO-POS members need a PCP referral for certain specialist visits. Its published exceptions include mental health, oncology, hematology, and urgent care providers.
Requirement ≠ automatic denial
UnitedHealthcare’s current notice extends its grace period for adverse payment decisions related to these referrals. Providers should continue submitting required referrals. Delegated arrangements and state-specific processes also need review.
Program and facility billing are scoped separately from professional office claims. Provider eligibility, contracts, and service requirements are confirmed for the practice.
Check the applicable plan and current notice before assigning a denial reason or changing a scheduling workflow.
Need to understand where payer requirements intersect with your billing process?
RESPONSE-BASED FOLLOW-UP
“Unpaid” Describes a Balance. It Does Not Explain the Action.
The next step depends on where the claim stopped and what the payer actually returned. Sending the same claim again does not resolve every exception.
BEFORE ADJUDICATION
Rejection
Review the clearinghouse or payer response, correct the submission issue, and confirm the claim reaches the intended destination. A rejection is not the same as an adjudicated denial.
Evidence to retain
Response detail · correction · resubmission receipt
AFTER A DETERMINATION
Denial
Read the reason, remark, and policy context. Decide whether the issue needs corrected data, missing evidence, reconsideration, or an appeal through the plan’s process.
Evidence to retain
Determination · supporting record · applicable deadline
AFTER PAYMENT
Payment variance
Compare the remittance with the relevant contract or fee schedule. Separate contractual adjustments, member cost sharing, coordination of benefits, and a disputed payment amount.
Evidence to retain
Allowed amount · adjustment basis · expected payment
For example, UnitedHealthcare distinguishes corrected claims from reconsiderations and post-service appeals. Verify the applicable process and filing period rather than using one action for every outcome.
CODING EDITS & COVERAGE
A Clean Code Pair Does Not Establish Coverage.
CMS describes NCCI edits as correct coding edits, not medical necessity edits. Passing an edit does not establish the plan’s benefit, the authorization, or the documentation supporting the service.
Commercial and managed care payers may adopt NCCI methodologies differently. We review the payer’s actual response and effective policy instead of assuming every plan applies Medicare edits in the same way.
Are the codes, units, and modifiers supported?
Does the plan cover this service in this context?
Do the approval details match the service?
How do the contract and adjudication explain the balance?
Review each layer. One favorable result does not answer the others.
PAYER DATA & AI-ASSISTED REVIEW
Connect the Responses. Keep the Reviewer in Control.
Your EMR / EHR and practice management system need a way to reconcile information from the clearinghouse, payer portal, and remittance. Each response answers a different question.
270 / 271
Eligibility
What coverage and benefit information was returned?
837
Claim
What services and billing information were submitted?
276 / 277
Claim status
What status did the payer report for the inquiry?
835
Remittance
How were payment and adjustments reported?
Patterns can guide review. They cannot decide the appeal.
AI-assisted analysis can group recurring rejection messages, flag missing responses, and prioritize payment exceptions. A reviewer still checks the plan, source record, policy date, and available evidence before deciding the action.
QUESTIONS BEFORE WE BEGIN
Clarify the Payer Context. Then Define the Support.
The working relationship should establish access, responsibilities, and the information needed to follow an issue through to resolution.
No. Network participation belongs to the provider or practice and the applicable payer agreement. A billing relationship does not create participating status. We review the enrollment and contract context for the work in scope.
Tell us the payer, plan type, state, specialty, and issue you are seeing, without patient details. We can discuss the applicable workflow, information needs, and service scope before making a commitment.
Access depends on the agreed responsibilities and the payer’s available tools. During implementation, define authorized accounts, permissions, and how responses and supporting documents will be retained. Do not send portal credentials through the inquiry form.
No. The available path depends on the reason, coverage, documentation, filing requirements, and payer determination. We focus on a supported response and a traceable outcome rather than promising payment.
YOUR PRACTICE’S PAYER ENVIRONMENT
Tell Us Where Payer Follow-Up Gets Stuck.
Share the plans your practice encounters and the recurring issue you want to understand. We can discuss the benefit route, billing dependencies, and evidence needed for a useful review.
- Plan types and state
- Specialty and provider structure
- Rejections, denials, or payment questions
Discuss Your Insurance & Payer Workflow
No obligation. Just a focused conversation about your payer environment.