X12 HIPAA
/
Health Insurance Exchange Related Payments (X306)
  • Specification
  • EDI Inspector
Stedi maintains this guide based on public documentation from X12 HIPAA. Contact X12 HIPAA for official EDI specifications. To report any errors in this guide, please contact us.
Go to Stedi Network
X12 HIPAA logo

X12 820 Health Insurance Exchange Related Payments (X306)

X12 Release 5010

This X12 Transaction Set contains the format and establishes the data contents of the Payment Order/Remittance Advice Transaction Set (820) for use within the context of an Electronic Data Interchange (EDI) environment.
The transaction set can be used to make a payment, send a remittance advice, or make a payment and send a remittance advice.

This transaction set can be an order to a financial institution to make a payment to a payee. It can also be a remittance advice identifying the detail needed to perform cash application to the payee's accounts receivable system. The remittance advice can go directly from payer to payee, through a financial institution, or through a third party agent.

Delimiters
  • ~ Segment
  • * Element
  • > Component
  • ^ Repetition
EDI samples
View the latest version of this implementation guide as an interactive webpage
https://www.stedi.com/app/guides/view/hipaa/health-insurance-exchange-related-payments-x306/01HQ4HZB22GES43ZEA8H62Y77C
Powered by
Build EDI implementation guides at stedi.com
Overview
ISA
-
Interchange Control Header
Max use 1
Required
GS
-
Functional Group Header
Max use 1
Required
heading
ST
0100
820 Header
Max use 1
Required
BPR
0200
Financial Information
Max use 1
Required
TRN
0350
Reassociation Trace Number
Max use 1
Required
REF
0500
Exchange Assigned Qualified Health Plan Identifier
Max use 1
Optional
REF
0500
Issuer Assigned Qualified Health Plan Identifier
Max use 1
Optional
REF
0500
Exchange Assigned Employer Group Identifier
Max use 1
Optional
REF
0500
Issuer Assigned Employer Group Identifier
Max use 1
Optional
Payee Name Loop
detail
Remittance Information Loop
ENT
0100
Remittance Information
Max use 1
Required
Individual Name Loop
GE
-
Functional Group Trailer
Max use 1
Required
IEA
-
Interchange Control Trailer
Max use 1
Required
ISA

Interchange Control Header

RequiredMax use 1

To start and identify an interchange of zero or more functional groups and interchange-related control segments

Example
ISA-01
I01
Authorization Information Qualifier
Required
Identifier (ID)

Code identifying the type of information in the Authorization Information

00
No Authorization Information Present (No Meaningful Information in I02)
ISA-02
I02
Authorization Information
Required
String (AN)
Min 10Max 10

Information used for additional identification or authorization of the interchange sender or the data in the interchange; the type of information is set by the Authorization Information Qualifier (I01)

ISA-03
I03
Security Information Qualifier
Required
Identifier (ID)

Code identifying the type of information in the Security Information

00
No Security Information Present (No Meaningful Information in I04)
ISA-04
I04
Security Information
Required
String (AN)
Min 10Max 10

This is used for identifying the security information about the interchange sender or the data in the interchange; the type of information is set by the Security Information Qualifier (I03)

ISA-05
I05
Interchange ID Qualifier
Required
Identifier (ID)
Min 2Max 2

Code indicating the system/method of code structure used to designate the sender or receiver ID element being qualified

Codes
ISA-06
I06
Interchange Sender ID
Required
String (AN)
Min 15Max 15

Identification code published by the sender for other parties to use as the receiver ID to route data to them; the sender always codes this value in the sender ID element

ISA-07
I05
Interchange ID Qualifier
Required
Identifier (ID)
Min 2Max 2

Code indicating the system/method of code structure used to designate the sender or receiver ID element being qualified

Codes
ISA-08
I07
Interchange Receiver ID
Required
String (AN)
Min 15Max 15

Identification code published by the receiver of the data; When sending, it is used by the sender as their sending ID, thus other parties sending to them will use this as a receiving ID to route data to them

ISA-09
I08
Interchange Date
Required
Date (DT)
YYMMDD format

Date of the interchange

ISA-10
I09
Interchange Time
Required
Time (TM)
HHMM format

Time of the interchange

ISA-11
I65
Repetition Separator
Required
String (AN)
Min 1Max 1

Type is not applicable; the repetition separator is a delimiter and not a data element; this field provides the delimiter used to separate repeated occurrences of a simple data element or a composite data structure; this value must be different than the data element separator, component element separator, and the segment terminator

^
Repetition Separator
ISA-12
I11
Interchange Control Version Number
Required
Identifier (ID)

Code specifying the version number of the interchange control segments

00501
Standards Approved for Publication by ASC X12 Procedures Review Board through October 2003
ISA-13
I12
Interchange Control Number
Required
Numeric (N0)
Min 9Max 9

A control number assigned by the interchange sender

ISA-14
I13
Acknowledgment Requested
Required
Identifier (ID)
Min 1Max 1

Code indicating sender's request for an interchange acknowledgment

0
No Interchange Acknowledgment Requested
1
Interchange Acknowledgment Requested (TA1)
ISA-15
I14
Interchange Usage Indicator
Required
Identifier (ID)
Min 1Max 1

Code indicating whether data enclosed by this interchange envelope is test, production or information

I
Information
P
Production Data
T
Test Data
ISA-16
I15
Component Element Separator
Required
String (AN)
Min 1Max 1

Type is not applicable; the component element separator is a delimiter and not a data element; this field provides the delimiter used to separate component data elements within a composite data structure; this value must be different than the data element separator and the segment terminator

>
Component Element Separator
GS

Functional Group Header

RequiredMax use 1

To indicate the beginning of a functional group and to provide control information

Example
GS-01
479
Functional Identifier Code
Required
Identifier (ID)

Code identifying a group of application related transaction sets

RA
Payment Order/Remittance Advice (820)
GS-02
142
Application Sender's Code
Required
String (AN)
Min 2Max 15

Code identifying party sending transmission; codes agreed to by trading partners

GS-03
124
Application Receiver's Code
Required
String (AN)
Min 2Max 15

Code identifying party receiving transmission; codes agreed to by trading partners

GS-04
373
Date
Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year

GS-05
337
Time
Required
Time (TM)
HHMM, HHMMSS, HHMMSSD, or HHMMSSDD format

Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)

GS-06
28
Group Control Number
Required
Numeric (N0)
Min 1Max 9

Assigned number originated and maintained by the sender

GS-07
455
Responsible Agency Code
Required
Identifier (ID)
Min 1Max 2

Code identifying the issuer of the standard; this code is used in conjunction with Data Element 480

T
Transportation Data Coordinating Committee (TDCC)
X
Accredited Standards Committee X12
GS-08
480
Version / Release / Industry Identifier Code
Required
String (AN)

Code indicating the version, release, subrelease, and industry identifier of the EDI standard being used, including the GS and GE segments; if code in DE455 in GS segment is X, then in DE 480 positions 1-3 are the version number; positions 4-6 are the release and subrelease, level of the version; and positions 7-12 are the industry or trade association identifiers (optionally assigned by user); if code in DE455 in GS segment is T, then other formats are allowed

