810 Invoice. Introduction. Reference. General Notes. Page 2

Size: px
Start display at page:

Download "810 Invoice. Introduction. Reference. General Notes. Page 2"

Transcription

1 Duke Energy Implementation Guideline for E lectronic Data I nterchange TRANSACTION SET 810 Invoice Ver/Rel Outbound to Customer or Energy Service Provider

2 810 Invoice Introduction This implementation guide documents the EDI-810 transaction set that Duke Energy provides to its customers for accounts in the following states: Ohio Kentucky Indiana North Carolina South Carolina Reference The format and contents of this document are based on: Consumer Service Provider (CSP) Billing and Payment Guide Version 003 Release Invoice Transaction Set Section Version 1.0, June 1996 ASC X12 Finance Subcommittee Utility Industry Group Implementation Guideline for Electronic Data Interchange Transaction Set 810 Invoice Ver/Rel Version 1, June 7, 2000 General Notes Duke Energy provides invoices as a local distribution utility (LDC) for electric service in Indiana, Ohio, Kentucky, North Carolina, and South Carolina; and gas service in Ohio and Kentucky. At the current time Duke Energy invoices its customers from two separate billing system: Indiana, Kentucky, and Ohio North Carolina and South Carolina As such there are minor differences in the EDI-810 data segments. In the customary, regulated environment, the principal parties involved in this Transaction Set 810 implementation are: The utility (Code 8S or RE) which provides energy and services to the end use customer The end use customer (Code 8R or BT) In Ohio, Duke Energy also provides invoices to customers on behalf of alternative energy service providers where customers take their gas supply or electric generation service from an alternative provider. For these customers, Duke Energy accepts payment on behalf of alternative providers. Duke Energy identifies alternative providers on the Transaction Set 810 via the Code SJ on N1 Segment loops in the Heading Section. The primary processes addressed by this Transaction Set 810 are: Billing the end use customer for energy and services provided by the utility or by the ESP Page 2

3 Specific Notes EDI Billing EDI-820/Electronic Funds Transfer (EFT) is the method of payment for EDI Billing. Use of 810 as a Single Invoice Duke Energy s implementation of this transaction set is used to represent a single invoice for a single account. One account may contain multiple meters Functional Acknowledgment A Functional Acknowledgement (also referred to as a 997 transaction), is a requirement to confirm receipt of Duke Energy s EDI The Functional Acknowledgement is created by the trading partner, or the VAN working on behalf of the trading partner. Customers can use the Van connection, or a secure FTP connection. If a secure FTP connection is used to receive Duke Energy s EDI-810, the equivalent to a 997 transaction must be returned to Duke Energy. The Functional Acknowledgment confirms that an EDI transaction has been received and accepted by Duke Energy s trading partner and indicates the time and date of receipt. The Functional Acknowledgment shall constitute evidence that an Energy Bill has been received, but does not verify the Energy Bill s content. Interchange Control Number A unique and sequential interchange control number is used on every envelope that is transmitted to a trading partner. This approach allows the receiver to audit the interchange for any duplicate or missing transmissions. Use of the NTE Segment Although the UIG recommends that the NTE segment be avoided, there are occasions when Duke Energy is required by law or regulation to include messages or notices in all invoices. Duke Energy includes all billing messages that appear on customer bills via NTE segments. Use of the IT1 Segment An IT1 loop is used to accumulate all consumption and charge detail for a single meter or service. Each meter or service is detailed in a separate IT1 loop. IT1 loops are also used for unmetered services such as street lights, traffic signals, outdoor lights, etc and for agreements and payment plans. Use of the MEA Segment The MEA segment is used to convey consumption readings for one metering period. Use of the PID Segment The PID segment is used to convey required messages that apply to a particular service only. Use of the Detail IT1/REF Segment, Position 120 In addition to using SAC15 to describe charges and usage, Duke Energy uses IT1 loops to present account information. In some situations, REF segments are used to convey messages that are specific to a meter. Use of the SLN Segment The IT1/SLN segment is used to overcome the limitation on the number of IT1/SAC loops. In some situations, several charges or allowances are associated with one IT1. Use of the SLN segment provides for a mechanism to group individual SAC and related segments together. Page 3

4 Values in Elements SAC01 and SAC05 Previous editions of the EDI-810 guideline stated that the amount shown in SAC05 will always be positive and that the code used in SAC01 will indicate whether to add or subtract the SAC05 amount to or from the TDS. As a result of a clarification provided by X12F, it has been determined that the above statement is incorrect. The code used in SAC01 does not indicate the sign of the amount in SAC05. The amount shown in SAC05 may be either positive or negative; if negative, the minus sign, " - ", is transmitted. Duke Energy does set SAC01 to C when SAC05 is positive and Duke Energy sets SAC01 to A when SAC05 is negative. Use of Delimiters, Separators and Segment Terminators EDI-810 documents for Duke Energy use the following: Interconnect Mailbox Header IH12 ~ ~ ~ ~ ~ Element Separator ISA Char 4 * * Segment Terminator ISA Char 106 > > > > > Subelement Separator ISA16 : : : : : Stds ID ISA11 U U U U U Repeat Separator (Default) ISA11 ^ ^ ^ ^ ^ Note: To avoid data conflicts for the above characters and for the standard EDI defaults, if these characters appear in Indiana, Kentucky, and Ohio billing data (names, addresses, messages, etc) they are replaced with a similar character: Delimiter, Separator, Terminator Replaced with: ~ - / > ) : } \ / ^ = Page 4

5 810 Invoice Functional Group ID=IN Heading Pos. Seg. Req. Max Loop Notes and No. ID Name Des. Use Repeat Comments Must Use 010 ST Transaction Set Header M 1 Must Use 020 BIG Beginning Segment for Invoice M NTE Note/Special Instruction O CUR Currency O REF Reference Identification O 12 LOOP ID - N N1 Name O N2 Additional Name Information O N3 Address Information O N4 Geographic Location O REF Reference Identification O PER Administrative Communications Contact O ITD Terms of Sale/Deferred Terms of Sale O >1 212 BAL Balance Detail O >1 214 PAM Period Amount O >1 Detail Pos. Seg. Req. Max Loop Notes and No. ID Name Des. Use Repeat Comments LOOP ID - IT IT1 Baseline Item Data (Invoice) O TXI Tax Information O MEA Measurements O 40 LOOP ID - PID PID Product/Item Description O REF Reference Identification O >1 Must Use 150 DTM Date/Time Reference O 10 LOOP ID - SLN SLN Subline Item Detail O SAC Service, Promotion, Allowance, or Charge Information O TXI Tax Information O 10 LOOP ID - N N1 Name O N2 Additional Name Information O N3 Address Information O N4 Geographic Location O 1 Summary Pos. Seg. Req. Max Loop Notes and No. ID Name Des. Use Repeat Comments Must Use 010 TDS Total Monetary Value Summary M 1 LOOP ID - SAC SAC Service, Promotion, Allowance, or Charge Information O TXI Tax Information O CTT Transaction Totals O 1 n1 Must Use 080 SE Transaction Set Trailer M 1 Transaction Set Notes 1. Number of line items (CTT01) is the accumulation of the number of IT1 segments. Page 5

6 The following are layout specifications for EDI transmissions from Duke Energy, following Accredited Standards Committee X12 (ASC X12) Standards, preferably in Version 4, Release 1 (4010) or later as extended by the Utility Industry Group ( Files transmitted in X12 standard formats are referred to as Transaction Sets, and each different type of file is assigned a Transaction Set Id. 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 cannot 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). Page 6

7 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: Must Use ST Transaction Set Identifier Code M ID 3/3 Code uniquely identifying a Transaction Set 810 Invoice Must Use 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 Page 7

8 Page 8 Segment: BIG Beginning Segment for Invoice Position: 020 Loop: Level: Heading: Usage: Mandatory Max Use: 1 Purpose: To indicate the beginning of an invoice transaction set and to transmit identifying numbers and dates Syntax Notes: Semantic Notes: 1 BIG01 is the invoice issue date. Comments: 1 BIG07 is used only to further define the type of invoice when needed. Must Use BIG Date M DT 8/8 Date expressed as CCYYMMDD The transaction creation date. This is the date that the transaction was created by Duke Energy s billing system. Must Use BIG02 76 Invoice Number M AN 1/22 Identifying number assigned by issuer Unique invoice number identifying this bill. Duke Energy uses the customer s 11 digit account number (OH, KY, IN) or 10 digit account number (NC, SC) plus the date in BIG01 to insure uniqueness for each invoice. Duke Energy requires that the customer 10 or11 digit account number (depending on state) must be returned with payment. X BIG Date M DT 8/8 CCYYMMDD Date that the invoice data is translated into EDI-810 format. Recomm BIG Transaction Type Code O ID 2/2 Code specifying the type of transaction AI Adjusted Invoice Used when this is an adjusted invoice DI Debit Invoice FB Final Bill ME Memorandum PR SL Product or Service Summary Lease Bill Indicates summary bill An 810 is designed to show invoice information for one customer. The use of the SL code is not meant to imply that the 810 should be used as a summary of bills for more than one customer. Recomm BIG Transaction Set Purpose Code O ID 2/2 Code identifying purpose of transaction set (not used in NC & SC) 00 Original CO Corrected Reissue of an entire invoice. BIG Segment Examples: BIG DI 00 BIG ME 00 BIG FB 00 BIG DI CO BIG* * *****PR BIG* * *****FB

9 Segment: NTE Note/Special Instruction Position: 030 Loop: Level: Heading: Usage: Optional Duke Energy Utilization: Max Use: 100 Purpose: To transmit information in a free-form format, if necessary, for comment or special instruction Syntax Notes: Semantic Notes: Comments: 1 The NTE segment permits free-form information/data which, under ANSI X12 standard implementations, is not machine processable. Notes: Used for required messages and notices that are printed on the invoice. A PID segment is used to provide additional information within selected IT1 loops. NTE Note Reference Code O ID 3/3 Code identifying the functional area or purpose for which the note applies ADD Additional Information Utility-required messages or notices. Must Use NTE Description M AN 1/80 A free-form description to clarify the related data elements and their content If a bill message exceeds 80 characters, the message is continued in additional NTE segments. NTE Segment Examples: NTE ADD Last Payment: Payment Received NOV 17 NTE ADD Bill Prepared On NOV 24, 2010 NTE ADD Next meter reading date: Dec 28, 2010 NTE ADD Payments after this date not included Nov 24, 2010 NTE PMT Submit payment to Duke Energy OH NTE ADD Gas - Commercial Current Gas Charges - Gas Cost Recovery $ /CCF NTE ADD Electric - Commercial Current Electric Charges - Based on 85% of Previous NTE ADD Maximum Actual Demand of kw Billed in Sep 10. NTE ADD After: Dec 20, 2010 amount due is $ NTE ADD IMPORTANT- Your service may be disconnected if your past due amount of NTE ADD $8, is not paid before 12/16/2010. A reconnection charge will be NTE ADD required. For questions, please call the number shown above. NTE ADD PLEASE NOTE: A service deposit is being charged to your account because your NTE ADD service was previously disconnected for nonpayment. If your deposit has not yet NTE ADD been paid, please pay the stated deposit amount, by the due date indicated, in NTE ADD order to avoid disconnection. NTE ADD This bill contains final charges for gas service on Meter # NTE ADD This month's Gas Cost Recovery (GCR) charge for customers purchasing their NTE ADD natural gas from Duke Energy is $ per CCF, which includes a base GCR of NTE ADD $ and Ohio excise tax of $ Page 9

