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 of an Electronic Data Interchange (EDI) environment. 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.

Heading:

	Pos.	Seg.		Req.		Loop	Notes and
	No.	ID	Name	Des.	Max.Use	Repeat	Comments	
M	010	ST	Transaction Set Header	M	1									
M	020	BIG	Beginning Segment for Invoice	M	1									
	050	REF	Reference Identification (Supplier Account ID)	O	12									
	050	REF	Reference Identification (Original Invoice ID)	O	12									
M/U	050	REF	Reference Identification (Customer Account ID or SDID)	O	12									
M/U	050	REF	Reference Identification (Party Sending Bill)	O	12									
M/U	050	REF	Reference Identification (Party Calculating Non-Billing Party Charges)	O	12									
			LOOP ID - N1			200								
	070	N1	Name (Distribution Company)	O	1									
														
			LOOP ID - N1			200								
	070	N1	Name (Supplier)	O	1									
														
	130	ITD	Terms of Sale/Deferred Terms of Sale	O	>1									

Detail:

	Pos.	Seg.		Req.		Loop	Notes and
	No.	ID	Name	Des.	Max.Use	Repeat	Comments	
			LOOP ID - IT1			200000								
	010	IT1	Baseline Item Data 	O	1									
	150	DTM	Date/Time Reference (Service Period Start Date)	O	10									
	150	DTM	Date/Time Reference (Service Period End Date)	O	10									
			LOOP ID - SLN			1000								
	200	SLN	Subline Item Detail	O	1									
	230	SAC	Service, Promotion, Allowance, or Charge Information	O	25									
	237	TXI	Tax Information	O	10									

Summary:

	Pos.	Seg.		Req.		Loop	Notes and
	No.	ID	Name	Des.	Max.Use	Repeat	Comments	
M	010	TDS	Total Monetary Value Summary	M	1									
M/U	070	CTT	Transaction Totals	O	1		n1							
M	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. If used, hash total (CTT02) is the sum of the value of quantities invoiced (IT102) for each IT1 segment.

	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) is used by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set).
	Comments:
Notes:		Required
	
		ST~810~000000001	

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	Attributes
Must Use	ST01	143	Transaction Set Identifier Code	M		ID 3/3	
	Code uniquely identifying a Transaction Set	
 	810		Invoice	
Must Use	ST02	329	Transaction Set Control Number	M		AN 4/9	
	Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set	

	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 transmit identifying numbers and dates
	Syntax Notes:
	Semantic Notes:	1	BIG01 is the invoice issue date.
		2	BIG03 is the date assigned by the purchaser to purchase order.
		3	BIG10 indicates the consolidated invoice number. When BIG07 contains code CI, BIG10 is not used.
	Comments:	1	BIG07 is used only to further define the type of invoice when needed.
Notes:		Required
	
		BIG~20010201~123567890120010201~~~2048392934504~~PR~00	

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	Attributes
Must Use	BIG01	373	Date	M		DT 8/8	
	Date expressed as CCYYMMDD	
	The transaction creation date - the date that the data was processed by the sender's application system.	
Must Use	BIG02	76	Invoice Number	M		AN 1/22	
	Identifying number assigned by issuer	
	A unique transaction identification number assigned by the originator of this transaction.  This number must be unique over time.  This number will be returned in the RMR02 of the 820 and/or the OTI03 of the 824.

Transaction Reference Numbers will only contain uppercase letters (A to Z) and digits (0 to 9).  Note that punctuation (spaces, dashes, etc.) must be excluded.	
Dep	BIG05	328	Release Number	O		AN 1/30	
	Number identifying a release against a Purchase Order previously placed by the parties involved in the transaction	
	Monthly Invoice:  The cross-reference number originally transmitted in the 867 in the BPT02 must be sent in the BIG05 of the 810 and in the RMR loop  REF~6O of the 820.

For a cancelled invoice the cross-reference will be made to the original meter read BPT02, not the cancelled meter read BPT02 transaction.	
Must Use	BIG07	640	Transaction Type Code	O		ID 2/2	
	Code specifying the type of transaction	
	May use "FB" or "PR" as appropriate.
	
 	FB		Final Bill	
	Final bill sent for this customer from the Non-Billing Party.	
 	PR		Product (or Service)	
	Used for Monthly Invoice	
