What Did OBGYN Underpayments Cost Your Group in H1 2026?

Schedule Your Free Consultation

Your payer paid the claim. But did they pay what your contract actually says they owe? Most OBGYN groups closed out H1 2026 looking at a collections number that felt reasonable and never asked that second question. Denials get worked because they're impossible to ignore. Underpayments get overlooked because the claim already shows “paid” in the system. Our team at MedCloudMD spends a lot of time in exactly that gap, and this piece walks through what it actually costs and how to check your own numbers before H2 2026 starts.

Why “Paid” Doesn't Always Mean “Paid Correctly”

A claim can clear adjudication, post a payment, and still be wrong. Contracted rates get loaded incorrectly into billing systems. Global OB packages get reimbursed against the wrong fee schedule. Multiple-procedure reductions get applied when they shouldn't be. None of that trips a denial — it just quietly reduces the check. Unless someone compares the actual payment against the expected contracted amount, the gap sits there indefinitely.

What Counts as an OBGYN Underpayment?

An underpayment is any claim paid below the amount your contract, fee schedule, or coverage terms actually specify as distinct from a denial, where nothing was paid at all. Common OBGYN underpayment categories include contractual rate discrepancies, incorrect global-package reimbursement, modifier-related payment reductions, incorrect units, missed multiple-gestation adjustments, and coordination-of-benefits errors on secondary claims.

The Financial Impact of Underpayments in H1 2026

Illustrative Calculation

Expected Reimbursement − Actual Reimbursement = Potential Underpayment. Example: if your contracted rate for a global vaginal delivery package is $2,400 and the payer reimbursed $2,150 with no denial explanation, that's a $250 gap on one claim. Multiply an unnoticed pattern like that across a busy OBGYN group's H1 delivery volume, and the number stops looking small. This is a hypothetical illustration only, not a claim about your practice's actual numbers or any industry average.

Common OBGYN Underpayment Drivers

Global Obstetric Billing and Reimbursement Risk

Global OB codes bundle antepartum care, delivery, and postpartum care into one payment — CPT 59400 (vaginal), 59510 (cesarean), 59610 (VBAC), and 59618 (attempted VBAC converting to cesarean) are the four primary global packages. When one provider or group completes all three components, the global code applies. When care is split a patient transfers, changes insurance, or another practice handles part of the pregnancy component codes apply instead (59425/59426 for antepartum-only care, 59409/59410 or 59514/59515 for delivery with or without postpartum). Billing the wrong structure for a split-care pregnancy is a common source of both denials and underpayments, since payers increasingly audit what's actually inside a global claim rather than paying it at face value.

Did You Know?

Ultrasounds, non-stress tests, amniocentesis, and complication-related visits fall outside the global OB package and are separately billable with supporting documentation. Practices that don't itemize these leave legitimate revenue uncaptured — a different problem than underpayment, but one that shows up in the same collections gap.

Watch This Before H2 2026 Planning

Multiple industry sources describe a coming CPT restructuring that would delete the current global OB package codes (59400, 59510, and related component codes) effective January 1, 2027, replacing bundled global billing with itemized encounter-based reporting for antepartum visits, delivery, and postpartum care. Current codes reportedly remain billable through the end of 2026. This is a significant enough shift that OBGYN groups should start tracking official AMA CPT and payer guidance now rather than waiting for a January surprise treat this as a heads-up to verify, not a confirmed final rule.

Coding, Modifiers, and Payment Variance

Modifier 22 (increased procedural complexity), modifier 51 (multiple procedures), and payer-specific multiple-gestation billing instructions all affect what a claim should pay — and payers don't always apply them consistently, even when your documentation supports the modifier used. A payment that's lower than expected without a denial reason attached is exactly the kind of claim worth a second look, not a claim to file away as “paid.”

How to Calculate Potential Underpayment Leakage

Claim Paid → Compare Expected vs. Actual Payment → Difference Found → Verify Contract Terms → Review Coding and Modifiers → Appeal or Correct → Recover Revenue. The step most practices skip is the second one — actually comparing the posted payment against what the contract specifies, rather than just confirming a payment landed.

H1 2026 OBGYN Underpayment Risk Assessment

Could Your Practice Be Underpaid? Quick Check

