Bindinglaw

US · guidance

CMS Pub. 100-05, ch. 5, § 50.1.5

Carrier MSPPAY Processing Requirements

activein force · 2026-08-25 – presentas-observed

The following processing requirements apply:

• Process all MSP physician/supplier claims through the MSPPAY

software to determine MSP payment amount, at the line level, where

applicable, deductible, coinsurance, and savings;

• Claims processed by MSPPAY must be in ready- to-pay status, e.g., the

amount that Medicare would have paid as the primary payer, the type of MSP

situation, the amount of the primary insurer's payment, information regarding

outstanding deductible and coinsurance must be available to MSPPAY; and

• All data elements required by MSPPAY must be passed to it. Section

50.1.7.A lists these data elements. The Medicare Secondary Payment Technical

Manual also contains additional information about them.

• The shared systems must accept MSP claims for services at the line level

including incoming charges, the OTAF amount, the other payer allowed and paid

amounts for incoming MSP claims at the line level.

• Forward the service line level amounts to the MSPPAY Module for

payment calculation.

• Receive the MSP payment at the line level when the completed

calculations are returned to the system from the MSPPAY module.

History

(Rev. 11550; Issued: 08-12-22; Effective: 10-13-22; Implementation:10-13-22)

Provenance

Source
cms.gov
Retrieved
2026-08-25
Edition
iom-2026-08-25
Content hash
507aab1f5080ca1ce66f2ddd11ed56ee604bf35f76da1896f9dacc9e8908e714
View the official source →

The link goes to the issuing authority’s own document — the one we read to produce this record. Where a source publishes whole titles rather than sections, your browser may need a moment to jump to the provision.

Unofficial copy of government-published law, reproduced from official sources with full provenance. Not an official publication; verify against official sources before relying on it in a filing. Records in the 'guidance' corpus, and only that corpus, are sub-regulatory (interpretive guidelines, survey procedures) and are not binding law. Validity bounds follow each jurisdiction's declared temporalBasis.

Coverage · API docs

Bindinglaw

Point-in-time US law with the receipt attached. Source URL, retrieval time, content hash, and validity dates on every answer.

curl api.binding.law/v1/law/coverage

© 2026 binding.law · a Jubal, Inc. productAttorneys and firms never pay. Ever.