Transcription
Instructions: Using the enclosed 820 Remittance Advice/Payment Order Mappingspecifications and the sample rawRemittance Advice SlipEDI data 820 transaction, fill in the blank paper REMITTANCE ADVICE SLIP.General InformationTotal Remittance Amount Paid:Payer’s ABA Routing # :Payer’s Demand Deposit AccountNumber:Payee’s ABA Routing #:Payee’s Demand Account Number :Date Created:Remittance Trace InformationTransaction Trace Numbers:Payer Name:Payee Name:Payer Duns #:Remittance Advice Accounts Receivable Open Item Reference: (1 of 3)Seller's Invoice Number:Invoice Date:Amount Paid:Amount Invoiced:Amount of Discount Taken :Adjustment Information:Adjustment Amount :Adjustment Reason:Remittance Advice Accounts Receivable Open Item Reference: (2 of 3)Seller's Invoice Number:Invoice Date:Amount Paid:Amount Invoiced:Amount of Discount Taken :PO #:Adjustment Information:Adjustment Amount :Adjustment Reason:Remittance Advice Accounts Receivable Open Item Reference: (3 of 3)Accounts Receivable Open Item Number:Amount Paid :
0030129TRN*1*EP10019N1*PR*JONES PLUMBING*1*807685339N1*PE*SMITH *R7*3920394930203DTM*003*20030123ADX*-8*01*TD*USED CATALOG 22319*MARKETING DEPARTMENT 45SE*16*0001This exercise is intended to demonstrate the use of Mapping Specifications and how machine-processable EDIstandard file might look on a real business document.Instructions: Using the enclosed 820 Remittance Advice/Payment Order Mapping specifications and the sample rawEDI data 820 transaction, fill in the blank paper REMITTANCE ADVICE SLIP.
Straight Through ProcessingAppendix B: STP 820 SpecificationsBPRSegPositiment:Beginning Segment for Payment Order/Remittance Adviceon:020Loop:Level: HeadingUsage: MandatoryMax Use: 1Purpose:To indicate the beginning of a Payment Order/Remittance Advice Transaction Set andtotal payment amount, or to enable related transfer of funds and/or information from payerto payee to occur1 If either BPR06 or BPR07 is present, then the other is required.Syntax Notes:2 If BPR08 is present, then BPR09 is required.3 If either BPR12 or BPR13 is present, then the other is required.4 If BPR14 is present, then BPR15 is required.Semantic Notes:1 BPR02 specifies the payment amount.2 When using this transaction set to initiate a payment, all or some of BPR06 throughBPR16 may be required, depending on the conventions of the specific financialchannel 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 bedebited or credited depending on the type of payment order.6 BPR12 and BPR13 relate to the receiving depository financial institution (RDFI).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 withthe payment order.9 BPR16 is the date the originating company intends for the transaction to be settled(i.e., Payment Effective Date).Comments:1 For security reasons, to prevent identify theft of originating account information,BPR06-09 are not recommended in the STP 234567**01*021000021*DA*182389281*20030129\Data Element SummaryDataElement NameEPN/STPImpl. UseRef.Des.Must UseBPR01305Must UseBPR02782AttributesTransaction Handling CodeM ID 1/2Code designating the action to be taken by all partiesCPayment Accompanies Remittance AdvicePayment AmtM R 1/10Maps to NACHA 6 Record 30-39 (Total Amount).Note: The NACHA amount field does not include commas or adecimal point. The rightmost two positions of the NACHAamount field represent cent values.February 2008Issue 2.4B-17
Straight Through ProcessingAppendix B: STP 820 SpecificationsDataElement NameEPN/STPImpl. UseRef.Des.Must UseBPR03478Credit/Debit Flag CodeM ID 1/1Code indicating whether amount is a credit or debitData maps to NACHA 6 record 02-03 (Transaction Code “22”)CCreditMust UseBPR04591Payment Method CodeM ID 3/3Code identifying the method for the movement of payment instructionsACHAutomated Clearing House (ACH)Must UseBPR05812Payment Format CodeO ID 1/10Code identifying the payment format to be usedMapped to NACHA 5 Record 51-53 (Standard Entry Class “CTX”)CTXCorporate Trade Exchange (CTX) (ACH)UsedBPR06506(ODFI) ID Number QualifierX ID 2/2Code identifying the type of identification number of Depository FinancialInstitution (DFI)01ABA Transit Routing Number Including Check Digits (9digits)UsedBPR07507ABA ROUTING NUMBER OriginatorX AN 9/9Depository Financial Institution (DFI) identification numberTransit ABA number of the Originator at the ODFIMapped to the first 8 positions of the ODFI field inthe NACHA 5 Record 80-87 (ODFI positions 1-8)UsedBPR08569Account Number QualifierCode indicating the type of accountThe Originators Account Type at the ODFIDADemand DepositOID 1/3UsedBPR09508Account NumberAccount number assignedOriginators Bank Account at the ODFIXAN 1/17BPR10509Originating Company IdentifierO AN 10/10A unique identifier designating the company initiating the funds transfersinstructions. The first character is a one-digit ANSI identification codedesignation (ICD) followed by the nine-digit identification number which maybe an IRS employer identification number (EIN), data universal numberingsystem (DUNS), or a user assigned number; the ICD for an EIN is 1, DUNS is 3,user assigned number is 9.Attributes- DUNS numberMapped to NACHA 5 record 41-50 (CompanyIdentification)Note:February 2008Determined by the originating bank.Inclusion of this field is recommended.Issue 2.4B-18
Straight Through ProcessingEPN/STPImpl. UseRef.Des.Not UsedBPR11Appendix B: STP 820 SpecificationsDataElement Name510AttributesOriginating Company Supplemental CodeA code defined between the originating company and theoriginating depository financial institution (ODFI) thatuniquely identifies the company initiating the transferinstructionsOAN 9/9Use “*” as place holderRequiredBPR12506(RDFI) ID Number QualifierXID 2/2Code identifying the type of identification number of Depository FinancialInstitution (DFI)01ABA Transit Routing Number Including Check Digits (9digits)In the STP 820 Specification theinclusion of this field is recommended.RequiredBPR13507(RDFI) Identification NumberX AN 9/9Depository Financial Institution (DFI) identification numberTransit ABA number and check digit of the Receiversbank (RDFI)Maps to NACHA 6 record 4-12 (Receiving DFIIdentification)In the STP 820 Specification the inclusion of thisfield is recommended.RequiredBPR14569Account Number QualifierCode indicating the type of accountCode values 22 for Demand DepositDADemand DepositOID 1/3XAN 1/17Maps to NACHA 6 record 02-03(Transaction Code)In the STP 820 Specification theinclusion of this field is recommendedRequiredBPR15508Account NumberAccount number assignedReceivers Account NumberMaps to NACHA 6 record 13-29 (DFI Account Number)In the STP 820 Specification theinclusion of this field is recommendedBPR16373DateDate expressed as CCYYMMDDTransaction Value DateODT 8/8Mapped to NACHA 5 record 70-75 (Effective Entry Datein the format YYMMDD)February 2008Issue 2.4B-19
Straight Through ProcessingAppendix B: STP 820 SpecificationsTRNTraceSegment:on:035Loop:ngLevel: HeadiUsage: MandatoryMax Use: 1Purpose:To identify a transaction to an applicationSyntax Notes:Semantic Notes:1 TRN02 provides unique identification for the transaction.Electronic Payment reference number may be equivalent to a check serial number.Comments:The purpose of this segment is to uniquely identify this a Element SummaryEPN/STP RefImpl. Use Des.DataElementNam eAttributesMust UseTRN01481Trace Type CodeCode identifying which transaction is being referenced1Current Transaction Trace NumberMID 1/2Must UseTRN02127Reference Identification NumberMAN 1/30Reference information as defined for a particular Transaction Set or as specifiedby the Reference Identification QualifierTo be used to identify the electronic payment reference number – equivalentto a check serial number.February 2008Issue 2.4B-20
Straight Through ProcessingSegPositiAppendix B: STP 820 SpecificationsN1ment:Originator Name Identificationon:065Loop:N1OptionalLevel: HeadingUsage: MandatoryMax Use: 1Purpose:To identify a party by type of organization, name, and codeSyntax Notes:1 N101 and N102 are required.Semantic Notes:Comments:1Notes:The first N1 loop is used to identify the Originator of thepayment.Example:EPN/STP RefImpl. Use Des.This segment, used alone, provides the most efficient method of providingorganizational identification.N1*PR*JONES PLUMBING*91*123456789012345\Data Element SummaryDataElementNam e AttributesMust UseN10198Entity Identifier CodeM ID 2/3Code identifying an organizational entity, a physical location, property or anindividualPRPayerMust UseN10293NameX AN 1/16Free-form nameOriginating Company NameMapped to NACHA 5 Record 5-20 (Company Name)Must UseN10366Identification Code QualifierX ID 1/2Code designating the system/method of code structure used for IdentificationCode (67)01 DUNS NUMBER67Identification CodePAYER'S DUNS #Code identifying a party9Must UseFebruary 2008N104Issue 2.4X AN 2/80B-21
Straight Through ProcessingAppendix B: STP 820 SpecificationsN1SegPositiment:Receiver Name Identificationon:070Loop:N1MandatoryLevel: HeadingUsage: MandatoryMax Use: 1Purpose:To identify a party by type of organization, name, and codeSyntax Notes:1 N101 and N102 are required.Semantic Notes:1 This segment, used alone, provides the most efficient method of providingComments:organizational identification.Notes:Example:EPN/STP RefImpl. Use Des.The second N1 loop is used to identify the Receiver of thePayment.N1*PE*SMITH FAUCETS\Data Element SummaryDataElementNam e AttributesMust UseN10198Entity Identifier CodeM ID 2/3Code identifying an organizational entity, a physical location, property or anindividualPEPayeeMust UseN10293NameFree-form nameReceiver Name February 2008XAN 1/16Mapped to NACHA 6 Record 59-74 (Receiving CompanyName/ID Number)Issue 2.4B-22
Straight Through ProcessingAppendix B: STP 820 yLevel: DetailtionalUsage: OpMax Use: 1Purpose:To designate the entities which are parties to a transaction and specify a referencemeaningful to those entitiesSyntax Notes:Semantic Notes:Comments:In this implementation, subsidiary accounting will not be utilized.SegPositiExample:EPN/STP RefImpl. Use Des.Must Use.ENT*1\Data Element SummaryDataElementNam e AttributesENT01554Assigned NumberNumber assigned for differentiation within a transaction setON0 1/6This element will always contain a sequential number starting with 1 andincremented by 1.February 2008Issue 2.4B-23
Straight Through ProcessingPositiAppendix B: STP 820 SpecificationsRMRSegment:Remittance Advice Accounts Receivable Open Item Referenceon:150Loop:RMRMandatoryLevel: DetailUsage: MandatoryMax Use: 1Purpose:To specify the accounts receivable open item(s) to be included in the cash application andto convey the appropriate detailSyntax Notes:1 If either RMR01 or RMR02 is present, then the other is required.Semantic Notes:123Comments:Notes:RMR04 is the amount paid.RMR05 is the amount of invoice (including charges, less allowance) before termsdiscount (if discount is applicable) or debit amount or credit amount of referenceditems.RMR06 is the amount of discount or adjustment taken, if the adjustment segment isnot used.1RMR04 is the net amount being paid inclusive of discounts and adjustments.When paying an original invoice the calculation of the RMR04 is:(RMR05 - RMR06 (Discounts) (ADX01 (Adjustment)). For this implementation,adjustments (ADX01) are always signed negative.2Additional explanatory notes can be added in the REF segment REF03. ADX04 mayalso be utilized to provide additional comments. The explanatory notes will not beautomatically processed by the AR application.3The sum of all RMR04 data elements should equal BPR02.1If no invoice number can be provided, the RMR segment may include the PO orother identifier, which identifies the item being paid.2If both invoice and PO are provided, put the invoice in the RMR and PO in theREF segment.3If RMR04 RMR05, only use RMR04.4RMR06 is the amount of discount or adjustment taken, if the adjustment segment isnot used.5RMR04 is the net amount being paid inclusive of discounts and adjustments.When paying an original invoice, the calculation of the RMR04 is:(RMR05 - RMR06 (Discounts) (ADX01 (Adjustment)). For this implementation,adjustments (ADX01) are always signed negative.125 6.Example:February 2008Additional explanatory notes can be added in the REF segment REF03.ADX04 may also be utilized to provide additional comments. The explanatory noteswill not be automatically processed by the AR application.7The sum of all RMR04 data elements should equal BPR02.8When RMR01 IV, RMR05 and the DTM segment is required,DTM01 should be 003 (invoice) and the DTM02 is ue 2.4B-24
Straight Through ProcessingAppendix B: STP 820 SpecificationsData Element SummaryDataElement NameEPN/STPImpl. UseRef.Des.RequiredRMR01128Reference Identification QualifierX ID 2/3Code qualifying the Reference IdentificationIVSeller's Invoice NumberIf used the DTM01 and DTM02 are required.POPurchase Order NumberR7Accounts Receivable Open ItemRequiredRMR02127Reference IdentificationX AN 1/30Reference information as defined for a particular Transaction Set or asspecified by the Reference Identification QualifierAttributesSeller's Invoice Number, PO or any other document identified.Not UsedRMR03482Payment Action CodeCode specifying the accounts receivable open item(s), if any to be included inthe cash applicationUse “*” as place holderRequiredRMR04782Monetary AmountM R 1/10Monetary amountAmount PaidThe dollar amount must be from .01 to a maximum of 99,999,999.99.The X12 standard specifies that the decimal point must be included only ifthere are cent values. The use of triad separators (commas) is expresslyprohibited in the X12 Standard. For further explanation, refer to DecimalNumber - Data Element Types.OptionalRMR05782Monetary AmountO R 1/10Monetary amountInvoice Amount including charges (less allowance), before terms discounts ordebit amount of referenced items.The dollar amount must be from .01 to a maximum of 99,999,999.99.The X12 standard specifies that the decimal point must be included only ifthere are cent values. The use of triad separators (commas) is expresslyprohibited in the X12 Standard. For further explanation, refer to DecimalNumber - Data Element Types.OptionalRMR06782Monetary AmountO R 1/10Monetary amountAmount of discount takenThis field is used to indicate dollar discount taken when no further explanationis required. The ADX segment may be used if further explanation of adjustmentis required.This value is a positive number and will be subtracted from the Invoice Amount(RMR05.)The dollar amount must be from .01 to a maximum of 99,999,999.99.February 2008Issue 2.4B-25
Straight Through ProcessingAppendix B: STP 820 SpecificationsREFSegment:Reference Identificationon:170Loop:RMROptionalLevel: DetailtionalUsage: OpMax Use: 1Purpose:To specify identifying informationSyntax Notes:Semantic Notes:Comments:Segment will be used when a purchase order number is supplied in addition to theNotes:invoice provided in the RMR segment, or to provide additional information relatedto the payment amount in the RMR segment.PositiExample:EPN/STP RefImpl. Use Des.Must Use.REF*R7*3920394930203*DISCOUNT OK D SMITHE\REF*PO*5722319*MARKETING DEPARTMENT DISCOUNT\Data Element SummaryDataElementNam e AttributesREF01128Reference Identification QualifierCode qualifying the Reference IdentificationBMBill of Lading NumberPOPurchase Order NumberR7Accounts Receivable Open ItemVVVoucherMID 2/3Accounts Receivable Open Items (can be an invoice)Must UseREF02127Reference IdentificationX AN 1/30Reference information as defined for a particular Transaction Set or asspecified by the Reference Identification QualifierEnter Purchase Order Number, Bill of Lading Number,Voucher Number (authorization to pay) or AccountsReceivable Open Item (can be an invoice)OptionalFebruary 2008REF03352DescriptionX AN 1/80A free-form description to clarify the related data elements and their contentsIssue 2.4B-27
Straight Through ProcessingAppendix B: STP 820 SpecificationsDTMDate/Time ReferenceSegment:on:180Loop:RMROptionalLevel: DetailUsage: OptionalMax Use: 1Purpose:To specify pertinent dates and timesSyntax Notes:Semantic Notes:Comments:Notes:1 May be used to specify date of invoice or document specified as referenced in RMR02.Positi2When RMR01 IV, RMR05, DTM01 and DTM02 are required. DTM01should be 003 (invoice).Example:EPN/STP RefImpl. Use 0129\Data Element SummaryDataElementNam e AttributesMust UseDTM01374Date/Time QualifierCode specifying type of date or time, or both date and time003Invoice004Purchase Order092Contract EffectiveOptionalDTM02373DateX DT 8/8Date expressed as CCYYMMDDSeller's Invoice Date, PO Date or date of document specified as referencedin RMR02February 2008Issue 2.4MID 3/3B-28
Straight Through ProcessingAppendix B: STP 820 ptionalLevel: DetailtionalUsage: OpMax Use: 1Purpose:To convey accounts-payable adjustment information for the purpose of cash application,including payer-generated debit/credit memos1 If either ADX03 or ADX04 is present, then the other is required.Syntax Notes:Semantic Notes:1 ADX01 specifies the amount of the adjustment and must be signed if negative. Ifnegative, it reduces the payment 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.Comments:1 The ADX segment is provided to enable invoices or POs not fully paid to beprocessed electronically by AR applications by providing a level of automation with asmall set of adjustment codes.2 Only one ADX is permitted per RMR.PositiNotes:Example:1Only one ADX segment per RMR may used to define an adjustment code and dollaramount indicating a difference in the payment of the invoice or PO or other openitem.2This ADX loop contains an adjustment that is netted to the preceding RMR segmentin this transaction, for example an allowance taken for missing items pertaining to thisremittance item (invoice or PO or open item).3In the STP 820 Implementation, the ADX is not intended to provide a vehicle todefine line item related differences but rather to identify one adjustment amount toone or more items in the associated invoice or open item. Select and use oneadjustment reason code to represent the sum of all adjustments. Use ADX04 toprovide additional explanation if desired.ADX*-8*01*TD*USED CATALOG 199JAN2003\ADX*-1.01*04\Data Element SummaryEPN/STPImpl. UseRef.Des.Must UseADX01DataElement Name782AttributesMonetary AmountMR 1/10For this implementation, this field will always be negative.The dollar amount must be from .01 to a maximum of 99,999,999.99.The X12 standard specifies that the decimal point must be included only ifthere are cent values. The use of triad separators (commas) is expresslyprohibited in the X12 Standard. For further explanation, refer to DecimalNumber - Data Element Types.February 2008Issue 2.4B-29
Straight Through ProcessingAppendix B: STP 820 SpecificationsDataElement NameEPN/STPImpl. UseRef.Des.Must UseADX024
This exercise is intended to demonstrate the use of Mapping Specifications and how machine-processable EDI standard file might look on a real business document. Instructions: Using the enclosed 820 Remittance Advice/Payment Order Mapping specifications and the sample raw EDI data 820 tra