Must Use	BIG08	353	Transaction Set Purpose Code	O		ID 2/2	
	Code identifying purpose of transaction set	
 	00		Original	
 	01		Cancellation	
	Cancels an entire invoice/transaction	
 	07		Duplicate	
	This code will be used only in a Rate Ready scenario when the Distribution company changes the bill due date for the customer.  The Distribution company will send an 810 to the supplier, the only things changing from the original 810 are the duplicate code and the due date.	

	Segment:	REF Reference Identification (Supplier Account ID)
	Position:	050
	Loop:
	Level:	Heading
	Usage:	Optional
	Max Use:	12
	Purpose:	To specify identifying information
	Syntax Notes:	1	At least one of REF02 or REF03 is required.
		2	If either C04003 or C04004 is present, then the other is required.
		3	If either C04005 or C04006 is present, then the other is required.
	Semantic Notes:	1	REF04 contains data relating to the value cited in REF02.
	Comments:
Notes:		RBC
	
		REF~11~123456789019990102	

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	Attributes
Must Use	REF01	128	Reference Identification Qualifier	M		ID 2/3	
	Code qualifying the Reference Identification	
 	11		Account Number	
	Number identifies a telecommunications industry account	
	Customer Account ID assigned by Supplier.	
Must Use	REF02	127	Reference Identification	X		AN 1/30	
	Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier	
	Customer Account ID assigned by Supplier.	

	Segment:	REF Reference Identification (Original Invoice ID)
	Position:	050
	Loop:
	Level:	Heading
	Usage:	Optional
	Max Use:	12
	Purpose:	To specify identifying information
	Syntax Notes:	1	At least one of REF02 or REF03 is required.
		2	If either C04003 or C04004 is present, then the other is required.
		3	If either C04005 or C04006 is present, then the other is required.
	Semantic Notes:	1	REF04 contains data relating to the value cited in REF02.
	Comments:
Notes:		Required on a Cancel (BIG08=01)  transaction.
	
		REF~OI~123456789019990102	

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	Attributes
Must Use	REF01	128	Reference Identification Qualifier	M		ID 2/3	
	Code qualifying the Reference Identification	
 	OI		Original Invoice Number	
Must Use	REF02	127	Reference Identification	X		AN 1/30	
	Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier	
	Original Invoice Number	

	Segment:	REF Reference Identification (Customer Account ID or SDID)
	Position:	050
	Loop:
	Level:	Heading
	Usage:	Optional (Must Use)
	Max Use:	12
	Purpose:	To specify identifying information
	Syntax Notes:	1	At least one of REF02 or REF03 is required.
		2	If either C04003 or C04004 is present, then the other is required.
		3	If either C04005 or C04006 is present, then the other is required.
	Semantic Notes:	1	REF04 contains data relating to the value cited in REF02.
	Comments:
Notes:		Conditional on Governing Documents. Either REF~12 or REF~Q5 is required.	
		REF~12~10111111234567890ABCDEFGHIJKL	
		REF~Q5~~10111111234567890ABCDEFGHIJKL	

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	Attributes
Must Use	REF01	128	Reference Identification Qualifier	M		ID 2/3	
	Code qualifying the Reference Identification	
 	12		Billing Account	
	Account number under which billing is rendered	
	Distribution Company assigned account number for the customer sent in REF02	
 	Q5		Property Control Number	
	Customer SDID - sent in REF03.	
Used	REF02	127	Reference Identification	X		AN 1/30	
	Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier	
	Customer Account ID - use when REF01 = 12.	
Used	REF03	352	Description	X		AN 1/80	
	A free-form description to clarify the related data elements and their content	
	Customer SDID - use when REF01 = Q5.	
	This free-form text can not contain any characters that may be used as element delimiters, sub-element delimiters, segment terminators, or field separators.  (This includes: asterisk *, pipes |, tabs, linefeeds, carets ^, angle brackets < >, and tildes ~).	

	Segment:	REF Reference Identification (Party Sending Bill)
	Position:	050
	Loop:
	Level:	Heading
	Usage:	Optional (Must Use)
	Max Use:	12
	Purpose:	To specify identifying information
	Syntax Notes:	1	At least one of REF02 or REF03 is required.
		2	If either C04003 or C04004 is present, then the other is required.
		3	If either C04005 or C04006 is present, then the other is required.
	Semantic Notes:	1	REF04 contains data relating to the value cited in REF02.
	Comments:
