Bindinglaw

US · guidance

CMS Pub. 100-04, ch. 27, § 20.3.2

Claims Basic Reply

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

When the Host receives each claim or adjustment, it searches the Beneficiary File to find

the Beneficiary Record. If the Beneficiary Record is found, the record is processed and a

reply record is transmitted to the MAC. See §20.3.3, for an explanation of the procedure

if the Beneficiary Record is not found ("Not in File.") The record type returned by CWF

is dictated by the claim record type as follows:

• A/B MAC (B) Basic Reply Record - Reply record for each CWF A/B MAC (B)

bill (HUBC) processed.

• DMEPOS Basic Reply Record - Reply record for each CWF DMEPOS bill

(HUDC) processed.

• Inpatient/SNF Bill Basic Reply Record - Reply record for each Inpatient/SNF

bill (HUIP) processed.

• Outpatient/Home Health Bill Basic Reply Record - Reply record for each

Outpatient/Home Health bill (HUOP and HUHH) processed

• NOE/Hospice Bill Basic Reply Record - Reply record for each Hospice Notice

of Election and all subsequent Hospice bills (HUHC) processed.

Each reply record will contain a disposition code and error code that indicates the action

taken on the bill by the Host and what action the MAC should take next.

The following is a list of actions that CWF may take on a claim record. Disposition

codes, cross-reference/alpha search/NIF situations, their associated trailers, and bill

recycling instructions are also included:

History

(Rev. 4009, Issued: 03-23-18, Effective: 04-23-18, Implementation: 04-23-18)

Provenance

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