005010X306

Heading

ST
0100
Heading > ST

820 Header

RequiredMax use 1

To indicate the start of a transaction set and to assign a control number

Example
ST-01
143
Transaction Set Identifier Code
Required
Identifier (ID)

Code uniquely identifying a Transaction Set

  • The transaction set identifier (ST01) is used by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set).
820
Payment Order/Remittance Advice
ST-02
329
Transaction Set Control Number
Required
Numeric (N)
Min 4Max 9

Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set

ST-03
1705
Implementation Convention Reference
Required
String (AN)

Reference assigned to identify Implementation Convention

  • The implementation convention reference (ST03) is used by the translation routines of the interchange partners to select the appropriate implementation convention to match the transaction set definition. When used, this implementation convention reference takes precedence over the implementation reference specified in the GS08.
Usage notes
  • The value in ST03 must be the same as the value in GS08.
005010X306
BPR
0200
Heading > BPR

Financial Information

RequiredMax use 1

To indicate the beginning of a Payment Order/Remittance Advice Transaction Set and total payment amount, or to enable related transfer of funds and/or information from payer to payee to occur

Usage notes
  • Use the BPR to address a single payment to a single issuer. The BPR contains mandatory information, even though this transaction is not being used to move funds electronically.
  • See section 1.10.2.3, Balancing, for information on balancing requirements.
Example
If either Depository Financial Institution (DFI) Identification Number Qualifier (BPR-12) or Receiving Depository Financial Institution (DFI) Identifier (BPR-13) is present, then the other is required
If Account Number Qualifier (BPR-14) is present, then Receiver Bank Account Number (BPR-15) is required
BPR-01
305
Transaction Handling Code
Required
Identifier (ID)

Code designating the action to be taken by all parties

I
Remittance Information Only

Indicates to the payee that the remittance detail is moving separately from the payment. This also includes when the resulting payment would be zero.

BPR-02
782
Total Payment Amount
Required
Decimal number (R)
Min 1Max 15

Monetary amount

  • BPR02 specifies the payment amount.
Usage notes
  • Use BPR02 for the total payment amount for this 820. The total payment amount for this 820 cannot exceed eleven characters, including decimals (99999999.99). Although the value can be zero, the 820 cannot be issued for less than zero dollars.
BPR-03
478
Credit or Debit Flag Code
Required
Identifier (ID)

Code indicating whether amount is a credit or debit

Usage notes
  • This indicates a credit to the payee's account, and a debit to the Payer's account.
C
Credit
BPR-04
591
Payment Method Code
Required
Identifier (ID)

Code identifying the method for the movement of payment instructions

ACH
Automated Clearing House (ACH)

Use this code to notify the issuer that an ACH transfer was requested. When this code is used, see BPR05 and BPR12 through BPR15 for additional requirements.

CHK
Check

Use this code to indicate that a check has been issued for payment.

FWT
Federal Reserve Funds/Wire Transfer - Nonrepetitive

Use this code to notify the issuer that a wire transfer was requested. When this code is used, see BPR05 through BPR15 for additional requirements.

NON
Non-Payment Data

Use this code when BPR02 equals 0 (zero) indicating no dollars are to be paid.

BPR-05
812
Payment Format Code
Optional
Identifier (ID)

Code identifying the payment format to be used

CCP
Cash Concentration/Disbursement plus Addenda (CCD+) (ACH)

Use the CCD+ format to move money. The addenda must contain a copy of the TRN segment.

BPR-12
506
Depository Financial Institution (DFI) Identification Number Qualifier
Optional
Identifier (ID)

Code identifying the type of identification number of Depository Financial Institution (DFI)

  • BPR12 and BPR13 relate to the receiving depository financial institution (RDFI).
Usage notes
  • BPR12 THROUGH BPR15 relate to the receiver's bank account.
01
ABA Transit Routing Number Including Check Digits (9 digits)

ABA is a unique number identifying every bank in the United States.

02
Swift Identification (8 or 11 characters)

See Code Source 327: Society for Worldwide Interbank Financial Telecommunication (SWIFT).

04
Canadian Bank Branch and Institution Number
BPR-13
507
Receiving Depository Financial Institution (DFI) Identifier
Optional
String (AN)
Min 3Max 12

Depository Financial Institution (DFI) identification number

Usage notes
  • This is the identifying number of the Receiving Depository Financial Institution receiving the transaction into the ACH network.
BPR-14
569
Account Number Qualifier
Optional
Identifier (ID)

Code indicating the type of account

  • BPR14 is a code identifying the type of bank account or other financial asset.
Usage notes
  • BPR14 identifies the type of account in BPR15.
DA
Demand Deposit
SG
Savings
BPR-15
508
Receiver Bank Account Number
Optional
String (AN)
Min 1Max 35

Account number assigned

  • BPR15 is the account number of the receiving company to be debited or credited with the payment order.
Usage notes
  • This is the premium receiver's bank account at the Receiving Depository Financial Institution.
BPR-16
373
Check Issue or EFT Effective Date
Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year

  • BPR16 is the date the originating company intends for the transaction to be settled (i.e., Payment Effective Date).
Usage notes
  • For check payment, this data element specifies the check issuance date.
  • For payments other than check this data element specifies the date the originator (premium payer) intends to provide funds to the receiver (premium receiver).
  • When the remittance detail contained in this transaction results in a Total Payment Amount (BPR02) of $0.00, the date reported here must equal the date the remittance was created.
TRN
0350
Heading > TRN

Reassociation Trace Number

RequiredMax use 1

To uniquely identify a transaction to an application

Usage notes
  • The purpose of this segment is to uniquely identify this transaction set and aid in reassociating payment and remittance data that have been separated. See section 1.10.2.4 for more information.
Example
TRN-01
481
Trace Type Code
Required
Identifier (ID)

Code identifying which transaction is being referenced

3
Financial Reassociation Trace Number

The payment and remittance information have been separated and need to be reassociated by the receiver.

TRN-02
127
Check or EFT Trace Number
Required
String (AN)
Min 1Max 50

Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

  • TRN02 provides unique identification for the transaction.
Usage notes
  • This number must be unique within the sender/receiver relationship. The number is assigned by the sender.
    If payment is made by check, this must be the check number.
    If payment is made by EFT, this is the payer assigned reference number for this payment, to be passed through the EFT clearing system to the payment receiver (This is NOT the ACH Trace number assigned by the originating depository financial institution).
    If this is a non-payment 820, this must be a unique remittance advice identification number.
  • This field is used to reassociate the payment and remittance information.
REF
0500
Heading > REF

Exchange Assigned Qualified Health Plan Identifier

OptionalMax use 1

To specify identifying information

Usage notes
  • Required when an exchange assigned QHP identifier was provided in the 834 enrollment transaction and all enrollees within this transaction apply to a single QHP. If not required by this implementation guide, do not send.
Example
Variants (all may be used)
REFIssuer Assigned Qualified Health Plan IdentifierREFExchange Assigned Employer Group IdentifierREFIssuer Assigned Employer Group Identifier
REF-01
128
Reference Identification Qualifier
Required
Identifier (ID)