Notes:		Required
	
		REF~BLT~LDC	

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	Attributes
Must Use	REF01	128	Reference Identification Qualifier	M		ID 2/3	
	Code qualifying the Reference Identification	
 	BLT		Billing Type	
	Identifies the party sending the bill	
Used	REF02	127	Reference Identification	X		AN 1/30	
	Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier	
	When REF01 is BLT, valid values for REF02 are:
LDC (meaning the distribution company sends the bill to the customer)
ESP (meaning the suppliers sends the bill to the customer)

	Segment:	REF Reference Identification (Party Calculating Non-Billing Party Charges)
	Position:	050
	Loop:
	Level:	Heading
	Usage:	Optional (Must Use)
	Max Use:	12
	Purpose:	To specify identifying information
	Syntax Notes:	1	At least one of REF02 or REF03 is required.
		2	If either C04003 or C04004 is present, then the other is required.
		3	If either C04005 or C04006 is present, then the other is required.
	Semantic Notes:	1	REF04 contains data relating to the value cited in REF02.
	Comments:
Notes:		Required
	
		REF~PC~LDC	

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	Attributes
Must Use	REF01	128	Reference Identification Qualifier	M		ID 2/3	
	Code qualifying the Reference Identification	
 	PC		Production Code	
	Identifies the party that calculates the Non-Billing Party charges.	
Used	REF02	127	Reference Identification	X		AN 1/30	
	Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier	
	When REF01 is PC, valid values for REF02 are:
LDC (meaning the distribution company calculates the charges on the bill)
ESP (meaning the supplier calculates the charges on the bill)	

	Segment:	N1 Name (Distribution Company)
	Position:	070
	Loop:	N1        Optional
	Level:	Heading
	Usage:	Optional
	Max Use:	1
	Purpose:	To identify a party by type of organization, name, and code
	Syntax Notes:	1	At least one of N102 or N103 is required.
		2	If either N103 or N104 is present, then the other is required.
	Semantic Notes:
	Comments:	1	This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.
		2	N105 and N106 further define the type of entity in N101.
Notes:		Required
	
		N1~8S~DISCO LTD~1~007909411~~41	

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	Attributes
Must Use	N101	98	Entity Identifier Code	M		ID 2/3	
	Code identifying an organizational entity, a physical location, property or an individual	
 	8S		Consumer Service Provider (CSP)	
	Distribution Company	
Must Use	N102	93	Name	X		AN 1/60	
	Free-form name	
	Distribution Company Name	
	This free-form text can not contain any characters that may be used as element delimiters, sub-element delimiters, segment terminators, or field separators.  (This includes: asterisk *, pipes |, tabs, linefeeds, carets ^, angle brackets < >, and tildes ~).	
Must Use	N103	66	Identification Code Qualifier	X		ID 1/2	
	Code designating the system/method of code structure used for Identification Code (67)	
 	1		D-U-N-S Number, Dun & Bradstreet	
 	9		D-U-N-S+4, D-U-N-S Number with Four Character Suffix	
Must Use	N104	67	Identification Code	X		AN 2/80	
	Code identifying a party or other code	
	Distribution Company Common Code Identifier	
Must Use	N106	98	Entity Identifier Code	O		ID 2/3	
	Code identifying an organizational entity, a physical location, property or an individual	
 	40		Receiver	
 	41		Submitter	

	Segment:	N1 Name (Supplier)
	Position:	070
	Loop:	N1        Optional
	Level:	Heading
	Usage:	Optional
	Max Use:	1
	Purpose:	To identify a party by type of organization, name, and code
	Syntax Notes:	1	At least one of N102 or N103 is required.
		2	If either N103 or N104 is present, then the other is required.
	Semantic Notes:
	Comments:	1	This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.
		2	N105 and N106 further define the type of entity in N101.