10 Segment: CUR Currency Position: 040 Loop: Level: Heading: Usage: Optional Duke Energy Utilization: Max Use: 1 Purpose: To specify the currency (dollars, pounds, francs, etc.) used in a transaction Syntax Notes: Semantic Notes: Comments: 1 See Figures Appendix for examples detailing the use of the CUR segment. Notes: Amounts are specified in the currency of the party that bills the end use customer. Must Use CUR01 98 Entity Identifier Code M ID 2/3 Code identifying an organizational entity, a physical location, property or an individual 85 Billing Provider Must Use CUR Currency Code M ID 3/3 Code (Standard ISO) for country in whose currency the charges are specified USD US Dollars Page 10

11 Segment: REF Reference Identification Position: 050 Loop: Level: Heading: Usage: Optional Duke Energy Utilization: Max Use: 12 Purpose: To specify identifying information Syntax Notes: 1 At least one of REF02 or REF03 is required. Semantic Notes: Comments: Must Use REF Reference Identification Qualifier M ID 2/3 Code qualifying the Reference Identification 12 Billing Account Utility-assigned account number for the end use customer. The Duke Energy 11 digit account number (OH, KY, IN) or 10 digit account number (NC, SC) as shown on a printed bill excluding dashes. If payment is communicated to Duke Energy by EDI-820 transaction this value must be placed into RMR02 in the EDI-820 document. REF Reference Identification X AN 1/30 Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier REF Segment (Header) Example: REF REF*AL* Page 11

12 Segment: N1 Name Position: 070 Loop: N1 Level: Heading: Usage: Optional Duke Energy Utilization: Max Use: 1 Purpose: To identify a party by type of organization, name, and code Syntax Notes: 1 N102 is required. Semantic Notes: Comments: 1 This segment, used alone, provides the most efficient method of providing organizational identification. Must Use N Entity Identifier Code M ID 2/3 8R Consumer Service Provider (CSP) Customer BT Bill To Party Used when directly billing the end use customer BY Customer supplied number RE Party to receive commercial invoice remittance Used if the remit-to party is not the Utility or the Energy Service Provider. MQ Metering Location SJ Service Provider Energy Service Provider N Name X AN 1/60 Free-form name Page 12

13 Segment: N2 Additional Name Information Position: 080 Loop: N1 Level: Heading: Usage: Optional Duke Energy Utilization: Max Use: 2 Purpose: To specify additional names or those longer than 60 characters in length Syntax Notes: Semantic Notes: Comments: 1 This segment follows an N1 segment (where N101 = BT ) if the customer name on the Duke Energy account overflows N102. Must Use N Name M AN 1/60 Free-form name N Name O AN 1/60 Free-form name Page 13

14 Segment: N3 Address Information Position: 090 Loop: N1 Level: Heading: Usage: Optional Duke Energy Utilization: Max Use: 2 Purpose: To specify the location of the named party Syntax Notes: Semantic Notes: Comments: 1 This segment follows an N1 segment: When N101 = BT, this segment contains the billing mail-to address from the customer s Duke Energy account When N101 = RE, this segment contains the Duke Energy remittance mail-to address. Must Use N Address Information M AN 1/55 Address information N Address Information O AN 1/55 Address information Page 14

15 Segment: N4 Geographic Location Position: 100 Loop: N1 Level: Heading: Usage: Optional Duke Energy Utilization: Max Use: 1 Purpose: To specify the geographic place of the named party Syntax Notes: Semantic Notes: Comments: 1 A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location. 2 This segment follows an N1 segment: When N101 = BT, this segment contains the billing mail-to address from the customer s Duke Energy account When N101 = RE, this segment contains the Duke Energy remittance mail-to address. N City Name O AN 2/30 Free-form text for city name N State or Province Code O ID 2/2 Code (Standard State/Province) as defined by appropriate government agency N Postal Code O ID 3/15 Code defining international postal zone code excluding punctuation and blanks (zip code for United States) N Country Code O ID 2/3 Code identifying the country Page 15

16 Segment: REF Reference Identification Position: 110 Loop: N1 Level: Heading: Usage: Optional Duke Energy Utilization: Max Use: 12 Purpose: To specify identifying information Syntax Notes: 1 At least one of REF02 or REF03 is required. Semantic Notes: Comments: Must Use REF Reference Identification Qualifier M ID 2/3 Code qualifying the Reference Identification 11 Account Number Energy Service Provider-assigned account number for the end use customer. REF Reference Identification X AN 1/30 Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier REF Segment (Header, N1 Loop) Example: REF*11* Page 16

17 Segment: PER Administrative Communications Contact Position: 120 Loop: N1 Level: Heading: Usage: Optional Duke Energy Utilization: Max Use: 3 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. 3 If either PER07 or PER08 is present, then the other is required. Semantic Notes: Comments: Must Use PER Contact Function Code M ID 2/2 Code identifying the major duty or responsibility of the person or group named CN General Contact Used for ESP contact information CR Customer Relations Used when customer has an assigned contact IC Information Contact Used for generic contact information (PER02 is not used) EA EDI Coordinator Identifies contact information for EDI related issues PER02 93 Name O AN 1/60 Free-form name PER Communication Number Qualifier X ID 2/2 Code identifying the type of communication number EM Electronic mail TE Telephone PER Communication Number X AN 1/80 Complete communications number including country or area code when applicable PER Segment Examples: PER IC TE PER CN Integrys Energy Services TE PER IC TE PER CR Mary Smith PER EA EDI TEAM EM summary@duke-energy.com Page 17

18 Segment: ITD Terms of Sale/Deferred Terms of Sale Position: 130 Loop: Level: Heading: Usage: Optional Duke Energy Utilization: Max Use: >1 Purpose: To specify terms of sale Syntax Notes: Semantic Notes: Comments: ITD Terms Net Due Date O DT 8/8 Date when total invoice amount becomes due, expressed in format CCYYMMDD Payment due date (if applicable). ITD Segment Example: ITD Page 18

19 Segment: BAL Balance Detail Position: 212 Loop: Level: Heading: Usage: Optional Duke Energy Utilization: Max Use: >1 Purpose: To identify the specific monetary balances associated with a particular account Syntax Notes: Semantic Notes: Comments: Must Use BAL Balance Type Code M ID 1/2 Code indicating the type of balance M Current Month Billed, payment, and balance amounts shown in BAL03 are in this billing period. Must Use BAL Amount Qualifier Code M ID 1/3 Code to qualify amount PB Billed Amount Total amount due on the period bill Must Use BAL Monetary Amount M R 1/18 Monetary amount BAL Segment Example: BAL M PB Page 19

20 Segment: PAM Period Amount Position: 214 Loop: Level: Heading: Usage: Optional Duke Energy Utilization: Max Use: >1 Purpose: To indicate a quantity, and/or amount for an identified period Syntax Notes: 1 If any of PAM01 PAM02 or PAM03 is present, then all are required. 2 PAM02 3 If either PAM06 or PAM07 is present, then the other is required. 4 If PAM07 is present, then PAM08 is required. 5 If PAM07 is present, then PAM06 is required. 6 If PAM08 is present, then PAM07 is required. Semantic Notes: Comments: Notes: This segment is used to provide historical consumption data PAM Quantity Qualifier X ID 2/2 Code specifying the type of quantity 99 Quantity Used Quantity of units used PAM Quantity X R 1/15 Numeric value of quantity Must Use PAM Unit or Basis for Measurement Code M ID 2/2 Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken HH Hundred Cubic Feet KH Kilowatt Hour PAM Unit of Time Period or Interval X ID 2/2 Code indicating the time period or interval AM Average Monthly MO Month PM Preceding 12 Months PAM Date/Time Qualifier X ID 3/3 Code specifying type of date or time, or both date and time MRR Meter Reading PAM Date X DT 8/8 Date expressed as CCYYMMDD PAM Segment Examples: PAM HH AM MRR PAM HH PM MRR PAM HH MO MRR PAM HH MO MRR PAM 99 0 HH MO MRR PAM 99 0 HH MO MRR PAM KH AM MRR PAM KH PM MRR PAM KH MO MRR PAM KH MO MRR Page 20

21 Segment: IT1 Baseline Item Data (Invoice) Position: 010 Loop: IT1 Level: Detail: Usage: Optional Duke Energy Utilization: Max Use: 1 Purpose: To specify the basic and most frequently used line item data for the invoice and related transactions Syntax Notes: 1 IT102 IT103 and IT104 are not used. 2 If either IT106 or IT107 is present, then the other is required. 3 if either IT108 or IT109 is present, then the other is required. 4 If either IT110 or IT111 is present, then the other is required. Semantic Notes: Comments: 1 Element 235/234 combinations should be interpreted to include products and/or services. 2 IT106 through IT125 provide for ten different product/service IDs for each item. Notes: 1 The typical usage of the IT1 entails including all usage and charges attributed to one meter; in this case, the IT1 loop is qualified with METER in the IT108/IT109 pair. IT Assigned Identification O AN 1/20 Alphanumeric characters assigned for differentiation within a transaction set Line item counter IT Quantity Invoiced X R 1/10 Number of units invoiced (supplier units) IT Unit or Basis of Measurement Code X ID 2/2 Code specifying the units in which a value is being expressed or manner in which a measurement has ben taken K1 KWH used ZZ N/A IT Unit Price X R 1/17 Price per unit of product, service, commodity, etc. IT Product/Service ID Qualifier X ID 2/2 Code identifying the type/source of the descriptive number used in Product/Service ID (234) SV Service Rendered IT Product/Service ID X AN 1/48 Identifying number for a product or service Examples: ELECTRIC GAS UNMETERED SERVICES MULTIPLE * * Will have other charges, credits, payment plans, taxes, etc. IT Product/Service ID Qualifier X ID 2/2 Code identifying the type/source of the descriptive number used in Product/Service ID (234) C3 Classification Page 21

22 IT Product/Service ID X AN 1/48 Identifying number for a product or service Examples: ACCOUNT METER BILLDET UNMET (To designate Unmetered Services) SUPCHG IT Product/Service ID Qualifier X ID 2/2 Code identifying the type/source of the descriptive number used in Product/Service ID (234) IT110 and IT111 are used only if IT109 = METER BS Bill Subgroup Code IT Product/Service ID X AN 1/48 Identifying number for a product or service Examples: Current Electric Charges Current Gas Charges IT Product/Service ID Qualifier X ID 2/2 Code identifying the type/source of the descriptive number used in Product/Service ID (234) Not used (reserved by UIG standard for equipment) IT Product/Service ID X AN 1/48 Identifying number for a product or service Not used (reserved by UIG standard for equipment) IT Product/Service ID Qualifier X ID 2/2 Code identifying the type/source of the descriptive number used in Product/Service ID (234) IT110 and IT111 are used only if IT109 = METER BS Bill Subgroup Code EK Settlement/Payout Option IT Product/Service ID X AN 1/48 Identifying number for a product or service Examples: a) Current Charges b) Prior Month(s) Charges c) Agreement Information d) Budget Billing Plan (BBP) Information e) Percentage of Income Payment Plan (PIPP) Plus IT Product/Service ID Qualifier X ID 2/2 Code identifying the type/source of the descriptive number used in Product/Service ID (234) GE Generic Name Description IT Product/Service ID X AN 1/48 Identifying number for a product or service Examples: a) Outdoor Lighting (OL) b) Unmetered Services c) Street Lights d) Summary Billing Information ###* e) Summary Bill Charges by Group f) Billing Charges by Type of Service * Three digits that identify groups of charges as previously requested by customer on Duke Energy s billing system IT1 Segment Examples: Duke Energy uses the IT1 loops to list and itemize products and services on the Customer s bill; for example: gas charges and usage, electric charges and usage, non-metered services, taxes, products, services, agreements/payments plans. See Appendix: Bill Examples at the end of this document. IT SV GAS C3 METER BS Current Charges Page 22