Code qualifying the Reference Identification

38
Master Policy Number
REF-02
127
Exchange Assigned Qualified Health Plan Identifier
Required
String (AN)
Min 1Max 50

Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

REF
0500
Heading > REF

Issuer Assigned Qualified Health Plan Identifier

OptionalMax use 1

To specify identifying information

Usage notes
  • Required when all enrollees within this transaction apply to a single QHP and the Issuer Assigned QHP Identifier is known to the submitter. If not required by this implementation guide, do not send.
Example
REF-01
128
Reference Identification Qualifier
Required
Identifier (ID)

Code qualifying the Reference Identification

TV
Line of Business
REF-02
127
Issuer Assigned Qualified Health Plan Identifier
Required
String (AN)
Min 1Max 50

Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

REF
0500
Heading > REF

Exchange Assigned Employer Group Identifier

OptionalMax use 1

To specify identifying information

Usage notes
  • Required when an exchange assigned employer group identifier was provided in the 834 enrollment transaction and all enrollees within this transaction apply to a single employer group. If not required by this implementation guide, do not send.
Example
REF-01
128
Reference Identification Qualifier
Required
Identifier (ID)

Code qualifying the Reference Identification

18
Plan Number
REF-02
127
Exchange Assigned Employer Group Identifier
Required
String (AN)
Min 1Max 50

Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

REF
0500
Heading > REF

Issuer Assigned Employer Group Identifier

OptionalMax use 1

To specify identifying information

Usage notes
  • Required when:

all enrollees within this transaction apply to a single employer group,
the issuer has assigned an identifier to that employer group,
and the identifier is known to the submitter.

If not required by this implementation guide, do not send.

Example
REF-01
128
Reference Identification Qualifier
Required
Identifier (ID)

Code qualifying the Reference Identification

1L
Group or Policy Number
REF-02
127
Issuer Assigned Employer Group Identifier
Required
String (AN)
Min 1Max 50

Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

1000A Payee Name Loop
RequiredMax 1
Variants (all may be used)
Payer's Name Loop
N1
0700
Heading > Payee Name Loop > N1

Payee Name

RequiredMax use 1

To identify a party by type of organization, name, and code

Example
N1-01
98
Entity Identifier Code
Required
Identifier (ID)

Code identifying an organizational entity, a physical location, property or an individual

PE
Payee
N1-02
93
Payee Organization Name
Required
String (AN)
Min 1Max 60

Free-form name

N1-03
66
Identification Code Qualifier
Required
Identifier (ID)

Code designating the system/method of code structure used for Identification Code (67)

FI
Federal Taxpayer's Identification Number
N1-04
67
Payee's Tax Identification Number
Required
String (AN)
Min 2Max 80

Code identifying a party or other code

  • This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.
REF
1100
Heading > Payee Name Loop > REF

Unique Health Plan Identifier

OptionalMax use 1

To specify identifying information

Usage notes
  • Required when the Payee has obtained a Unique Health Plan Identifier and that identifier is known to the submitter. If not required by this implementation guide, do not send.
Example
REF-01
128
Reference Identification Qualifier
Required
Identifier (ID)

Code qualifying the Reference Identification

ABY
Centers for Medicare and Medicaid Services PlanID
REF-02
127
Unique Health Plan Identifier
Required
String (AN)
Min 1Max 50

Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

1000A Payee Name Loop end
1000B Payer's Name Loop
RequiredMax 1
Variants (all may be used)
Payee Name Loop
N1
0700
Heading > Payer's Name Loop > N1

Payer's Name

RequiredMax use 1

To identify a party by type of organization, name, and code

Usage notes
  • The "payer" in the context of this transaction is not the health plan. The payer is the entity making payment to the plan. This will be either a government entity (HHS, IRS, etc) or a Health Insurance Exchange.
Example
N1-01
98
Entity Identifier Code
Required
Identifier (ID)

Code identifying an organizational entity, a physical location, property or an individual

RM
Party that remits payment
N1-02
93
Payer Name
Required
String (AN)
Min 1Max 60

Free-form name

N1-03
66
Identification Code Qualifier
Required
Identifier (ID)

Code designating the system/method of code structure used for Identification Code (67)

58
Originating Company Number
N1-04
67
Payer Identifier
Required
String (AN)
Min 2Max 80

Code identifying a party or other code

  • This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.
Usage notes
  • The identifier reported here identifies the government agency or Health Insurance Exchange making the payment. Its value is established by trading partner agreement.
PER
1200
Heading > Payer's Name Loop > PER

Payer's Administrative Contact Information

OptionalMax use >1

To identify a person or office to whom administrative communications should be directed

Usage notes
  • Required when specified by the terms of the trading partner agreement. If not required by this implementation guide, do not send.
  • When the communication number represents a telephone number in the United States and other countries using the North American Dialing Plan (for voice, data, fax, etc.), the communication number must always include the area code and phone number using the format AAABBBCCCC, where AAA is the area code, BBB is the telephone number prefix, and CCCC is the telephone number. For example, (534)224-2525 would be represented as 5342242525.
Example
If either Communication Number Qualifier (PER-05) or Communication Number (PER-06) is present, then the other is required
If either Communication Number Qualifier (PER-07) or Communication Number (PER-08) is present, then the other is required
PER-01
366
Contact Function Code
Required
Identifier (ID)

Code identifying the major duty or responsibility of the person or group named

IC
Information Contact
PER-02
93
Premium Payer Contact Name
Required
String (AN)
Min 1Max 60

Free-form name

PER-03
365
Communication Number Qualifier
Required
Identifier (ID)

Code identifying the type of communication number

EM
Electronic Mail
FX
Facsimile
TE
Telephone
PER-04
364
Communication Number
Required
String (AN)
Min 1Max 256

Complete communications number including country or area code when applicable

PER-05
365
Communication Number Qualifier
Optional
Identifier (ID)

Code identifying the type of communication number

EM
Electronic Mail
EX
Telephone Extension

When used, the value following this code is the extension for the preceding communications contact number.

FX
Facsimile
TE
Telephone
PER-06
364
Communication Number
Optional
String (AN)
Min 1Max 256

Complete communications number including country or area code when applicable

PER-07
365
Communication Number Qualifier
Optional
Identifier (ID)

Code identifying the type of communication number

EM
Electronic Mail
EX
Telephone Extension

When used, the value following this code is the extension for the preceding communications contact number.

FX
Facsimile
TE
Telephone
PER-08
364
Communication Number
Optional
String (AN)
Min 1Max 256

Complete communications number including country or area code when applicable

1000B Payer's Name Loop end
Heading end

Detail

2000 Remittance Information Loop
RequiredMax >1
ENT
0100
Detail > Remittance Information Loop > ENT

Remittance Information

RequiredMax use 1

To designate the entities which are parties to a transaction and specify a reference meaningful to those entities

