Electronic Data Interchange- Inbound Payments EDI 820/EFT Specifications for Duke Energy

Transcription

1 Electronic Data Interchange- Inbound Payments EDI 820/EFT Specifications for Duke Energy To: Electronic Data Interchange (EDI) Partners: The following pages contain layout specifications for EDI/EFT transmissions to Duke Energy, following Accredited Standards Committee X12 (ASC X12) Standards, preferably in Version 4, Release 1 (4010) or later. This document contains a sample of a payment transaction. Please direct any questions or comments to electronicpay@duke-energy.com.

2 EFT Receivables Specs.DOC Updated on 2/23/2012 Duke Energy Corporation EFT Payments to Duke Printed: 4/4/13 Page: 2 Electronic Funds Transfer (EFT) allows customers to pay their Duke Energy bills at the time of their choosing and without using a paper check. EFT is available to customers equipped with the appropriate computer technology and is normally associated with customers who have a large number of electric accounts. Utilizing this payment method allows a customer to eliminate many of the manual steps associated with issuing paper checks and also helps ensure accuracy in posting payments to the correct Duke Energy electric accounts. Duke Energy does not charge a fee for accepting EFT payments. However, there are costs a customer must incur (transaction software and network mailboxes) which are often offset by the savings realized by eliminating manual processes associated with payment remittance. Note if formatting payment from EDI-810: RMR02 is the Duke Energy Account Number from the customer bill. If you are formatting payment from EDI-810, the contents of RMR02 are derived from REF02 from REF segment in the heading section of Duke Energy s EDI-810 document where REF01 is equal to 12. The following pages contain instructions for originating ACH payments to JPMorgan Chase for the following Duke Energy companies:

3 Updated on 2/23/2012 EFT Payments to Duke Page: 3 JPMorgan Chase accepts electronic payments for DUKE ENERGY. These payments may be made via the ACH network with a CCD, CCD+ or CTX format as of February 1, 2011 Cash Concentration & Disbursement (CCD+) or Corporate Trade Exchange (CTX) COMPANY/BATCH HEADER RECORD (5) ENTRY DETAIL RECORDS (6) Field 3 Originating Company Name Your Company Name Field 4 Company Discretionary Data DUKE ENERGY Field 5 Originating Company Identification Your Company Identification Number Field 3&4 Chase Transit & Routing Number Field 5 Chase Account Number Follow Instructions below Ensure the Routing Number of the detail record (positions 4-12) is: Ensure the DFI account number of the detail record (positions 13-29) To obtain the Duke Energy Chase bank account numbers send an to electronicpay@duke-energy.com Duke Energy uses four bank accounts to accept payments. Payments must be submitted by jurisdiction which means payments for Carolinas accounts cannot be mixed with payments for Indiana accounts, payments for Indiana accounts cannot be in a payment file for Ohio accounts etc. Jurisdictions are listed below Duke Utility Accounts cannot be mixed within these files. A separate file should be created for each jurisdiction: Duke Energy Carolinas - North Carolina and South Carolina accounts Duke Energy Indiana Indiana accounts Duke Energy Kentucky Kentucky accounts Duke Energy Ohio Ohio accounts One single CTX transaction can be used to make multiple account payments as long as the there is one RMR segment for each payment. The RMR segment contains the account numbers being paid and the individual payment amounts. The addenda records must be formatted following EDI rules. Please ensure the following rules are strictly met: - The amount in the detail record (positions 30-39) matches the amount in the BPR segment. - The sum of all RMR amounts matches the amount in the detail record. CTX Sample Transaction: Each CTX transaction may contain multiple addenda records. Each RMR represents a payment. The RMR must contain the account being paid and amount of the payment. 5200ABC CO CTXEPOSPYMNTS ###### E DUKE ENERGY INDI ISA*00* *00* *ZZ* *ZZ* *110405* *U*00201* *0*P*!\GS*RA* * * *1803* *X* \ST*820* \BPR*C* *C*ACH*CTX*01* *DA* * **01* *DA*######* \TRN*1*E563500\DTM*097* \N1*PR*ABC CO *1* \N1*PE*DUKE ENERGY INDIANA INC*92*K \N3*ST22M PO BOX 1107\N4*C HARLOTTE*NC* \ENT*14\NM1*PR*4*CINCINNATI*****92* \RMR*CR* *ER* * \DTM*003* \RMR*CR*NNNNNNNNNNN*ER*708.75* \DTM*003* \ENT*14\NM1*PR*4*CINCINNATI*****92* U00730\RMR*CR* NNNNNNNNNNN*ER*565.78*565.78\DTM*003* \ENT*14\NM1*PR*4*CINCINNATI*****92* U00730\RMR*CR*NNNNNNNNNNN*ER*719.89*719.89\DTM*003* \RMR*CR*NNNNN NNNNNN*ER* * \DTM*003* \ENT*60\NM1*PR*4*ABC CO CORP OFFICE**** *92*060U00730\RMR*CR*NNNNNNNNNNN*ER* * \REF*BT*2UAAN\DTM*003* \ENT*90\NM1*PR*4*JAY-C CABLE*****92* U00730\RMR*CR*NNNNNNNNNNN*ER*47.70* \DTM*003* \SE*34* \GE*1* \IEA*1* \ Note: ###### (above) is the Duke bank account reference. NNNNNNNNNNN Duke Energy Utility Account Number 10 digits for Carolina accounts 11 digits for IN, KY, OH accounts * If you are formatting payment from EDI-810 for RMR02 use REF02 from header when REF01= 12.