23 IT SV GAS C3 BILLDET BS Current Charges IT SV ELECTRIC C3 METER BS Current Charges IT SV ELECTRIC C3 BILLDET BS Current Charges IT SV ELECTRIC C3 UNMET BS Current Charges GE Outdoor Lighting (OL) IT SV GAS C3 BILLDET BS Prior Month(s) Charges IT SV GAS C3 METER BS Prior Month(s) Charges IT SV ELECTRIC C3 BILLDET BS Prior Month(s) Charges IT SV ELECTRIC C3 METER BS Prior Month(s) Charges IT SV ELECTRIC C3 BILLDET BS Current Electric Charges IT SV MULTIPLE C3 ACCOUNT BS Current Charges IT SV MULTIPLE C3 SUPCHG EK Agreement Information IT SV MULTIPLE C3 SUPCHG EK Budget Billing Plan (BBP) Information IT SV MULTIPLE C3 SUPCHG EK Percentage of Income Payment Plan (PIPP) Plus IT SV ELECTRIC C3 UNMET BS Current Charges GE Unmetered Services IT SV ELECTRIC C3 UNMET BS Current Charges GE Street Lights IT SV MULTIPLE C3 BILLDET BS Current Charges GE Summary Billing Information 000 IT SV MULTIPLE C3 BILLDET GE Summary Bill Charges by Group IT SV MULTIPLE C3 BILLDET GE Billing Charges by Type of Service IT1*3*30*K1*0**SV*ELECTRIC IT1*4*1618*KH*0**SV*ELECTRIC IT1*5*0*ZZ*0**SV*ELECTRIC Page 23

24 Segment: TXI Tax Information Position: 040 Loop: IT1 Level: Detail/IT1: Usage: Optional Duke Energy Utilization: Max Use: 10 Purpose: To specify tax information Syntax Notes: 1 At least one of TXI02 TXI03 or TXI06 is required. Semantic Notes: 1 TXI02 is the monetary amount of the tax. 2 TXI03 is the tax percent expressed as a decimal. 3 TXI07 is a code indicating the relationship of the price or amount to the associated segment. Comments: Notes: Duke Energy creates a separate IT1 loop for tax data with IT107 = MULTIPLE and IT109 = ACCOUNT. Taxes included in this position are account invoice level tax charges. Must Use TXI Tax Type Code M ID 2/2 Code specifying the type of tax ST = State SC = School CP = County FR = Franchise ZZ = Other or combination of above (Note: exception to ASC X12 Standards) TXI Monetary Amount X R 1/18 Monetary amount TXI Relationship Code O ID 1/1 Code indicating the relationship between entities A Add The amount in the TXI02 should be added when summing the invoice total. O Information Only The amount in the TXI02 should be ignored when summing the invoice total. TXI Segment Examples: TXI Assigned Identification O AN 1/20 Alphanumeric characters assigned for differentiation within a transaction set TXI CP 1.01 A Hamilton County Sale TXI ST A Indiana State Tax TXI CP 2.46 A Adams County Sales T TXI SC 0.02 A Rate Incr for School TXI FR 7.83 A Franchise Fee-Coving TXI ST A Kentucky State Tax TXI ZZ 2.27 A Tax on Gas Supplier TXI ST Page 24

25 Segment: MEA Measurements Position: 059 Loop: IT1 Level: Detail: Usage: Optional Duke Energy Utilization: Max Use: 40 Purpose: To specify physical measurements or counts, including dimensions, tolerances, variances, and weights Syntax Notes: 1 At least one of MEA03 MEA05 MEA06 or MEA08 is required. 2 If MEA05 is present, then MEA04 is required. 3 If MEA06 is present, then MEA04 is required. 4 If MEA07 is present, then at least one of MEA03 MEA05 or MEA06 is required. 5 Only one of MEA08 or MEA03 may be present. Semantic Notes: 1 MEA04 defines the unit of measure for MEA03, MEA05, and MEA06. Comments: 1 When citing dimensional tolerances, any measurement requiring a sign (+ or -), or any measurement where a positive (+) value cannot be assumed, use MEA05 as the negative (-) value and MEA06 as the positive (+) value. Notes: The MEA segment conveys metering data for one period. MEA Measurement Reference ID Code O ID 2/2 Code identifying the broad category to which a measurement applies AA Meter reading-beginning actual/ending actual AE Meter reading-beginning actual/ending estimated AN Work Period Actual BC Billed Actual EA Meter reading-beginning estimated/ending actual EE Meter reading-beginning estimated/ending estimated EL Electrical Characteristics TI Time MEA Measurement Qualifier O ID 1/3 Code identifying a specific product or process characteristic to which a measurement applies MU Multiplier PU Pressure Base RUD Usage Deviation (Applies to Kilowatt Hours, Kilowatt Demand and Reactive Demand) ZA Power Factor Relationship between watts and volt - amperes necessary to supply electric load ZD Load Factor Relationship between watt hours and watt demand necessary to supply electric load MEA Measurement Value X R 1/20 The value of the measurement Page 25

26 MEA04 C001 Composite Unit of Measure To identify a composite unit of measure Must Use C Unit or Basis for Measurement Code M ID 2/2 Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken CF Cubic Feet DA Days EA Each HH K1 K2 K4 KH Hundred Cubic Feet Kilowatt Demand Represents potential power load measured at predetermined intervals Kilovolt Amperes Reactive Demand Reactive power that must be supplied for specific types of customer's equipment; billable when kilowatt demand usage meets or exceeds a defined parameter Kilovolt Amperes Kilowatt Hour Recomm MEA Range Minimum X R 1/20 The value specifying the minimum of the measurement range Beginning reading Recomm MEA Range Maximum X R 1/20 The value specifying the maximum of the measurement range Ending reading or single reading (e.g., demand). MEA Measurement Significance Code O ID 2/2 Code used to benchmark, qualify or further define a measurement value 41 Off Peak 42 On Peak MEA Segment Examples: MEA TI 7 DA MEA AA HH MEA AA PU 1 HH MEA AA MU 160 KH MEA EE KH MEA EA MU 160 KH MEA EL ZA MEA AA PU 1 HH MEA AA MU 1 KH MEA MU 48 K1 MEA AN KH 42 MEA AN KH 41 MEA AN K1 42 MEA AN 1020 K1 41 MEA AA MU 300 K MEA TI DA 32 Page 26

27 Segment: PID Product/Item Description Position: 060 Loop: PID Level: Detail: Usage: Optional Duke Energy Utilization: Max Use: 1 Purpose: To describe a product or process in coded or free form format Syntax Notes: 1 At least one of PID04 or PID05 is required. Semantic Notes: Comments: 1 If PID01 equals "F", then PID05 is used. Notes: Used to provide required IT1 level billing messages. Must Use PID Item Description Type M ID 1/1 Code indicating the format of a description F Free-form PID Description X AN 1/80 A free-form description to clarify the related data elements and their content PID Segment Examples: PID F Old Rate Effective Dec 09 To Jan 04 PID F New Rate Effective Jan 04 To Jan 12 PID F CSN0 - Commercial Service PID F HDN0 - HLF Primary Direct Srv PID F HSN0 - High Load Factor Sec Srv PID F LSN0 - Low Load Factor Sec Srv PID F SMLC - Metered Outdoor Ltg Srv PID F SMS - Metered Signal Srv PID F SMHL - Metered Highway Ltg Srv PID F BBP Option: Annual BBP Installment Amount PID F BBP Option: Quarterly BBP Installment Amount Page 27

28 Segment: REF Reference Identification Position: 120 Loop: IT1 Level: Detail: Usage: Optional Duke Energy Utilization: Max Use: 12 Purpose: To specify identifying information Syntax Notes: 1 At least one of REF02 or REF03 is required. Semantic Notes: Comments: Notes: This segment contains information only when the IT1 loop is used to present account information and or meter related information Must Use REF Reference Identification Qualifier M ID 2/3 Code qualifying the Reference Identification AH Agreement BE MG NH RB Examples of REF03 entries Business Activity Meter not billed Meter serves multiple apartments Misc demand messages pertaining to meter Misc load factor messages pertaining to meter Status of current month information Etc. Meter Number Rate Code Number Identifies a utility rate class or tariff Duke Energy Rate Code Number Identifies an Energy Service Provider rate class REF Reference Identification X AN 1/30 Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier Account number Meter number Agreement number Rate Code REF Description X AN 1/80 A free-form description to clarify the related data elements and their content REF04 C040 Reference Identifier O To identify one or more reference numbers or identification numbers as specified by the Reference Qualifier REF Segment Examples (Detail section): REF AH REF BE Meter } Not Billed REF MG New Meter REF RB FE25 FirstEnergy Solutions-FirstEnergy Solutions REF NH GSL General Service-Large-Duke Energy REF RB IS06 IGS Energy-IGS Energy REF NH LSN0 Low Load Factor Sec Srv-Duke Energy REF RB DR16 Duke Energy Retail-Duke Energy Retail REF NH SOL Outdoor Lighting Srv-Duke Energy REF NH SOLU Outdoor Lighting Srv-Duke Energy REF NH DP01 Distribution Svc-Primary-Duke Energy Page 28

29 REF NH SULP Unmetered Outdoor Ltg Srv-Duke Energy REF NH HSN0 High Load Factor Sec Srv-Duke Energy REF NH DS01 Distribution Service-Duke Energy REF NH CSN0 Commercial Service-Duke Energy REF RB D200 DER 0% Discount-Duke Energy Retail REF NH FTL1 Firm Transportation-Large-Duke Energy REF NH GSL General Service-Large- Duke Energy REF NH OLF OL Flood Lighting-Duke Energy REF NH TL03 Traffic Light-Energy & Maint-Duke Energy REF BE Meter } Bill Dmnd 85% of Prev Max actl dmnd of kW 07/11 REF BE Meter } Billing demand reduced to attain min load factor of 71 hours use REF BE Meter } Billing Demand kw based on 90% of kva REF MG > REF RB GT> REF AL > Page 29

30 Segment: DTM Date/Time Reference Position: 150 Loop: IT1 Level: Detail: Usage: Required Max Use: 10 Purpose: To specify pertinent dates and times Syntax Notes: 1 At least one of DTM02 DTM03 or DTM05 is required. 2 If either DTM05 or DTM06 is present, then the other is required. Semantic Notes: Comments: Notes: This segment is required for all services Must Use DTM Date/Time Qualifier M ID 3/3 Code specifying type of date or time, or both date and time 150 Service Period Start Recommended by UIG. 151 Service Period End Recommended by UIG. LLP Date of off peak usage PPP Date of peak usage DTM Date X DT Date expressed as CCYYMMDD Use of DTM02/03 allows the translator to validate date and time. DTM Time X DT Time expressed as HHMMSS where HH ranges from 00 to 23 Use of DTM02/03 allows the translator to validate date and time. DTM Time Code X DT Code identifying the time LT Local Time DTM Segment Examples: DTM DTM DTM PPP LT Page 30

31 Segment: SLN Subline Item Detail Position: 200 Loop: SLN Level: Detail: Usage: Optional Duke Energy Utilization: Max Use: 1 Purpose: To specify product subline detail item data Syntax Notes: Semantic Notes: 1 SLN01 is the identifying number for the subline item. 2 SLN03 is the configuration code indicating the relationship of the subline item to the baseline item. Comments: 1 See the Data Element Dictionary for a complete list of IDs. 2 SLN01 is related to (but not necessarily equivalent to) the baseline item number. Example: 1.1 or 1A might be used as a subline number to relate to baseline number 1. Notes: The IT1/SLN segment is used to overcome the limitation on the number of IT1/SAC loops. Each SLN loop contains only one SAC and TXI. Multiple charges/allowances require multiple SLN loops. Must Use SLN Assigned Identification M AN 1/20 Alphanumeric characters assigned for differentiation within a transaction set Used as a loop counter Must Use SLN Relationship Code M ID 1/1 Code indicating the relationship between entities A Add Page 31