Notes:		Required
	
		N1~SJ~SUPPLY LTD~9~007909422CRN1~~40	

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	Attributes
Must Use	N101	98	Entity Identifier Code	M		ID 2/3	
	Code identifying an organizational entity, a physical location, property or an individual	
 	SJ		Service Provider	
	Supplier	
Must Use	N102	93	Name	X		AN 1/60	
	Free-form name	
	Supplier Name	
	This free-form text can not contain any characters that may be used as element delimiters, sub-element delimiters, segment terminators, or field separators.  (This includes: asterisk *, pipes |, tabs, linefeeds, carets ^, angle brackets < >, and tildes ~).	
Must Use	N103	66	Identification Code Qualifier	X		ID 1/2	
	Code designating the system/method of code structure used for Identification Code (67)	
 	1		D-U-N-S Number, Dun & Bradstreet	
 	9		D-U-N-S+4, D-U-N-S Number with Four Character Suffix	
Must Use	N104	67	Identification Code	X		AN 2/80	
	Code identifying a party or other code	
	Supplier Common Code Identifier	
Must Use	N106	98	Entity Identifier Code	O		ID 2/3	
	Code identifying an organizational entity, a physical location, property or an individual	
 	40		Receiver	
 	41		Submitter	

	Segment:	ITD Terms of Sale/Deferred Terms of Sale
	Position:	130
	Loop:
	Level:	Heading
	Usage:	Optional
	Max Use:	>1
	Purpose:	To specify terms of sale
	Syntax Notes:	1	If ITD03 is present, then at least one of ITD04 ITD05 or ITD13 is required.
		2	If ITD08 is present, then at least one of ITD04 ITD05 or ITD13 is required.
		3	If ITD09 is present, then at least one of ITD10 or ITD11 is required.
	Semantic Notes:	1	ITD15 is the percentage applied to a base amount used to determine a late payment charge.
	Comments:	1	If the code in ITD01 is "04", then ITD07 or ITD09 is required and either ITD10 or ITD11 is required; if the code in ITD01 is "05", then ITD06 or ITD07 is required.
Notes:		Required
	
		ITD~~~~~~20010215	

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	Attributes
Must Use	ITD06	446	Terms Net Due Date	O		DT 8/8	
	Date when total invoice amount becomes due expressed in format CCYYMMDD	
	Payment due date 	

	Segment:	IT1 Baseline Item Data 
	Position:	010
	Loop:	IT1        Optional
	Level:	Detail
	Usage:	Optional
	Max Use:	1
	Purpose:	To specify the basic and most frequently used line item data for the invoice and related transactions
	Syntax Notes:	1	If any of IT102 IT103 or IT104 is present, then all are required.
		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.
		5	If either IT112 or IT113 is present, then the other is required.
		6	If either IT114 or IT115 is present, then the other is required.
		7	If either IT116 or IT117 is present, then the other is required.
		8	If either IT118 or IT119 is present, then the other is required.
		9	If either IT120 or IT121 is present, then the other is required.
		10	If either IT122 or IT123 is present, then the other is required.
		11	If either IT124 or IT125 is present, then the other is required.
	Semantic Notes:	1	IT101 is the purchase order line item identification.
	Comments:	1	Element 235/234 combinations should be interpreted to include products and/or services. See the Data Dictionary for a complete list of IDs.
		2	IT106 through IT125 provide for ten different product/service IDs for each item. For example: Case, Color, Drawing No., U.P.C. No., ISBN No., Model No., or SKU.
Notes:		Note: Late Payment Charges will be sent on a separate 810 and may not be included on  the normal, monthly invoice.	
		Required
	
		IT1~1~~~~~SV~EL~C3~ACCOUNT

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	Attributes
Must Use	IT101	350	Assigned Identification	O		AN 1/20	
	Alphanumeric characters assigned for differentiation within a transaction set	
Must Use	IT106	235	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	
Must Use	IT107	234	Product/Service ID	X		AN 1/48	
	Identifying number for a product or service	
	There may be only one commodity (Electric or Gas) for each 810 transaction.	
 	ELECTRIC			
 	GAS			