Usage notes
  • Each iteration of the ENT loop represents an identifiable detail payment and or adjustment(s). The detail payment or adjustment may be specific to an individual or represent an aggregate to the issuer.;Examples of individual specific detail payments include: premium payments, advance tax credit payments, advance cost share payments, etc.

Examples of detail payments or adjustments that are not individual include: risk adjustments, reinsurance, tax liens, etc.

When reporting a detail payment or adjustment that is not specific to an individual, Loop ID 2100 (Individual Name) is not used.

Example
ENT-01
554
Assigned Number
Required
Numeric (N0)
Min 1Max 6

Number assigned for differentiation within a transaction set

Usage notes
  • The first ENT01 within each ST-SE envelope must begin with "1", and be incremented by one each time an ENT is used in the transaction.
2100 Individual Name Loop
OptionalMax 1
NM1
0200
Detail > Remittance Information Loop > Individual Name Loop > NM1

Individual Name

RequiredMax use 1

To supply the full name of an individual or organizational entity

Usage notes
  • Required when the payment and/or adjustment amounts within this iteration of Loop ID 2000 are attributed to a specific individual. If not required by this implementation guide, do not send.
Example
NM1-01
98
Entity Identifier Code
Required
Identifier (ID)

Code identifying an organizational entity, a physical location, property or an individual

IL
Insured or Subscriber
NM1-02
1065
Entity Type Qualifier
Required
Identifier (ID)

Code qualifying the type of entity

  • NM102 qualifies NM103.
1
Person
NM1-03
1035
Individual Last Name
Optional
String (AN)
Min 1Max 60

Individual last name or organizational name

NM1-04
1036
Individual First Name
Optional
String (AN)
Min 1Max 35

Individual first name

NM1-05
1037
Individual Middle Name
Optional
String (AN)
Min 1Max 25

Individual middle name or initial

NM1-06
1038
Individual Name Prefix
Optional
String (AN)
Min 1Max 10

Prefix to individual name

NM1-07
1039
Individual Name Suffix
Optional
String (AN)
Min 1Max 10

Suffix to individual name

NM1-08
66
Identification Code Qualifier
Required
Identifier (ID)

Code designating the system/method of code structure used for Identification Code (67)

C1
Insured or Subscriber
NM1-09
67
Exchange Assigned Subscriber Identifier
Required
String (AN)
Min 2Max 80

Code identifying a party or other code

Usage notes
  • This is the subscriber's Exchange assigned identifier.
REF
0600
Detail > Remittance Information Loop > Individual Name Loop > REF

Exchange Assigned Qualified Health Plan Identifier

OptionalMax use 1

To specify identifying information

Usage notes
  • Required when the header level Exchange Assigned QHP Identifier segment is not used and an exchange assigned QHP identifier was provided to the issuer in the 834. If not required by this implementation guide, do not send.
Example
REF-01
128
Reference Identification Qualifier
Required
Identifier (ID)

Code qualifying the Reference Identification

38
Master Policy Number
REF-02
127
Exchange Assigned Qualified Health Plan Identifier
Required
String (AN)
Min 1Max 50

Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

REF
0600
Detail > Remittance Information Loop > Individual Name Loop > REF

Issuer Assigned Qualified Health Plan Identifier

OptionalMax use 1

To specify identifying information

Usage notes
  • Required when the Issuer Assigned QHP segment in the header is not used, and the Issuer Assigned QHP Identifier is known by the submitter.

If not required by this implementation guide, do not send.

Example
REF-01
128
Reference Identification Qualifier
Required
Identifier (ID)

Code qualifying the Reference Identification

TV
Line of Business
REF-02
127
Issuer Assigned Qualified Health Plan Identifier
Required
String (AN)
Min 1Max 50

Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

REF
0600
Detail > Remittance Information Loop > Individual Name Loop > REF

Exchange Assigned Employer Group Identifier

OptionalMax use 1

To specify identifying information

Usage notes
  • Required when the enrollment is from a SHOP exchange and the header exchange assigned employer group segment is not used. If not required by this implementation guide, do not send.
Example
REF-01
128
Reference Identification Qualifier
Required
Identifier (ID)

Code qualifying the Reference Identification

18
Plan Number
REF-02
127
Exchange Assigned Employer Group Identifier
Required
String (AN)
Min 1Max 50

Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

REF
0600
Detail > Remittance Information Loop > Individual Name Loop > REF

Issuer Assigned Employer Group Identifier

OptionalMax use 1

To specify identifying information

Usage notes
  • Required when:

the enrollment is from a SHOP exchange,
the header issuer assigned employer group segment is not used,
the issuer has assigned an identifier to that employer group,
and the identifier is known to the submitter.

If not required by this implementation guide, do not send.

Example
REF-01
128
Reference Identification Qualifier
Required
Identifier (ID)

Code qualifying the Reference Identification

1L
Group or Policy Number
REF-02
127
Issuer Assigned Employer Group Identifier
Required
String (AN)
Min 1Max 50

Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

REF
0600
Detail > Remittance Information Loop > Individual Name Loop > REF

Exchange Assigned Policy Identifier

RequiredMax use 1

To specify identifying information

Usage notes
  • For the purposes of this implementation, policy is defined as the collective of enrollees constituting a family unit or household.
Example
REF-01
128
Reference Identification Qualifier
Required
Identifier (ID)

Code qualifying the Reference Identification

POL
Policy Number
REF-02
127
Exchange Assigned Policy Identifier
Required
String (AN)
Min 1Max 50

Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

REF-01
128
Reference Identification Qualifier
Required
Identifier (ID)

Code qualifying the Reference Identification

AZ
Health Insurance Policy Number
REF-02
127
Issuer Assigned Policy Identifier
Required
String (AN)
Min 1Max 50

Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

REF
0600
Detail > Remittance Information Loop > Individual Name Loop > REF

Exchange Assigned APTC Contributor/Tax Payer Identifier

OptionalMax use 1

To specify identifying information

Usage notes
  • Required when:

an exchange has assigned an identifier to an ATPC contributor/Tax Payer, who is not the subscriber or a dependent of the policy, for which this payment is directed,
AND
the exchange/government agency manages payment information to this level of granularity,
AND
the identifier is permitted for use under applicable regulation.

If not required by this implementation guide, do not send.

Example
REF-01
128
Reference Identification Qualifier
Required
Identifier (ID)

Code qualifying the Reference Identification

4A
Personal Identification Number (PIN)
REF-02
127
Exchange Assigned APTC Contributor/Tax Payer Identifier
Required
String (AN)
Min 1Max 50

Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

REF
0600
Detail > Remittance Information Loop > Individual Name Loop > REF

Issuer Assigned APTC Contributor/Tax Payer Identifier

OptionalMax use 1

To specify identifying information

Usage notes
  • Required when:

the issuer has assigned an identifier to an ATPC contributor/Tax Payer who is not the subscriber or a dependent of the policy for which this payment is directed,
AND
that identifier has been made known to the submitter,
AND
the exchange/government agency manages payment information to this level of granularity.

If not required by this implementation guide, do not send.

Example
REF-01
128
Reference Identification Qualifier
Required
Identifier (ID)

Code qualifying the Reference Identification