32 Page 32 Segment: SAC Service, Promotion, Allowance, or Charge Information Position: 230 Loop: SLN Level: Detail: Usage: Optional Duke Energy Utilization: Max Use: 25 Purpose: To request or identify a service, promotion, allowance, or charge; to specify the amount or percentage for the service, promotion, allowance, or charge Syntax Notes: 1 At least one of SAC02 or SAC03 is required. 2 If either SAC03 or SAC04 is present, then the other is required. 3 If either SAC06 or SAC07 is present, then the other is required. 4 If either SAC09 or SAC10 is present, then the other is required. Semantic Notes: 1 If SAC01 is "A" or "C", then at least one of SAC05, SAC07, or SAC08 is required. The value of the SAC01 indicator is not to be used to indicate the sign of the amount in SAC05. 2 SAC05 is the total amount for the service, promotion, allowance, or charge. If SAC05 is present with SAC07 or SAC08, then SAC05 takes precedence. 3 SAC08 is the allowance or charge rate per unit. 4 SAC10 and SAC11 used together indicate a quantity range, which could be a dollar amount that is applicable to service, promotion, allowance, or charge. Comments: Notes: Each SLN loop will contain only one SAC and TXI. Multiple charges/allowances require multiple SLN loops. IF SAC01 = A or C implies that the value in SAC05 accumulates to TDS01. IF SAC01 = C then SAC05 is a positive number. If SAC01 = A then SAC05 is a negative number and SAC05 contains a dash. Must Use SAC Allowance or Charge Indicator M ID 1/1 Code which indicates an allowance or charge for the service specified A Allowance SAC01 = A implies that the value in SAC05 accumulates to TDS01. When SAC01 = A then SAC05 is a negative number and SAC05 contains a dash. C Charge SAC01 = C implies that the value in SAC05 accumulates to TDS01. When SAC01 = C then SAC05 is a positive number. N No Allowance or Charge The amount in the SAC05 should be ignored when summing the invoice total. SAC Agency Qualifier Code X ID 2/2 Code identifying the agency assigning the code values EU Electric Utilities Duke Energy uses this code for both gas and electric data SAC Agency Service, Promotion, Allowance, or Charge Code X AN 1/10 Agency maintained code identifying the service, promotion, allowance, or charge The Utility Industry Group maintains this code list. See the UIG web site at for the most current listing of codes. SAC Amount O N2 1/15 Monetary amount When negative, the minus sign, " - ", is transmitted.

33 Page 33 SAC Rate O R 1/9 Rate expressed in the standard monetary denomination for the currency specified SAC Unit or Basis for Measurement Code X ID 2/2 Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken 99 Watt CF Cubic Feet EA Each HH Hundred Cubic Feet Ccf HR K1 K2 K3 K4 K7 KH UN Hours Kilowatt Demand Represents potential power load measured at predetermined intervals Kilovolt Amperes Reactive Demand Reactive power that must be supplied for specific types of customer's equipment; billable when kilowatt demand usage meets or exceeds a defined parameter Kilovolt Amperes Reactive Hour Represents actual electricity equivalent to kilowatt hours; billable when usage meets or exceeds defined parameters Kilovolt Amperes Kilowatt Kilowatt Hour Unit SAC Quantity X R 1/15 Numeric value of quantity SAC Reference Information X AN 1/80 Reference Information as defined for a particular Transaction Set or as specified by the Reference Information Qualifier Used as a sequencing number for non-billing party to sequence bill line items for printing the bill. SAC Description X AN 1/80 A free-form description to clarify the related data elements and their content SAC Segment (Detail) examples: SAC C EU ENC001 KH kwh Usage SAC C EU DMD007 K Actual kw On Peak SAC C EU BAS Distribution-Customer Chg SAC C EU DIS K Delivery Charges Distribution-Demand Chg SAC C EU MSC Delivery Riders SAC A EU CRE Shopping Credit SAC C EU TPI KH Supplier Generation Energy Chrg SAC A EU TPI Supplier 20% Discount SAC C EU ENC Energy Charge SAC C EU FUE Rider 60 - Fuel Adjustment SAC A EU MSC Rider 67 - Cinergy Merger Credit SAC N EU BUD Previous Budget Billing Balance SAC N EU BUD Budget Billing Balance (includes this bill) SAC N EU PAY Agreement Amount SAC N EU PAY Prior Amount Paid SAC N EU PAY Transfer From Current Billing SAC N EU PAY Number of Payments SAC*N**EU*MSC001*********ZZ**OPT-General-Optional Power Srv,TOU SAC*C**EU*BAS001*3651********06**Customer Charge SAC*N**EU*DMD000*****K1*552***ZZ**On-Peak Actual Demand(Summer) SAC*C**EU*DMD016*773242****K1*552***06**On-Peak Billing Demand Note: SAC detail segments for bill items associated with unmetered services, agreements, budget billing, payment plans, and summary bill synopsis items all have SAC01 = N. The billing impacts for these items are included as chargeable SAC segments in the summary section of the EDI-810 document.

34 Segment: N1 Name Position: 240 Loop: N1 Level: Detail/IT1: Usage: Optional Duke Energy Utilization: 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. 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 This segment is used to identify the account name for detailed bills that are consolidated into a summary bill Must Use N Entity Identifier Code M ID 2/3 Code identifying an organizational entity, a physical location, property or an individual 8R Consumer Service Provider (CSP) Customer End use Customer name on Duke Account 8S Consumer Service Provider (CSP) Duke Energy MQ Metering Location N Name X AN 1/60 Free-form name N1 Segment (Detail) example (Metering Location): N1*MQ*ABC Company Page 34

35 Segment: N2 Additional Name Information Position: 250 Loop: N1 Level: Detail: Usage: Optional Duke Energy Utilization: Max Use: 2 Purpose: To specify additional names or those longer than 60 characters in length Syntax Notes: Semantic Notes: Comments: 1 This segment is used to identify the account name for detailed bills that are consolidated into a summary bill 2 This segment follows an N1 segment (where N101 = 8R ) if the customer name on the Duke Energy account overflows N102. Must Use N Name M AN 1/60 Free-form name N Name O AN 1/60 Free-form name Page 35

36 Segment: N3 Address Information Position: 260 Loop: N1 Level: Detail: Usage: Optional Duke Energy Utilization: Max Use: 2 Purpose: To specify the location of the named party Syntax Notes: Semantic Notes: Comments: 1 This segment is used to identify the account address information for detailed bills that are consolidated into a summary bill 2 This segment follows an N1 segment (where N101 = 8R ) if the customer name on the Duke Energy account overflows N102. Notes: Service Address Must Use N Address Information M AN 1/55 Address information N Address Information O AN 1/55 Address information Page 36

37 Segment: N4 Geographic Location Position: 270 Loop: N1 Level: Detail: Usage: Optional Duke Energy Utilization: Max Use: 1 Purpose: To specify the geographic place of the named party Syntax Notes: 1 If N406 is present, then N405 is required. Semantic Notes: Comments: 1 A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location. 2 N402 is required only if city name (N401) is in the U.S. or Canada. 3 This segment is used to identify the address information for detailed bills that are consolidated into a summary bill 4 This segment follows an N1 segment (where N101 = 8R ) if the customer name on the Duke Energy account overflows N102. Notes: Service address N City Name O AN 2/30 Free-form text for city name N State or Province Code O ID 2/2 Code (Standard State/Province) as defined by appropriate government agency N Postal Code O ID 3/15 Code defining international postal zone code excluding punctuation and blanks (zip code for United States) N Country Code O ID 2/3 Code identifying the country N Location Qualifier X ID 1/2 Code identifying type of location CO County/Parish and State N Location Identifier O AN 1/30 Code which identifies a specific location Page 37

38 Segment: TDS Total Monetary Value Summary Position: 010 Loop: Level: Summary: Usage: Mandatory Max Use: 1 Purpose: To specify the total invoice discounts and amounts Syntax Notes: Semantic Notes: 1 TDS01 is the total amount of invoice (including charges, less allowances) before terms discount (if discount is applicable). Comments: Notes: TDS01 is the total amount due for this invoice and it equals the algebraic sum of the amounts in TXI02 and SAC05 (where SAC01 is equal to A or C). If this amount is negative, it includes a minus sign. Must Use TDS Amount M N2 1/15 Monetary amount Page 38

39 Segment: SAC Service, Promotion, Allowance, or Charge Information Position: 040 Loop: SAC Level: Summary: Usage: Optional Duke Energy Utilization: Max Use: 1 Purpose: To request or identify a service, promotion, allowance, or charge; to specify the amount or percentage for the service, promotion, allowance, or charge Syntax Notes: 1 At least one of SAC02 or SAC03 is required. 2 If either SAC03 or SAC04 is present, then the other is required. 3 If either SAC06 or SAC07 is present, then the other is required. 4 If either SAC09 or SAC10 is present, then the other is required. Semantic Notes: 1 If SAC01 is "A" or "C", then at least one of SAC05, SAC07, or SAC08 is required. The value of the SAC01 indicator is not to be used to indicate the sign of the amount in SAC05. 2 SAC05 is the total amount for the service, promotion, allowance, or charge. If SAC05 is present with SAC07 or SAC08, then SAC05 takes precedence. 3 SAC08 is the allowance or charge rate per unit. 4 SAC10 and SAC11 used together indicate a quantity range, which could be a dollar amount that is applicable to service, promotion, allowance, or charge. Comments: Notes: Account/Invoice level charges and allowances. IF SAC01 = A or C implies that the value in SAC05 accumulates to TDS01. IF SAC01 = A then SAC05 is a positive number. If SAC01 = C then SAC05 is a negative number and SAC05 contains a dash. Page 39 Must Use SAC Allowance or Charge Indicator M ID 1/1 Code which indicates an allowance or charge for the service specified A Allowance SAC01 = A implies that the value in SAC05 accumulates to TDS01. When SAC01 = A then SAC05 is a negative number and SAC05 contains a dash. C Charge SAC01 = C implies that the value in SAC05 accumulates to TDS01. When SAC01 = C then SAC05 is a positive number. N No Allowance or Charge The amount in the SAC05 should be ignored when summing the invoice total. SAC Agency Qualifier Code X ID 2/2 Code identifying the agency assigning the code values EU Electric Utilities Duke Energy uses this code for both gas and electric data SAC Agency Service, Promotion, Allowance, or X AN 1/10 Charge Code Agency maintained code identifying the service, promotion, allowance, or charge The Utility Industry Group maintains this code list. See the UIG web site at for the most current listing of codes. SAC Amount O N2 1/15 Monetary amount

40 When negative, the minus sign, " - ", is transmitted. SAC Rate O R 1/9 Rate expressed in the standard monetary denomination for the currency specified SAC Unit or Basis for Measurement Code X ID 2/2 Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken 99 Watt CF Cubic Feet Ccf EA Each HH Hundred Cubic Feet HR K1 K2 K3 K4 K7 KH UN Hours Kilowatt Demand Represents potential power load measured at predetermined intervals Kilovolt Amperes Reactive Demand Reactive power that must be supplied for specific types of customer's equipment; billable when kilowatt demand usage meets or exceeds a defined parameter Kilovolt Amperes Reactive Hour Represents actual electricity equivalent to kilowatt hours; billable when usage meets or exceeds defined parameters Kilovolt Amperes Kilowatt Kilowatt Hour Unit SAC Quantity X R 1/15 Numeric value of quantity SAC Description X AN 1/80 A free-form description to clarify the related data elements and their content SAC Segment Examples (Summary Section): SAC C EU BAS Amt Due - Previous Bill SAC A EU BAS Payment(s) Received SAC C EU LPC Late Payment Charge(s) SAC C EU DAB Deposit Amt Due SAC C EU LPC Late Payment Charge(s) SAC A EU ADJ Canceled Charges: Electric Charges SAC A EU ADJ Canceled Charges: Gas Charges SAC C EU BAS Current Electric Charges SAC A EU ADJ Net Metering Adj SAC C EU SUR TAXES SAC C EU MSC Other Credits/Charges SAC A EU TRS Trans Credit From Summ Acct SAC C EU ODL Current OL Charges SAC C EU IBC Gas Balancing Charge SAC C EU SUR State Tax SAC C EU PAY PIPP Plus Monthly Amt Due SAC A EU PAY PIPP Plus Adjustment SAC A EU CRE PwrSh Capacity Premium SAC C EU PAY Agmt # Amt Due SAC A EU PAY Transfer to Agmt # SAC C EU PAY Agmt # Amt Due Page 40

