820 - Payment (version 3010)

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: BPS - Beginning segment for payment

Loop

Level: Heading

Usage: Must use

Semantic note:

  • If BPS12 is the effective date, BPS13 is the settlement date.
Reference Element name Requirement Usage
BPS02 totalAmount Mandatory Must use
BPS12 paymentDate Mandatory Must use
BPS13 paymentDate Optional Used

Segment: CUR - Currency

Loop

Level: Heading

Usage: Optional - Used

Comments: Either CUR02 or USD is hardcoded.

Reference Element name Requirement Usage
CUR01 Currency Identifier Code Mandatory Must use
CUR02
  • currency in Header
  • lineCurrency in LoopRMT or in Header
 Mandatory Must use

Segment: NTE - Description

Loop

Level: Heading

Usage: Optional - Used

Comment: NTE02 from header section applies to all lines as a constant.

Reference Element name Requirement Usage
NTE02 lineDescription Mandatory Must use

Segment: REF - Reference Identification

Loop

Level: Heading

Usage: Optional - Used

Reference Element name Requirement Usage
REF01 Reference Identification Mandatory Must use
REF02
  • paymentTraceNumber if REF01 = TN or EF
  • linePONumber or PONumber if REF01 = PO or VN
  • invoiceNumber if REF01 = IV, CR, IK, AI, I5, IN, or OI
  • shipNumber if REF01 = SI
 Optional Used

Segment: RMT - Remittance reference

Reference Element name Requirement Usage
RMT01 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
RMT02
  • lineInvoiceNumber if RMT01 = IV, CR, IK, AI, I5, IN, or OI
  • linePONumber if RMT01 = PO or VN
 Mandatory Must use
RMT03 lineAmoumt Optional Used