23
Client Number
REF-02
127
Issuer Assigned APTC Contributor/Tax Payer Identifier
Required
String (AN)
Min 1Max 50

Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

REF
0600
Detail > Remittance Information Loop > Individual Name Loop > REF

Exchange Assigned Dependent Identifier

OptionalMax use 1

To specify identifying information

Usage notes
  • Required when the associated payment for a subscriber policy is not directly attributable to the subscriber.

If not required by this implementation guide, do not send.

  • An example of when this would be used is as follows. When dependents of a policy file taxes separately from the subscriber, it is possible they may be eligible for an Advance payment of the Premium Tax Credit (APTC) separate from, and in addition to, any APTC of which the subscriber may qualify.
Example
REF-01
128
Reference Identification Qualifier
Required
Identifier (ID)

Code qualifying the Reference Identification

6O
Cross Reference Number
REF-02
127
Exchange Assigned Dependent Identifier
Required
String (AN)
Min 1Max 50

Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

REF
0600
Detail > Remittance Information Loop > Individual Name Loop > REF

Issuer Assigned Dependent Identifier

OptionalMax use 1

To specify identifying information

Usage notes
  • An example of when this would be used is as follows. When dependents of a policy file taxes separately from the subscriber, it is possible they may be eligible for an Advance payment of the Premium Tax Credit (APTC) separate from, and in addition to, any APTC of which the subscriber may qualify.
  • Required when the associated payment for a subscriber policy is not directly attributable to the subscriber AND the issuer assigned identifier is known by the payer.

If not required by this implementation guide, do not send.

Example
REF-01
128
Reference Identification Qualifier
Required
Identifier (ID)

Code qualifying the Reference Identification

1W
Member Identification Number
REF-02
127
Issuer Assigned Dependent Identifier
Required
String (AN)
Min 1Max 50

Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

REF
0600
Detail > Remittance Information Loop > Individual Name Loop > REF

Issuer Assigned Subscriber Identifier

OptionalMax use 1

To specify identifying information

Usage notes
  • Required when the issuer assigned subscriber number is known to the payer.

If not required by this implementation guide, do not send.

Example
REF-01
128
Reference Identification Qualifier
Required
Identifier (ID)

Code qualifying the Reference Identification

0F
Subscriber Number
REF-02
127
Issuer Assigned Subscriber Identifier
Required
String (AN)
Min 1Max 50

Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

2100 Individual Name Loop end
2300 Remittance Detail Loop
RequiredMax >1
RMR
1500
Detail > Remittance Information Loop > Remittance Detail Loop > RMR

Remittance Detail

RequiredMax use 1

To specify the accounts receivable open item(s) to be included in the cash application and to convey the appropriate detail

Usage notes
  • Relays detailed health insurance exchange-related remittance information.
Example
RMR-01
128
Reference Identification Qualifier
Required
Identifier (ID)

Code qualifying the Reference Identification

  • Parties using this segment should agree on the content of RMR01 and RMR02 prior to initiating communication.
ZZ
Mutually Defined

Exchange-Payment Type

RMR-02
127
Exchange Payment Type
Required
String (AN)
Min 1Max 50

Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

Usage notes
  • This code identifies the type or purpose for the payment amount identified in RMR04.

Codification and Definitions can be found on the CMS Health Insurance Exchange web site.

RMR-04
782
Payment Amount
Required
Decimal number (R)
Min 1Max 15

Monetary amount

  • RMR04 is the amount paid.
Usage notes
  • The Payment Amount must be greater than or less than zero. Zero "0" is not an acceptable value for this element.
  • This is the amount being paid on this remittance item.
REF
1700
Detail > Remittance Information Loop > Remittance Detail Loop > REF

Exchange Report Document Control Number

OptionalMax use >1

To specify identifying information

Usage notes
  • Required when the Exchange needs to provide supporting documentation pertaining to this payment.

If not required by this implementation guide, do not send.

Example
REF-01
128
Reference Identification Qualifier
Required
Identifier (ID)

Code qualifying the Reference Identification

0N
Attached To
REF-02
127
Exchange-related Report Type
Required
String (AN)
Min 1Max 50

Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

Usage notes
  • This element defines the type of report being described. Examples include Risk Adjustment Supporting Documentation, Reinsurance Supporting Documentation, etc. Codification and Definitions can be found on the CMS Health Insurance Exchange web site.
REF-03
352
Exchange Report Document Control Number
Required
String (AN)
Min 1Max 80

A free-form description to clarify the related data elements and their content

Usage notes
  • This is the Document Control Number assigned to the supplemental report which details how the payment amount reported in RMR04 was calculated.
DTM
1800
Detail > Remittance Information Loop > Remittance Detail Loop > DTM

Individual Coverage Period

RequiredMax use 1

To specify pertinent dates and times

Usage notes
  • This segment relays the start and end dates related to the payment reported in the RMR segment.
Example
DTM-01
374
Date Time Qualifier
Required
Identifier (ID)

Code specifying type of date or time, or both date and time

582
Report Period
DTM-05
1250
Date Time Period Format Qualifier
Required
Identifier (ID)

Code indicating the date format, time format, or date and time format

RD8
Range of Dates Expressed in Format CCYYMMDD-CCYYMMDD
DTM-06
1251
Coverage Period
Required
String (AN)
Min 1Max 35

Expression of a date, a time, or range of dates, times or dates and times

2300 Remittance Detail Loop end
2000 Remittance Information Loop end
Detail end

Summary

SE
0100
Summary > SE

Transaction Set Trailer

RequiredMax use 1

To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)

Example
SE-01
96
Transaction Segment Count
Required
Numeric (N0)
Min 1Max 10

Total number of segments included in a transaction set including ST and SE segments

SE-02
329
Transaction Set Control Number
Required
Numeric (N)
Min 4Max 9

Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set

Summary end
GE

Functional Group Trailer

RequiredMax use 1

To indicate the end of a functional group and to provide control information

Example
GE-01
97
Number of Transaction Sets Included
Required
Numeric (N0)
Min 1Max 6

Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element

GE-02
28
Group Control Number
Required
Numeric (N0)
Min 1Max 9

Assigned number originated and maintained by the sender

IEA

Interchange Control Trailer

RequiredMax use 1

To define the end of an interchange of zero or more functional groups and interchange-related control segments

Example
IEA-01
I16
Number of Included Functional Groups
Required
Numeric (N0)
Min 1Max 5

A count of the number of functional groups included in an interchange

IEA-02
I12
Interchange Control Number
Required
Numeric (N0)
Min 9Max 9

A control number assigned by the interchange sender

EDI Samples

Example 1: Different Types of Payment Made by the HIX