41 Segment: TXI Tax Information Position: 050 Loop: IT1 Level: Summary: Usage: Optional Duke Energy Utilization: Max Use: 10 Purpose: To specify tax information Syntax Notes: 1 At least one of TXI02 TXI03 or TXI06 is required. Semantic Notes: 1 TXI02 is the monetary amount of the tax. 2 TXI03 is the tax percent expressed as a decimal. 3 TXI07 is a code indicating the relationship of the price or amount to the associated segment. Comments: Notes: Taxes included in this position relate to the immediately preceding SAC charges. Must Use TXI Tax Type Code M ID 2/2 Code specifying the type of tax ZZ = Other (Note: exception to ASC X12 Standards) TXI Monetary Amount X R 1/18 Monetary amount TXI Relationship Code O ID 1/1 Code indicating the relationship between entities A Add The amount in the TXI02 should be added when summing the invoice total. O Information Only The amount in the TXI02 should be ignored when summing the invoice total. TXI Segment Examples: TXI Assigned Identification O AN 1/20 Alphanumeric characters assigned for differentiation within a transaction set TXI ZZ 2.27 A Tax Page 41

42 Segment: CTT Transaction Totals Position: 070 Loop: Level: Summary: Usage: Optional Duke Energy Utilization: Max Use: 1 Purpose: To transmit a hash total for a specific element in the transaction set Syntax Notes: Semantic Notes: Comments: 1 This segment is intended to provide hash totals to validate transaction completeness and correctness. Must Use CTT Number of Line Items M N0 1/6 Total number of line items in the transaction set The number of IT1 segments. Page 42

43 Segment: SE Transaction Set Trailer Position: 080 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. 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 Page 43

44 Appendix: Bill Examples Ohio, Kentucky Indiana Bill name & address: BIG DI 00 N1 BT AB COMPANY N3 PO BOX 1212 N4 NASHVILLE TX N1 RE DUKE ENERGY N3 PO BOX 1326 N4 CHARLOTTE NC N1 MQ AB COMPANY N MAIN ST N4 CINCINNATI OH PER IC TE PER CR Mary Smith PER EA EDI TEAM EM Ohio, Kentucky Indiana Bill Charges Summary: TDS SAC C EU BAS Amt Due - Previous Bill SAC A EU BAS Payment(s) Received CTT 5 SE Page 44

45 Ohio Kentucky Indiana Monthly Usage Summary: PAM HH AM MRR PAM HH PM MRR PAM HH MO MRR PAM HH MO MRR PAM HH MO MRR PAM HH MO MRR PAM HH MO MRR PAM HH MO MRR PAM HH MO MRR PAM HH MO MRR PAM HH MO MRR PAM HH MO MRR PAM HH MO MRR PAM HH MO MRR PAM HH MO MRR PAM KH AM MRR PAM KH PM MRR PAM KH MO MRR PAM KH MO MRR PAM KH MO MRR PAM KH MO MRR PAM KH MO MRR PAM KH MO MRR PAM KH MO MRR PAM KH MO MRR PAM KH MO MRR PAM KH MO MRR PAM KH MO MRR PAM KH MO MRR PAM KH MO MRR Page 45

46 Ohio, Kentucky Indiana, Current Usage Detail (Electric): IT SV ELECTRIC C3 METER BS Current Charges MEA TI DA 29 MEA EL ZA 91.7 REF MG DTM DTM SLN 0001 A SAC C EU ENC001 KH kwh Usage SLN 0002 A SAC C EU DMD007 K Actual kw On Peak SLN 0003 A SAC C EU DMD004 K Actual kva On Peak IT SV ELECTRIC C3 BILLDET BS Current Charges REF NH Duke Energy Rate DP01 - Distribution Svc-Primary SLN 0001 A SAC C EU BAS Distribution-Customer Chg SLN 0002 A SAC C EU DIS K Delivery Charges Distribution-Demand Chg SLN 0003 A SAC C EU MSC Delivery Riders SLN 0004 A SAC A EU CRE Shopping Credit IT SV ELECTRIC C3 BILLDET BS Current Charges REF RB Duke Energy Retail Rate D200 - DER 20% Discount SLN 0001 A SAC C EU TPI K Supplier Generation Demand Chrg SLN 0002 A SAC C EU TPI KH Supplier Generation Energy Chrg SLN 0003 A SAC C EU TPI KH Supplier Generation Energy Chrg SLN 0004 A SAC C EU MSC Supplier FPP SLN 0005 A SAC C EU MSC Supplier AAC SLN 0006 A SAC C EU MSC Supplier TCR SLN 0007 A SAC A EU TPI Supplier 20% Discount Page 46

47 Ohio, Kentucky Indiana Current Usage Detail (Outdoor Lighting): IT SV ELECTRIC C3 UNMET BS Current Charges GE Outdoor Lighting (OL) REF NH Duke Energy Rate SOL - Outdoor Lighting Srv SLN 0001 A SAC C EU ENC Energy Charge SLN 0002 A SAC C EU FUE Rider 60 - Fuel Adjustment SLN 0003 A SAC C EU MSC Rider 61 - Coal Gasification Adj SLN 0004 A SAC C EU MSC Rider 62 - Pollution Cntl Adj SLN 0005 A SAC C EU MSC Rider 63 - Emission Allowance SLN 0006 A SAC A EU MSC Rider 67 - Cinergy Merger Credit SLN 0007 A SAC C EU MSC Rider 68 - Midwest Ind Sys Oper Adj SLN 0008 A SAC C EU MSC Rider 71 - Clean Coal Adjustment Ohio Kentucky Indiana Current Usage Detail (Agreement Information): IT SV MULTIPLE C3 SUPCHG EK Agreement Information REF AH DTM D8 SLN 0001 A SAC N EU PAY Number of Payments SLN 0002 A SAC N EU PAY Agreement Amount SLN 0003 A SAC N EU PAY Prior Amount Paid SLN 0004 A SAC N EU PAY Agreement Balance SLN 0005 A SAC N EU PAY Previous Agreement Balance SLN 0006 A SLN 0007 A SAC N EU PAY Current Agreement Amount Due SLN 0008 A SAC N EU PAY Monthly Amount Due Page 47

48 Ohio Kentucky Indiana Current Usage Detail (Budget Billing Summary): IT SV MULTIPLE C3 SUPCHG EK Budget Billing Plan (BBP) Information PID F BBP Option: Quarterly BBP Installment Amount SLN 0001 A SAC N EU BUD Previous Budget Billing Balance SLN 0002 A SAC N EU BUD Budget Billing Balance (includes this bill) SLN 0003 A SAC N EU BUD Transfer to Budget Billing SLN 0004 A SAC N EU BAS Current Gas Charges SLN 0005 A SAC N EU BAS Current Electric Charges SLN 0006 A SAC N EU BUD Budget Billing Amt Due Page 48

810 Invoice ANSI ASC X12 Version 4010

810 Invoice ANSI ASC X12 Version 4010 810 Invoice ANSI ASC X12 Version 4010 ERICO International 31700 Solon Rd. Solon, OH 44139 7/15/2009 Purchase Order Acknowledgment Invoice-810-855 ii 7/15/2009 Purchase Order Acknowledgment Invoice-810-855

More information

Portland General Electric Implementation Standard

Portland General Electric Implementation Standard Portland General Electric Implementation Standard for Electronic Data Interchange TRANSACTION SET 810 Ver/Rel 004010 Invoice Inbound from Vendor 8104010I 1 August 18, 2004 810 Invoice Functional Group

More information

ADOBE ANSI X12 810 4010. Version: 1.0

ADOBE ANSI X12 810 4010. Version: 1.0 ADOBE ANSI X12 810 4010 Version: 1.0 Author: Adobe Systems Modified: 06/15/2009 810 Invoice Functional Group=IN This Draft Standard for Trial Use contains the format and establishes the data contents of

More information

810 Invoice Revised 01/26/15

810 Invoice Revised 01/26/15 Functional Group ID=IN Introduction: This Standard contains the format and establishes the data contents of the Invoice Transaction Set (810) for use within the context of an Electronic Data Interchange

More information

850 Purchase Order. X12/V4030/850: 850 Purchase Order. Version: 1.0 Draft

850 Purchase Order. X12/V4030/850: 850 Purchase Order. Version: 1.0 Draft 850 Purchase Order X12/V4030/850: 850 Purchase Order Version: 1.0 Draft Author: Supplier Automation Trading Partner: Ross Stores, Inc. Notes: This is the standard guide prepared by JPMC/Xign for Merchandise

More information

ANSI X12 version 4010 856 Advance Ship Notice

ANSI X12 version 4010 856 Advance Ship Notice ANSI X12 version 4010 856 Advance Ship Notice VERSION: 1.0 FINAL Author: Superior Essex Publication Date: 05/01/07 Trading Partner: All 856 All Partners 4010 Outbound.rtf 1 856 Ship Notice/Manifest Functional

More information

ANSI X12 version 4010 820 Remittance Advice

ANSI X12 version 4010 820 Remittance Advice ANSI X12 version 4010 820 Remittance Advice VERSION: 1.0 FINAL Author: Superior Essex Publication Date: 08/18/00 Trading Partner: All Notes: Remittance Advice 820's are transmitted with payment to the

More information

Customer EDI Guidelines United States 810 Invoice

Customer EDI Guidelines United States 810 Invoice Customer EDI Guidelines United States 810 Invoice Author: CSC Consulting EMD 810_USA.doc 1 For internal only 810 Invoice Functional Group=IN This Draft Standard for Trial Use contains the format and establishes

More information

CVS/Caremark. Implementation Guide. 810 RX DC Invoice. Version X12-4010

CVS/Caremark. Implementation Guide. 810 RX DC Invoice. Version X12-4010 CVS/Caremark Implementation Guide 810 RX DC Invoice Version X12-4010 810 Mapping Specifications v4010 i Table of Contents 810 Invoice... 1 ST Transaction Set Header... 2 BIG Beginning Segment for Invoice...

More information

3/31/08 ALTRA INDUSTRIAL MOTION Invoice - 810. Inbound 810 X12 4010. Page 1 Created by Ralph Lenoir

3/31/08 ALTRA INDUSTRIAL MOTION Invoice - 810. Inbound 810 X12 4010. Page 1 Created by Ralph Lenoir Inbound 810 X12 4010 Page 1 DOCUMENT OVERVIEW This document contains the requirements for the standard EDI 810 document in ANSI version 4010 as d by ALTRA INDUSTRIAL MOTION. It describes the layout, syntax,

More information

EDI 210 Invoice. Motor Freight 210 Invoice with Stop Offs. Version: 1.0 ANSI X.12-4010 Draft

EDI 210 Invoice. Motor Freight 210 Invoice with Stop Offs. Version: 1.0 ANSI X.12-4010 Draft EDI 210 Invoice Motor Freight 210 Invoice with Stop Offs Version: 1.0 ANSI X.12-4010 Draft Motor Freight Invoice 210 EDI Transaction. ANSI X.12 Standards Version 4010 1 Table of Contents 210 Motor Carrier

More information

