Lowe's
/
Remittance Advice
  • Specification
  • EDI Inspector
Import guide into your account
Stedi maintains this guide based on public documentation from Lowe's. Contact Lowe's for official EDI specifications. To report any errors in this guide, please contact us.
Go to Stedi Network
Lowe's logo

X12 820 Remittance Advice

X12 Release 4010

This Draft Standard for Trial Use 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
EDI sample
  • sample
View the latest version of this implementation guide as an interactive webpage
https://www.stedi.com/app/guides/view/lowes/remittance-advice/01GV5GZ8ST1GHGY8N9AZPY3JFP
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
010
Transaction Set Header
Max use 1
Required
BPR
020
Beginning Segment for Payment Order/Remittance Advice
Max use 1
Required
TRN
035
Trace
Max use 1
Required
CUR
040
Currency
Max use 1
Optional
REF
050
Reference Identification
Max use 1
Optional
DTM
060
Date/Time Reference
Max use 1
Optional
N1 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

Code to identify 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

Code to identify 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

Qualifier to designate 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

Qualifier to designate 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
YYMMDD format

Date of the interchange

ISA-10
I09
Interchange Time
Required
HHMM format

Time of the interchange

ISA-11
I10
Interchange Control Standards Identifier
Required

Code to identify the agency responsible for the control standard used by the message that is enclosed by the interchange header and trailer

U
U.S. EDI Community of ASC X12, TDCC, and UCS
ISA-12
I11
Interchange Control Version Number
Required

This version number covers the interchange control segments

00401
Draft Standards for Trial Use Approved for Publication by ASC X12 Procedures Review Board through October 1997
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 sent by the sender to request an interchange acknowledgment (TA1)

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

Code to indicate 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

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

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
CCYYMMDD format

Date expressed as CCYYMMDD

GS-05
337
Time
Required
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 used in conjunction with Data Element 480 to identify the issuer of the standard

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

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

004010
Draft Standards Approved for Publication by ASC X12 Procedures Review Board through October 1997

Heading

ST
010
Heading > ST

Transaction Set 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

Code uniquely identifying a Transaction Set

  • The transaction set identifier (ST01) 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

BPR
020
Heading > BPR

Beginning Segment for Payment Order/Remittance Advice

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

Example:

BPRI700.00CACHCCP**041111111DA2222222333333333304444444444DA55555555519980702
or
BPRI700.00CACHCCD**01111111111DA2222222223333333333014444444444DA5555555551998
0702\

Example
If either (DFI) ID Number Qualifier (BPR-06) or (DFI) Identification Number (BPR-07) is present, then the other is required
If Account Number Qualifier (BPR-08) is present, then Account Number (BPR-09) is required
If either (DFI) ID Number Qualifier (BPR-12) or (DFI) Identification Number (BPR-13) is present, then the other is required
If Account Number Qualifier (BPR-14) is present, then Account Number (BPR-15) is required
BPR-01
305
Transaction Handling Code
Required

Code designating the action to be taken by all parties

Usage notes

If vendor receives 820 directly from Lowe's the BPR01 will always contain an I.

C
Payment Accompanies Remittance Advice
D
Make Payment Only
I
Remittance Information Only
BPR-02
782
Monetary Amount
Required
Decimal number (R)
Min 1Max 15

Monetary amount

  • BPR02 specifies the payment amount.
Usage notes

Total amount of remittance.

BPR-03
478
Credit/Debit Flag Code
Required

Code indicating whether amount is a credit or debit

C
Credit
BPR-04
591
Payment Method Code
Required

Code identifying the method for the movement of payment instructions

ACH
Automated Clearing House (ACH)
DXC
ACH Demand Corporate Trade Exchange (CTX) Credit
BPR-05
812
Payment Format Code
Optional

Code identifying the payment format to be used

Usage notes

Will be used for US Payments Only.

CCD
Cash Concentration/Disbursement (CCD) (ACH)
CCP
Cash Concentration/Disbursement plus Addenda (CCD+) (ACH)
CTX
Corporate Trade Exchange (CTX) (ACH)
BPR-06
506
(DFI) ID Number Qualifier
Optional

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

  • When using this transaction set to initiate a payment, all or some of BPR06 through BPR16 may be required, depending on the conventions of the specific financial channel being used.
  • BPR06 and BPR07 relate to the originating depository financial institution (ODFI).
01
ABA Transit Routing Number Including Check Digits (9 digits)
04
Canadian Bank Branch and Institution Number
BPR-07
507
(DFI) Identification Number
Optional
String (AN)
Min 3Max 12

Depository Financial Institution (DFI) identification number

Usage notes

Originating Bank ABA Transit/Routing Number.

BPR-08
569
Account Number Qualifier
Optional

Code indicating the type of account

  • BPR08 is a code identifying the type of bank account or other financial asset.
DA
Demand Deposit
BPR-09
508
Account Number
Optional
String (AN)
Min 1Max 35