ISA*00* *00* *ZZ*SENDER *ZZ*RECEIVER *240221*1259*^*00501*000000001*0*T*>~
GS*RA*SENDERGS*RECEIVERGS*20240221*125918*000000001*X*005010X306~
ST*820*0001*005010X306~
BPR*I*220*C*ACH*CCP*******01*199999999*DA*98765*20140604~
TRN*3*78905~
REF*38*123456~
REF*TV*12565496~
N1*PE*BATA INSURANCE CO.*FI*012222222~
N1*RM*GOVERNMENT AGENCY*58*123ABC~
ENT*1~
NM1*IL*1*DOE*JOHN****C1*777222~
REF*POL*1232456~
REF*AZ*12565496~
REF*0F*555666~
RMR*ZZ*APTC**35~
DTM*582****RD8*20120501-20140531~
ENT*2~
NM1*IL*1*FIRSTONE*EMILY****C1*777333~
REF*POL*1232457~
REF*AZ*12565497~
REF*0F*555777~
RMR*ZZ*APTC**35~
DTM*582****RD8*20120501-20140531~
ENT*3~
NM1*IL*1*MIDDLEONE*JULIE****C1*777444~
REF*POL*1232458~
REF*AZ*12565498~
REF*0F*544477~
RMR*ZZ*APTC**-350~
DTM*582****RD8*20140101-20140331~
ENT*4~
NM1*IL*1*NEWONE*KELLY****C1*777111~
REF*POL*1232459~
REF*AZ*12565499~
RMR*ZZ*APTC**450~
DTM*582****RD8*20140501-20140531~
RMR*ZZ*CSR**50~
DTM*582****RD8*20140501-20140531~
SE*37*0001~
GE*1*000000001~
IEA*1*000000001~

Example 10: Debt Amount Covered by an Affiliate’s Payment — Initial (Optional)

ISA*00* *00* *ZZ*SENDER *ZZ*RECEIVER *240221*1348*^*00501*000000001*0*T*>~
GS*RA*SENDERGS*RECEIVERGS*20240221*134856*000000001*X*005010X306~
ST*820*0001*005010X306~
BPR*I*0*C*NON************20140210~
TRN*3*123456789123385~
N1*PE*NATIONAL EAST*FI*121231244~
N1*RM*CMS*58*CMS~
PER*IC*EXCHANGE OPERATIONS CENTER*EM*CMS_FEPS@cms.hhs.gov*TE*8002671515~
ENT*1~
NM1*IL*1*HOPE*AMY****C1*777339~
REF*38*12345MD000011500~
REF*POL*4599~
REF*AZ*PLAN2~
REF*0F*SUB1234~
RMR*ZZ*APTC**100~
DTM*582****RD8*20140201-20140228~
RMR*ZZ*CSR**50~
DTM*582****RD8*20140201-20140228~
RMR*ZZ*UF**-35~
DTM*582****RD8*20140201-20140228~
RMR*ZZ*APTCADJ**-450~
DTM*582****RD8*20140101-20140131~
RMR*ZZ*APTCADJ**100~
DTM*582****RD8*20140101-20140131~
ENT*2~
NM1*IL*1*RENEE*JENNIFER****C1*777335~
REF*38*12346MD000011501~
REF*POL*5678~
REF*AZ*PLAN4~
REF*0F*SUB2348~
RMR*ZZ*APTC**100~
DTM*582****RD8*20140201-20140228~
RMR*ZZ*CSR**50~
DTM*582****RD8*20140201-20140228~
RMR*ZZ*UF**-40~
DTM*582****RD8*20140201-20140228~
ENT*3~
RMR*ZZ*BAL**125~
DTM*582****RD8*20140201-20140228~
SE*38*0001~
GE*1*000000001~
IEA*1*000000001~

Example 11: Current Month Debt Amount Covered by an Affiliate’s Payment — Final

ISA*00* *00* *ZZ*SENDER *ZZ*RECEIVER *240221*1404*^*00501*000000001*0*T*>~
GS*RA*SENDERGS*RECEIVERGS*20240221*140425*000000001*X*005010X306~
ST*820*0002*005010X306~
BPR*I*0*C*NON************20140228~
TRN*3*12345678945678~
N1*PE*NATIONAL EAST*FI*121231244~
N1*RM*CMS*58*CMS~
PER*IC*EXCHANGE OPERATIONS CENTER*EM*CMS_FEPS@cms.hhs.gov*TE*8002671515~
ENT*1~
NM1*IL*1*HOPE*AMY****C1*777339~
REF*38*12345MD000011501~
REF*POL*4599~
REF*AZ*PLAN2~
REF*0F*SUB1234~
RMR*ZZ*APTC**100~
DTM*582****RD8*20140201-20140228~
RMR*ZZ*CSR**50~
DTM*582****RD8*20140201-20140228~
RMR*ZZ*UF**-35~
DTM*582****RD8*20140201-20140228~
RMR*ZZ*APTCADJ**-450~
DTM*582****RD8*20140101-20140131~
RMR*ZZ*APTCADJ**100~
DTM*582****RD8*20140101-20140131~
ENT*2~
NM1*IL*1*RENEE*JENNIFER****C1*777335~
REF*38*12346MD000011501~
REF*POL*5674~
REF*AZ*PLAN4~
REF*0F*SUB2348~
RMR*ZZ*APTC**100~
DTM*582****RD8*20140201-20140228~
RMR*ZZ*CSR**50~
DTM*582****RD8*20140201-20140228~
RMR*ZZ*UF**-40~
DTM*582****RD8*20140201-20140228~
ENT*3~
RMR*ZZ*DEBTADJ**125~
REF*0N*AFFRPT*5551202-123456789123459~
DTM*582****RD8*20140201-20140228~
SE*39*0002~
GE*1*000000001~
IEA*1*000000001~

Example 12: CSR Manual Adjustment — Optional

ISA*00* *00* *ZZ*SENDER *ZZ*RECEIVER *240221*1405*^*00501*000000001*0*T*>~
GS*RA*SENDERGS*RECEIVERGS*20240221*140549*000000001*X*005010X306~
ST*820*0001*005010X306~
BPR*I*0*C*NON************20140210~
TRN*3*123456789123456~
N1*PE*NATIONAL*FI*121231233~
N1*RM*CMS*58*CMS~
PER*IC*EXCHANGE OPERATIONS CENTER*EM*CMS_FEPS@cms.hhs.gov*TE*8002671515~
ENT*1~
NM1*IL*1*SMITH*JANE****C1*777222~
REF*38*12345MD000011221~
REF*POL*4567~
REF*AZ*PLAN1~
REF*0F*SUB123~
RMR*ZZ*APTC**100~
DTM*582****RD8*20140201-20140228~
RMR*ZZ*UF**-35~
DTM*582****RD8*20140201-20140228~
ENT*2~
NM1*IL*1*DOE*JOHN****C1*777223~
REF*38*12346MD000011232~
REF*POL*5678~
REF*AZ*PLAN2~
REF*0F*SUB234~
RMR*ZZ*APTC**100~
DTM*582****RD8*20140201-20140228~
RMR*ZZ*UF**-40~
DTM*582****RD8*20140201-20140228~
ENT*3~
RMR*ZZ*BAL**-125~
DTM*582****RD8*20140201-20140228~
SE*30*0001~
GE*1*000000001~
IEA*1*000000001~

Example 2: Payments Exceed Charges — Initial Payment (Optional)