810 Invoice. Introduction: Heading: Functional Group ID=IN

810 Invoice. Introduction: Heading: Functional Group ID=IN 810 Invoice Functional Group ID=IN Introduction: This Draft Standard for Trial Use contains the format and establishes the data contents of the Invoice Transaction Set (810) for use within the context

More information

2.8 861 Receiving Advice/Acceptance Certificate - SERVICE PARTS ONLY

2.8 861 Receiving Advice/Acceptance Certificate - SERVICE PARTS ONLY 2.8 861 Receiving Advice/Acceptance Certificate - SERVICE PARTS ONLY INFORMATION TMM REQUIRES FROM TRADING PARTNER SCOPE THIS INFORMATION INCLUDES START-UP INFORMATION SPECIFIC TO TRADING PARTNER. APPROACH

More information

Implementation Guidelines: ANSI X12 Transaction Set 850 Purchase Order (Suppliers) DOCUMENT NUMBER: ICS 004010 850 S Supplier

Implementation Guidelines: ANSI X12 Transaction Set 850 Purchase Order (Suppliers) DOCUMENT NUMBER: ICS 004010 850 S Supplier Implementation Guidelines: ANSI X12 Transaction Set 850 (Suppliers) DOCUMENT NUMBER: ICS 004010 850 S Supplier ESSAR Steel Algoma Inc. Information Systems and Business Process Improvement Author: Greg

More information

EDI GUIDELINES INVOICE 810 VERSION 4010

EDI GUIDELINES INVOICE 810 VERSION 4010 EDI GUIDELINES INVOICE 810 VERSION 4010 Rev. 7/23/2013 GLOSSARY OF TERS Seg. Use: Reference : Number: : Consists of a segment identifier, one or more data element each preceded by an element separator,

More information

810 Invoice. Version: 2.3 Final. X12/V4010/810 : 810 Invoice. Advance Auto Parts. Publication: 3/17/2014 Trading Partner: Notes:

810 Invoice. Version: 2.3 Final. X12/V4010/810 : 810 Invoice. Advance Auto Parts. Publication: 3/17/2014 Trading Partner: Notes: 810 Invoice X12/V4010/810 : 810 Invoice Version: 2.3 Final Author: Advance Auto Parts Company: Advance Auto Parts Publication: 3/17/2014 Trading Partner: Notes: Table of Contents 810 Invoice... 1 ISA

More information

ANSI X12 version 4010 864 Text Message

ANSI X12 version 4010 864 Text Message ANSI X12 version 4010 864 Text Message VERSION: 1.0 FINAL Author: Superior Essex Publication Date: 08/22/00 Trading Partner: All Partners 864 All Partners 4010 Inbound.rtf 1 Superior Essex 864 Text Message

More information

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

Electronic Data Interchange- Inbound Payments EDI 820/EFT Specifications for Duke Energy 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

More information

Invoice. Transaction Set (810) (Outbound from TI)

Invoice. Transaction Set (810) (Outbound from TI) Invoice Transaction Set (810) (Outbound from TI) ANSI X12 Version Format: 3020 Date: October 1996 Copyright 1996 Texas Instruments Inc. All Rights Reserved The information and/or drawings set forth in

More information

BORGWARNER IMPLEMENTATION GUIDELINE FOR V4010 830 PLANNING SCHEDULE

BORGWARNER IMPLEMENTATION GUIDELINE FOR V4010 830 PLANNING SCHEDULE BORGWARNER IMPLEMENTATION GUIDELINE FOR V4010 830 PLANNING SCHEDULE 1 Implementation Guideline 830 3-Jun-15 830 BorgWarner Material Release v004010 Functional Group ID=PS Introduction: This Standard contains

More information

ANSI X12 4010 867 - Product Transfer and Resale Report

ANSI X12 4010 867 - Product Transfer and Resale Report ANSI X12 4010 867 - Product Transfer and Resale Report Version: R8674010v1 Draft Modified: 10/27/2004 Notes: 10/26/2004 - In an effort to validate that 100% of a partners reporting locations have been

More information

Implementation Guideline

Implementation Guideline Pennsylvania New Jersey Delaware Maryland Implementation Guideline For Electronic Data Interchange TRANSACTION SET 814 Advance Notice of Intent to Drop Request and Response Ver/Rel 004010 814 Advance Notice

More information

ANSI X12 version 4010 830 Planning Schedule with Release Capability

ANSI X12 version 4010 830 Planning Schedule with Release Capability ANSI X12 version 4010 830 Planning Schedule with Release Capability VERSION: 1.0 FINAL Author: Superior Essex Publication Date: 04/07/00 Trading Partner: All 830 All Partners 4010 Inbound.rtf 1 830 Planning

More information

ACE HARDWARE 810 INVOICE (FOR CREDIT MEMO ONLY) ANSI X12 4010 PLEASE DO NOT TRANSMIT WAREHOUSE OR REBATE CREDIT MEMOS.

ACE HARDWARE 810 INVOICE (FOR CREDIT MEMO ONLY) ANSI X12 4010 PLEASE DO NOT TRANSMIT WAREHOUSE OR REBATE CREDIT MEMOS. ACE HARDWARE 810 INVOICE (FOR CREDIT MEMO ONLY) ANSI X12 4010 *NOTES: PLEASE DO NOT TRANSMIT WAREHOUSE OR REBATE CREDIT MEMOS. EXISTING DOCUMENT - SEE HIGHLIGHTED FIELDS FOR NEW ADDITIONS PLEASE REVIEW

More information

EDI GUIDELINES. Motor Carrier Load Tender 204 VERSION 004010

EDI GUIDELINES. Motor Carrier Load Tender 204 VERSION 004010 EDI GUIDELINES otor Carrier Load Tender 204 VERSION 004010 ASC X12 Version 4010 1 April 5, 2007 204 otor Carrier Load Tender Functional Group ID=S Introduction: This Draft Standard for Trial Use contains

More information

860 Purchase Order Change Request Buyer Initiated

860 Purchase Order Change Request Buyer Initiated 860 Purchase Order Change Request Buyer Initiated Set Number - 860 Set Name Purchase Order Change Request Buyer Initiated Functional Group - PC This Draft Standard for Trail Use contains the format and

More information

Pos. Seg. Req. Loop No. ID Name Des. Max.Use Repeat LOOP ID IT1 200000 0100 IT1 Baseline Item Data M 1 0600 PID Product / Item Description M 1 1000

Pos. Seg. Req. Loop No. ID Name Des. Max.Use Repeat LOOP ID IT1 200000 0100 IT1 Baseline Item Data M 1 0600 PID Product / Item Description M 1 1000 810 Invoice Introduction: Functional Group ID=IN This Standard contains the format and establishes the data contents of the Invoice Transaction Set (810) for use within the context of an Electronic Data

More information

84 LUMBER ELECTRONIC DATA INTERCHANGE VENDOR IMPLEMENTATION PROGRAM INFORMATION PACKAGE 810 INVOICES VERSION 4010. August 21, 2007

84 LUMBER ELECTRONIC DATA INTERCHANGE VENDOR IMPLEMENTATION PROGRAM INFORMATION PACKAGE 810 INVOICES VERSION 4010. August 21, 2007 84 LUMBER ELECTRONIC DATA INTERCHANGE VENDOR IMPLEMENTATION PROGRAM INFORMATION PACKAGE 810 INVOICES VERSION 4010 August 21, 2007 1 of 16 84 LUMBER EDI PROFILE 1. 84 LUMBER PERSONNEL Linda Smitley, EDI

More information

Electronic Data Interchange (EDI) Standards 810 Invoice Version 4010

Electronic Data Interchange (EDI) Standards 810 Invoice Version 4010 Electronic Data Interchange (EDI) Standards 810 Invoice Version 4010 Approved: 07/26/2010 Authors: Dave Danko HCR ManorCare is a leading provider of short and long term medical and rehabilitation care.

More information

867 Product Transfer and Resale Report Ver/Rel 003060. Electronic Data I nterchange. Utility Industry Group Implementation Guideline.

867 Product Transfer and Resale Report Ver/Rel 003060. Electronic Data I nterchange. Utility Industry Group Implementation Guideline. Utility Industry Group Implementation Guideline for Electronic Data I nterchange TRANSACTION SET 867 Product Transfer and Resale Report Ver/Rel 003060 Acid Rain Allowance Transfer Reporting to the U.S.

More information

Pennsylvania New Jersey Delaware Maryland. Implementation Guideline

Pennsylvania New Jersey Delaware Maryland. Implementation Guideline Pennsylvania New Jersey Delaware Maryland Implementation Guideline For Electronic Data Interchange TRANSACTION SET 867 Interval Usage Ver/Rel 004010 867 Interval Usage (4010) 1 Table of Contents Summary

More information

Now, suppliers can also select EDI as a method for receiving Change and Cancel Orders.

Now, suppliers can also select EDI as a method for receiving Change and Cancel Orders. 850 Purchase Order Functional Group ID=PO Introduction: This Draft Standard for Trial Use contains the format and establishes the data contents of the Purchase Order Transaction Set (850) for use within

More information

EDI Specifications. 810 - Invoice (Supplier v4010)

EDI Specifications. 810 - Invoice (Supplier v4010) (Supplier v400) December 200 80 Purchase rder - Functional Group=IN VER. 400 FISHER SCIENTIFIC This Standard contains the format and establishes the data contents of the Fisher Scientific Customer Invoice

More information

214 Transportation Carrier Shipment Status Message

214 Transportation Carrier Shipment Status Message 214 Transportation Carrier Shipment Status Message Introduction: Functional Group ID=QM This Draft Standard for Tria l Use contains the format and establishes the data contents of the Transportation Carrier

More information

DoD Transportation Electronic Data Interchange (EDI) Convention

DoD Transportation Electronic Data Interchange (EDI) Convention Department of Defense DoD Transportation Electronic Data Interchange (EDI) Convention ASC X12 Transaction Set 824 Application Advice Invoice Acknowledgment (004010) INITIAL DRAFT August 2003 20030829 TTC

More information

Virginia Implementation Standard

Virginia Implementation Standard Virginia Implementation Standard For Electronic Data Interchange TRANSACTION SET 867 Product Transfer and Resale Report Historical Usage Ver/Rel 004010 VA 867 Historical Usage (4010) 1 867hu-stan2-3.doc

More information

Dart Container Corporation. EDI 810 Outbound Invoice Version 4010

Dart Container Corporation. EDI 810 Outbound Invoice Version 4010 Dart Container Corporation EDI 810 Outbound Invoice Version 4010 HEADER SECTION ST - Transaction Set Header 01 Transaction Set Identifier N0 1/10 810 02 Transaction Set Control Number AN 4/9 Unique Sequence

More information

Electronic Data Interchange

Electronic Data Interchange Electronic Data Interchange Transaction Set: 850 Supplier Purchase Order ANSI X12 Version 4010 This specification covers the requirements for Grainger and our Business Units. Grainger Industrial Supply

More information

Ultramar Ltd IMPLEMENTATION GUIDE

Ultramar Ltd IMPLEMENTATION GUIDE IMPLEMENTATION GUIDE for electronic data interchange November 2002 TABLE OF CONTENTS INTRODUCTION... 1 KEY CONTACTS... 1 EDI STANDARDS... 1 DOCUMENT PROCESSING FREQUENCY... 1 RESPONSIBILITY FOR COMMUNICATION

More information

The EDI 810 specification is separated into logically distinct groups, which are composed of particular segment types.

The EDI 810 specification is separated into logically distinct groups, which are composed of particular segment types. EDI 810 File Format Direct Commerce (DCI) supports the EDI 810 format for uploaded invoice transactions. This document describes our implementation of the EDI 810 format for invoicing Carolinas Healthcare

More information

Eaton Corporation Electronic Data Interchange (EDI) Standards Application Advice (824) Version 4010