Account number assigned

  • BPR09 is the account of the company originating the payment. This account may be debited or credited depending on the type of payment order.
Usage notes

Sending account number.

BPR-10
509
Originating Company Identifier
Optional
String (AN)
Min 10Max 10

A unique identifier designating the company initiating the funds transfer instructions. The first character is one-digit ANSI identification code designation (ICD) followed by the nine-digit identification number which may be an IRS employer identification number (EIN), data universal numbering system (DUNS), or a user assigned number; the ICD for an EIN is 1, DUNS is 3, user assigned number is 9

BPR-12
506
(DFI) ID Number Qualifier
Optional

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

  • BPR12 and BPR13 relate to the receiving depository financial institution (RDFI).
01
ABA Transit Routing Number Including Check Digits (9 digits)
04
Canadian Bank Branch and Institution Number
BPR-13
507
(DFI) Identification Number
Optional
String (AN)
Min 3Max 12

Depository Financial Institution (DFI) identification number

Usage notes

Receiving bank ABA Routing/Transit ID.

BPR-14
569
Account Number Qualifier
Optional

Code indicating the type of account

  • BPR14 is a code identifying the type of bank account or other financial asset.
DA
Demand Deposit
BPR-15
508
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

Payee's account number.

BPR-16
373
Date
Optional
CCYYMMDD format

Date expressed as CCYYMMDD

  • BPR16 is the date the originating company intends for the transaction to be settled (i.e., Payment Effective Date).
Usage notes

Good Funds Date at payee's bank.

TRN
035
Heading > TRN

Trace

RequiredMax use 1

To uniquely identify a transaction to an application

  • The TRN segment is used to uniquely identify a payment order/remittance advice.
Usage notes

TRN10000201

Example
TRN-01
481
Trace Type Code
Required

Code identifying which transaction is being referenced

1
Current Transaction Trace Numbers
TRN-02
127
Reference Identification
Required
String (AN)
Min 1Max 30

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

Trace Number - Will be the same as the Lowe's Check Number.

CUR
040
Heading > CUR

Currency

OptionalMax use 1

To specify the currency (dollars, pounds, francs, etc.) used in a transaction

  • The CUR segment does not initiate a foreign exchange transaction.
Usage notes

The currency code used is the three letter ISO 4217 international standard code (USD/CAD).

Example:

CURPRUSD\

Example
CUR-01
98
Entity Identifier Code
Required

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

PR
Payer
CUR-02
100
Currency Code
Required

Code (Standard ISO) for country in whose currency the charges are specified

CAD
Canadian Dollar
USD
US Dollar
REF
050
Heading > REF

Reference Identification

OptionalMax use >1

To specify identifying information

Usage notes

Example:

REFCK0000201\

Example
REF-01
128
Reference Identification Qualifier
Required

Code qualifying the Reference Identification

CK
Check Number
REF-02
127
Reference Identification
Optional
String (AN)
Min 1Max 30

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

Usage notes

Lowe's payment number.

DTM
060
Heading > DTM

Date/Time Reference

OptionalMax use >1

To specify pertinent dates and times

Usage notes

Example:

DTM09719980702\

Example
DTM-01
374
Date/Time Qualifier
Required

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

097
Transaction Creation
DTM-02
373
Date
Optional
CCYYMMDD format

Date expressed as CCYYMMDD

Usage notes

Date payment was generated.

N1 Loop
OptionalMax >1
N1
070
Heading > N1 Loop > N1

Name

RequiredMax use 1

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

  • The N1 loop allows for name/address information for the payer and payee which would be utilized to address remittance(s) for delivery.
Usage notes

N1PEABC COMPANY
N1PRLOWE'S
N1RBEI TEST BANK
N1RI**9312345\

Example
At least one of Name (N1-02) or Identification Code Qualifier (N1-03) is required
If either Identification Code Qualifier (N1-03) or Identification Code (N1-04) is present, then the other is required
N1-01
98
Entity Identifier Code
Required

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

PE
Payee
PR
Payer
RB
Receiving Bank
RI
Remit To
N1-02
93
Name
Optional
String (AN)
Min 1Max 60

Free-form name

Usage notes

Name of entity type identified in N101.

N1-03
66
Identification Code Qualifier
Optional

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

93
Code assigned by the organization originating the transaction set
N1-04
67
Identification Code
Optional
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.
N1 Loop end
Heading end

Detail

ENT Loop
OptionalMax >1
ENT
010
Detail > ENT Loop > ENT

Entity

RequiredMax use 1

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

  • The ENT loop is for vendor or consumer third party consolidated payments.
  • ENT09 may contain the payee's accounts receivable customer number.
Usage notes

Example:

ENT*1\

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

Number assigned for differentiation within a transaction set

Usage notes

Lowe's assigned number will be 1.

NM1 Loop
OptionalMax >1
NM1
020
Detail > ENT Loop > NM1 Loop > NM1

Individual or Organizational Name

RequiredMax use 1

