Transcription
ANSI X12820 (Remittance Advice)Outbound (from Eclipse)Version 4010Eclipse 820 4010 (Vendor)110/12/2012
820Payment Order/Remittance AdviceFunctional Group RAPurpose: This Draft Standard for Trial Use contains the format and establishes the data contents of the PaymentOrder/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 andsend 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 accountsreceivable system. The remittance advice can go directly from payer to payee, through a financial institution, orthrough a third party OP ID - N1070N1090N3100N4Segment NameTransaction Set HeaderBeginning Segment forPayment Order/RemittanceAdviceCurrencyReference IdentificationDate/Time ReferenceReqMMMax Use11OOO1 1 1OOO1 11ReqMax UseO1Repeat 1NameAddress InformationGeographic LocationNotesUsageMust useMust il:PosIdSegment NameLOOP ID - ENT010ENTEntityLOOP ID - RMR150RMR Remittance AdviceAccounts Receivable OpenItem Reference180DTM Date/Time ReferenceLOOP ID - ADX210ADXAdjustment220NTENote/Special InstructionRepeat 1 1O1O 1OO1 1ReqMMax Used 1C2/210LC2/210UsedUsedSummary:Pos010IdSESegment NameTransaction Set TrailerRepeatNotesUsageMust useNotes:2/010L2/010The ENT loop is for vendor or consumer third party consolidated payments.The ENT loop is for vendor or consumer third party consolidated payments.Eclipse 820 4010 (Vendor)210/12/2012
Pos: 010Max: 1Heading - MandatoryLoop: N/AElements: 2Transaction Set HeaderSTUser Option (Usage): Must usePurpose: To indicate the start of a transaction set and to assign a control numberElement Summary:RefST01Id143Element NameTransaction Set Identifier CodeReqMTypeIDMin/Max3/3UsageMust use4/9Must useDescription: Code uniquely identifying a Transaction SetCodeList Summary (Total Codes: 298, Included: 1)CodeName820Payment Order/Remittance AdviceST02329Transaction Set Control NumberMANDescription: Identifying control number that must be unique within the transaction setfunctional group assigned by the originator for a transaction setSemantics:1. The transaction set identifier (ST01) used by the translation routines of the interchange partners to select theappropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set).Eclipse 820 4010 (Vendor)310/12/2012
Beginning Segment forPayment Order/RemittanceAdviceBPRPos: 020Max: 1Heading - MandatoryLoop: N/AElements: 5User Option (Usage): Must usePurpose: To indicate the beginning of a Payment Order/Remittance Advice Transaction Set and total paymentamount, or to enable related transfer of funds and/or information from payer to payee to occurElement Summary:RefBPR01Id305Element NameTransaction Handling CodeReqMTypeIDMin/Max1/2UsageMust useDescription: Code designating the action to be taken by all partiesCodeList Summary (Total Codes: 23, Included: 1)CodeNameIRemittance Information OnlyBPR02782Monetary AmountMR1/18Must useMID1/1Must use3/3Must useDescription: Monetary amountBPR03478Credit/Debit Flag CodeDescription: Code indicating whether amount is a credit or debitCodeList Summary (Total Codes: 2, Included: 1)CodeNameDDebitBPR04591Payment Method CodeMIDDescription: Code identifying the method for the movement of payment instructionsCodeList Summary (Total Codes: 54, Included: 1)CodeNameACHAutomated Clearing House (ACH)BPR16373DateODT8/8UsedDescription: Date expressed as CCYYMMDDSyntax Rules:1.2.3.4.5.6.P0607 - If either BPR06 or BPR07 is present, then the other is required.C0809 - If BPR08 is present, then BPR09 is required.P1213 - If either BPR12 or BPR13 is present, then the other is required.C1415 - If BPR14 is present, then BPR15 is required.P1819 - If either BPR18 or BPR19 is present, then the other is required.C2021 - If BPR20 is present, then BPR21 is required.Semantics:1. BPR02 specifies the payment amount.2. 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.3. BPR06 and BPR07 relate to the originating depository financial institution (ODFI).4. BPR08 is a code identifying the type of bank account or other financial asset.5. BPR09 is the account of the company originating the payment. This account may be debited or crediteddepending on the type of payment order.6. BPR12 and BPR13 relate to the receiving depository financial institution (RDFI).Eclipse 820 4010 (Vendor)410/12/2012
7. BPR14 is a code identifying the type of bank account or other financial asset.8. BPR15 is the account number of the receiving company to be debited or credited with the payment order.9. BPR16 is the date the originating company intends for the transaction to be settled (i.e., Payment EffectiveDate).10. BPR17 is a code identifying the business reason for this payment.11. BPR18, BPR19, BPR20 and BPR21, if used, identify a third bank identification number and account to be usedfor return items only.12. BPR20 is a code identifying the type of bank account or other financial asset.Eclipse 820 4010 (Vendor)510/12/2012
Pos: 040Max: 1Heading - OptionalLoop: N/AElements: 2CurrencyCURUser Option (Usage): UsedPurpose: To specify the currency (dollars, pounds, francs, etc.) used in a transactionElement Summary:RefCUR01Id98Element NameEntity Identifier CodeReqMTypeIDMin/Max2/3UsageMust useDescription: Code identifying an organizational entity, a physical location, property or anindividualCodeList Summary (Total Codes: 1312, Included: 1)CodeNameSESelling PartyCUR02100Currency CodeMID3/3Must useDescription: Code (Standard ISO) for country in whose currency the charges are specifiedUser Note 1: 'CAD' - Canadien dollar'MXP' - Mexican peso'USD' - US dollarSyntax Rules:1.2.3.4.5.6.7.8.9.10.11.12.13.14.C0807 - If CUR08 is present, then CUR07 is required.C0907 - If CUR09 is present, then CUR07 is required.L101112 - If CUR10 is present, then at least one of CUR11 or CUR12 is required.C1110 - If CUR11 is present, then CUR10 is required.C1210 - If CUR12 is present, then CUR10 is required.L131415 - If CUR13 is present, then at least one of CUR14 or CUR15 is required.C1413 - If CUR14 is present, then CUR13 is required.C1513 - If CUR15 is present, then CUR13 is required.L161718 - If CUR16 is present, then at least one of CUR17 or CUR18 is required.C1716 - If CUR17 is present, then CUR16 is required.C1816 - If CUR18 is present, then CUR16 is required.L192021 - If CUR19 is present, then at least one of CUR20 or CUR21 is required.C2019 - If CUR20 is present, then CUR19 is required.C2119 - If CUR21 is present, then CUR19 is required.Eclipse 820 4010 (Vendor)610/12/2012
Pos: 050Max: 1Heading - OptionalLoop: N/AElements: 2Reference IdentificationREFUser Option (Usage): UsedPurpose: To specify identifying informationElement Summary:RefREF01Id128Element NameReference Identification QualifierReqMTypeIDMin/Max2/3UsageMust use1/30UsedDescription: Code qualifying the Reference IdentificationCodeList Summary (Total Codes: 1503, Included: 1)CodeNameCKCheck NumberREF02127Reference IdentificationXANDescription: Reference information as defined for a particular Transaction Set or asspecified by the Reference Identification QualifierSyntax Rules:1. R0203 - At least one of REF02 or REF03 is required.Semantics:1. REF04 contains data relating to the value cited in REF02.Eclipse 820 4010 (Vendor)710/12/2012
DTMPos: 060Max: 1Heading - OptionalLoop: N/AElements: 2Date/Time ReferenceUser Option (Usage): UsedPurpose: To specify pertinent dates and timesElement Summary:RefDTM01Id374Element NameDate/Time QualifierReqMTypeIDMin/Max3/3UsageMust useDescription: Code specifying type of date or time, or both date and timeCodeList Summary (Total Codes: 1112, Included: 1)CodeName097Transaction CreationDTM02373DateXDT8/8UsedDescription: Date expressed as CCYYMMDDSyntax Rules:1. R020305 - At least one of DTM02, DTM03 or DTM05 is required.2. C0403 - If DTM04 is present, then DTM03 is required.3. P0506 - If either DTM05 or DTM06 is present, then the other is required.Eclipse 820 4010 (Vendor)810/12/2012
Pos: 070Max: 1Heading - OptionalLoop: N1Elements: 4NameN1User Option (Usage): UsedPurpose: To identify a party by type of organization, name, and codeElement Summary:RefN101Id98Element NameEntity Identifier CodeReqMTypeIDMin/Max2/3UsageMust useDescription: Code identifying an organizational entity, a physical location, property or anindividualCodeList Summary (Total Codes: 1312, Included: 2UsedDescription: Free-form nameN10366Identification Code QualifierDescription: Code designating the system/method of code structure used for IdentificationCode (67)CodeList Summary (Total Codes: 215, Included: 1)CodeName1D-U-N-S Number, Dun & BradstreetN10467Identification CodeXAN2/80UsedDescription: Code identifying a party or other codeSyntax Rules:1. R0203 - At least one of N102 or N103 is required.2. P0304 - If either N103 or N104 is present, then the other is required.User Note 1:N3 and N4 segment are sent for N1*PR only.Eclipse 820 4010 (Vendor)910/12/2012
N3Pos: 090Max: 1Heading - OptionalLoop: N1Elements: 2Address InformationUser Option (Usage): UsedPurpose: To specify the location of the named partyElement Summary:RefN301Id166Element NameAddress InformationReqMTypeANMin/Max1/55UsageMust useOAN1/55UsedDescription: Address informationN302166Address InformationDescription: Address informationEclipse 820 4010 (Vendor)1010/12/2012
Pos: 100Max: 1Heading - OptionalLoop: N1Elements: 3Geographic LocationN4User Option (Usage): UsedPurpose: To specify the geographic place of the named partyElement Summary:RefN401Id19Element NameCity ption: Free-form text for city nameN402156State or Province CodeDescription: Code (Standard State/Province) as defined by appropriate government agencyN403116Postal CodeOID3/15UsedDescription: Code defining international postal zone code excluding punctuation and blanks(zip code for United States)Syntax Rules:1. C0605 - If N406 is present, then N405 is required.Eclipse 820 4010 (Vendor)1110/12/2012
ENTPos: 010Max: 1Detail - OptionalLoop: ENTElements: 1EntityUser Option (Usage): UsedPurpose: To designate the entities which are parties to a transaction and specify a reference meaningful to thoseentitiesElement Summary:RefENT01Id554Element NameAssigned NumberReqOTypeN0Min/Max1/6UsageUsedDescription: Number assigned for differentiation within a transaction setSyntax Rules:1. P020304 - If either ENT02, ENT03 or ENT04 are present, then the others are required.2. P050607 - If either ENT05, ENT06 or ENT07 are present, then the others are required.3. P0809 - If either ENT08 or ENT09 is present, then the other is required.Eclipse 820 4010 (Vendor)1210/12/2012
RMR Remittance AdviceAccounts Receivable OpenItem ReferencePos: 150Max: 1Detail - OptionalLoop: RMRElements: 6User Option (Usage): UsedPurpose: To specify the accounts receivable open item(s) to be included in the cash application and to convey theappropriate detailElement Summary:RefRMR01Id128Element NameReference Identification ription: Code qualifying the Reference IdentificationCodeList Summary (Total Codes: 1503, Included: 1)CodeNameIVSeller's Invoice NumberRMR02127Reference IdentificationXANDescription: Reference information as defined for a particular Transaction Set or asspecified by the Reference Identification QualifierRMR03482Payment Action CodeOID2/2UsedDescription: Code specifying the accounts receivable open item(s), if any, to be included inthe cash application.CodeList Summary (Total Codes: 9, Included: 1)CodeNamePOPayment on AccountRMR04782Monetary AmountOR1/18UsedOR1/18UsedOR1/18UsedDescription: Monetary amountUser Note 1: Payment amountRMR05782Monetary AmountDescription: Monetary amountUser Note 1: Invoice amountRMR06782Monetary AmountDescription: Monetary amountUser Note 1: Discount amountSyntax Rules:1. P0102 - If either RMR01 or RMR02 is present, then the other is required.2. P0708 - If either RMR07 or RMR08 is present, then the other is required.Semantics:1. If RMR03 is present, it specifies how the cash is to be applied.2. RMR04 is the amount paid.3. RMR05 is the amount of invoice (including charges, less allowance) before terms discount (if discount isapplicable) or debit amount or credit amount of referenced items.4. RMR06 is the amount of discount taken.5. RMR08, if present, represents an interest penalty payment, amount late interest paid, or amount anticipation.Eclipse 820 4010 (Vendor)1310/12/2012
DTMPos: 180Max: 1Detail - OptionalLoop: RMRElements: 2Date/Time ReferenceUser Option (Usage): UsedPurpose: To specify pertinent dates and timesElement Summary:RefDTM01Id374Element NameDate/Time QualifierReqMTypeIDMin/Max3/3UsageMust useDescription: Code specifying type of date or time, or both date and timeCodeList Summary (Total Codes: 1112, Included: ion: Date expressed as CCYYMMDDSyntax Rules:1. R020305 - At least one of DTM02, DTM03 or DTM05 is required.2. C0403 - If DTM04 is present, then DTM03 is required.3. P0506 - If either DTM05 or DTM06 is present, then the other is required.Eclipse 820 4010 (Vendor)1410/12/2012
Pos: 210Max: 1Detail - OptionalLoop: ADXElements: 2AdjustmentADXUser Option (Usage): UsedPurpose: To convey accounts-payable adjustment information for the purpose of cash application, including payergenerated debit/credit memosElement Summary:RefADX01Id782Element NameMonetary AmountReqMTypeRMin/Max1/18UsageMust useMID2/2Must useDescription: Monetary amountADX02426Adjustment Reason CodeDescription: Code indicating reason for debit or credit memo or adjustment to invoice, debitor credit memo, or paymentCodeList Summary (Total Codes: 370, Included: 5)CodeName01Pricing Error04Item Not Accepted - Damaged06Quantity Contested54Freight Deducted55Tax DeductedSyntax Rules:1. P0304 - If either ADX03 or ADX04 is present, then the other is required.Semantics:1. ADX01 specifies the amount of the adjustment and must be signed if negative. If negative, it reduces thepayment amount; if positive, it increases the payment amount.2. ADX02 specifies the reason for claiming the adjustment.3. ADX03 and ADX04 specify the identification of the adjustment.Eclipse 820 4010 (Vendor)1510/12/2012
NTEPos: 220Max: 1Detail - OptionalLoop: ADXElements: 2Note/Special InstructionUser Option (Usage): UsedPurpose: To transmit information in a free-form format, if necessary, for comment or special instructionElement Summary:RefNTE01Id363Element NameNote Reference CodeReqOTypeIDMin/Max3/3UsageUsedDescription: Code identifying the functional area or purpose for which the note appliesCodeList Summary (Total Codes: 241, Included: 1)CodeNameOTHOther InstructionsNTE02352DescriptionMAN1/80Must useDescription: A free-form description to clarify the related data elements and their contentEclipse 820 4010 (Vendor)1610/12/2012
Pos: 010Max: 1Summary - MandatoryLoop: N/AElements: 2Transaction Set TrailerSEUser Option (Usage): Must usePurpose: To indicate the end of the transaction set and provide the count of the transmitted segments (including thebeginning (ST) and ending (SE) segments)Element Summary:RefSE01Id96Element NameNumber of Included SegmentsReqMTypeN0Min/Max1/10UsageMust useDescription: Total number of segments included in a transaction set including ST and SEsegmentsSE02329Transaction Set Control NumberMAN4/9Must useDescription: Identifying control number that must be unique within the transaction setfunctional group assigned by the originator for a transaction setEclipse 820 4010 (Vendor)1710/12/2012
Eclipse 820 4010 (Vendor) 2 10/12/2012 820 Payment Order/Remittance Advice Functional Group RA This Draft Standard for Trial Use contains the format and establishes the data contents of the Payment Purpose: Order/Remittance Advice Transaction Set (820) for use within the context of an El