ISA*00* *00* *ZZ*SENDER *ZZ*RECEIVER *240221*1259*^*00501*000000001*0*T*>~
GS*RA*SENDERGS*RECEIVERGS*20240221*125902*000000001*X*005010X306~
ST*820*0001*005010X306~
BPR*I*0*C*NON************20140110~
TRN*3*123456789123456~
N1*PE*NATIONAL*FI*121231233~
N1*RM*CMS*58*CMS~
PER*IC*EXCHANGE OPERATIONS CENTER*EM*CMS_FEPS@cms.hhs.gov*TE*8002671515~
ENT*1~
NM1*IL*1*SMITH*JANE****C1*777222~
REF*38*12345MD000011221~
REF*POL*4567~
REF*AZ*PLAN1~
REF*0F*SUB123~
RMR*ZZ*APTC**600~
DTM*582****RD8*20140101-20140131~
RMR*ZZ*CSR**100~
DTM*582****RD8*20140101-20140131~
RMR*ZZ*UF**-25~
DTM*582****RD8*20140101-20140131~
ENT*2~
NM1*IL*1*DOE*JOHN****C1*777223~
REF*38*12346MD000011232~
REF*POL*5678~
REF*AZ*PLAN2~
REF*0F*SUB234~
RMR*ZZ*APTC**400~
DTM*582****RD8*20140101-20140131~
RMR*ZZ*CSR**50~
DTM*582****RD8*20140101-20140131~
RMR*ZZ*UF**-15~
DTM*582****RD8*20140101-20140131~
ENT*3~
RMR*ZZ*BAL**-1110~
DTM*582****RD8*20140101-20140131~
SE*34*0001~
GE*1*000000001~
IEA*1*000000001~

Example 3: Payments Exceed Charges — Final Payment

ISA*00* *00* *ZZ*SENDER *ZZ*RECEIVER *240221*1331*^*00501*000000001*0*T*>~
GS*RA*SENDERGS*RECEIVERGS*20240221*133138*000000001*X*005010X306~
ST*820*0002*005010X306~
BPR*I*1110*C*ACH*CCP*******01*000000001*DA*123456772123*20140128~
TRN*3*123456789123459~
N1*PE*NATIONAL*FI*121231233~
N1*RM*CMS*58*CMS~
PER*IC*EXCHANGE OPERATIONS CENTER*EM*CMS_FEPS@cms.hhs.gov*TE*8002671515~
ENT*1~
NM1*IL*1*SMITH*JANE****C1*777222~
REF*38*12345MD000011221~
REF*POL*4567~
REF*AZ*PLAN1~
REF*0F*SUB123~
RMR*ZZ*APTC**600~
DTM*582****RD8*20140101-20140131~
RMR*ZZ*CSR**100~
DTM*582****RD8*20140101-20140131~
RMR*ZZ*UF**-25~
DTM*582****RD8*20140101-20140131~
ENT*2~
NM1*IL*1*DOE*JOHN****C1*777223~
REF*38*12346MD000011232~
REF*POL*5678~
REF*AZ*PLAN2~
REF*0F*SUB234~
RMR*ZZ*APTC**400~
DTM*582****RD8*20140101-20140131~
RMR*ZZ*CSR**50~
DTM*582****RD8*20140101-20140131~
RMR*ZZ*UF**-15~
DTM*582****RD8*20140101-20140131~
SE*31*0002~
GE*1*000000001~
IEA*1*000000001~

Example 4: Charges Exceed Payments (SHOP) — Initial Payment (Optional)

ISA*00* *00* *ZZ*SENDER *ZZ*RECEIVER *240221*1335*^*00501*000000001*0*T*>~
GS*RA*SENDERGS*RECEIVERGS*20240221*133549*000000001*X*005010X306~
ST*820*0001*005010X306~
BPR*I*0*C*NON************20140110~
TRN*3*123456789123457~
N1*PE*USINS*FI*121231234~
N1*RM*CMS*58*CMS~
PER*IC*EXCHANGE OPERATIONS CENTER*EM*CMS_FEPS@cms.hhs.gov*TE*8002671515~
ENT*1~
NM1*IL*1*SMITH*JANE****C1*777222~
REF*38*12346MD000011222~
REF*1L*987654~
REF*POL*4567~
REF*AZ*PLAN1~
REF*0F*SUB123~
RMR*ZZ*UF**-25~
DTM*582****RD8*20140101-20140131~
ENT*2~
NM1*IL*1*DOE*JOHN****C1*777223~
REF*38*12346MD000011237~
REF*1L*678910~
REF*POL*5678~
REF*AZ*PLAN2~
REF*0F*SUB234~
RMR*ZZ*UF**-15~
DTM*582****RD8*20140101-20140131~
ENT*3~
RMR*ZZ*BAL**40~
DTM*582****RD8*20140101-20140131~
SE*28*0001~
GE*1*000000001~
IEA*1*000000001~

Example 5: Charges Exceed Payments (SHOP) — Final Payment

ISA*00* *00* *ZZ*SENDER *ZZ*RECEIVER *240221*1338*^*00501*000000001*0*T*>~
GS*RA*SENDERGS*RECEIVERGS*20240221*133811*000000001*X*005010X306~
ST*820*0002*005010X306~
BPR*I*0*C*NON************20140128~
TRN*3*123456789123567~
N1*PE*USINS*FI*121231234~
N1*RM*CMS*58*CMS~
PER*IC*EXCHANGE OPERATIONS CENTER*EM*CMS_FEPS@cms.hhs.gov*TE*8002671515~
ENT*1~
NM1*IL*1*SMITH*JANE****C1*777222~
REF*38*12345MD000011222~
REF*1L*987654~
REF*POL*4567~
REF*AZ*PLAN1~
REF*0F*SUB123~
RMR*ZZ*UF**-25~
DTM*582****RD8*20140101-20140131~
ENT*2~
NM1*IL*1*DOE*JOHN****C1*777223~
REF*38*12346MD000011237~
REF*1L*678910~
REF*POL*5678~
REF*AZ*PLAN2~
REF*0F*SUB234~
RMR*ZZ*UF**-15~
DTM*582****RD8*20140101-20140131~
ENT*3~
RMR*ZZ*INVOICE**40~
DTM*582****RD8*20140101-20140131~
SE*28*0002~
GE*1*000000001~
IEA*1*000000001~

Example 6: APTC Adjustments — Initial (Optional)