Must Use	IT108	235	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	
Must Use	IT109	234	Product/Service ID	X		AN 1/48	
	Identifying number for a product or service	
 	ACCOUNT		Charges/Taxes at an Account level	
	Account equates to a Customer Account	

	Segment:	DTM Date/Time Reference (Service Period Start Date)
	Position:	150
	Loop:	IT1        Optional
	Level:	Detail
	Usage:	Optional
	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 DTM04 is present, then DTM03 is required.
		3	If either DTM05 or DTM06 is present, then the other is required.
	Semantic Notes:
	Comments:
Notes:		Required 
The full service period should match the applicable PTD loops from the 867.
	
		DTM~150~20010106	

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	Attributes
Must Use	DTM01	374	Date/Time Qualifier	M		ID 3/3	
	Code specifying type of date or time, or both date and time	
 	150		Service Period Start	
Must Use	DTM02	373	Date	X		DT 8/8	
	Date expressed as CCYYMMDD	

	Segment:	DTM Date/Time Reference (Service Period End Date)
	Position:	150
	Loop:	IT1        Optional
	Level:	Detail
	Usage:	Optional
	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 DTM04 is present, then DTM03 is required.
		3	If either DTM05 or DTM06 is present, then the other is required.
	Semantic Notes:
	Comments:
Notes:		Required 
The full service period should match the applicable PTD loops from the 867.
	
		DTM~151~20010204	

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	Attributes
Must Use	DTM01	374	Date/Time Qualifier	M		ID 3/3	
	Code specifying type of date or time, or both date and time	
 	151		Service Period End	
Must Use	DTM02	373	Date	X		DT 8/8	
	Date expressed as CCYYMMDD	

	Segment:	SLN Subline Item Detail
	Position:	200
	Loop:	SLN        Optional
	Level:	Detail
	Usage:	Optional
	Max Use:	1
	Purpose:	To specify product subline detail item data
	Syntax Notes:	1	If either SLN04 or SLN05 is present, then the other is required.
		2	If SLN07 is present, then SLN06 is required.
		3	If SLN08 is present, then SLN06 is required.
		4	If either SLN09 or SLN10 is present, then the other is required.
		5	If either SLN11 or SLN12 is present, then the other is required.
		6	If either SLN13 or SLN14 is present, then the other is required.
		7	If either SLN15 or SLN16 is present, then the other is required.
		8	If either SLN17 or SLN18 is present, then the other is required.
		9	If either SLN19 or SLN20 is present, then the other is required.
		10	If either SLN21 or SLN22 is present, then the other is required.
		11	If either SLN23 or SLN24 is present, then the other is required.
		12	If either SLN25 or SLN26 is present, then the other is required.
		13	If either SLN27 or SLN28 is present, then the other is required.
	Semantic Notes:	1	SLN01 is the identifying number for the subline item.
		2	SLN02 is the identifying number for the subline level. The subline level is analogous to the level code used in a bill of materials.
		3	SLN03 is the configuration code indicating the relationship of the subline item to the baseline item.
		4	SLN08 is a code indicating the relationship of the price or amount to the associated segment.
	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.
		3	SLN09 through SLN28 provide for ten different product/service IDs for each item. For example: Case, Color, Drawing No., U.P.C. No., ISBN No., Model No., or SKU.
Notes:		The SLN will be used to group charges together.  	
		Required
	
		SLN~1~~A	

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	Attributes
Must Use	SLN01	350	Assigned Identification	M		AN 1/20	
	Alphanumeric characters assigned for differentiation within a transaction set	
	Used as a loop counter	