4 Updated on 2/23/2012 EFT Payments to Duke Page: 4 CCD+ Sample Transactions: Each CCD+ transaction contains one addenda record. The addenda record contains an RMR segment. The RMR segment contains the account number and it may contain the amount. If the account is not included as part of the RMR segment, it is obtained from the amount in the detail record. Each CCD+ transaction is used to make a payment to a single account. 5200ABC COMPANY CCD MISC PAY ###### DUKE POWER COMPANY RMR*CR* \ ###### DUKE POWER COMPANY RMR*CR* \ ###### DUKE POWER -OHIO RMR*CR* \ ###### DUKE POWER - OHIO RMR*CR* \ ###### DUKE POWER OHIO12345 A RMR*CR* \ ###### DUKE POWER OHIO12345 A RMR*CR* \ ###### DUKE POWER OHIO12345 A RMR*CR* \ ###### DUKE POWER OHIO12345 A RMR*CR* \ Note: ###### (above) is the Duke bank account reference Billing Account Number Structure Billing account numbers should be left justified and all spaces removed Carolinas - 10 bytes numeric including leading zeros exactly as displayed on the bill Indiana, Kentucky, Ohio 11 bytes numeric including leading zeros exactly as displayed on the bill Remittance Address Duke Energy Carolina accounts: P O Box Charlotte, NC P O Box Charlotte, NC Duke Energy Midwest accounts - Indiana, Kentucky, Ohio PO Box 1326 Charlotte, NC PO Box 1327 Charlotte, NC