Eaton Corporation Electronic Data Interchange (EDI) Standards Application Advice (824) Version 4010 Eaton Corporation Electronic Data Interchange (EDI) Standards Application Advice (824) Version 4010 Revision date: 12/15/2003 Author: Kathy Grubar Copyright 2003 Eaton Corporation. All rights reserved.

More information

VERSION: ANSI X-12 004010

VERSION: ANSI X-12 004010 855 Purchase Order Acknowledgment VERSION: ANSI X-12 004010 Author: Family Dollar Stores FDS 855 layout ( VMI Order s) 1 For internal only 855 Purchase Order Acknowledgment Functional Group=PR This Draft

More information

810 Invoice ANSI X.12 Version 5010

810 Invoice ANSI X.12 Version 5010 810 Invoice SI X.12 Version 5010 *** HEADE AEA *** SEG SEGMENT EQ MAX LOOP NAME DES USE EPEAT ISA Interchange Control Header M 1 GS Functional Group Header M 1 ST Transaction Set Header M 1 BIG Beginning

More information

BIG LOTS STORES INC. IMPLEMENTATION SPECIFICATIONS ASC X12 INVOICE TRANSACTION SET 810 VERSION 5010

BIG LOTS STORES INC. IMPLEMENTATION SPECIFICATIONS ASC X12 INVOICE TRANSACTION SET 810 VERSION 5010 BIG LOTS STORES INC. IMPLEMENTATION SPECIFICATIONS ASC X12 INVOICE TRANSACTION SET 810 VERSION 5010 Last revised 3/2/2015 9:47:55 AM - 1 - Summary of Changes 2012 Changes Return merchandise must be on

More information

Bill of Lading Number REF02 127 Reference Identification M AN 1/30 MustUse

Bill of Lading Number REF02 127 Reference Identification M AN 1/30 MustUse Updated 05/08/06 810 Invoice Version 005010 X12 Functional Group=IN BIG Beginning Segment for Invoice Pos: 020 Max: 1 Heading - Mandatory Loop: N/A Elements: 4 BIG01 373 Date Description: Invoice Date

More information

ANSI ASC X.12 Standard Version 4010 Transaction Set 214 Transportation Carrier Shipment Status Message

ANSI ASC X.12 Standard Version 4010 Transaction Set 214 Transportation Carrier Shipment Status Message ANSI ASC X.12 Standard Version 4010 Transaction Set 214 Transportation Carrier Shipment Status Message Revised 01/04/11 214 Transportation Carrier Shipment Status Message Functional Group=QM This Draft

More information

UNDERSTANDING YOUR UTILITY BILL A GUIDE FOR BUSINESSES IN OHIO

UNDERSTANDING YOUR UTILITY BILL A GUIDE FOR BUSINESSES IN OHIO UNDERSTANDING YOUR UTILITY BILL A GUIDE FOR BUSINESSES IN OHIO TABLE OF CONTENTS INTRODUCTION Introduction... 3 Basic Billing Concepts... 4 Customer Choice Programs... 4 Gas Consumption and Charges...

More information

824 Application Advice

824 Application Advice 824 Application Advice X12/V4040/824: 824 Application Advice Version: 2.1 Final Author: Insight Direct USA, Inc. Modified: 10/12/2006 824 Application Advice Functional Group=AG This Draft Standard for

More information

Supply Chain Merchandise Logistics E-Commerce Purchase Order

Supply Chain Merchandise Logistics E-Commerce Purchase Order Supply Chain Merchandise Logistics E-Commerce Purchase Order E-Commerce Purchase Order Page 1 of 53 Contents Introduction 3 E-Commerce ordering How Myer Orders merchandise 4 Purchase order format 4 Basic

More information

997 MUST be sent to Safeway to confirm receipt of 824 transmission. This is unrelated to EDI syntax errors as reported on 997.

997 MUST be sent to Safeway to confirm receipt of 824 transmission. This is unrelated to EDI syntax errors as reported on 997. This document defines Safeway Inc. s guidelines of EDI Transaction Set 824, Application Advice, VICS Version 004010. It does not vary from the X12/UCS/VICS standards. Only segments and elements that are

More information

Transaction Set 824 - Application Advice

Transaction Set 824 - Application Advice TS 824 for TS 264 in X12 Version 003040 IMPLEMENTATION GUIDE Transaction Set 824 - Application Advice Transaction set (TS) 824 can be used to provide the ability to report the results of an application

More information

Electronic Data Interchange

Electronic Data Interchange Electronic Data Interchange Transaction Set: 856 Supplier Advance Ship Notice ANSI X12 Version 4010 This specification covers the requirements for Grainger and our Business Units. Grainger Industrial Supply

More information

Note: The following information is required on all Merchandise Invoices:

Note: The following information is required on all Merchandise Invoices: 810 NORDSTROM CANADA Invoice Functional Group=IN Purpose: This Draft Standard for Trial Use contains the format and establishes the data contents of the Invoice Transaction Set (810) for use within the

More information

ASC X12 Finance Subcommittee. Consumer Service Provider (CSP) Billing and Payment Guide

ASC X12 Finance Subcommittee. Consumer Service Provider (CSP) Billing and Payment Guide ASC X12 FINANCE SUBCOMMITTEE VERSION 003 ù RELEASE 061 820 ASC X12 Finance Subcommittee Consumer Service Provider (CSP) Billing and Payment Guide Version 003 Release 061 - CSP - Consumer Service Provider

More information

EDI GUIDELINES PURCHASE ORDER 850 VERSION 4010

EDI GUIDELINES PURCHASE ORDER 850 VERSION 4010 EDI GUIDELINES PURCHASE RDER 850 VERSIN 4010 Rev. 7/23/2013 GLSSARY F TERS BLACKHAWK NETWRK s 850 GUIDELINES Seg. Use: Reference : Number: : Consists of a segment identifier, one or more data element each

More information

Mazda North American Operations EDI Supplier Documentation October 20, 2015

Mazda North American Operations EDI Supplier Documentation October 20, 2015 EDI Supplier Documentation October 20, 2015 March 2006 Revision History Merged separate files into this one document Sept 13, 2007 Revised 856 BSN, Element 02, on page 101 Aug 18, 2008 Revised sample 830

More information

Electronic Commerce Customer Guide

Electronic Commerce Customer Guide Electronic Commerce Customer Guide 811 Transaction Set (Version/Release 004010) Electronic Data Interchange - Electronic Funds Transfer AT&T Trading Partners Business Customers Value Added Networks Payment

More information

HIPAA EDI Companion Guide for 835 Electronic Remittance Advice

HIPAA EDI Companion Guide for 835 Electronic Remittance Advice HIPAA EDI Companion Guide for 835 Electronic Remittance Advice ASC X12 Standards for Electronic Data Interchange Technical Report Type 3 (TR3) Version 005010X221A1 Companion Guide Version: 2.0 Disclosure

More information

944 Warehouse Stock Transfer Receipt Advice. X12/V4030/944: 944 Warehouse Stock Transfer Receipt Advice

944 Warehouse Stock Transfer Receipt Advice. X12/V4030/944: 944 Warehouse Stock Transfer Receipt Advice 944 Warehouse Stock Transfer Receipt Advice X12/V4030/944: 944 Warehouse Stock Transfer Receipt Advice Author: Tim Wright Company: Created: 09/04/2012 Current: 09/04/2012 Table of Contents 944 Warehouse

More information

EDI 214 ANSI X12 Version 4010 Transportation Carrier Shipment Status Message

EDI 214 ANSI X12 Version 4010 Transportation Carrier Shipment Status Message EDI 214 ANSI X12 Version 4010 Transportation Carrier Shipment Status Message 214 Transportation Carrier Shipment Status Message Functional Group=QM This Draft Standard for Trial Use contains the format

More information

EDI IMPLEMENTATION GUIDE. 856 ANSI X12 V4010 Ship Notice/Manifest Regular (Non Steel)

EDI IMPLEMENTATION GUIDE. 856 ANSI X12 V4010 Ship Notice/Manifest Regular (Non Steel) EDI IMPLEMENTATION GUIDE 856 ANSI X12 V4010 Ship Notice/Manifest Regular (Non Steel) Revision Date: November 7, 2013 Regular (Non Steel) Rev 6 X12 004010 pg. 1 856 Ship Notice/Manifest Introduction: Functional

More information

Because the 810 implementation ultimately maps to an InvoiceDetailRequest, it must conform to its rules.

Because the 810 implementation ultimately maps to an InvoiceDetailRequest, it must conform to its rules. 810 Implementation Guidelines 1 Overview Ariba Supplier Network (SN) allows suppliers to send invoices to buying organisations in the form of cxml InvoiceDetailRequest documents. As a service to suppliers

More information

810 - Invoice. Set Number - 810 Set Name - Invoice Functional Group - IN

810 - Invoice. Set Number - 810 Set Name - Invoice Functional Group - IN 810 - Invoice Set Number - 810 Set Name - Invoice Functional Group - IN This standard contains the format and establishes the data contents of the Invoice Transaction Set (810) for use within the context

More information

VOLVO Dealer Programs 810 Invoice EDI Guideline

VOLVO Dealer Programs 810 Invoice EDI Guideline VOLVO 1. 810 INVOICE General This document describes Volvo's application of the ANSI X12 transaction set. The specification offers a detailed description of those data elements which will be used. The

More information

IMPLEMENTATION GUIDELINES FOR ANSI ASC X12 EDI CONVENTIONS APPLICATION ADVICE (824) TRANSACTION SET

IMPLEMENTATION GUIDELINES FOR ANSI ASC X12 EDI CONVENTIONS APPLICATION ADVICE (824) TRANSACTION SET IMPLEMENTATION GUIDELINES FOR ANSI ASC X12 EDI CONVENTIONS APPLICATION ADVICE (824) TRANSACTION SET FCA US INFORMATION & COMMUNICATION TECHNOLOGY MANAGEMENT ANSI ASC X12 VERSION/RELEASE 002040CHRY FCA

More information

Unified Grocers 820 EFT Specifications Remittance Advice Document Structure

Unified Grocers 820 EFT Specifications Remittance Advice Document Structure Unified Grocers 820 EFT Specifications Remittance Advice Document Structure LEVEL SEGMENT NAME Req Max Use Envelope Header ISA Interchange Header M 1 GS Group Header M 1 ST Transaction Set Header M 1 Loop

More information

Data Exchange and Protocol Process Flows for Electric Deregulation in The State of New Jersey

Data Exchange and Protocol Process Flows for Electric Deregulation in The State of New Jersey Data Exchange and Protocol Process Flows for Electric Deregulation in The State of New Jersey Prepared by: The Consumer Process Working Groups July 17, 2000 Version 1.2 Table of Contents Table of Contents...

More information

RANDOM HOUSE. EDI Implementation Guide. 8 10 Invoice X12 Version 4010

RANDOM HOUSE. EDI Implementation Guide. 8 10 Invoice X12 Version 4010 RANDOM HOUSE EDI Implementation Guide 8 10 Invoice X12 Version 4010 Effective: 9-2-2006 Notes: The Random House EDI Implementation Guide for the 810 transaction documents only the segments and elements

More information

820 Payroll Deducted and Other Group Premium Payment for Insurance Products

820 Payroll Deducted and Other Group Premium Payment for Insurance Products Companion Document 820 820 Payroll Deducted and Other Group Premium Payment for Insurance Products This companion document is for informational purposes only to describe certain aspects and expectations

More information

Implementation Guidelines For ANSI X12 Interchange Control Structures Inbound & outbound. (v2002)

Implementation Guidelines For ANSI X12 Interchange Control Structures Inbound & outbound. (v2002) Implementation Guidelines For ANSI X12 Interchange Control Structures Inbound & outbound (v2002) ICS Interchange Control Structures Functional Group ID= Introduction: The purpose of this standard is to

