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.
EFT Receivables Specs.DOC
Updated on 2/23/2012
Duke Energy Corporation
EFT Payments to Duke
X12 820 Payment Order / Remittance Advice format
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:
EFT Receivables Specs.DOC
Updated on 2/23/2012
Duke Energy Corporation
EFT Payments to Duke
X12 820 Payment Order / Remittance Advice format
Printed: 4/4/13
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)
Field 3
Field 4
Field 5
Originating
Company
Originating Company
Company
Discretionary
Identification
Name
Data
Your
DUKE
Your Company
Company
ENERGY
Identification
Name
Number
ENTRY DETAIL RECORDS (6)
Field 3&4
Field 5
Chase Transit & Routing
Chase Account Number
Number
021409169
Follow Instructions below
Ensure the Routing Number of the detail record (positions 4-12) is: 021409169
Ensure the DFI account number of the detail record (positions 13-29)
To obtain the Duke Energy Chase bank account numbers send an email 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
90130
5137224933CTXEPOSPYMNTS
1104060961021000022719124
622021409169######
0004226093E563500
0014DUKE ENERGY INDI 1072000320002026
705ISA*00*
*00*
*ZZ*072000326
*ZZ*021409169
*110405*18000010002026
7053*U*00201*110405791*0*P*!\GS*RA*5137224933*071000013*20110405*1803*110405791*X*000020002026
70504010\ST*820*11464212\BPR*C*42260.93*C*ACH*CTX*01*011111111*DA*111111111*513762400030002026
705961**01*021409169*DA*######*20110406\TRN*1*E563500\DTM*097*20110405\N1*PR*ABC CO00040002026
705*1*006999528\N1*PE*DUKE ENERGY INDIANA INC*92*K0223511\N3*ST22M PO BOX 1107\N4*C00050002026
705HARLOTTE*NC*282011007\ENT*14\NM1*PR*4*CINCINNATI*****92*01400431110730\RMR*CR*2600060002026
705802074025*ER*19825.76*19825.76\DTM*003*20110321\RMR*CR*NNNNNNNNNNN*ER*708.75*70800070002026
705.75\DTM*003*20110321\ENT*14\NM1*PR*4*CINCINNATI*****92*01444432U00730\RMR*CR*45200080002026
NNNNNNNNNNN*ER*565.78*565.78\DTM*003*20110319\ENT*14\NM1*PR*4*CINCINNATI*****92*01400090002026
70500438U00730\RMR*CR*NNNNNNNNNNN*ER*719.89*719.89\DTM*003*20110321\RMR*CR*NNNNN17700100002026
NNNNNN*ER*18154.00*18154.00\DTM*003*20110321\ENT*60\NM1*PR*4*ABC CO CORP OFFICE****00110002026
705*92*060U00730\RMR*CR*NNNNNNNNNNN*ER*2239.05*2239.05\REF*BT*2UAAN\DTM*003*201103200120002026
7051\ENT*90\NM1*PR*4*JAY-C CABLE*****92*09000011U00730\RMR*CR*NNNNNNNNNNN*ER*47.70*00130002026
70547.70\DTM*003*20110321\SE*34*11464212\GE*1*110405791\IEA*1*110405791\
00140002026
820000001500021409160000000000000000042260935137224933
021000022719124
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”.
EFT Receivables Specs.DOC
Updated on 2/23/2012
Duke Energy Corporation
EFT Payments to Duke
X12 820 Payment Order / Remittance Advice format
Printed: 4/4/13
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
3101036009CCD MISC PAY0406111104060961021000022722329
622071000013######
0000001836000005520124011DUKE POWER COMPANY 001101036151053559
705RMR*CR*1327011145\
00011053559
622071000013######
0000148787000005520124011DUKE POWER COMPANY 001101036151053560
705RMR*CR*0011113744\
00011053560
622071000013######
0000006300000005520124011DUKE POWER -OHIO
001101036151053561
705RMR*CR*1655111130\
00011053561
622071000013######
0000006833000005520124011DUKE POWER - OHIO
001101036151053562
705RMR*CR*0011113745\
00011053562
622071000013######
0000006217000005520124011DUKE POWER OHIO12345 A001101036151053563
705RMR*CR*1777774068\
00011053563
622071000013######
0000003975000005520124011DUKE POWER OHIO12345 A001101036151053564
705RMR*CR*1376888847\
00011053564
622071000013######
0000002972000005520124011DUKE POWER OHIO12345 A001101036151053565
705RMR*CR*1999975487\
00011053565
622071000013######
0000005350000005520124011DUKE POWER OHIO12345 A001101036151053566
705RMR*CR*1866663194\
00011053566
820000001600568000080000000000000000001822703101036009
021000022722329
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 70515
Charlotte, NC 28272
P O Box 70516
Charlotte, NC 28272
Duke Energy Midwest accounts - Indiana, Kentucky, Ohio
PO Box 1326
Charlotte, NC 28201-1326
PO Box 1327
Charlotte, NC 28201-1327
EFT Receivables Specs.DOC
Updated on 2/23/2012
Duke Energy Corporation
EFT Payments to Duke
X12 820 Payment Order / Remittance Advice format
Printed: 4/4/13
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 X12 820 “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
EFT Receivables Specs.DOC
Updated on 2/23/2012
Duke Energy Corporation
EFT Payments to Duke
X12 820 Payment Order / Remittance Advice format
Printed: 4/4/13
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 X12 820.
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).
EFT Receivables Specs.DOC
Updated on 2/23/2012
Duke Energy Corporation
EFT Payments to Duke
X12 820 Payment Order / Remittance Advice format
Printed: 4/4/13
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
Element
ISA01
ISA02
ISA03
ISA04
ISA05
Data Element Name
Authorization Information Qualifier
Authorization Information
Security Information Qualifier
Security Information
Interchange Sender Id Qualifier
Req
Des
M
M
M
M
M
Data Min/Max
Type Length
ID
2/2
AN
10/10
ID
2/2
AN
10/10
ID
2/2
ISA06
ISA07
ISA08
ISA09
ISA10
ISA11
ISA12
Interchange Sender Id
Interchange Receiver Id Qualifier
Interchange Receiver Id
Interchange Date
Interchange Time
Interchange Control Standards Id
Interchange Control Version Number
M
M
M
M
M
M
M
AN
ID
AN
DT
TM
ID
ID
15/15
2/2
15/15
6/6
4/4
1/1
5/5
ISA13
Interchange Control Number
M
N0
9/9
ISA14
ISA15
ISA16
Acknowledgement Requested
Test Indicator
Sub-element Separator
M
M
M
ID
ID
AN
1/1
1/1
1/1
Preferred Value for
Duke Energy
00
10 blanks
00
10 blanks
Sender’s preference of:
01 - DUNS# or ABA#
02 - SCAC Id
12 - Telephone#
ZZ - Miscellaneous
Sender’s Id, per above
01
###############
System Date (when sent)
System Time
U
00401 (abbreviated form of
Version 4, Release 1)
Sender-assigned sequential number,
matching that in IEA02.
0=No; 1=Yes
P=Production; T=Test
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*8033762678
*01*006996052250
*990524*0758*U*00401*000000097*0*P*:\
GS*RA*8033762678*006996052250*19990524*0758*99052401*X*004010\
ST*820*000000001\
SE*361*000000001\
GE*000001*99052401\
EFT Receivables Specs.DOC
Updated on 2/23/2012
IEA*1*000000097\
Duke Energy Corporation
EFT Payments to Duke
X12 820 Payment Order / Remittance Advice format
Printed: 4/4/13
Page: 8
EFT Receivables Specs.DOC
Updated on 2/23/2012
Duke Energy Corporation
EFT Payments to Duke
X12 820 Payment Order / Remittance Advice format
Printed: 4/4/13
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 X12 820 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
Element
GS01
GS02
GS03
GS04
GS05
GS06
Data Element Name
Functional Identifier Code
Application Sender’s Code
Application Receiver’s Code
Date
Time
Group Control Number
Req
Des
M
M
M
M
M
M
GS07
GS08
Responsible Agency Code
M
Version / Release / Industry Id Code M
Data Min/Max
Type Length
ID
2/2
AN
2/15
AN
2/15
DT
8/8
TM
4/8
N0
1/9
ID
AN
1/2
1/12
Preferred Value for
Duke Energy
RA
same as ISA 06
same as ISA 08
System Date (when sent)
System Time
Sender-assigned
sequential number,
matching that in GE02.
X (meaning ASC X12)
004010
The X12 820 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
Element Data Element Name
Des
GE01
Number of Transaction Sets Included M
GE02
Group Control Number
M
Data Min/Max
Type Length
N0
1/6
AN
1/9
Preferred Value for
Duke Energy
1 (1 820 per group)
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
Element Data Element Name
Des
IEA01
Number of Included Functional Groups
IEA02
Interchange Control Number
M
Data Min/Max
Type Length
M
N0
N0
9/9
Preferred Value for
Duke Energy
1/5
1 (1 group in interchange)
same as ISA13
EFT Receivables Specs.DOC
Updated on 2/23/2012
Duke Energy Corporation
EFT Payments to Duke
X12 820 Payment Order / Remittance Advice format
Printed: 4/4/13
Page: 10
820 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 X12 820 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.
EFT Receivables Specs.DOC
Updated on 2/23/2012
Duke Energy Corporation
EFT Payments to Duke
X12 820 Payment Order / Remittance Advice format
Printed: 4/4/13
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 X12 820 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
Use
Must Use
Must Use
Pos. Seg.
No.
ID
010 ST
020 BPR
Must Use 070
Must Use 120
N1
PER
Req.
Name
Des.
Transaction Set Header
M
Beginning Segment for Payment
M
Order/Remittance Advice
Trace
O
LOOP ID - N1 (Payer's Name / Address)
Name
O
Administrative Communications Contact
O
Must Use 070
Must Use 120
N1
PER
LOOP ID - N1 (Payee's Name / Address)
Name
Administrative Communications Contact
O
O
Req. Max Loop
Des. Use Repeat
>1
O
1
>1
O
1
Must Use 035
TRN
Max Loop
Use Repeat
1
1
1
Notes and
Comments
C1
>1
1
>1
C2
>1
1
>1
Detail:
DUKE
Use
Pos.
No.
Seg.
ID
Must Use 010
ENT
Must Use 020
N1
Name
LOOP ID - ENT
Entity
LOOP ID - N1/ENT
Individual or Organization Name
Must Use 120
PER
Administrative Communications Contact
O
>1
Must Use 150
RMR
LOOP ID - RMR/ENT
Remittance Advice Accounts Receivable
Open Item Reference
O
1
Notes and
Comments
C3
>1
C4
Summary:
DUKE
Use
Pos.
No.
Must Use 010
Seg.
ID
Name
SE
Transaction Set Trailer
Req.
Des.
M
Max Loop
Use Repeat
Notes and
Comments
1
Transaction Set Comments
1.
2.
3.
4.
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.
st
The N1 loop allows for name / address information for the payer (1 occurrence of the N1 loop) and payee
nd
(2 occurrence of the N1 loop).
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).
Loop RMR is for payments.
EFT Receivables Specs.DOC
Updated on 2/23/2012
Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:
Semantic Notes:
Comments:
Notes:
Examples:
DUKE
Use
Must
Use
Must
Use
Ref.
Des.
ST01
ST02
Duke Energy Corporation
EFT Payments to Duke
X12 820 Payment Order / Remittance Advice format
Printed: 4/4/13
Page: 12
ST Transaction Set Header
010
Heading
Mandatory
1
To indicate the start of a transaction set and to assign a control number
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).
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\
Data Element Summary
Data
Elemen Name
t
143
Transaction Set Identifier Code
329
Attributes
M
ID
Code uniquely identifying a Transaction Set.
820
X12.4 Payment Order/Remittance Advice
Transaction Set Control Number
M AN
3/3
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.
EFT Receivables Specs.DOC
Updated on 2/23/2012
Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:
Semantic Notes:
Comments:
Notes:
Examples:
DUKE
Ref.
Use
Des.
Must Use BPR01
Must Use BPR02
Must Use BPR03
Duke Energy Corporation
EFT Payments to Duke
X12 820 Payment Order / Remittance Advice format
Printed: 4/4/13
Page: 13
BPR Beginning Segment for Payment Order/Remittance Advice
020
Heading
Mandatory
1
(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
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.
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.
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.
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*5875.22*C*ACH*CTX*01*123456789*DA*12345678*3123123123**01*0
71000013*DA*5759838*19990322\
Data Element Summary
Data
Element Name
Attributes
305
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.
782
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. 99999999.99) 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 ($$$$$$$$¢¢).
478
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.
EFT Receivables Specs.DOC
Updated on 2/23/2012
DUKE
Ref.
Use
Des.
Must Use BPR04
Must Use BPR05
Must Use BPR06
Must Use BPR07
Must Use BPR08
Must Use BPR09
Must Use BPR10
Optional
BPR11
Duke Energy Corporation
EFT Payments to Duke
X12 820 Payment Order / Remittance Advice format
Printed: 4/4/13
Page: 14
Data
Element Name
Attributes
591
Payment Method Code
M ID
3/3
Code identifying the method for the movement of payment instructions
ACH
Automated Clearing House (ACH)
812
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”.
506
(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)
507
(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).
569
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
508
Account Number
X
AN 1/35
Account number assigned.
The Originator's account number.
509
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.
510
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.
EFT Receivables Specs.DOC
Updated on 2/23/2012
Must Use BPR12
506
Must Use BPR13
507
Must Use BPR14
569
Must Use BPR15
508
Must Use BPR16
373
Duke Energy Corporation
EFT Payments to Duke
X12 820 Payment Order / Remittance Advice format
Printed: 4/4/13
Page: 15
(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)
(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).
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
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.
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.
EFT Receivables Specs.DOC
Updated on 2/23/2012
Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:
Semantic Notes:
Comments:
Notes:
Examples:
Duke Energy Corporation
EFT Payments to Duke
X12 820 Payment Order / Remittance Advice format
Printed: 4/4/13
Page: 16
TRN Trace
035
Heading
Mandatory
1
To uniquely identify a transaction to an application.
1
2
3
TRN02 provides unique identification for the transaction.
TRN03 identifies an organization.
TRN04 identifies a further subdivision within the organization.
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\
Must Use TRN02
127
Optional
TRN03
509
Optional
TRN04
127
Data Element Summary
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.
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.
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.
EFT Receivables Specs.DOC
Updated on 2/23/2012
Segment:
Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:
Semantic Notes:
Comments:
Notes:
Examples:
DUKE
Use
Ref.
Des.
Must Use
N101
Must Use
N102
Optional
N103
Optional
N104
Optional
N105
Optional
N106
Duke Energy Corporation
EFT Payments to Duke
X12 820 Payment Order / Remittance Advice format
Printed: 4/4/13
Page: 17
N1 Name
070
N1
Heading
Mandatory
1
To identify a party by type of organization, name and code
1 At least one of N102 or N103 is required.
2 If either N103 or N104 is present, then the other is required.
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.
The first N1 loop in the heading area is used to identify the originating company
(Payer) for this remittance.
N1*PR*BILL PAYMENT SERVICE, INC.\
Data Element Summary
Data
Elemen Name
Attributes
t
98
Entity Identifier Code
M ID
2/2
Code identifying an organizational entity, a physical location, or an
individual
PR
Payer
93
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.
66
Identification Code Qualifier
X
ID
1/2
Code designating the system/method of code structure used for
Identification Code (67).
67
Identification Code
X
AN 2/80
Code identifying a party or other code.
706
Entity Relationship Code
O ID
2/2
Code describing entity relationship.
98
Entity Identifier Code
O ID
2/3
Code identifying an organizational entity, a physical location, or an
individual
EFT Receivables Specs.DOC
Updated on 2/23/2012
Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:
Semantic Notes:
Comments:
Notes:
Examples:
DUKE
Use
Ref.
Des.
Must Use
PER01
Must Use
PER02
Must Use
PER03
Must Use
PER04
Must Use
PER05
Must Use
PER06
Optional
Optional
Optional
PER07
PER08
PER09
Duke Energy Corporation
EFT Payments to Duke
X12 820 Payment Order / Remittance Advice format
Printed: 4/4/13
Page: 18
PER Administrative Communications Contact
120
N1
Heading
Mandatory
1
To identify a person or office to whom administrative communications should be directed
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.
This segment is optional, and not required for this application.
PER*CR*HENRY TREMBLECHIN*TE*1115551234*FX*1115554321\
Data Element Summary
Data
Elemen Name
Attributes
t
366
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
93
Name
O AN 1/35
Free-form name.
365
Communication Number Qualifier
O ID
2/2
Code identifying the type of communication number.
TE
Telephone
364
Communication Number
O AN 1/80
Complete communications number including country or area code when
applicable.
This element contains the telephone number.
365
Communication Number Qualifier
O ID
2/2
Code identifying the type of communication number.
EM
Electronic Mail
FX
Facsimile
364
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 E-mail identification.
365
Communication Number Qualifier
O ID
2/2
364
Communication Number
O AN
1/80
443
Contact Inquiry Reference
O AN
1/20
EFT Receivables Specs.DOC
Updated on 2/23/2012
Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:
Semantic Notes:
Comments:
Notes:
Examples:
DUKE
Use
Ref.
Des.
Must Use ENT01
Optional
ENT02
Optional
ENT03
Optional
ENT04
Optional
ENT05
Optional
ENT06
Optional
ENT07
Optional
ENT08
Optional
ENT09
Duke Energy Corporation
EFT Payments to Duke
X12 820 Payment Order / Remittance Advice format
Printed: 4/4/13
Page: 19
ENT Entity
010
ENT
Detail
Mandatory
1
To designate the entities which are parties to a transaction and specify a reference
meaningful to those entities
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.
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 Element Summary
Data
Elemen Name
Attributes
t
554
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.
98
Entity Identifier Code
O ID
2/3
Code identifying an organizational entity, a physical location, or an
individual
66
Identification Code Qualifier
O ID
1/2
Code designating the system/method of code structure used for
Identification Code (67).
67
Identification Code
O AN 2/80
Code identifying a party or other code.
Originating company sub-entity.
98
Entity Identifier Code
O ID
2/3
Code identifying an organizational entity, a physical location, or an
individual
66
Identification Code Qualifier
O ID
1/2
Code designating the system/method of code structure used for
Identification Code (67).
67
Identification Code
O AN 2/80
Code identifying a party or other code.
Receiving company sub-entity.
128
Reference Number Qualifier
X
ID
2/3
Code qualifying the Reference Number.
EM
Electronic Payment Reference Number (Confirmation#)
127
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.
EFT Receivables Specs.DOC
Updated on 2/23/2012
Segment: N1 Name
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:
Semantic Notes:
Comments:
Notes:
Examples:
DUKE
Use
Ref.
Des.
Must Use
N101
Must Use
N102
Optional
N103
Optional
N104
Optional
N105
Optional
N106
Duke Energy Corporation
EFT Payments to Duke
X12 820 Payment Order / Remittance Advice format
Printed: 4/4/13
Page: 20
070
N1
Heading
Mandatory
1
To identify a party by type of organization, name and code
1 At least one of N102 or N103 is required.
2 If either N103 or N104 is present, then the other is required.
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.
The second N1 loop in the Heading area is used to identify the receiving
company (Payee) for this remittance.
N1*PE*DUKE ENERGY CORPORATION\
Data Element Summary
Data
Elemen Name
Attributes
t
98
Entity Identifier Code
M ID
2/3
Code identifying an organizational entity, a physical location, or an
individual
PE
Payee
93
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
66
Identification Code Qualifier
X
ID
1/2
Code designating the system/method of code structure used for
Identification Code (67).
67
Identification Code
X
AN 2/80
Code identifying a party or other code.
706
Entity Relationship Code
O ID
2/2
Code describing entity relationship.
98
Entity Identifier Code
O ID
2/2
Code identifying an organizational entity, a physical location, or an
individual
EFT Receivables Specs.DOC
Updated on 2/23/2012
Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:
Semantic Notes:
Comments:
Notes:
Examples
DUKE
Use
Ref.
Des.
Must Use N101
Must Use N102
Optional
N103
Optional
N104
Optional
N105
Optional
N106
Duke Energy Corporation
EFT Payments to Duke
X12 820 Payment Order / Remittance Advice format
Printed: 4/4/13
Page: 21
N1 Individual or Organization Name
020
N1/ENT
Detail
Mandatory
1
To supply the full name of an individual or organizational entity.
1 At least one of N102 or N103 is required
2 If either N103 or N104 is present then the other is required.
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
define The first N1 loop in the Detail area is used to identify the paying company
(payer) for this remittance.
N1*PR*3*Stephen A Brookdale*FI*246649999\
Data Element Summary
Data
Elemen Name
Attributes
t
98
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
93
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.
66
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
67
Identification Code
X
AN 2/80
Code identifying a party or other code.
Customer's Social Security Number
706
Entity Relationship Code
X
ID
2/2
Code describing entity relationship.
98
Entity Identifier Code
O ID
2/3
Code identifying an organizational entity, a physical location, or an
individual
EFT Receivables Specs.DOC
Updated on 2/23/2012
Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:
Semantic Notes:
Comments:
Notes:
Examples:
DUKE
Use
Ref.
Des.
Must Use
PER01
Optional
PER02
Must Use
PER03
Must Use
PER04
Optional
PER05
Optional
PER06
Duke Energy Corporation
EFT Payments to Duke
X12 820 Payment Order / Remittance Advice format
Printed: 4/4/13
Page: 22
PER Administrative Communications Contact
120
N1
Detail
Mandatory
1
To identify a person or office to whom administrative communications should be directed
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.
PER*CA**TE*1115551234*FX*1115554321\
Data Element Summary
Data
Elemen Name
Attributes
t
366
Contact Function Code
M ID
2/2
Code identifying the major duty or responsibility of the person or group
named.
CA
Customer Account
93
Name
O AN 1/35
Free-form name.
365
Communication Number Qualifier
O ID
2/2
Code identifying the type of communication number.
TE
Telephone
364
Communication Number
O AN 1/80
Complete communications number including country or area code when
applicable.
This element contains the telephone number.
365
Communication Number Qualifier
O ID
2/2
Code identifying the type of communication number.
EM
Electronic Mail
FX
Facsimile
364
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 E-mail identification.
EFT Receivables Specs.DOC
Updated on 2/23/2012
Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:
Semantic Notes:
Comments:
Notes:
Examples:
DUKE
Use
Ref.
Des.
Must Use
RMR01
Must Use
RMR02
Must Use
RMR03
Must Use
RMR04
Not Used
RMR05
Not Used
RMR06
Not Used
Not Used
RMR07
RMR08
Duke Energy Corporation
EFT Payments to Duke
X12 820 Payment Order / Remittance Advice format
Printed: 4/4/13
Page: 23
RMR Remittance Advice Accounts Receivable Open Item Reference
150
RMR/ENT
Detail
Mandatory
l
1
To specify the accounts receivable open item(s) to be included in the cash application
and to convey the appropriate detail
1 If either RMR01 or RMR02 is present, then the other is required.
1 If RMR03 is present, it specifies how the cash is to be applied.
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.
Loop RMR provides a Customer Account Reference# and Payment Amount.
RMR*CR*12345678901*CR*137.00\
RMR*CR*12345678901*CR*45.00\
Data Element Summary
Data
Elemen Name
Attributes
t
128
Reference Number Qualifier
X
ID
2/3
Code qualifying the Reference Number.
CR
Customer Reference Number (Duke Energy
Account#)
127
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”.
482
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
782
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)
782
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.
782
Monetary Amount
O R
1/15
Amount of discount taken, which may be less than or equal to the
amount of discount permitted.
426
Adjustment Reason Code
X
782
Monetary Amount
* If you are formatting payment from EDI-810 – for RMR02 use REF from header when REF01=12.
EFT Receivables Specs.DOC
Updated on 2/23/2012
Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:
Semantic Notes:
Comments:
Notes:
Examples:
DUKE
Use
Ref.
Des.
Must Use
SE01
Must Use
SE02
Duke Energy Corporation
EFT Payments to Duke
X12 820 Payment Order / Remittance Advice format
Printed: 4/4/13
Page: 24
SE Transaction Set Trailer
010
Summary
Mandatory
1
To indicate the end of the transaction set and provide the count of the transmitted
segments (including the beginning (ST) and ending (SE) segments).
1
SE is the last segment of each transaction set.
SE*85*0001\
Data Element Summary
Data
Elemen Name
Attributes
t
96
Number of Included Segments
M N0 1/10
Total number of segments included in a transaction set including ST
and SE segments.
329
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.
EFT Receivables Specs.DOC
Updated on 2/23/2012
Duke Energy Corporation
EFT Payments to Duke
X12 820 Payment Order / Remittance Advice format
Printed: 4/4/13
Page: 25
All segments and fields listed are required
ISA01
ISA02
ISA03
ISA04
ISA05
ISA06
ISA07
ISA08
ISA09
ISA10
ISA11
ISA12
ISA13
ISA14
ISA15
ISA16
-----------Might occur multiple times (for each remittance advice)---------------------------------------à
GS01
GS02
GS03
GS04
GS05
GS06
GS07
GS08
ST01
ST02
BPR0
1
BPR0
2
BPR0
3
BPR0
4
BPR0
5
BPR0
6
BPR0
7
BPR0
8
BPR0
9
BPR1
0
BPR1
1
BPR1
2
BPR1
3
BPR1
4
BPR1
5
BPR1
6
TRN0
1
TRN0
2
N101
ISA SEGMENT – Only one of this segment can appear in the entire file
Authorization Information Qualifier
00
Authorization Information
Blank
Security Information Qualifier
00
Security Information
10 Blanks
Interchange ID Qualifier
ZZ
Interchange Sender ID
nnnnnnnnn
Interchange ID Qualifier
ZZ
Interchange Receiver ID
nnnnnnnnnnnn
Interchange Date
Date in YYMMDD format
Interchange Time
Time in hhmm format
Interchange Control Standards ID
U
Interchange Control Version Number
00401
Interchange Control Number
nnnnnnnnn
Acknowledgement Requested
0=No; 1=Yes Test Indicator
P(for Production)
Subelement Separator
* or any character per customer preference
GS SEGMENT –only one of this segment can appear in the entire file
Functional ID code
RA
Application Sender's Code
nnnnnnnnn
Application Receiver's Code
nnnnnnnnnnnn
Date
Date in YYMMDD format (same as ISA09)
Time
Time in hhmm format (same as ISA10)
Group Control Number
Build as JJJhhmmss where JJJ is julian date
Responsible Agency Code
X
Version/Rel. Ind. ID Code
004010
ST SEGMENT – at least one of this segment must appear in the output file
Transaction set ID code
820
Initial value is the value of GS06 field and it is increased by 1
Transaction set control number
with each new ST segment.
BPR SEGMENT – one for each ST segment must appear in the output file
Transaction Handling Code 305
C
Monetary Amount
No leading zeroes
Credit/Debit Flag Code
C - credit
Payment Method Code
ACH
Payment Format Code
CTX, PPD OR CCP (CIE = CTX)
Originating DFI ID Number Qualifier
01
Originating DFI ID Number
DFI Id Number
Account Number Qualifier Code
DA Demand Deposit (For Transactions not CTX)
03 Checking Account
SG Savings
Truncate to 2 positions if CTX
Account Number
Originator’s Financial Institution Account Number
Originating Company Identifier
ACH Company ID
Originating Company Supplemental
Not Used
Receiving DFI ID Number Qualifier
01
Receiving DFI ID Number
nnnnnnnnn - Duke bank ABA
Account Number Qualifier
DA - Demand Deposit Account
Account Number
####### - Duke bank account mnemonic
Effective Entry Date
Format: CCYYMMDD
TRN SEGMENT
Trace Type Code
Reference Number
Entity ID Code
‘1’ - Current Transaction Trace
Trace Number
N1 SEGMENT
‘PR’ – payer
EFT Receivables Specs.DOC
Updated on 2/23/2012
occur
multiple
times
RMR0
1
RMR0
2
RMR0
3
RMR0
4
SE01
SE02
GE01
GE02
IEA01
IEA02
Duke Energy Corporation
EFT Payments to Duke
X12 820 Payment Order / Remittance Advice format
Printed: 4/4/13
Page: 26
Reference Number Qualifier
CR = customer/bill account number
Reference Number
Duke account number (from customer bill or REF02 from REF
segment in EDI-810 header where REF01=”12”)
Payment Action Code
PO
Monetary Amount
Amount (Always positive; never negative)
SE SEGMENT
Number of included segments
nnnnnnnnnn
Transaction set control number
(same as ST02)
GE SEGMENT
Number of Transaction Sets Included in this
Number of ST-SE segment pairs in the entire file.
Function Group
Group Control Number
(same as GS06)
IEA SEGMENT
Number of Included Functional Groups
Always 1 – Only 1 ISA-IEA segment pair in the entire file
Interchange Control Number
(same as ISA13)
Sample EFT Payment Data - Indiana, Kentucky, Ohio
Example 1: This example represents the 820 as it would be sent from a Bill Payment Service to DUKE ENERGY.
EXAMPLE – IN, KY, OH
ST*820*131044727 Start of a transaction, assigned unique control number
BPR*C*200814.59*C*ACH*CTX*01*098765432*DA*111111111*5222222222**01*987654321*DA*123456789*110511
BPR01 - C – Payment accompanies remittance advice
BPR02 - 200814.59 = The Sum of all RMR04 segments
BPR03 - C – Credit Flag
BPR04 - ACH – Payment Method Code
BPR05 - CTX – Payment Format Code
BPR06 - 01 – Code identifying the type of identification number of DFI 01=ABA
BPR07 – 098765432 – Identification Number Originating banks transit routing number
BPR08 – DA Account Number Qualifier DA – Demand Deposit (03-checking, SG-savings)
BPR09 – 111111111 - The Originators Account number
BPR10 – 110511 - Originating Company Identifier followed by nine digits
BPR11 – 5222222222- A code between originating co and ODFI that identifies the co initiating the transfer
BPR12 – 01 - ID number qualifier – (note BPR 12-15 relate to the receiving depository fin institution)
BPR13 – 987654321 - Receiver’s bank transit routing number – Duke Energy EFT bank transit routing number
BPR14 – DA - Code identifying type of bank account – DA = Demand Deposit
BPR15 – 123456789 - The receiver’s Bank Account number
BPR16 – 110511- Date the originating company intends for the transaction to be settled
TRN*1*1514273 Reference number or identification number as defined for a particular Transaction Set
N1*PR*BillPay Service Co*1*006999528 Payer
PER*CA*Ms. Accounts Payable*TE*8125551212*EM*ap_dept@billpaysv.com Contact Information
ENT*01 A number assigned for differentiation within a transaction set.
N1*PE*DUKE ENERGY INDIANA INC*92*K0223595 - Payee
N1*PR*Cust Account Name Customer’s account name
RMR*CR*NNNNNNNNNNN*PO*11507.45 NNNNNNNNNNN Duke Energy Indiana account number and amount paid
RMR*CR*nnnnnnnnnnn*PO*453.46 NNNNNNNNNNN Duke Energy Account Number and amount paid
SE*11*131044727
EFT Receivables Specs.DOC
Updated on 2/23/2012
Duke Energy Corporation
EFT Payments to Duke
X12 820 Payment Order / Remittance Advice format
Printed: 4/4/13
Page: 28
Sample EFT Payment Data – Carolinas
Example 2: This example represents the 820 as it would be sent from a Bill Payment Service to DUKE ENERGY.
Example of a Carolinas Payment
ISA*00*
*00*
*ZZ*sender-id *ZZ*006996052250 *110516*0822*U*00200*090626580*0*P*^\
GS*RA*ROUTINGNO*006996052250*110516*0822*864082236*X*004010\
ST*820*136050512\ Start of a transaction, assigned unique control number
BPR*C*4576.66*C*ACH*CTX*01*ROUTINGNO*DA*BANKACCT*1234567890*110511*01*ROUTINGNO*DA*BANKACCT*110516\
BPR01 - C – Payment accompanies remittance advice
BPR02 – 4576.66 = The Sum of all RMR04 segments
BPR03 - C – Credit Flag
BPR04 - ACH – Payment Method Code
BPR05 - CTX – Payment Format Code
BPR06 - 01 – Code identifying the type of identification number of DFI 01=ABA
BPR07 – ROUTINGNO - Identification Number Originating banks transit routing number –
BPR08 – DA - Account Number Qualifier DA – Demand Deposit (03-checking, SG-savings)
BPR09 – BANKACCT - The Originators Account number
BPR10 – 1234567890 - Originating Company Identifier followed by nine digits
BPR11 – 110511 - A code between originating co and the ODFI that identifies the co initiating the transfer
BPR12 – 01 - ID number qualifier – (note BPR 12-15 relate to the receiving depository fin institution)
BPR13 – ROUTINGNO - Receiver’s bank transit routing number – Duke Energy EFT bank transit routing number
BPR14 – DA - Code identifying type of bank account – DA = Demand Deposit
BPR15 – BANKACCT - The receiver’s Bank Account number
BPR16 – 110516 - Date the originating company intends for the transaction to be settled
TRN*1*1774305\ Reference number or identification number as defined for a particular Transaction Set
N1*PR*SGS FKA IPP*ZZ*PAYER FROM ACH\ Payer
PER*IC*SGS CUSTOMER SERVICE*TE*(XXX) XXX-XXXX\ Customer contact info.
ENT*01\ A number assigned for differentiation within a transaction set.
N1*PE*DUKE ENERGY*1*DUKE POWER\ Payee
N1*PR*SGS FKA IPP*ZZ*PAYER FROM ACH\ Payer account name
RMR*CR*NNNNNNNNNN*PO*2310.22\ NNNNNNNNNN Duke Energy Carolinas Account Number and amount paid
RMR*CR*nnnnnnnnnn*PO*2266.44\ nnnnnnnnnn Duke Energy Carolinas Account Number and amount paid
SE*13*136050512\
GE*01*864082236
IEA*1*090626580
©2013 Duke Energy Corporation LU 4/13