Must Use	SLN03	662	Relationship Code	M		ID 1/1	
	Code indicating the relationship between entities	
 	A		Add	

	Segment:	SAC Service, Promotion, Allowance, or Charge Information
	Position:	230
	Loop:	SLN        Optional
	Level:	Detail
	Usage:	Optional
	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.
		5	If SAC11 is present, then SAC10 is required.
		6	If SAC13 is present, then at least one of SAC02 or SAC04 is required.
		7	If SAC14 is present, then SAC13 is required.
		8	If SAC16 is present, then SAC15 is required.
	Semantic Notes:	1	If SAC01 is "A" or "C", then at least one of SAC05, SAC07, or SAC08 is required.
		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 is the quantity basis when the allowance or charge quantity is different from the purchase order or invoice quantity.
			SAC10 and SAC11 used together indicate a quantity range, which could be a dollar amount, that is applicable to service, promotion, allowance, or charge.
		5	SAC13 is used in conjunction with SAC02 or SAC04 to provide a specific reference number as identified by the code used.
		6	SAC14 is used in conjunction with SAC13 to identify an option when there is more than one option of the promotion.
		7	SAC16 is used to identify the language being used in SAC15.
	Comments:	1	SAC04 may be used to uniquely identify the service, promotion, allowance, or charge. In addition, it may be used in conjunction to further the code in SAC02.
		2	In some business applications, it is necessary to advise the trading partner of the actual dollar amount that a particular allowance, charge, or promotion was based on to reduce ambiguity. This amount is commonly referred to as "Dollar Basis Amount". It is represented in the SAC segment in SAC10 using the qualifier "DO" - Dollars in SAC09.
Notes:		Required
	
		SAC~C~~EU~DIS001~2400~~~.016~KH~1500~~~~~DUOS
SAC~C~~EU~LPC001~500~~~100.00~EA~.05
SAC~C~~EU~INT001~500~~~100.00~EA~.05
SAC~C~~EU~INT003~-500~~~100.00~EA~-.05
SAC~C~~EU~MSC003~2500~~~1~EA~25.00~~~~~METER SEAL REPLACEMENT CHARGE 

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	Attributes
Must Use	SAC01	248	Allowance or Charge Indicator	M		ID 1/1	
	Code which indicates an allowance or charge for the service specified	
 	C		Charge	
 	N		No Allowance or Charge	
	The amount in the SAC05 will be ignored when summing the invoice total.	
Must Use	SAC03	559	Agency Qualifier Code	X		ID 2/2	
	Code identifying the agency assigning the code values	
 	EU		Electric Utilities	
 	GU		Natural Gas Utilities	
Must Use	SAC04	1301	Agency Service, Promotion, Allowance, or Charge Code	X		AN 1/10	
	Agency maintained code identifying the service, promotion, allowance, or charge	
	RBC. Refer to Governing Documents for list of valid codes	
Must Use	SAC05	610	Amount	O		N2 1/15	
	Monetary amount	
	This field must be signed if it is negative.  The SAC08 multiplied by the SAC10 must always equal the SAC05	
Must Use	SAC08	118	Rate	O		R 1/9	
	Rate expressed in the standard monetary denomination for the currency specified	
	This field must be signed if it is negative.  The SAC08 multiplied by the SAC10 must always equal the SAC05.	
Must Use	SAC09	355	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	
	Refer to Governing Documents	
 	4A		Bobbin	
	A cylinder or spindle on which yarn or thread is wound	
	use for 4CP - Kilowatt Demand	
 	4B		Cap	
	Designates that the cap of a container is manufactured to dimensions that enable it to be used as a measuring device when mixing the contents of the container with another substance	
	use for 4CP - KVA Demand	
 	4C		Centistokes	
	1 * 10/-6 square meters/second	
	use for 4CP - Power Factor Adjusted	
 	4D		Curie	
	A unit of radioactivity equal to 3.7 * 10/10 disintegrations per second	
	use for 4CP - KVAR Demand	
 	99		Watt	
 	AF		Centigram	
	A unit of metric weight equal to 0.01 gram or 0.000035 ounce	
 	DA		Days	
 	DO		Dollars, U.S.	
 	EA		Each	
 	HH		Hundred Cubic Feet	
	ccf	
 	K1		Kilowatt Demand	
 	K2		Kilovolt Amperes Reactive Demand	
 	K3		Kilovolt Amperes Reactive Hour	
 	K4		Kilovolt Amperes	
 	K5		Kilovolt Amperes Reactive	
 	K7		Kilowatt	
 	KH		Kilowatt Hour	
 	MO		Months	
 	NA		Milligrams per Kilogram	
	use for NCP - Kilowatt Demand	
 	NB		Barge	
	use for NCP - KVA Demand	
 	NC		Car	
	use for NCP - Power Factor Adjusted	
 	ND		Net Barrels	
	use for NCP - KVAR Demand	
 	RA		Rack	
	use for Ratchet -  Kilowatt Demand	
 	RB		Radian	
	use for Ratchet -  KVA Demand	
 	RC		Rod (area) - 16.25 Square Yards	
	use for Ratchet -  Power Factor Adjusted	
 	RD		Rod (length) - 5.5 Yards	
	use for Ratchet -  KVAR Demand	
 	TD		Therms	
 	TZ		Thousand Cubic Feet	
