Bindinglaw

US · guidance

CMS Pub. 100-04, ch. 28, § 80.3.1

A/B MAC (A)/A/B MAC (HH) Crossover Claim Requirements

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

A. Outbound COB

The outbound COB transaction is a post-adjudicative transaction. This transaction

includes the incoming claim data as well as COB data. A/B MACs (A) are required to

receive all possible data on the incoming ASC X12 837 although they do not have to

process non-Medicare data. However, the shared system must store that data in a SFR.

This repository file will be designed and maintained by the shared system. This data

must be re-associated with Medicare claim and payment data in order to create an IG

compliant outbound COB transaction using the Medicare Part A Claim/COB flat file as

input. The shared system is to use post-adjudicated Medicare data (data used from

history and reference files to adjudicate the claim) instead of data received when building

the outbound COB transaction. The shared system must retain the data in the SFR for a

minimum of six months.

The Medicare Part A Claim/COB flat file is the format to be used to re-associate all data

required to map to the COB transaction. The translator will build the outbound COB

transaction from the Medicare Part A Claim/COB flat file.

The shared system maintainer must accommodate the COB transaction.

A/B MACs (A) shall refer to §70.6 through 70.6.5 for additional guidance concerning the

national COBA crossover process.

B. Summary of Process

The following summarizes all A/B MAC (A) steps from receipt of the incoming claim to

creation of the outbound COB:

A/B MAC (A)’s translator/edit process performs syntax edits, IG edits, and

Medicare edits and maps incoming claim data to the Medicare Part A Claim/COB

flat file;

Medicare data on the Medicare Part A Claim/COB flat file is mapped to the core

system by the shared system.

NOTE: No changes are being made to core system data fields or field sizes;

Non-Medicare data (and Medicare data elements where field sizes are in excess of

the core system) are written to the SFR by the A/B MAC (A)’s shared system;

and

Adjudicated data is combined with SFR data to create the outbound COB

transaction.

History

(Rev. 2906, Issued: 03-14-14, Effective: 04-14-14, Implementation 04-14-14)

Provenance

Source
cms.gov
Retrieved
2026-08-25
Edition
iom-2026-08-25
Content hash
23fdc310706212e8f2ff4f5e0d5fcd408be8a068d96d98066c7a86daa6ca3dc6
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.