5 Updated on 2/23/2012 EFT Payments to Duke Page: 5 How does EFT payment processing work? Duke Energy requires payment information to be converted to a standard EDI format specified by the Accredited Standards Committee X12 (ASC X12) of the American National Standards Institute, preferably in Version 4, Release 1 (4010) or later. (Details are included in the attachment.) Using the ASC X transaction set, payment and posting data MUST BE sent by a customer to Duke s processor, JP MORGAN CHASE (note: this may be done over a public Value-Added Network or other secure link). Duke Energy does not require a signed, formal agreement or contract to receive EFT payments. Customer Responsibilities: The Payer can send one or more CTX transactions for a day to Duke s account at JP MORGAN CHASE. The details of the CTX transaction should include the ten or eleven-digit (depending on jurisdiction) Duke Energy account number (including all leading zero's) in the RMR segment where an Account Number would normally appear. Additional Name / Address / Phone information to identify the Customer should be included in the N1, N3, N4, and PER segments, if available. The Payer needs to provide Duke with a contact number to assist us in resolving any problems with the posting of payments. Posting files must always match the deposit amount. Negative amounts (ex: credit balances) must never be included and sent via the posting file. Reversal transactions will not be accepted and will be rejected by Duke s bank. For further information, contact us at electronicpay@duke-energy.com

6 Updated on 2/23/2012 EFT Payments to Duke Page: 6 The following are layout specifications for EDI/EFT transmissions to Duke Energy, following Accredited Standards Committee X12 (ASC X12) Standards, preferably in Version 4, Release 1 (4010) or later. The specific examples used are for 820 Payment Order / Remittance Advices, as used to receive payments from customers or from Bill Payment Services acting on behalf of our customers. Files transmitted in X12 standard formats are referred to as Transaction Sets, and each different type of file is assigned a Transaction Set Id. For instance, a Payment Order / Remittance Advice transaction set uses a Transaction Set Id of 820, so you may refer to a Payment Order as an X Records in X12 standards are referred to as Segments, and a record type code is a Segment Id. The Segment Id is the first 2 or 3 alphanumeric characters (e.g. ISA ) in the segment. Segments are normally variable length, and are separated by a Segment Terminator, which is normally a special character such as a New Line code (or N/L), or a backslash as used in these examples. Data Fields are referred to as Data Elements, and are identified by the Segment Id and relative position. For example, ISA01 is the first Data Element following the ISA Segment Id. Data Elements are normally variable length and are separated by a Data Element Separator, typically an asterisk (*) or some other special character. Data Element Separators and Segment Terminators can not appear anywhere as a character within a data element for obvious reasons. Though not commonly used, Data Elements may also have Subelements, requiring the use of a Subelement Separator character. Data Types are as follows: Data Type AN DT TM Nx R ID Format Alphanumeric - any combination of alphabetic, numeric or special characters Other than the Data Element Separator, Segment Terminator, or Sub-element Separator characters. Date, in CCYYMMDD format. (Version 4010 and later use 8-digit dates in every Date Type data element other than the one in the ISA Header Record.) Time, in HHMM or HHMMSSd..d format. Numeric, with x decimals to the right of a fixed, implied decimal point, and may contain a negative sign (-) preceding the number. The decimal point is not transmitted. Absence of a sign implies a positive number. Decimal numbers, which may contain an explicit decimal, a variable number of digits to the right of the decimal, and may contain a negative sign (-) preceding the number. Note that the minus sign and decimal are not counted against the maximum length of the data element. A coded data element identifier, where a list of valid codes is provided in the X12 standards, or in some externally referenced standard. Data Element Lengths are represented as N/M, where N is the Minimum and M is the Maximum Length of the related data element. A Data Element Requirement Designator indicates whether an element is Mandatory (required), Optional or Conditional (may be required based upon the presence/absence of a value in a related data element).

7 Updated on 2/23/2012 EFT Payments to Duke Page: 7 ISA - Interchange Control Header Purpose: This segment provides identification of the Sender and Receiver of the transmission, along with Date/Time, Standards Version, etc. Notes: This is the only record in the X12 standard which is fixed length and contains trailing blanks and/or leading zeroes in all of its data elements. Most other segments and data elements are variable length, with trailing blanks removed from alphanumeric (AN) or coded (ID) data elements, and extraneous zeroes removed from numeric (Nx or R) data elements. Also, all fields in thex12 transmission envelope segments (ISA/IEA, GS/GE) are Mandatory (required). The Date fields in the ISA09 is the only DATE type (DT) data element in the 4010 Version which remains as a 6-digit date. ISA data elements are separated by a special character, normally an asterisk (*), so ISA01 begins in column 5, ISA02 in column 8, etc. Interchange Control Number is a sequentially incremented number assigned by the sender, uniquely identifying each interchange/transmission. The value in ISA13 must be identical to the Control Number which appears in the IEA02 data element at the end of the interchange. Data Req Data Min/Max Preferred Value for Element Data Element Name Des Type Length Duke Energy ISA01 Authorization Information Qualifier M ID 2/2 00 ISA02 Authorization Information M AN 10/10 10 blanks ISA03 Security Information Qualifier M ID 2/2 00 ISA04 Security Information M AN 10/10 10 blanks ISA05 Interchange Sender Id Qualifier M ID 2/2 Sender s preference of: 01 - DUNS# or ABA# 02 - SCAC Id 12 - Telephone# ZZ - Miscellaneous ISA06 Interchange Sender Id M AN 15/15 Sender s Id, per above ISA07 Interchange Receiver Id Qualifier M ID 2/2 01 ISA08 Interchange Receiver Id M AN 15/15 ############### ISA09 Interchange Date M DT 6/6 System Date (when sent) ISA10 Interchange Time M TM 4/4 System Time ISA11 Interchange Control Standards Id M ID 1/1 U ISA12 Interchange Control Version Number M ID 5/ (abbreviated form of Version 4, Release 1) ISA13 Interchange Control Number M N0 9/9 Sender-assigned sequential number, matching that in IEA02. ISA14 Acknowledgement Requested M ID 1/1 0=No; 1=Yes ISA15 Test Indicator M ID 1/1 P=Production; T=Test ISA16 Sub-element Separator M AN 1/1 Any character which does not conflict with data content, Data Element Separator or Segment Terminator character. Transmission Envelope Segment Examples: The following are examples of segments meeting the above specifications. In this example, the sender is using Telephone# as a Sender Id. The Data Element separator is an asterisk (*), and the Segment Terminator is a backslash (\). ISA*00* *00* *12* *01* *990524*0758*U*00401* *0*P*:\ GS*RA* * * *0758* *X*004010\ ST*820* \ SE*361* \ GE*000001* \

8 Updated on 2/23/2012 EFT Payments to Duke Page: 8 IEA*1* \

9 Updated on 2/23/2012 EFT Payments to Duke Page: 9 GS - Functional Group Header Purpose: This segment also provides identification of the Sender and Receiver of the transmission, Date/Time, X12 Standards Version, Group Control Number, etc. The RA Functional Id Code indicates that the data in this transmission group is composed of X Payment Order / Remittance Advices. Note: Group Control Number may have leading zeroes suppressed, if desired, but must be identical to the Control Number which appears in the GE segment at the end of the group. Data Req Data Min/Max Preferred Value for Element Data Element Name Des Type Length Duke Energy GS01 Functional Identifier Code M ID 2/2 RA GS02 Application Sender s Code M AN 2/15 same as ISA 06 GS03 Application Receiver s Code M AN 2/15 same as ISA 08 GS04 Date M DT 8/8 System Date (when sent) GS05 Time M TM 4/8 System Time GS06 Group Control Number M N0 1/9 Sender-assigned sequential number, matching that in GE02. GS07 Responsible Agency Code M ID 1/2 X (meaning ASC X12) GS08 Version / Release / Industry Id Code M AN 1/ The X transaction set appears between the GS and GE segments listed below. Specifications for the 820 transaction set are listed on the following pages. GE - Functional Group Trailer Purpose: This segment signals the end of a transaction group. Note: Group Control Number may have leading zeroes suppressed, if desired, but must be identical to the Control Number which appears in the GS segment at the beginning of the group. Data Req Data Min/Max Preferred Value for Element Data Element Name Des Type Length Duke Energy GE01 Number of Transaction Sets Included M N0 1/6 1 (1 820 per group) GE02 Group Control Number M AN 1/9 same as GS06 IEA - Interchange Control Trailer Purpose: This segment signals the end of an interchange. Note: Interchange Control Number must be identical to the Control Number which appears in the ISA segment at the beginning of the interchange. Data Req Data Min/Max Preferred Value for Element Data Element Name Des Type Length Duke Energy IEA01 Number of Included Functional Groups M N0 1/5 1 (1 group in interchange) IEA02 Interchange Control Number M N0 9/9 same as ISA13

10 Updated on 2/23/2012 EFT Payments to Duke Page: Payment Order/Remittance Advice Functional Group ID=RA Introduction: 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. Notes: This particular application of the 820 represents the flow of funds from a Bill Payment Service to Duke Energy Corporation on behalf of a customer. Payment will be made to Duke Energy by depositing check payments. This guideline makes recommendations based on Duke's minimum requirements to facilitate processing of payments and remittance advices for posting to customer accounts. This implementation guide contains Duke Energy s required format and data standards for the use of the ASC X12 Remittance Advice Transaction Set (820). The Heading area contains the total amount being transferred. The Detail area itemizes the invoices or accounts being paid. Duke Energy requires that the ASC X details be communicated in a NACHA CTX payment record and forwarded through the banking system to Duke Energy's account. This document does not contain information regarding CTX formatting. CTX formatting information is available from the payer s bank or from NACHA.

11 Updated on 2/23/2012 EFT Payments to Duke Page: 11 The transaction set segment tables below show only the actual segments that may be used for this particular application, and are not all of the segments possible in the X standard. The data element lists in the segment definitions include both the used and unused elements to demonstrate the need for data element separators for the elements not used prior to an element that is used. Data element separators are not required for blank elements at the end of the segments following the last non-blank element. Heading: DUKE Pos. Seg. Req. Max Loop Notes and Use No. ID Name Des. Use Repeat Comments Must Use 010 ST Transaction Set Header M 1 Must Use 020 BPR Beginning Segment for Payment M 1 Order/Remittance Advice Must Use 035 TRN Trace O 1 C1 LOOP ID - N1 (Payer's Name / Address) >1 Must Use 070 N1 Name O 1 C2 Must Use 120 PER Administrative Communications Contact O >1 LOOP ID - N1 (Payee's Name / Address) >1 Must Use 070 N1 Name O 1 Must Use 120 PER Administrative Communications Contact O >1 Detail: DUKE Pos. Seg. Req. Max Loop Notes and Use No. ID Name Des. Use Repeat Comments LOOP ID - ENT >1 Must Use 010 ENT Entity O 1 LOOP ID - N1/ENT >1 Must Use 020 N1 Individual or Organization Name O 1 C3 Must Use 120 PER Administrative Communications Contact O >1 LOOP ID - RMR/ENT >1 Must Use 150 RMR Remittance Advice Accounts Receivable Open Item Reference O 1 C4 Summary: DUKE Pos. Seg. Req. Max Loop Notes and Use No. ID Name Des. Use Repeat Comments Must Use 010 SE Transaction Set Trailer M 1 Transaction Set Comments 1. The TRN segment is used to uniquely identify a payment order/remittance advice. Ideally, this will be a Trace Reference Number that can be used to verify the deposit of funds in the payee's bank account. 2. The N1 loop allows for name / address information for the payer (1 st occurrence of the N1 loop) and payee (2 nd occurrence of the N1 loop). 3. Allowing the N1 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). 4. Loop RMR is for payments.

12 Updated on 2/23/2012 EFT Payments to Duke Page: 12 Segment: ST Transaction Set Header Position: 010 Loop: Level: Heading Usage: Mandatory Max Use: 1 Purpose: To indicate the start of a transaction set and to assign a control number Syntax Notes: Semantic Notes: 1 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). Comments: Notes: Examples: A unique number assigned by the originator to each transaction set within a functional group. This unique number aids in error reconciliation and research and must be the same as the number in the SE02 element. ST*820*0001\ DUKE Use Must Use Must Use Ref. Des. Data Elemen t Name Data Element Summary Attributes ST Transaction Set Identifier Code M ID 3/3 Code uniquely identifying a Transaction Set. 820 X12.4 Payment Order/Remittance Advice ST Transaction Set Control Number M AN 4/9 Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set This Control Number must match the Control Number in element SE02.