Answer yes or no: (1) Are contracted rates loaded correctly into your billing system? (2) Are expected reimbursements compared against actual payer payments? (3) Does your team audit high-value OBGYN claims specifically? (4) Are global OB payments reconciled against contract terms? (5) Are modifier-related payment reductions reviewed? (6) Are recurring payer discrepancies tracked over time? (7) Does your practice distinguish denials from underpayments in its reporting? (8) Is there a formal underpayment appeal process? Scoring: 0–2 yes — low visibility into this risk. 3–5 yes — moderate underpayment risk. 6+ yes — stronger process, though a high-priority revenue leakage review may still surface something. This is an educational self-assessment, not a financial audit.

Underpayment vs. Denial: Why the Difference Matters

A denial tells you nothing was paid, and your team already has a workflow for that appeal, correct, resubmit. An underpayment tells you something was paid, just not enough, and most billing workflows have no equivalent trigger to catch it. Treating both the same way means denials get worked while underpayments accumulate silently in the “paid” column.

H1 2026 OBGYN Revenue Leakage Warning Signs

Before You Accept the Payment: Checklist

☐   Compare the posted payment against the contracted rate for that specific code

☐   Confirm the correct global or component code was billed for the care actually provided

☐   Review any modifier-related reduction against the documentation

☐   Check multiple-gestation or multiple-procedure adjustments against payer policy

☐   Verify coordination-of-benefits math on secondary claims

☐   Flag and track recurring discrepancies by payer, not just by claim

How MedCloudMD Helps Identify Revenue Leakage

We're not going to hand you a fabricated ranking of “top OBGYN billing companies” — we don't have verified data on how every other vendor in this space actually performs, and neither does most content that claims to. What we can tell you plainly: our team reviews OBGYN claims against contracted rates, checks global OB and component coding against actual documented care, and tracks recurring payer discrepancies so they get flagged as a pattern instead of quietly repeating claim after claim. If your group ended H1 2026 with collections that looked fine but has never run a systematic underpayment review, that's exactly the kind of gap we help close.

What OBGYN Practices Should Audit Before H2 2026

•     Contracted rates loaded in your billing system, compared line-by-line against actual signed contracts

•     A sample of global OB claims, checked against which provider actually completed which care components

•     Modifier usage patterns on high-value claims, checked against documentation

•     Secondary claims with coordination-of-benefits calculations

•     Current CPT and payer guidance on the coming global OB code restructuring

Frequently Asked Questions

What is an OBGYN billing underpayment?

A claim paid below the amount your contract or fee schedule actually specifies — different from a denial, where nothing was paid.

How can an OBGYN practice identify insurance underpayments?

By systematically comparing posted payments against contracted rates for the specific code billed, not just confirming a payment was received.

What's the difference between an OBGYN denial and underpayment?

A denial means nothing was paid and typically triggers a known workflow; an underpayment means something was paid, just less than owed, and often goes unreviewed.

Why should OBGYN groups audit paid claims?

Because a “paid” status doesn't confirm the amount was correct — rate errors, modifier issues, and global-package misapplication can all reduce payment without triggering a denial.

How can global OB billing create reimbursement discrepancies?

Split-care situations, incorrect component coding, and multiple-gestation adjustments can all cause a global claim to be paid incorrectly without an obvious denial reason.

How often should an OBGYN practice perform an underpayment audit?

Many practices benefit from a recurring review — periodic sampling of high-value claims plus a more complete review at least twice a year, including before major coding transitions.

Can medical billing companies help recover OBGYN underpayments?

Yes — a team focused on contract comparison and coding review can identify patterns an internal team may not have bandwidth to catch systematically.

What should an OBGYN practice review before H2 2026?

Contracted rate accuracy, global OB coding against actual care delivered, modifier patterns, and current guidance on the coming global OB code changes.

Disclaimer

This content is provided for general educational and informational purposes and does not constitute legal, coding, compliance, reimbursement, or medical advice. Payer contracts, policies, coding requirements, and reimbursement rules can change, and CPT coding guidance referenced here — including any discussion of upcoming code changes — should be verified against current official AMA CPT® and payer sources before making billing decisions. Practices should verify applicable requirements and consult qualified professionals regarding their specific circumstances.