Must Use	SAC10	380	Quantity	X		R 1/15	
	Numeric value of quantity	
	Consumption or Quantity
	
	This field must be signed if it is negative.  The SAC08 multiplied by the SAC10 must always equal the SAC05.	

	Segment:	TXI Tax Information
	Position:	237
	Loop:	SLN        Optional
	Level:	Detail
	Usage:	Optional
	Max Use:	10
	Purpose:	To specify tax information
	Syntax Notes:	1	At least one of TXI02 TXI03 or TXI06 is required.
		2	If either TXI04 or TXI05 is present, then the other is required.
		3	If TXI08 is present, then TXI03 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:		Required if taxes are applicable to the preceding SAC charge.
	
		TXI~FR~2.5~~~~~A	

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	Attributes
Must Use	TXI01	963	Tax Type Code	M		ID 2/2	
	Code specifying the type of tax	
 	CA		City Tax	
	Service Tax imposed by City	
 	CT		County Tax	
 	FR		Franchise Tax	
	Franchise Fee	
 	GR		Gross Receipts Tax	
 	LO		Local Tax (Not Sales Tax)	
	Service tax imposed on a local level	
 	LS		State and Local Sales Tax	
 	ST		State Sales Tax	
Must Use	TXI02	782	Monetary Amount	X		R 1/18	
	Monetary amount	
	Calculated Tax Amount.  If negative, this amount must be preceded by a negative sign.	
Must Use	TXI07	662	Relationship Code	O		ID 1/1	
	Code indicating the relationship between entities	
 	A		Add	
	The amount in the TXI02 is included when summing the invoice total.	

	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).
		2	TDS02 indicates the amount upon which the terms discount amount is calculated.
		3	TDS03 is the amount of invoice due if paid by terms discount due date (total invoice or installment amount less cash discount).
		4	TDS04 indicates the total amount of terms discount.
	Comments:	1	TDS02 is required if the dollar value subject to discount is not equal to the dollar value of TDS01.
Notes:		Required
	
		TDS01 is the total amount due for this invoice and must equal the algebraic sum of the amounts in the TXI02 and SAC05 segments with the exception of any charges that are designated to be ignored in the calculation in the TXI07 or SAC01.  If this amoutn is negative, send the minus sign.
	
		TDS~19875       (Represents $198.75 the decimal is implied)	

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	Attributes
Must Use	TDS01	610	Amount	M		N2 1/15	
	Monetary amount	
	Total 

If negative, this amount must be preceded by a negative sign.  Please note that this is an implied decimal field, do not send the decimal point.	

	Segment:	CTT Transaction Totals
	Position:	070
	Loop:
	Level:	Summary
	Usage:	Optional (Must Use)
	Max Use:	1
	Purpose:	To transmit a hash total for a specific element in the transaction set
	Syntax Notes:	1	If either CTT03 or CTT04 is present, then the other is required.
		2	If either CTT05 or CTT06 is present, then the other is required.
	Semantic Notes:
	Comments:	1	This segment is intended to provide hash totals to validate transaction completeness and correctness.
Notes:		Required
	
		CTT~1	

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	Attributes
Must Use	CTT01	354	Number of Line Items	M		N0 1/6	
	Total number of line items in the transaction set	
	The number of IT1 segments.	

	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.
Notes:		Required
	
		SE~35~000000001	

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	Attributes
Must Use	SE01	96	Number of Included Segments	M		N0 1/10	
	Total number of segments included in a transaction set including ST and SE segments	
Must Use	SE02	329	Transaction Set Control Number	M		AN 4/9	
	Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set