ISA*00* *00* *ZZ*SENDER *ZZ*RECEIVER *240221*1342*^*00501*000000001*0*T*>~
GS*RA*SENDERGS*RECEIVERGS*20240221*134200*000000001*X*005010X306~
ST*820*0001*005010X306~
BPR*I*0*C*NON************20140210~
TRN*3*123456789123456~
N1*PE*NATIONAL*FI*121231233~
N1*RM*CMS*58*CMS~
PER*IC*EXCHANGE OPERATIONS CENTER*EM*CMS_FEPS@cms.hhs.gov*TE*8002671515~
ENT*1~
NM1*IL*1*SMITH*JANE****C1*777222~
REF*38*12345MD000011221~
REF*POL*4567~
REF*AZ*PLAN1~
REF*0F*SUB123~
RMR*ZZ*APTC**500~
DTM*582****RD8*20140201-20140228~
RMR*ZZ*CSR**100~
DTM*582****RD8*20140201-20140228~
RMR*ZZ*UF**-25~
DTM*582****RD8*20140201-20140228~
RMR*ZZ*APTCADJ**-600~
DTM*582****RD8*20140101-20140131~
RMR*ZZ*APTCADJ**500~
DTM*582****RD8*20140101-20140131~
ENT*2~
NM1*IL*1*DOE*JOHN****C1*777223~
REF*38*12346MD000011232~
REF*POL*5678~
REF*AZ*PLAN2~
REF*0F*SUB234~
RMR*ZZ*APTC**400~
DTM*582****RD8*20140201-20140228~
RMR*ZZ*CSR**50~
DTM*582****RD8*20140201-20140228~
RMR*ZZ*UF**-15~
DTM*582****RD8*20140201-20140228~
ENT*3~
RMR*ZZ*BAL**-910~
DTM*582****RD8*20140201-20140228~
SE*38*0001~
GE*1*000000001~
IEA*1*000000001~

Example 7: APTC Adjustments — Final Payment

ISA*00* *00* *ZZ*SENDER *ZZ*RECEIVER *240221*1343*^*00501*000000001*0*T*>~
GS*RA*SENDERGS*RECEIVERGS*20240221*134329*000000001*X*005010X306~
ST*820*0002*005010X306~
BPR*I*910*C*ACH*CCP*******01*000000001*DA*123456772123*20140228~
TRN*3*123456789123459~
N1*PE*NATIONAL*FI*121231233~
N1*RM*CMS*58*CMS~
PER*IC*EXCHANGE OPERATIONS CENTER*EM*CMS_FEPS@cms.hhs.gov*TE*8002671515~
ENT*1~
NM1*IL*1*SMITH*JANE****C1*777222~
REF*38*12345MD000011221~
REF*POL*4567~
REF*AZ*PLAN1~
REF*0F*SUB123~
RMR*ZZ*APTC**500~
DTM*582****RD8*20140201-20140228~
RMR*ZZ*CSR**100~
DTM*582****RD8*20140201-20140228~
RMR*ZZ*UF**-25~
DTM*582****RD8*20140201-20140228~
RMR*ZZ*APTCADJ**-600~
DTM*582****RD8*20140101-20140131~
RMR*ZZ*APTCADJ**500~
DTM*582****RD8*20140101-20140131~
ENT*2~
NM1*IL*1*DOE*JOHN****C1*777223~
REF*38*12346MD000011232~
REF*POL*5678~
REF*AZ*PLAN2~
REF*0F*SUB234~
RMR*ZZ*APTC**400~
DTM*582****RD8*20140201-20140228~
RMR*ZZ*CSR**50~
DTM*582****RD8*20140201-20140228~
RMR*ZZ*UF**-15~
DTM*582****RD8*20140201-20140228~
SE*35*0002~
GE*1*000000001~
IEA*1*000000001~

Example 8: Outstanding Debt Owed by the Payee or their Affiliates — Initial (Optional)

ISA*00* *00* *ZZ*SENDER *ZZ*RECEIVER *240221*1345*^*00501*000000001*0*T*>~
GS*RA*SENDERGS*RECEIVERGS*20240221*134520*000000001*X*005010X306~
ST*820*0001*005010X306~
BPR*I*0*C*NON************20140210~
TRN*3*1234512345098~
N1*PE*NATIONAL*FI*121231233~
N1*RM*CMS*58*CMS~
PER*IC*EXCHANGE OPERATIONS CENTER*EM*CMS_FEPS@cms.hhs.gov*TE*8002671515~
ENT*1~
NM1*IL*1*SMITH*JANE****C1*777222~
REF*38*12345MD000011221~
REF*POL*4567~
REF*AZ*PLAN1~
REF*0F*SUB123~
RMR*ZZ*APTC**600~
DTM*582****RD8*20140201-20140228~
RMR*ZZ*CSR**100~
DTM*582****RD8*20140201-20140228~
RMR*ZZ*UF**-25~
DTM*582****RD8*20140201-20140228~
ENT*2~
NM1*IL*1*DOE*JOHN****C1*777223~
REF*38*12346MD000011232~
REF*POL*5678~
REF*AZ*PLAN2~
REF*0F*SUB234~
RMR*ZZ*APTC**400~
DTM*582****RD8*20140201-20140228~
RMR*ZZ*CSR**50~
DTM*582****RD8*20140201-20140228~
RMR*ZZ*UF**-1~
DTM*582****RD8*20140201-20140228~
ENT*3~
RMR*ZZ*BAL**-1100~
DTM*582****RD8*20140201-20140228~
SE*34*0001~
GE*1*000000001~
IEA*1*000000001~

Example 9: Outstanding Debt Owed by the Payee or their Affiliates — Final Payment

ISA*00* *00* *ZZ*SENDER *ZZ*RECEIVER *240221*1347*^*00501*000000001*0*T*>~
GS*RA*SENDERGS*RECEIVERGS*20240221*134721*000000001*X*005010X306~
ST*820*0002*005010X306~
BPR*I*985*C*ACH*CCP*******01*000000001*DA*123456772123*20140228~
TRN*3*123456789123459~
N1*PE*NATIONAL*FI*121231233~
N1*RM*CMS*58*CMS~
PER*IC*EXCHANGE OPERATIONS CENTER*EM*CMS_FEPS@cms.hhs.gov*TE*8002671515~
ENT*1~
NM1*IL*1*SMITH*JANE****C1*777222~
REF*38*12345MD000011221~
REF*POL*4567~
REF*AZ*PLAN1~
REF*0F*SUB123~
RMR*ZZ*APTC**600~
DTM*582****RD8*20140101-20140131~
RMR*ZZ*CSR**100~
DTM*582****RD8*20140201-20140228~
RMR*ZZ*UF**-25~
DTM*582****RD8*20140201-20140228~
ENT*2~
NM1*IL*1*DOE*JOHN****C1*777223~
REF*38*12346MD000011232~
REF*POL*5678~
REF*AZ*PLAN2~
REF*0F*SUB234~
RMR*ZZ*APTC**400~
DTM*582****RD8*20140201-20140228~
RMR*ZZ*CSR**50~
DTM*582****RD8*20140201-20140228~
RMR*ZZ*UF**-15~
DTM*582****RD8*20140201-20140228~
ENT*3~
RMR*ZZ*REDUCED**-125~
REF*0N*AFFRPT*5551201-12345678945678~
DTM*582****RD8*20140201-20140228~
SE*35*0002~
GE*1*000000001~
IEA*1*000000001~

Stedi is a registered trademark of Stedi, Inc. All names, logos, and brands of third parties listed on this page are trademarks of their respective owners (including “X12”, which is a trademark of X12 Incorporated). Stedi, Inc. and its products and services are not endorsed by, sponsored by, or affiliated with these third parties. Use of these names, logos, and brands is for identification purposes only, and does not imply any such endorsement, sponsorship, or affiliation.