Bindinglaw

US · guidance

CMS Pub. 100-24, ch. 3, § 3.5.1

CMS/TPS Buy-in Exchange Header Record

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

Item Field Size Position Format Description

1 File Type

Identification,

“PROD” or

“TEST”

4 1-4 Alphabetic Identifies the file as

either a test file, “TEST,”

or a production file,

“PROD.”

2 Filler 1 5 Position reserved for

future use.

3 File Creation Date,

CCYYMMDD

8 6-13 Numeric This represents the date

on which CMS generated

the file. An eight-position numeric date

(e.g., November 1, 2019

would be 20191101).

4 Filler 59 14-72 NA Positions reserved for

future use.

5 Agency Code 3 73-75 Alpha-numeric

or

Numeric

The three-position alpha-numeric or numeric code

identifying the state

which has jurisdiction

over the account

associated with this file,

Item Field Size Position Format Description

and identifying the file as

being Part A or Part B.

6 Record

Identification Code,

“H”

1 76 Alphabetic “H” constant. The “H”

identifies this record as

the header record.

7 Filler 5 77-81 NA Positions reserved for

future use.

8 Bill Month,

CCYYMM

6 82-87 Numeric A six-position numeric

field that designates the

billing period (year and

month) for which the

response is associated.

9 Filler 73 88-160 Positions reserved for

future use.

History

(Rev. 4, Issued: 08-21-20, Effective: 09-08-20, Implementation: 09-08-20)

Provenance

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