More information

856 Advance Ship Notice Supplier Implementation Guide November 2015

856 Advance Ship Notice Supplier Implementation Guide November 2015 856 Advance Ship Notice Supplier Implementation Guide November 2015 856 Ship Notice/Manifest INTRODUCTION This implementation guideline for the 856 Ship Notice/Manifest electronic data interchange (EDI)

More information

820 ANSI X12 Version 003030

820 ANSI X12 Version 003030 820 ANSI X12 Version 003030 Remittance Advice (Credit Card) FUNCTIONAL GROUP = RA This document is used by Medtronic to forward Credit Card payment information captured by the MAPP-PC system to the Automated

More information

How To Write A Bill Of Sale

How To Write A Bill Of Sale 810 ASC X12 Finance Subcommittee Consumer Service Provider (CSP) Billing and Payment Guide Version 003 Release 061 - CSP - Consumer Service Provider Biller Consumer Network Payment System 810 Invoice Transaction

More information

Staples Supplier Electronic Data Interchange Implementation Guide

Staples Supplier Electronic Data Interchange Implementation Guide Staples Supplier Electronic Data Interchange Implementation Guide June 2010 ANSI 4010 Revision 002.13 Staples Supplier EDI Implementation Guide Table of Contents GETTING STARTED WITH STAPLES...3 VAN (Value

More information

Toyota Boshoku America EDI Implementation Manual Version 1 for: TBA o TBIN o TBMS o TBCA - Woodstock o TBCA - Elmira

Toyota Boshoku America EDI Implementation Manual Version 1 for: TBA o TBIN o TBMS o TBCA - Woodstock o TBCA - Elmira Toyota Boshoku America EDI Implementation Manual Version 1 for: TBA o TBIN o TBMS o TBCA - Woodstock o TBCA - Elmira Forward The widespread implementation of EDI (Electronic Data Interchange) throughout

More information

214 Transportation Carrier Shipment Status Message - LTL

214 Transportation Carrier Shipment Status Message - LTL 214 Transportation Carrier Shipment Status Message - LTL Lowe's 214 - LTL Shipment Status Message Version: 4010 Author: Lowe's Companies, Inc Modified: 2/27/2013 Notes: This 214 Implementation Guide should

More information

X12 Implementation. Guidelines. For. Transfer Version 3030. (996o)

X12 Implementation. Guidelines. For. Transfer Version 3030. (996o) X12 Implementation Guidelines For Outbound ss File Transfer Version 3030 (996o) 996_3030 (003030) 1 April 29, 2003 996 File Transfer Functional Group ID=FT Introduction: This Draft Standard for Trial Use

More information

Detail SE Transaction Set Trailer Summary GE Functional Group Trailer Summary IEA Interchange Control Trailer Summary. ISA Interchange Control Header

Detail SE Transaction Set Trailer Summary GE Functional Group Trailer Summary IEA Interchange Control Trailer Summary. ISA Interchange Control Header 820 Payment Order / Remittance Advice Segment ID Description Location ISA Interchange Control Header Heading GS Functional Group Header Heading ST Transaction Set Header Heading 1 BPR Beginning Segment

More information

997 Functional Acknowledgment

997 Functional Acknowledgment 997 Functional Acknowledgment Version: 1.0 Draft Author: Margie Stewart Publication: 06/10/2013 Notes: Table of Contents 997 Functional Acknowledgment.......................................................................................

More information

To indicate the beginning of an invoice transaction set and to transmit identifying numbers and dates. BIG^20001022^12345^20000930^0000123456^

To indicate the beginning of an invoice transaction set and to transmit identifying numbers and dates. BIG^20001022^12345^20000930^0000123456^ Invoice (810) VICS 004010 The transaction set can be used to provide for customary and established business and industry practice relative to the billing for goods and services provided. BIG Beginning

More information

IMPLEMENTATION GUIDELINES FOR ANSI ASC X12 EDI CONVENTIONS FILE TRANSFER (996) TRANSACTION SET

IMPLEMENTATION GUIDELINES FOR ANSI ASC X12 EDI CONVENTIONS FILE TRANSFER (996) TRANSACTION SET IMPLEMENTATION GUIDELINES FOR ANSI ASC X12 EDI CONVENTIONS FILE TRANSFER (996) TRANSACTION SET FCA US INFORMATION & COMMUNICATION TECHNOLOGY MANAGEMENT ANSI ASC X12 VERSION/RELEASE 003020 996 File Transfer

More information

CVS/Caremark. Implementation Guide. 852 Product Activity Data Warehouse Movement. Version X12-4010

CVS/Caremark. Implementation Guide. 852 Product Activity Data Warehouse Movement. Version X12-4010 CVS/Caremark Implementation Guide 852 Product Activity Data Warehouse Movement Version X12-4010 852 Mapping Specifications v4010 i Table of Contents 852 Product Activity Data... 1 ST Transaction Set Header...

More information

820 Payroll Deducted and Other Group Premium Payment for Insurance Products

820 Payroll Deducted and Other Group Premium Payment for Insurance Products Companion Document 820 820 Payroll Deducted and Other Group Premium Payment for Insurance Products This Companion Document serves as supplementary material to the primary resource, ASC X12 Standards for

More information

Geisinger Health Plan

Geisinger Health Plan Geisinger Health Plan Companion Guide for the 820 Payroll Deducted and Other Group Premium Payment for Insurance Products Refers to the Implementation Guides Based on X12 version 004010A1 Version Number:

More information

Produce Traceability Initiative Why and How to Use EDI 856 Advance Ship Notice/Manifest Transaction Set (ASN)

Produce Traceability Initiative Why and How to Use EDI 856 Advance Ship Notice/Manifest Transaction Set (ASN) Produce Traceability Initiative Why and How to Use EDI 856 Advance Ship Notice/Manifest Transaction Set (ASN) About this Guidance Document (Revision 1.0) Guidelines are generally accepted, informally standardized

More information

835 Claim Payment/Advice

835 Claim Payment/Advice Companion Document 835 835 Claim Payment/Advice Basic Instructions This section provides information to help you prepare for the ANSI ASC X12 Claim Payment/Advice (835) transaction. The remaining sections

More information

846 Inbound Inventory Advice WITH VENDOR DIRECT (TO CONSUMER) ORDERS Macy s VICS Version 4010 VICS Document Mapping Effective 08/27/2007

846 Inbound Inventory Advice WITH VENDOR DIRECT (TO CONSUMER) ORDERS Macy s VICS Version 4010 VICS Document Mapping Effective 08/27/2007 846 Inbound Inventory Advice WITH VENDOR DIRECT (TO CONSUMER) ORDERS Macy s VICS Version 4010 VICS Document Mapping Effective 08/27/2007 The following is an outline of what is expected when receiving VICS

More information

State of Tennessee Department of Revenue

State of Tennessee Department of Revenue State of Tennessee Department of Revenue PET 350 - Distributor Monthly Fuel Tax Return PET 368 - Blenders Return PET 372 - Petroleum Products Terminal Return PET 373 - Petroleum Products Transporter Return

More information

CSX EDI 824 Application Advice Version: 005030

CSX EDI 824 Application Advice Version: 005030 CSX EDI 824 Application Advice Version: 005030 Questions about the CSX EDI 284 Implementation Guide should be directed to: 877-SHIPCSX option 2, prompt 2 Monday Friday: 7:00 AM 6:00 PM Publication: September

More information

HIPAA - ASC X12N Outbound EDI 835 Electronic Remittance Advice Transaction

HIPAA - ASC X12N Outbound EDI 835 Electronic Remittance Advice Transaction HIPAA - ASC X12N Outbound EDI 835 Electronic Remittance Advice Transaction HIPAA Transaction Companion Guide Refers to the X12N Implementation Guide ANSI Version 4010 X091A1 Version 1.0 Date: November13,

More information

Delivery/Return Acknowledgment or 895 Adjustment 005010 UCS

Delivery/Return Acknowledgment or 895 Adjustment 005010 UCS Delivery/Return Acknowledgment or 895 Adjustment 005010 UCS Functional Group=DX Heading: Pos Id Segment Name Req Max Use Repeat Notes Usage 0100 G87 Delivery/Return Adjustment M 1 Must use Identification

More information

X12 Implementation Guidelines For Outbound Receiving Advice v002001 (861O)

X12 Implementation Guidelines For Outbound Receiving Advice v002001 (861O) X12 Implementation Guidelines For Outbound Receiving Advice v002001 (861O) 861 Receiving Advice/Acceptance Certificate Introduction: Functional Group ID=RC This Draft Standard for Trial Use contains the

More information

UNDERSTANDING YOUR UTILITY BILL A GUIDE FOR BUSINESSES IN INDIANA

UNDERSTANDING YOUR UTILITY BILL A GUIDE FOR BUSINESSES IN INDIANA UNDERSTANDING YOUR UTILITY BILL A GUIDE FOR BUSINESSES IN INDIANA TABLE OF CONTENTS Introduction... 5 Basic Billing Concepts... 6 Electric Energy and Demand... 6 Electric Consumption and Charges... 7

More information

EDI Specifications. 856 - Advance Ship Notice (Supplier v4010)

EDI Specifications. 856 - Advance Ship Notice (Supplier v4010) (Supplier v400) December 200 856 Ship Notice/anifest- Functional Group=SH VER. 400 FISHER SCIENTIFIC This Standard contains the format and establishes the data contents of the Fisher Scientific Customer

More information

S.2.2 CHARACTER SETS AND SERVICE STRING ADVICE: THE UNA SEGMENT

S.2.2 CHARACTER SETS AND SERVICE STRING ADVICE: THE UNA SEGMENT S.2 STRUCTURE OF AN EDIFACT TRANSMISSION This section is substantially based on the ISO 9735 document: EDIFACT application level syntax rules, first released on 1988-07-15, amended and reprinted on 1990-11-01,

More information

CONSOLIDATED BILLING BUSINESS PROCESSES (UTILITY RATE READY)

CONSOLIDATED BILLING BUSINESS PROCESSES (UTILITY RATE READY) This document describes business processes associated with rendering consolidated bills for end use retail customers under the Utility Rate Ready Model. The scope of this document addresses processes associated

More information

LOOP ID - N9 1000 295 N9 Reference Identification O 1 300 MSG Message Text O 1000

LOOP ID - N9 1000 295 N9 Reference Identification O 1 300 MSG Message Text O 1000 850 Purchase Order Functional Group ID=PO Introduction: This Draft Standard for Trial Use contains the format and establishes the data contents of the Purchase Order Transaction Set (850) for use within

More information

MV-STAR. I/O Reference Guide 5.0.213.1

MV-STAR. I/O Reference Guide 5.0.213.1 T MV-STAR I/O Reference Guide 5.0.213.1 ii Identification TDR-0017-004 06/04 MV-STAR Release 5.0.213.1 Trademark Notice Itron is a registered trademark of Itron, Inc. Windows, Windows 95, Windows 98, Windows

More information

State of Nebraska. Motor Fuels Division. EDI Implementation Guide. Revised May 2007 2005 ANSI ASC X12 V.4030

State of Nebraska. Motor Fuels Division. EDI Implementation Guide. Revised May 2007 2005 ANSI ASC X12 V.4030 State of Nebraska Motor Fuels Division EDI Implementation Guide Revised May 2007 2005 ANSI ASC X12 V.4030 (Adapted from the FTA Electronic Combined Reporting Methods Implementation Guide) Table of Contents

More information

Electronic Document Interchange Standards Version 5050

Electronic Document Interchange Standards Version 5050 Yazaki North America, Inc. Electronic Document Interchange Standards Version 5050 Dear Supplier. Enclosed you will find current versions of our EDI Document Guidelines for our Suppliers that are shipping

More information