820 - Payment (version 3020 and later)

This topic describes the Electronic Data Interchange (EDI) standards that Business Transaction Intelligence implements for document type 820, or payment, which confirms the amounts the buyer paid for purchases and includes other payment details.

Segment: BPR - Beginning segment for payment

Loop

Level: Heading

Usage: Must use

Semantic note:

  • If BPR04 has a value of ACH, BPR16 is the payment/settlement date.
Reference Element name Requirement Usage
BPR02 Monetary Amount Mandatory Must use
BPR16 Payment Effective Date Optional Used

Segment: TRN - Trace

Loop

Level: Heading

Usage: Optional - Used

Semantic notes:

  • If TRN01 is equal to 1, it is used to uniquely identify this transaction.
  • If TRN01 is equal to 2, it is used to reference a previous transaction.

Comment:

The TRN segment is used to uniquely identify the transaction with the application. If no TRN segment is used, the REF segment in the header is reviewed for a qualifier that indicates a trace number.

Reference Element name Requirement Usage
TRN01 Trace Type Code Mandatory Must use
TRN02 Reference Identification Mandatory Must use

Segment: REF - Reference Identification

Loop

Level: Heading

Usage: Optional - Used

Syntax notes:
  • The TRN segment is the primary location for the payment trace number. This segment is the secondary location for the payment trace number.
  • If REF01 is specified, REF02 is required.
Reference Element name Requirement Usage
REF01 Reference Identification Qualifier
  • IV - Seller's invoice number
  • CR - Customer reference #
  • IK - Invoice number
  • AI - Associated Invoices
  • I5 - Invoice Identification
  • IN - Consignee's Invoice Number
  • OI - Original Invoice Number
 Optional Used
REF02 Reference Identification Mandatory Must use

Segment: CUR - Currency

Loop

Level: Heading

Usage: Optional - Used

Comments: This segment specifies the currency that is used in this transaction.

Reference Element name Requirement Usage
CUR01 Entity Identifier Code Mandatory Must use
CUR02 Currency Code Mandatory Must use

Segment: DTM - Date/time reference

Loop

Level: Heading

Usage: Optional - Used

Syntax note:

  • One loop of the DTM segment specifies a transaction creation date for the message.

Semantic notes:

  • DTM01 equals 097.
  • DMT02 represents the transaction date for a DTM01 value of 097.
Reference Element name Requirement Usage
DTM01 Date/Time Qualifier Mandatory Must use
DTM02 Date Optional Must use

Segment: RMR - Remittance advice accounts receivable open item reference

Reference Element name Requirement Usage
RMR01 Reference Identification Qualifier
  • IV - Seller's invoice number
  • CR - Customer reference #
  • IK - Invoice number
  • AI - Associated Invoices
  • I5 - Invoice Identification
  • IN - Consignee's Invoice Number
  • OI - Original Invoice Number
 Mandatory Must use
RMR02 Reference Identification Mandatory Must use
RMR03 Payment Action Code Optional Used
RMR04 Monetary Amount Optional Used

Segment: REF - Reference identification

Reference Element name Requirement Usage
REF01 Reference Identification Qualifier
  • IV - Seller's invoice number
  • CR - Customer reference #
  • IK - Invoice number
  • AI - Associated Invoices
  • I5 - Invoice Identification
  • IN - Consignee's Invoice Number
  • OI - Original Invoice Number
 Mandatory Used
REF02 Reference Identification Mandatory Used