13 Updated on 2/23/2012 EFT Payments to Duke Page: 13 Segment: BPR Beginning Segment for Payment Order/Remittance Advice Position: 020 Loop: Level: Heading Usage: Mandatory Max Use: 1 Purpose: (1) To indicate the beginning of a Payment Order/Remittance Advice Transaction Set and total payment amount or (2) to enable related transfer of funds and/or information from payer to payee to occur Syntax Notes: 1 If either BPR06 or BPR07 is present, then the other is required. 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. 5 If either BPR18 or BPR19 is present, then the other is required. 6 If BPR20 is present, then BPR21 is required. Semantic Notes: 1 BPR02 specifies the payment amount. The sum of the amounts in the RMR segments (RMR04) must equal the amount in the BPR02 field. 2 When using this transaction set to initiate a payment, 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). 3 BPR12 and BPR13 relate to the receiving depository financial institution (RDFI). 4 BPR15 is the account number of the receiving company to be debited or credited with the payment order. 5 BPR17 is a code identifying the business reason for the this payment. 6 BPR18, BPR19, BPR20 and BPR21, if used, identify a third bank identification number and account to be used for return items only. Comments: 1 BPR09 is the account of the company originating the payment. This account may be debited or credited depending on the type of payment order. Notes: Examples: This is an example of a BPR segment used for an ACH/CTX payment, where dollars and data are sent together through the ACH Banking Network. BPR*C* *C*ACH*CTX*01* *DA* * **01* *DA* * \ Data Element Summary DUKE Use Ref. Des. Data Element Name Attributes Must Use BPR Transaction Handling Code M ID 1/2 Code designating the action to be taken by all parties. C Payment Accompanies Remittance Advice This transaction includes both payment information and supplier remittance details. Must Use BPR Monetary Amount M R 1/18 Monetary amount. This is the net payment amount including all remittance items and adjustments as shown in the detail area. The calculation of BPR02 should be the sum of all RMR04 (net amount paid) plus the sum of all ADX02 (adjustments) of the ADX outer loop (position 2/080). Total Deposit Amount (must be positive and cannot exceed eleven (11) characters including decimals (i.e ) when converted to a NACHA format. BPR02 is the equivalent of field 6 in the ACH Entry Detail Record, type 6, which has a length of ten (10) characters with an implied decimal between the eighth and ninth characters ($$$$$$$$ ). Must Use BPR Credit/Debit Flag Code M ID 1/1 Code indicating whether amount is a credit or debit C Credit A credit to the receiver and a debit to the originator.

14 Updated on 2/23/2012 EFT Payments to Duke Page: 14 DUKE Use Ref. Des. Data Element Name Attributes Must Use BPR Payment Method Code M ID 3/3 Code identifying the method for the movement of payment instructions ACH Automated Clearing House (ACH) Must Use BPR Payment Format Code O ID 1/10 Code identifying the payment format to be used. If BPR04 is ACH, use CCD, CCP, or CTX. CCD Cash Concentration/Disbursement (CCD) (ACH) Used if BPR04 is ACH. CCP Cash Concentration/Disbursement plus Addenda (CCD+) (ACH) Used if BPR04 is ACH. CTX Corporate Trade Exchange (CTX) (ACH) Used if BPR04 is ACH. Must Use BPR (DFI) ID Number Qualifier X ID 2/2 Code identifying the type of identification number of Depository Financial Institution (DFI). BPR06 through BPR09 relate to the originating depository financial institution and account. 01 ABA Transit Routing Number Including Check Digits (9 digits) Must Use BPR (DFI) Identification Number X AN 3/12 Depository Financial Institution (DFI) identification number. This element contains the originating bank's Transit Routing Number. BPR07 is the equivalent of field 12 in the ACH Company/Batch Header Record, type 5. Field 12 contains the eight (8) identification digits but does NOT contain the check digit (digit 9). Must Use BPR Account Number Qualifier O ID 1/3 Code indicating type of bank account or other financial asset Identifies the type of account making payment. Examples include: 03 Checking Account DA Demand Deposit SG Savings Must Use BPR Account Number X AN 1/35 Account number assigned. The Originator's account number. Must Use BPR Originating Company Identifier O AN 10/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. This data element should be identical to the TRN03, Originating Company Identifier of the TRN (Trace) segment. The preferred value is the originating company s D-U-N-S number. BPR10 is the equivalent of field 5, minus the first character, in the ACH Company/Batch Header Record, type 5. The ACH format allows for a maximum of ten (10) characters for this field. BPR10 also corresponds to field 7 in the ACH Company Batch Control Record, type 8. Optional BPR Originating Company Supplemental Code O AN 9/9 A code defined between the originating company and the originating depository financial institution (ODFI) that uniquely identifies the company initiating the transfer instructions.

15 Updated on 2/23/2012 EFT Payments to Duke Page: 15 Must Use BPR (DFI) ID Number Qualifier X ID 2/2 Code identifying the type of identification number of Depository Financial Institution (DFI). BPR12 through BPR15 relate to the receiving depository financial institution and account. These elements will contain DUKE s EFT Bank Transit Routing Number and Duke's account number. 01 ABA Transit Routing Number Including Check Digits (9 digits) Must Use BPR (DFI) Identification Number X AN 3/12 Depository Financial Institution (DFI) identification number. The receiver's Bank Transit Routing number to be supplied during trading partner set up process. BPR13 is the equivalent of fields 3 and 4 in the ACH Entry Detail Record, type 6. Field 3 contains the eight (8) identification digits and field 4 contains the check digit (digit 9). Must Use BPR Account Number Qualifier O ID 1/3 Code indicating type of bank account or other financial asset Type of account receiving payment. DA Demand Deposit Must Use BPR Account Number X AN 1/35 Account number assigned. The receiver's Bank Account number. BPR15 is the equivalent of field 5 in the ACH Entry Detail Record, type 6. The ACH format allows for a maximum of seventeen (17) characters for this field. Must Use BPR Date O DT 8/8 Date the originating company intends for the transaction to be settled. For ACH payments, this is the actual settlement date. For check payments, this is the check issuance date. For Fedwire payments, this is the value date. BPR16 is the equivalent of field 9 in the ACH Company/Batch Header Record, type 5. In the ACH format, this is the Effective Date with the format CCYYMMDD. This must be a valid banking day.

16 Updated on 2/23/2012 EFT Payments to Duke Page: 16 Segment: TRN Trace Position: 035 Loop: Level: Heading Usage: Mandatory Max Use: 1 Purpose: To uniquely identify a transaction to an application. Syntax Notes: Semantic Notes: 1 TRN02 provides unique identification for the transaction. 2 TRN03 identifies an organization. 3 TRN04 identifies a further subdivision within the organization. Comments: Notes: Examples: The purpose of this segment is to uniquely identify this transaction set and to reassociate payment and remittance that have been split. If the Payment Format Code (element BPR05) is CCD, the most likely location of the reference number is the Individual Identification Number, field 7, of the Entry Detail Record for CCD Entries, type 6. See the notes for element TRN02. If the Payment Format Code (element BPR05) is CCP, this TRN segment will be equivalent to the Payment Related Information, field 3, of the Addenda Record for CCD Plus Entries, type 7, of the incoming CCD Plus item. The ACH format allows for a maximum of eighty (80) characters for this field. TRN*3*990322\ Data Element Summary Must Use TRN Reference Number M AN 1/30 Reference number or identification number as defined for a particular Transaction Set, or as specified by the Reference Number Qualifier. This reference number uniquely identifies this payment order. This is a unique number within the originator/sender/receiver relationship and is assigned by the originator. When the payment and remittance are split, this number can be used for reassociation. If payment is made by check, this is the check number. Optional TRN Originating Company Identifier O AN 10/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. This data element should be identical to the BPR10, Originating Company Identifier, element of the BPR (Beginning Segment for Payment Order/Remittance Advice) segment. The preferred value is the originating company s D-U-N-S number. TRN03 is the equivalent of field 5, minus the first character, in the ACH Company/Batch Header Record, type 5. The ACH format allows for a maximum of ten (10) characters for this field. BPR10 also corresponds to field 7 in the ACH Company Batch Control Record, type 8. Optional TRN Reference Number O AN 1/30 Reference number or identification number as defined for a particular Transaction Set, or as specified by the Reference Number Qualifier.

17 Updated on 2/23/2012 EFT Payments to Duke Page: 17 Segment: Segment: N1 Name Position: 070 Loop: N1 Level: Heading Usage: Mandatory Max Use: 1 Purpose: To identify a party by type of organization, name and code Syntax Notes: 1 At least one of N102 or N103 is required. 2 If either N103 or N104 is present, then the other is required. Semantic Notes: Comments: 1 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. 2 N105 and N106 further define the type of entity in N101. Notes: The first N1 loop in the heading area is used to identify the originating company (Payer) for this remittance. Examples: N1*PR*BILL PAYMENT SERVICE, INC.\ DUKE Use Ref. Des. Data Elemen t Name Data Element Summary Attributes Must Use N Entity Identifier Code M ID 2/2 Code identifying an organizational entity, a physical location, or an individual PR Payer Must Use N Name X AN 1/60 Free-form name. If the Duke Energy customer is using a payment service, this is the name of the payment service; otherwise it is the name of the customer. N102 is the equivalent of field 3 in the ACH Company/Batch Header Record, type 5. The ACH format allows for a maximum of sixteen (16) characters for this field. Optional N Identification Code Qualifier X ID 1/2 Code designating the system/method of code structure used for Identification Code (67). Optional N Identification Code X AN 2/80 Code identifying a party or other code. Optional N Entity Relationship Code O ID 2/2 Code describing entity relationship. Optional N Entity Identifier Code O ID 2/3 Code identifying an organizational entity, a physical location, or an individual

18 Updated on 2/23/2012 EFT Payments to Duke Page: 18 Segment: PER Administrative Communications Contact Position: 120 Loop: N1 Level: Heading Usage: Mandatory Max Use: 1 Purpose: To identify a person or office to whom administrative communications should be directed Syntax Notes: 1 If either PER03 or PER04 is present, then the other is required. 2 If either PER05 or PER06 is present, then the other is required. Semantic Notes: Comments: This segment is optional, and not required for this application. Notes: Examples: PER*CR*HENRY TREMBLECHIN*TE* *FX* \ DUKE Use Ref. Des. Data Elemen t Name Data Element Summary Attributes Must Use PER Contact Function Code M ID 2/2 Code identifying the major duty or responsibility of the person or group named. CA Customer or Payment Service Contact Must Use PER02 93 Name O AN 1/35 Free-form name. Must Use PER Communication Number Qualifier O ID 2/2 Code identifying the type of communication number. TE Telephone Must Use PER Communication Number O AN 1/80 Complete communications number including country or area code when applicable. This element contains the telephone number. Must Use PER Communication Number Qualifier O ID 2/2 Code identifying the type of communication number. EM Electronic Mail FX Facsimile Must Use PER Communication Number O AN 1/80 Complete communications number including country or area code when applicable. If used, this element contains the Fax number or identification. Optional PER Communication Number Qualifier O ID 2/2 Optional PER Communication Number O AN 1/80 Optional PER Contact Inquiry Reference O AN 1/20

19 Updated on 2/23/2012 EFT Payments to Duke Page: 19 Segment: ENT Entity Position: 010 Loop: ENT Level: Detail Usage: Mandatory Max Use: 1 Purpose: To designate the entities which are parties to a transaction and specify a reference meaningful to those entities Syntax Notes: 1 If any of ENT02 ENT03 or ENT04 is present, then all are required. 2 If any of ENT05 ENT06 or ENT07 is present, then all are required. 3 If either ENT08 or ENT09 is present, then the other is required. Semantic Notes: DUKE Use Comments: Notes: Examples: Ref. Des. If any segments in the detail area are used, the ENT segment is mandatory to indicate a loop start. In a single/single entity relationship, this segment is used as a place holder and only the ENT01 is required. ENT*1\ ENT*2\ Data Elemen t Name Data Element Summary Attributes Must Use ENT Assigned Number O N0 1/6 Number assigned for differentiation within a transaction set. In the single/single relationship, the ENT01 is used as a place holder. No other data elements need be used. In this application, the Assigned Number is a number starting with 1 and incremented by 1 for each ENT loop in the transaction. Optional ENT02 98 Entity Identifier Code O ID 2/3 Code identifying an organizational entity, a physical location, or an individual Optional ENT03 66 Identification Code Qualifier O ID 1/2 Code designating the system/method of code structure used for Identification Code (67). Optional ENT04 67 Identification Code O AN 2/80 Code identifying a party or other code. Originating company sub-entity. Optional ENT05 98 Entity Identifier Code O ID 2/3 Code identifying an organizational entity, a physical location, or an individual Optional ENT06 66 Identification Code Qualifier O ID 1/2 Code designating the system/method of code structure used for Identification Code (67). Optional ENT07 67 Identification Code O AN 2/80 Code identifying a party or other code. Receiving company sub-entity. Optional ENT Reference Number Qualifier X ID 2/3 Code qualifying the Reference Number. EM Electronic Payment Reference Number (Confirmation#) Optional ENT Reference Number X AN 1/30 Reference number or identification number as defined for a particular Transaction Set, or as specified by the Reference Number Qualifier.

20 Updated on 2/23/2012 EFT Payments to Duke Page: 20 Segment: N1 Name Position: 070 Loop: N1 Level: Heading Usage: Mandatory Max Use: 1 Purpose: To identify a party by type of organization, name and code Syntax Notes: 1 At least one of N102 or N103 is required. 2 If either N103 or N104 is present, then the other is required. Semantic Notes: Comments: 1 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. 2 N105 and N106 further define the type of entity in N101. Notes: The second N1 loop in the Heading area is used to identify the receiving company (Payee) for this remittance. Examples: N1*PE*DUKE ENERGY CORPORATION\ DUKE Use Ref. Des. Data Elemen t Name Data Element Summary Attributes Must Use N Entity Identifier Code M ID 2/3 Code identifying an organizational entity, a physical location, or an individual PE Payee Must Use N Name X AN 1/60 Free-form name. This is the name of the company receiving the payment. N102 is the equivalent of field 8 in the ACH Entry Detail Record, type 6. The ACH format allows for a maximum of twenty-two (22) characters for this field. Example: Duke Energy Ohio, Duke Energy Ky, Duke Energy Indiana, Duke Energy Carolinas Optional N Identification Code Qualifier X ID 1/2 Code designating the system/method of code structure used for Identification Code (67). Optional N Identification Code X AN 2/80 Code identifying a party or other code. Optional N Entity Relationship Code O ID 2/2 Code describing entity relationship. Optional N Entity Identifier Code O ID 2/2 Code identifying an organizational entity, a physical location, or an individual

21 Updated on 2/23/2012 EFT Payments to Duke Page: 21 Segment: N1 Individual or Organization Name Position: 020 Loop: N1/ENT Level: Detail Usage: Mandatory Max Use: 1 Purpose: To supply the full name of an individual or organizational entity. Syntax Notes: 1 At least one of N102 or N103 is required 2 If either N103 or N104 is present then the other is required. Semantic Notes: Comments: 1 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. 2 N105 and N106 further defines the type of entity in N101. Use the header N1 loop to define the payer and payee. Use the N1 detail loop to Notes: define The first N1 loop in the Detail area is used to identify the paying company (payer) for this remittance. Examples N1*PR*3*Stephen A Brookdale*FI* \ DUKE Use Ref. Des. Data Elemen t Name Data Element Summary Attributes Must Use N Entity Identifier Code M ID 2/3 Code identifying an organizational entity, a physical location, or an individual Some commonly used codes include: PR Payer Must Use N Name O AN 1/35 Free-form name. If customer name is not available, the Payer Name from the header section of the transaction may be repeated here. This field should contain the customer account name from the bill. Optional N Identification Code Qualifier X ID 1/2 Code designating the system/method of code structure used for Identification Code (67). FI Federal Tax Id Number Optional N Identification Code X AN 2/80 Code identifying a party or other code. Customer's Social Security Number Optional N Entity Relationship Code X ID 2/2 Code describing entity relationship. Optional N Entity Identifier Code O ID 2/3 Code identifying an organizational entity, a physical location, or an individual

22 Updated on 2/23/2012 EFT Payments to Duke Page: 22 Segment: PER Administrative Communications Contact Position: 120 Loop: N1 Level: Detail Usage: Mandatory Max Use: 1 Purpose: To identify a person or office to whom administrative communications should be directed Syntax Notes: 1 If either PER03 or PER04 is present, then the other is required. 2 If either PER05 or PER06 is present, then the other is required. Semantic Notes: Comments: Notes: Examples: PER*CA**TE* *FX* \ DUKE Use Ref. Des. Data Elemen t Name Data Element Summary Attributes Must Use PER Contact Function Code M ID 2/2 Code identifying the major duty or responsibility of the person or group named. CA Customer Account Optional PER02 93 Name O AN 1/35 Free-form name. Must Use PER Communication Number Qualifier O ID 2/2 Code identifying the type of communication number. TE Telephone Must Use PER Communication Number O AN 1/80 Complete communications number including country or area code when applicable. This element contains the telephone number. Optional PER Communication Number Qualifier O ID 2/2 Code identifying the type of communication number. EM Electronic Mail FX Facsimile Optional PER Communication Number O AN 1/80 Complete communications number including country or area code when applicable. If used, this element contains the Fax number or identification.

23 Updated on 2/23/2012 EFT Payments to Duke Page: 23 Segment: RMR Remittance Advice Accounts Receivable Open Item Reference Position: 150 Loop: RMR/ENT Level: Detail Usage: Mandatory l Max Use: 1 Purpose: To specify the accounts receivable open item(s) to be included in the cash application and to convey the appropriate detail Syntax Notes: 1 If either RMR01 or RMR02 is present, then the other is required. Semantic Notes: 1 If RMR03 is present, it specifies how the cash is to be applied. Comments: 1 Parties using this segment should agree on the content of RMR01 and RMR02 prior to initiating communication. 2 If RMR03 is not present, this is a payment for an open item. If paying an open item, RMR02 must be present. If not paying a specific open item, RMR04 must be present. 3 RMR04 is the net amount paid. Notes: Examples: Loop RMR provides a Customer Account Reference# and Payment Amount. RMR*CR* *CR*137.00\ RMR*CR* *CR*45.00\ DUKE Use Ref. Des. Data Elemen t Name Data Element Summary Attributes Must Use RMR Reference Number Qualifier X ID 2/3 Code qualifying the Reference Number. CR Customer Reference Number (Duke Energy Account#) Must Use RMR Reference Number X AN 1/30 Reference number or identification number as defined for a particular Transaction Set, or as specified by the Reference Number Qualifier. Customer Account Number for which payment is made. The contents of this field are derived from the REF02 from the heading section of Duke Energy s EDI-810 document where REF01 is equal to 12. Must Use RMR Payment Action Code O ID 2/2 Code specifying the type of accounts receivable open item(s) to be included in a cash application. PO Payment on account Must Use RMR Monetary Amount O R 1/15 Monetary amount. RMR04 is the net amount being paid. MUST BE A POSITIVE AMOUNT. The sum of all amounts (RMR04) must equal the amount in the BPR segment (BPR02 field) Not Used RMR Monetary Amount O R 1/15 Total Amount of Invoice (including charges, less allowances) before terms discount (if discount is applicable) or debit amount or credit amount of referenced items. Not Used RMR Monetary Amount O R 1/15 Amount of discount taken, which may be less than or equal to the amount of discount permitted. Not Used RMR Adjustment Reason Code X Not Used RMR Monetary Amount * If you are formatting payment from EDI-810 for RMR02 use REF from header when REF01=12.

24 Updated on 2/23/2012 EFT Payments to Duke Page: 24 Segment: SE Transaction Set Trailer Position: 010 Loop: Level: Summary Usage: Mandatory Max Use: 1 Purpose: To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments). Syntax Notes: Semantic Notes: Comments: 1 SE is the last segment of each transaction set. DUKE Use Notes: Examples: Ref. Des. SE*85*0001\ Data Elemen t Name Data Element Summary Attributes Must Use SE01 96 Number of Included Segments M N0 1/10 Total number of segments included in a transaction set including ST and SE segments. Must Use SE Transaction Set Control Number M AN 4/9 Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set This Control Number must match the Control Number in element ST02.

25 Updated on 2/23/2012 EFT Payments to Duke Page: Might occur multiple times (for each remittance advice) à All segments and fields listed are required ISA SEGMENT Only one of this segment can appear in the entire file ISA01 Authorization Information Qualifier 00 ISA02 Authorization Information Blank ISA03 Security Information Qualifier 00 ISA04 Security Information 10 Blanks ISA05 Interchange ID Qualifier ZZ ISA06 Interchange Sender ID nnnnnnnnn ISA07 Interchange ID Qualifier ZZ ISA08 Interchange Receiver ID nnnnnnnnnnnn ISA09 Interchange Date Date in YYMMDD format ISA10 Interchange Time Time in hhmm format ISA11 Interchange Control Standards ID U ISA12 Interchange Control Version Number ISA13 Interchange Control Number nnnnnnnnn ISA14 Acknowledgement Requested 0=No; 1=Yes ISA15 Test Indicator P(for Production) ISA16 Subelement Separator * or any character per customer preference GS SEGMENT only one of this segment can appear in the entire file GS01 Functional ID code RA GS02 Application Sender's Code nnnnnnnnn GS03 Application Receiver's Code nnnnnnnnnnnn GS04 Date Date in YYMMDD format (same as ISA09) GS05 Time Time in hhmm format (same as ISA10) GS06 Group Control Number Build as JJJhhmmss where JJJ is julian date GS07 Responsible Agency Code X GS08 Version/Rel. Ind. ID Code ST SEGMENT at least one of this segment must appear in the output file ST01 Transaction set ID code 820 ST02 Transaction set control number Initial value is the value of GS06 field and it is increased by 1 with each new ST segment. BPR SEGMENT one for each ST segment must appear in the output file BPR0 1 Transaction Handling Code 305 C BPR0 2 Monetary Amount No leading zeroes BPR0 3 Credit/Debit Flag Code C - credit BPR0 4 Payment Method Code ACH BPR0 5 Payment Format Code CTX, PPD OR CCP (CIE = CTX) BPR0 6 Originating DFI ID Number Qualifier 01 BPR0 7 Originating DFI ID Number DFI Id Number BPR0 8 BPR0 9 BPR1 0 BPR1 1 BPR1 2 BPR1 3 BPR1 4 BPR1 5 BPR1 6 Account Number Qualifier Code Account Number Originating Company Identifier Originating Company Supplemental Receiving DFI ID Number Qualifier 01 Receiving DFI ID Number Account Number Qualifier Account Number Effective Entry Date DA Demand Deposit (For Transactions not CTX) 03 Checking Account SG Savings Truncate to 2 positions if CTX Originator s Financial Institution Account Number ACH Company ID Not Used nnnnnnnnn - Duke bank ABA DA - Demand Deposit Account ####### - Duke bank account mnemonic Format: CCYYMMDD TRN SEGMENT TRN0 1 Trace Type Code 1 - Current Transaction Trace TRN0 2 Reference Number Trace Number N1 SEGMENT N101 Entity ID Code PR payer