To supply the full name of an individual or organizational entity

  • Allowing the NM1 segment to repeat in this area allows the paying entity within a payer and the paid entity within a payee to be identified (not the payer and payee).
Usage notes

Example:
NM1AO2*ABC COMPANY\

Example
NM1-01
98
Entity Identifier Code
Required

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

AO
Account Of
NM1-02
1065
Entity Type Qualifier
Required

Code qualifying the type of entity

  • NM102 qualifies NM103.
2
Non-Person Entity
NM1-03
1035
Name Last or Organization Name
Optional
String (AN)
Min 1Max 35

Individual last name or organizational name

Usage notes

Name on receiving account.

NM1 Loop end
RMR Loop
OptionalMax >1
RMR
150
Detail > ENT Loop > RMR Loop > RMR

Remittance Advice Accounts Receivable Open Item Reference

RequiredMax use 1

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

  • Loop RMR is for open items being referenced or for payment on account.
Usage notes

Example:

RMRIV1932017*450451*1\

Example
If either Reference Identification Qualifier (RMR-01) or Reference Identification (RMR-02) is present, then the other is required
RMR-01
128
Reference Identification Qualifier
Optional

Code qualifying the Reference Identification

  • Parties using this segment should agree on the content of RMR01 and RMR02 prior to initiating communication.
IV
Seller's Invoice Number
RMR-02
127
Reference Identification
Optional
String (AN)
Min 1Max 30

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

Usage notes

Your invoice number or Lowe's debit memo number if debit is issued (DM12345). Lowe's Payables system can only handle a 10 digit invoice number. If you send more than 10 digits the invoice number will be truncated.

RMR-04
782
Monetary Amount
Optional
Decimal number (R)
Min 1Max 15

Monetary amount

  • RMR04 is the amount paid.
Usage notes

Net amount being remitted for this invoice.

RMR-05
782
Monetary Amount
Optional
Decimal number (R)
Min 1Max 15

Monetary amount

  • RMR05 is the amount of invoice (including charges, less allowance) before terms discount (if discount is applicable) or debit amount or credit amount of referenced items.
  • RMR05 may be needed by some payees to distinguish between duplicate reference numbers.
Usage notes

Total amount of invoice before any applicable discounts.

RMR-06
782
Monetary Amount
Optional
Decimal number (R)
Min 1Max 15

Monetary amount

  • RMR06 is the amount of discount taken.
Usage notes

Amount of discount being taken (RMR05-RMR06 = RMR04).

NTE
160
Detail > ENT Loop > RMR Loop > NTE

Note/Special Instruction

OptionalMax use >1

To transmit information in a free-form format, if necessary, for comment or special instruction

Usage notes

Example:

NTEZZZDESCRIPTION ADJUSTMENTS TO INVOICE

Example
NTE-01
363
Note Reference Code
Optional

Code identifying the functional area or purpose for which the note applies

ZZZ
Mutually Defined
NTE-02
352
Description
Required
String (AN)
Min 1Max 80

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

Usage notes

Description related to adjustment or deduction not referenced on original invoice.

REF
170
Detail > ENT Loop > RMR Loop > REF

Reference Identification

OptionalMax use >1

To specify identifying information

Usage notes

Example:

REFPO74949
REFVVD33097\

Example
REF-01
128
Reference Identification Qualifier
Required

Code qualifying the Reference Identification

PO
Purchase Order Number
VV
Voucher
REF-02
127
Reference Identification
Optional
String (AN)
Min 1Max 30

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

DTM
180
Detail > ENT Loop > RMR Loop > DTM

Date/Time Reference

OptionalMax use >1

To specify pertinent dates and times

Usage notes

Example:

DTM00319980602\

Example
DTM-01
374
Date/Time Qualifier
Required

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

003
Invoice
DTM-02
373
Date
Optional
CCYYMMDD format

Date expressed as CCYYMMDD

Usage notes

Invoice Date.

RMR Loop end
ENT Loop end
Detail end

Summary

SE
010
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
Number of Included Segments
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

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

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

sample

ISA*00* *00* *ZZ*SENDER *ZZ*RECEIVER *231101*0122*U*00401*000000001*0*T*>
GS*RA*SENDERGS*RECEIVERGS*20231101*012237*000000001*X*004010
ST*820*2275
BPR*I*700.00*C*ACH*CCP*04*1111111*DA*2222222*3333333333**04*444444444*DA*555555555*19980702
TRN*1*0000201
CUR*PR*USD
REF*CK*0000201
DTM*097*19980702
N1*PE*ABC COMPANY
N1*PR*LOWE'S
N1*RB*EI TEST BANK
N1*RI**93*12345
ENT*1
NM1*AO*2*ABC COMPANY
RMR*IV*1932017**450*451*1
NTE*ZZZ*DESCRIPTION ADJUSTMENTS TO INVOICE
REF*PO*74949
REF*VV*D33097
DTM*003*19980602
SE*18*2275
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.