Tracelink University ## Breadcrumb 1. [Home](/) 2. [Resources](/resources/resource-center) 3. [TraceLink University](/resources/tracelink-university) # Remittance advice (X12) - [Download PDF](/node/29691/pdf) - [Share](#) - [ LinkedIn ](https://www.linkedin.com/shareArticle?mini=true&url=https://www.tracelink.com/resources/tracelink-university/remittance-advice-x12&title=Remittance advice (X12)&summary=Buyers use remittance advices to notify suppliers of payment confirmation and details for one or more invoices. &source=TraceLink "LinkedIn") - [ Facebook ](https://www.facebook.com/share.php?u=https://www.tracelink.com/resources/tracelink-university/remittance-advice-x12&t=Remittance advice (X12) "Facebook") - [ Mail ](mailto:?subject=Remittance advice (X12)+|+TraceLink&body=https://www.tracelink.com/resources/tracelink-university/remittance-advice-x12 "Mail") - [ Twitter ](https://twitter.com/intent/tweet?text=Remittance advice (X12) https://www.tracelink.com/resources/tracelink-university/remittance-advice-x12&via=TraceLink "Twitter") #### Table of contents Buyers use remittance advices to notify suppliers of payment confirmation and details for one or more invoices. ![](/sites/default/files/tech_comms/mpl/Content/Resources/Images/global_images/note_tip_24x24.png) Contact your TraceLink Services representative for more information about integrating with this message. - **Message Type**: MPC\_REMITTANCE\_ADVICE (Remittance Advice) - **X12 Format**: 820 - **Transform Name:** B2B\_EDI\_X12\_820\_RemittanceAdvice\_IB\_V2 - **Direction**: Inbound to TraceLink [![Closed](/sites/default/files/tech_comms/mpl/Skins/Default/Stylesheets/Images/transparent.gif)Guidelines](#) Input Element Occurs Length Description Examplet ISA \[1…1\] – ISA interchange envelope. – ISA01 \[1…1\] 2/2 Qualifier for authorization control number in ISA02. 00 ISA02 \[1…1\] 10/10 Information used for additional identification or authorization of the interchange sender or the data in the interchange/ 10 spaces a valid entry. – ISA03 \[1…1\] 2/2 Qualifier for security information in ISA04. 00 ISA04 \[1…1\] 10/10 Identifies security information about the interchange sender or data – ISA05 \[1…1\] 2/2 Interchange sender partner ID qualifier. 07 ISA06 \[1…1\] 15/15 Interchange sender identification mapping to fileSenderNumber with party type defined in ISA05. 7777776067344 ISA07 \[1…1\] 2/2 Interchange receiver partner ID qualifier. 01 ISA08 \[1…1\] 15/15 Instance 1 EDI receiver ID mapping to file control header and to ServiceLinkId. 888888404358877 ISA09 \[1…1\] 6/6 Interchange date in 6 char YYMMDD format 231020 ISA10 \[1…1\] 4/4 Interchange time in 4 char HHMM format 1420 ISA11 \[1…1\] 1/1 This value is dependent on X12 version. - `Version 4012 and earlier` – Interchange control standards identifier. The valid value is `U`. - `Version 004020 and later` – Repetition separator, a delimiter that separates repeated occurrences of a data element or composite data structure, which must be different from the data element separator, component separator, and segment terminator. ^ ISA12 \[1…1\] 5/5 Interchange control version number. This could be any X12 version. 00501 ISA13 \[1…1\] 9/9 Interchange Control Number mapping to file control header 0000000000619827 ISA14 \[1…1\] 1/1 Interchange level acknowledgement requested. Valid values: - `0` - No acknowledgment requested. - `1` - Interchange level acknowledgment requested. 0 ISA15 \[1…1\] 1/1 Indicates whether the interchange is for production, test, or information purposes. Valid values: - `I` - Information. - `P` - Production data. - `T` - Test data. P ISA16 \[1…1\] 1/1 Component element separator. Delimiter that separates data elements within a composite data structure. Must be different than the data element separator and segment terminator > GS \[1…\*\] – GS group functional envelope. Child of ISA. Only one GS group expected per interchange. – GS01 \[1…1\] 2/2 GS group function code. The valid value is `RA` - Payment Order/Remittance Advice X12 820. RA GS02 \[1…1\] 2/15 Application sender's code. 2222224043588 GS03 \[1…1\] 2/15 Application receiver's code. TRACELINK GS04 \[1…1\] 8/8 Current date stamp in 8 char X12 date format YYYYMMDD. 20301020 GS05 \[1…1\] 4/8 Current time stamp in 6 char X12 time format HHMMSS. 142000 GS06 \[1…1\] 1/9 Group control ID number. 619827 GS07 \[1…1\] 1/2 Responsible Agency Code. Valid values: - `T` – Transportation data coordinating committee (TDCC). - `X` – X12 accredited standards committee. X GS08 \[1…1\] 1/12 X12 message version code. This could be any X12 version. 005010 ST \[1…\*\] – ST transaction set envelope. Child of GS group. Only one ST transaction expected. – ST01 \[1…1\] 3/3 Transaction set identifier code. 820 ST02 \[1…1\] 4/9 Transaction set ID number. Counter for each ST segment beginning with 1. 0001 BPR \[1…1\] – Remittance advice beginning segment. Note: there is no transaction identifier in BPR. – BPR01 \[1…1\] 1/2 Transaction handling code specifying the action to be taken by all parties. Valid values: - `I` - Remittance - `D` - Payment I BPR02 \[1…1\] 1/18 Amount of payment in remittance advice. 4023567.26 BPR03 \[1…1\] 1/1 Credit or debit flag specifying the amount as a credit or debit. Valid values: - `C` - Credit - `D` - Debit C BPR04 \[1…1\] '3/3 Payment method code. Valid values: - `ACH` - Automated clearing house - `CAS` - Cash - `CCC` - Credit card - `CCH` - Bank check - `CHK` - Check - `DDP` = Direct deposit - `PBD` - Draft - `ZZZ` - Custom CHK BPR05 \[0…1\] 1/10 Payment format code identifying the payment format to be used. Pass thru mapping for X12. ARC BPR06 \[0…1\] 2/2 Depository financial institution (bank) identifier type code for the paying party. Valid values: - `01` - ABA - `02` - SWIFT - `03` - CHIPS - `04` - Canadian bank branch & institution identifier - `ZZ` - Custom SWIFT BPR07 \[0…1\] 3/12 Depository financial institution (bank) identifier value for the paying party. 002356874148 BPR08 \[0…1\] 1/3 Account identifier type for the paying party. X12 pass thru. No account type in IDoc or EDIFACT. 03 BPR09 \[0…1\] 1/35 Account identifier code for the paying party. 0025841269 BPR10 \[0…1\] 1/10 Originating company identifier code (paying party). X12 pass thru. 123456 BPR11 \[0…1\] 9/9 Originating company supplemental identifier code (paying party). X12 pass thru. – BPR12 \[0…1\] 2/2 Depository financial institution (bank) identifier type code for the receiving payee party. Valid values: - `01` - ABA - `02` - SWIFT - `03` - CHIPS - `04` - Canadian bank branch & institution identifier - `ZZ` - Custom SWIFT BPR13 \[0…1\] 3/12 Depository financial institution (bank) identifier value for the receiving payee party. 002356874148 BPR14 \[0…1\] 1/3 Account identifier type for the receiving payee party. X12 pass thru. No account type in IDoc or EDIFACT. 03 BPR15 \[0…1\] 1/35 Account identifier code for the receiving payee party. 0045872560 BPR16 \[0…1\] 8/8 Payment date mapping to canonical header in date format YYYYMMDD. 20240628 BPR17 \[0…1\] 1/3 Business function code. Pass thru mapping for X12. VEN TRN \[1…1\] – TRN trace segment recording reference document identifier for Remittance Advice – TRN01 \[1…1\] 1/2 Trace type code qualifying identifier value in TRN02. Valid values: - `1` - Current transaction trace document number. - `2` - Referenced transaction trace document number. - `3` - Financial re-association trace document number. 1 TRN02 \[1…1\] 1/80 Transaction trace reference document identification value for Remittance Advice as qualified by TRN01 mapping to canonical header.transactionReferenceIdentifierList group. Required for TL internal system processing. 002621337 TRN03 \[0…1\] 10/10 Originating -- paying -- company identifier – TRN04 \[0…1\] 1/80 Additional reference document identification value as qualified by TRN01. – CUR \[0…1\] – Currency code info for payment record in Remittance Advice. – CUR01 \[1…1\] 2/3 Entity identifier code, for an organization, physical location, property or individual for use of the currency. The valid value is `PR` - Payer currency. PR CUR02 \[1…1\] 3/3 Standard ISO currency code for the country in which the payments are specified. USD CUR03 \[0…1\] 4/10 Exchange rate value to be used as a multiplier conversion factor to convert monetary value from one currency to another – REF \[0…\*\] – REF reference segment for mapping to the check number. – REF01 \[1…1\] 2/3 Reference identification qualifier for the check number. Valid value: - `CK` - Check number. - `EM` - Electronic payment number. - `TN` - Transaction reference - `CD` - Credit memo - `14` - Master account CK REF02 \[0…1\] 1/80 Reference identifier value. 002621337 DTM \[0…\*\] – DTM date segment for mapping to the processing date – DTM01 \[1…1\] 3/3 Date type qualifier for the processing date. Valid value: - `009` - Processing date - `020` - Check date - `097` - Transaction date - `814` - Payment due date - `582` - Report date 009 DTM02 \[0…1\] 8/8 Processing date in date format YYYYMMDD 20240628 DTM03 \[0…1\] 4/8 Processing time in time format HHMMSS 123422 N1 \[0…1\] – Name segment loop for - Bill to (buyer) party. - Invoice payer party - Payment recipient payee party. – N101 \[1…1\] 2/3 Entity qualifier for the bill to party identifier and address information. Valid values: - `BT` - Bill to party - `PR` - Invoice payer party - `PE` - Payee party BT N102 \[1…1\] 1/60 Name Pharma customer N103 \[1…1\] 1/2 Identifier code qualifier. Valid values: - `01` – DUNS - `09` – DUNS+4 - `11` – Drug Enforcement Agency registration number - `21` – Health Industry Number - `91` – Company identifier - `92` – Company location identifier - `UL` – Global Location Number UL N104 \[1…1\] 2/80 Bill to party identifier as qualified by N103 mapping to companyIdentifierValue. 3333331013655 N3 \[0…1\] – N3: Address: Child of warehouse party N1 name segment. – N301 \[1…1\] 1/55 Street address 1 555 Neelan Road N302 \[0…1\] 1/55 Street address 2 Suite 123 N4 \[0…1\] – N4: Geographic Location. Child of warehouse party N1 name segment. – N401 \[1…1\] 2/30 City name Sacramento N402 \[1…1\] 2/2 State or province code. Code (Standard state/province) as defined by appropriate government agency CA N403 \[1…1\] 3/15 Postal code. Code defining international postal zone code excluding punctuation and blanks. 95833 N404 \[1…1\] 2/3 Country code US PER \[0…6\] – Contact Information. – PER01 \[1…1\] 2/2 Contact function code identifying major duty or responsibility of person or group named as contact. The valid value is `AJ` - Primary contact. AJ PER02 \[1…1\] 1/40 Name of the contact person responsible for authenticating the pedigree information. John Smith PER03 \[1…1\] 2/2 Communication Number Qualifier identifying the contact person's telephone number or email address. Valid values: - `TE` - Telephone number - `EM` - Email address TE PER04 \[1…1\] 11/20 Communication number: Telephone number of the contact person expected in this field. +1.516.747.6849 PER04 \[1…1\] 11/20 Communication number: Email address of the contact person. jsmith@manufac.com PER05 \[1…1\] 2/2 Communication Number Qualifier identifying the contact person's telephone number or email address. Valid values: - `TE` - Telephone number - `EM` - Email address EM PER06 \[1…1\] 6/50 Communication numbe: Email address for the contact person expected in this field. jsmith@manufac.com PER06 \[1…1\] 6/50 Communication number: Telephone number of the contact person. +1.516.747.6849 ENT \[0…\*\] – Entity payment loop 2000 for consolidated payments. – ENT01 \[1…1\] 1/6 Assigned number for entity. This may appear only once or it may appear more than once, depending on the requirements of the recipient. It may be hard coded to 1 or it may represent some specific identifier required by a recipient. We will map whatever we find. 1 ADX \[0…\*\] – Standalone adjustment loop. Adjustments with reason codes but without reference to an invoice. – ADX01 \[1…1\] 1/18 Monetary amount of adjustment. –25.45 ADX02 \[1…1\] 2/2 Adjustment reason code. Pass thru mapping to canonical. 02 ADX03 \[0…1\] 2/3 Reference identification qualifier. Valid values: - ` CM` - Credit memo = amount always negative - `DB` - Debit memo = amount always positive Currently only these two are supported. CM ADX04 \[0…1\] 1/80 Reference document identification value as qualified by ADX03. 2194761 NTE \[0…\*\] – Note or special instruction about the standalone adjustment in ENT-ADX loop group 2300. – NTE01 \[0…1\] 3/3 Note reference code. – NTE02 \[1…1\] 1/80 Description, free text. – REF \[0…\*\] – REF reference segment loop for standalone adjustment in ENT-ADX loop group 2300. – REF01 \[1…1\] 2/3 Reference identification qualifier for the referenced document for the standalone adjustment in the ENT-ADX loop. [![Closed](/sites/default/files/tech_comms/mpl/Skins/Default/Stylesheets/Images/transparent.gif)Valid values:](#)- `CD` – CREDITMEMO. - `DB` – DEBITMEMO - `IK` – INVOICE - `IV` – SELLERINVOICE - `OI` – ORIGINALINVOICE - `60` – CROSSREFERENCE - `CT` – CONTRACT - `DP` – DEPARTMENT. - `LT` – LOT - `LU` – LOCATION - `MC` – MICROFILM - `MR` – MERCHANDISETYPE - `PO` – PURCHASEORDER - `ST` – STORE PO REF02 \[0…1\] 1/80 Reference identifier value: check number 4500018486 DTM \[0…1\] – DTM date segment for standalone adjustment in ENT-ADX loop group 2300. – DTM01 \[1…1\] 3/3 Date type qualifier for the standalone adjustment in the ENT-ADX loop. Valid values: - `003` - Invoice date - `004` - Purchase order date - `133` - Accounts receivable date - `814` - Payment date - `999` - Document date 003 DTM02 \[0…1\] 8/8 Processing date in date format YYYYMMDD 20240628 DTM03 \[0…1\] 4/8 Processing time in time format HHMMSS. 123422 RMR \[0…\*\] – Remittance advice accounts receivable open items reference in ENT-RMR loop 2400. – RMR01 \[0…1\] 2/3 Reference identification qualifier. Valid values: - `IK` - Invoice - `CD` - Credit memo = amount always negative - `DB` - Debit memo = amount always positive One of the top 3 invoice enumerations most likely to appear in RMR01. IK RMR02 \[0…1\] 1/80 Reference document identifier as defined by RMR01. 3629621 RMR03 \[0…1\] 2/2 Payment action code. Valid values: - `PO` - Payment on account - `PI` - Payment for item - `AJ` - Adjustment - `ER` - Evaluated receipt settlement - `FL` - Final PO RMR04 \[0…1\] 1/18 Amount paid against referenced document. 12547.25 RMR05 \[0…1\] 1/18 Total amount invoiced. 12600.00 RMR06 \[0…1\] 1/18 Amount of discount 52.75 REF \[0…\*\] – REF reference segment loop for standalone adjustment in ENT-RMR loop 2400. – REF01 \[1…1\] 2/3 Reference identification qualifier for the referenced document for the standalone adjustment in the ENT-ADX loop. [![Closed](/sites/default/files/tech_comms/mpl/Skins/Default/Stylesheets/Images/transparent.gif)Valid values:](#)- `CD` – CREDITMEMO. - `DB` – DEBITMEMO - `IK` – INVOICE - `IV` – SELLERINVOICE - `OI` – ORIGINALINVOICE - `60` – CROSSREFERENCE - `CT` – CONTRACT - `DP` – DEPARTMENT. - `LT` – LOT - `LU` – LOCATION - `MC` – MICROFILM - `MR` – MERCHANDISETYPE - `PO` – PURCHASEORDER - `ST` – STORE PO REF02 \[0…1\] 1/80 Reference identifier value: check number 002621337 DTM \[0…\*\] – DTM date segment for standalone adjustment in ENT-RMR loop 2400. – DTM01 \[1…1\] 3/3 Date type qualifier for the standalone adjustment in the ENT-ADX loop. Valid values: - `003` - Invoice date - `004` - Purchase order date - `133` - Accounts receivable date - `814` - Payment date - `999` - Document date 004 DTM02 \[0…1\] 8/8 Processing date in date format YYYYMMDD 20240628 DTM03 \[0…1\] 4/8 Processing time in time format HHMMSS 123422 ADX \[0…\*\] – ADX adjustments looping group 2420 within ENT-RMR 2400 loop, referencing invoice or other document identified in RMR01 and RMR02. – ADX01 \[1…1\] 1/18 Monetary amount of adjustment. -25.45 ADX02 \[1…1\] 2/2 Adjustment reason code. Pass thru mapping to canonical. 02 ADX03 \[0…1\] 2/3 Reference identification qualifier. Valid values: - ` CM` - Credit memo = amount always negative - `DB` - Debit memo = amount always positive Currently only these two are supported. CM ADX04 \[0…1\] 1/80 Reference document identification value as qualified by ADX03. 2194761 NTE \[0…\*\] – Note or special instruction about the standalone adjustment in ENT-RMR-ADX loop group 2400. – NTE01 \[0…1\] 3/3 Note reference code. – NTE02 \[1…1\] 1/80 Description, free text – REF \[0…\*\] – REF reference segment loop for standalone adjustment in ENT-RMR-ADX looping group 2400-2420. – REF01 \[1…1\] 2/3 Reference identification qualifier for the referenced document for the standalone adjustment in the ENT-ADX loop. [![Closed](/sites/default/files/tech_comms/mpl/Skins/Default/Stylesheets/Images/transparent.gif)Valid values:](#)- `CD` – CREDITMEMO. - `DB` – DEBITMEMO - `IK` – INVOICE - `IV` – SELLERINVOICE - `OI` – ORIGINALINVOICE - `60` – CROSSREFERENCE - `CT` – CONTRACT - `DP` – DEPARTMENT. - `LT` – LOT - `LU` – LOCATION - `MC` – MICROFILM - `MR` – MERCHANDISETYPE - `PO` – PURCHASEORDER - `ST` – STORE PO REF02 \[0…1\] 1/80 Reference identifier value: check number 002621337 SE \[1…1\] – ST … SE transaction set trailer envelope. Child of GS group. Only one ST transaction expected. – SE01 \[1…1\] 1/10 Total count of segments in ST … SE transaction set including ST and SE segments. 10 SE02 \[1…1\] 4/9 Transaction set control number 0001 GE \[1…1\] – GS … GE functional group trailer envelope. Child of ISA interchange. Only one GS group expected. – GE01 \[1…1\] 1/6 Number of transaction sets in functional group 5 GE02 \[1…1\] 1/9 Functional group control number 619827 IEA \[1…1\] – ISA … IEA interchange control trailer envelope. Only one interchange expected per transmission. – IEA01 \[1…1\] 1/5 Number of functional groups in interchange. 1 IEA02 \[1…1\] 9/9 Interchange control number 0000000000619827 [![Closed](/sites/default/files/tech_comms/mpl/Skins/Default/Stylesheets/Images/transparent.gif)Example](#)```xml ISA*00* *00* *01*7777776067344 *01*888888404358877*240424*1511*^*00501*000619827*0*P*> GS*RA*2222224043588*TRACELINK*20240424*151112*619827*X*005010 ST*820*0001 BPR*I*4023567.26*C*CHK*ARC*01*002356874148*ANN*0025841269*1234567890*bpr126789*01*0 02356870099*03*0045872560*20240424*VEN TRN*1*002621337*8965432712*Additional reference document identification value as qualified by TRN01 CUR*PR*USD*4011 REF*CK*s44 DTM*020*20240421*161114 N1*BT*BT Pharma Customer*1*3333331013655 N3*555 Neelan Road*Suite123 N4*Sacramento*CA*95833*US PER*AJ*John Smith*TE*+1.516.747.6849*EM*jsmith@manufac.com N1*PR*PR Wholesale Inc*1*3333331013666 N3*556 Neelan Road*Suite456 N4*Sacramento*CA*95844*US PER*AJ*Derek Smith*EM*derek@abc.com*TE*12344567890 N1*PE*PE Pharma supplier*1*8568745 N3*557 Neelam Road*Suite789 N4*Sacramento*CA*95855*US PER*AJ*RemitTo*EM*remitto@email.com*TE*1-444-444-4444 ENT*90 ADX*-91.06*02*CM*2194761 NTE*AAA*Description, free text No 1 REF*PO*4500018486 DTM*003*20240524*154112 RMR*OI*3629621*PO*12547.25*12600.00*52.75 REF*6O*002621337 REF*LT*002621338 DTM*004*20240628*151112 SE*29*0001 GE*5*619827 IEA*1*000619827 ``` ![](/sites/default/files/tech_comms/mpl/Content/Resources/Images/global_images/note_tip_24x24.png) Review TraceLink's [API: Terms of Use](https://www.tracelink.com/legal-and-trust/api-terms-of-use) #### Table of contents ##### Related Content [ ![Related content](https://www.tracelink.com/sites/default/files/2024-09/cloud.svg) ](/resources/tracelink-university/forecast-plan-idoc) ##### Forecast plan (IDoc) Forecasting APIs allow companies to exchange data about anticipated product demand and supply availability with upstream supply chain Partners without giving these Partners access to their serialization system of record. [View More](/resources/tracelink-university/forecast-plan-idoc) [ ![Related content](https://www.tracelink.com/sites/default/files/2024-09/cloud.svg) ](/resources/tracelink-university/forecast-plan-x12) ##### Forecast plan (X12) Forecasting APIs allow companies to exchange data about anticipated product demand and supply availability with upstream supply chain Partners without giving these Partners access to their serialization system of record. [View More](/resources/tracelink-university/forecast-plan-x12) [ ![Related content](https://www.tracelink.com/sites/default/files/2024-09/cloud.svg) ](/resources/tracelink-university/forecast-plan-response-idoc) ##### Forecast plan response (IDoc) Forecasting APIs allow companies to exchange data about anticipated product demand and supply availability with downstream supply chain Partners without giving these Partners access to their serialization system of record. [View More](/resources/tracelink-university/forecast-plan-response-idoc)