248 Account Assignment/Inquiry and Service/Status

Functional Group ID=SU

Introduction:

This Draft Standard for Trial Use contains the format and establishes the data contents of the Account Assignment/Inquiry and Service/Status Transaction Set (248) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used for two-way, multi-transactional purposes of assigning accounts for collection, reporting status inquiries and inquiry responses and to update accounts between entities.

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	BHT	Beginning of Hierarchical Transaction	M	1									
			LOOP ID - NM1			2								
M	030	NM1	Individual or Organizational Name {Distribution Company)	M	1		n1							
														
			LOOP ID - NM1			2								
M	030	NM1	Individual or Organizational Name {Supplier)	M	1									

Detail:

	Pos.	Seg.		Req.		Loop	Notes and
	No.	ID	Name	Des.	Max.Use	Repeat	Comments	
			LOOP ID - HL			>1								
M	010	HL	Hierarchical Level	M	1		n2							
M	020	NM1	Individual or Organizational Name {Customer Name)	M	1		n3							
	060	REF	Reference Identification {Non-Billing Party Account ID)	O	>1									
	060	REF	Reference Identification {Customer Account ID or SDID)	O	>1									
	060	REF	Reference Identification {Distribution Company Old Account ID)	O	>1									
	070	PER	Administrative Communications Contact	O	>1									
	110	BAL	Balance Detail {Balance Returned}	O	1									
			LOOP ID - DTP			>1								
	120	DTP	Date or Time or Period {Date Changes are Written Off Billing Party Books)	O	1									
														
M	180	SE	Transaction Set Trailer	M	1									

Transaction Set Notes

1.	The NM1 loop will contain only information pertaining to the Credit Grantor and the Agency.
2.	The HL loop will contain parent-child (subordinate) data relationships pertaining to the debtor and/or any association to the debtor.
3.	The NM1 segment will contain only information pertaining to the debtor and/or any subordinate association to the debtor.

	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~248~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	
	Refer to 004010 Data Element Dictionary for acceptable code values.	
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:	BHT Beginning of Hierarchical Transaction
	Position:	020
	Loop:
	Level:	Heading
	Usage:	Mandatory
	Max Use:	1
	Purpose:	To define the business hierarchical structure of the transaction set and identify the business application purpose and reference data, i.e., number, date, and time
	Syntax Notes:
	Semantic Notes:	1	BHT03 is the number assigned by the originator to identify the transaction within the originator's business application system.
		2	BHT04 is the date the transaction was created within the business application system.
		3	BHT05 is the time the transaction was created within the business application system.
	Comments:
Notes:		Required	
		BHT~0057~22~1234567890~20051127	

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	Attributes
Must Use	BHT01	1005	Hierarchical Structure Code	M		ID 4/4	
	Code indicating the hierarchical application structure of a transaction set that utilizes the HL segment to define the structure of the transaction set	
 	0057		Supergroup, subgroup, member	
	Debtor Customer	
Must Use	BHT02	353	Transaction Set Purpose Code	M		ID 2/2	
	Code identifying purpose of transaction set	
 	01		Cancellation	
	Reinstate	
	Used to reinstate a balance if the billing party intends to resume collection activities for the customer.	
 	22		Information Copy	
	Write Off	
	Used to notify the non-billing party that the billing party will no longer pursue collections for this customer.	
Used	BHT03	127	Reference Identification	O		AN 1/30	
	Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier	
	Unique Number identifying this transaction assigned by the sender of the transaction.  This number should be unique over all time.	
Used	BHT04	373	Date	O		DT 8/8	
	Date expressed as CCYYMMDD	
	The transaction creation date - the date that the data was processed by the originator's application system.	

	Segment:	NM1 Individual or Organizational Name {Distribution Company)
	Position:	030
	Loop:	NM1        Mandatory
	Level:	Heading
	Usage:	Mandatory
	Max Use:	1
	Purpose:	To supply the full name of an individual or organizational entity
	Syntax Notes:	1	If either NM108 or NM109 is present, then the other is required.
		2	If NM111 is present, then NM110 is required.
	Semantic Notes:	1	NM102 qualifies NM103.
	Comments:	1	NM110 and NM111 further define the type of entity in NM101.
Notes:		Required	
		NM1~8S~3~DISCO LTD~~~~~1~999999999~40	

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	Attributes
Must Use	NM101	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	NM102	1065	Entity Type Qualifier	M		ID 1/1	
	Code qualifying the type of entity	
 	3		Unknown	
Used	NM103	1035	Name Last or Organization Name	O		AN 1/35	
	Individual last name or organizational 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 ~).	
Used	NM108	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	
Used	NM109	67	Identification Code	X		AN 2/80	
	Code identifying a party or other code	
	Distribution Company Common Code Identifier	
Used	NM111	98	Entity Identifier Code	O		ID 2/3	
	Code identifying an organizational entity, a physical location, property or an individual	
 	40		Receiver	
	Entity to accept transmission	
	The receiver is the 'Non-Billing Party'	
 	41		Submitter	
	Entity transmitting transaction set	
	The sender is the 'Billing Party'	

	Segment:	NM1 Individual or Organizational Name {Supplier)
	Position:	030
	Loop:	NM1        Mandatory
	Level:	Heading
	Usage:	Mandatory
	Max Use:	1
	Purpose:	To supply the full name of an individual or organizational entity
	Syntax Notes:	1	If either NM108 or NM109 is present, then the other is required.
		2	If NM111 is present, then NM110 is required.
	Semantic Notes:	1	NM102 qualifies NM103.
	Comments:	1	NM110 and NM111 further define the type of entity in NM101.
Notes:		Required	
		NM1~SJ~3~SUPPLY LTD~~~~~1~111222333~41	

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	Attributes
Must Use	NM101	98	Entity Identifier Code	M		ID 2/3	
	Code identifying an organizational entity, a physical location, property or an individual	
 	SJ		Service Provider	
	Identifies name and address information as pertaining to a service provider for which billing is being rendered	
	Supplier	
Must Use	NM102	1065	Entity Type Qualifier	M		ID 1/1	
	Code qualifying the type of entity	
 	3		Unknown	
Used	NM103	1035	Name Last or Organization Name	O		AN 1/35	
	Individual last name or organizational 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 ~).	
Used	NM108	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	
Used	NM109	67	Identification Code	X		AN 2/80	
	Code identifying a party or other code	
	Supplier Common Code Identifier	
Used	NM111	98	Entity Identifier Code	O		ID 2/3	
	Code identifying an organizational entity, a physical location, property or an individual	
 	40		Receiver	
	Entity to accept transmission	
	The receiver is the 'Non-Billing Party'	
 	41		Submitter	
	Entity transmitting transaction set	
	The sender is the 'Billing Party'	

	Segment:	HL Hierarchical Level
	Position:	010
	Loop:	HL        Mandatory
	Level:	Detail
	Usage:	Mandatory
	Max Use:	1
	Purpose:	To identify dependencies among and the content of hierarchically related groups of data segments
	Syntax Notes:
	Semantic Notes:
	Comments:	1	The HL segment is used to identify levels of detail information using a hierarchical structure, such as relating line-item data to shipment data, and packaging data to line-item data.
			The HL segment defines a top-down/left-right ordered structure.
		2	HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.
		3	HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.
		4	HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information.
		5	HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.
Notes:		Required	
		HL~1~~24	

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	Attributes
Must Use	HL01	628	Hierarchical ID Number	M		AN 1/12	
	A unique number assigned by the sender to identify a particular data segment in a hierarchical structure	
	There will only be one 248 transaction per account, thus, the Hierarchical Level identification should always be "1".	
Must Use	HL03	735	Hierarchical Level Code	M		ID 1/2	
	Code defining the characteristic of a level in a hierarchical structure	
 	24		Supergroup	
	Debtor Customer	

	Segment:	NM1 Individual or Organizational Name {Customer Name)
	Position:	020
	Loop:	HL        Mandatory
	Level:	Detail
	Usage:	Mandatory
	Max Use:	1
	Purpose:	To supply the full name of an individual or organizational entity
	Syntax Notes:	1	If either NM108 or NM109 is present, then the other is required.
		2	If NM111 is present, then NM110 is required.
	Semantic Notes:	1	NM102 qualifies NM103.
	Comments:	1	NM110 and NM111 further define the type of entity in NM101.
Notes:		Required	
		NM1~D4~3~JOHN DOE	

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	Attributes
Must Use	NM101	98	Entity Identifier Code	M		ID 2/3	
	Code identifying an organizational entity, a physical location, property or an individual	
 	D4		Debtor	
Must Use	NM102	1065	Entity Type Qualifier	M		ID 1/1	
	Code qualifying the type of entity	
 	3		Unknown	
	The entity name is not segmented and will be transmitted in NM103 only.	
Used	NM103	1035	Name Last or Organization Name	O		AN 1/35	
	Individual last name or organizational name	
	Customer Name as it appears on the Customer's bill	

	Segment:	REF Reference Identification {Non-Billing Party Account ID)
	Position:	060
	Loop:	HL        Mandatory
	Level:	Detail
	Usage:	Optional
	Max Use:	>1
	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:		Customer Account ID assigned by the NBP 	
		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	
	Non-Billing Party Account ID - account number for end use [debtor] customer.	
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	
	Non-Billing Party Account ID	

	Segment:	REF Reference Identification {Customer Account ID or SDID)
	Position:	060
	Loop:	HL        Mandatory
	Level:	Detail
	Usage:	Optional
	Max Use:	>1
	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 {Distribution Company Old Account ID)
	Position:	060
	Loop:	HL        Mandatory
	Level:	Detail
	Usage:	Optional
	Max Use:	>1
	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
Used if Account Number has changed in last 45 days.	
		REF~45~1235367812	

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	
 	45		Old Account Number	
	Identifies accounts being changed	
	Previous Distribution Company assigned account number for end use [debtor] customer.	
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	
	Non-Billing Party Account ID	

	Segment:	PER Administrative Communications Contact
	Position:	070
	Loop:	HL        Mandatory
	Level:	Detail
	Usage:	Optional
	Max Use:	>1
	Purpose:	To identify a person or office to whom administrative communications should be directed
	Syntax Notes:	1	If either PER03 or PER04 is present, then the other is required.
		2	If either PER05 or PER06 is present, then the other is required.
		3	If either PER07 or PER08 is present, then the other is required.
	Semantic Notes:
	Comments:
Notes:		Required if available	
		PER~IC~~TE~7175551111~TE~7175551112	

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	Attributes
Must Use	PER01	366	Contact Function Code	M		ID 2/2	
	Code identifying the major duty or responsibility of the person or group named	
 	IC		Information Contact	
Used	PER03	365	Communication Number Qualifier	X		ID 2/2	
	Code identifying the type of communication number	
 	TE		Telephone	
Used	PER04	364	Communication Number	X		AN 1/80	
	Complete communications number including country or area code when applicable	
	Last Known Customer Telephone Number #1	
Used	PER05	365	Communication Number Qualifier	X		ID 2/2	
	Code identifying the type of communication number	
 	TE		Telephone	
Used	PER06	364	Communication Number	X		AN 1/80	
	Complete communications number including country or area code when applicable	
	Last Known Customer Telephone Number #2	

	Segment:	BAL Balance Detail {Balance Returned}
	Position:	110
	Loop:	HL        Mandatory
	Level:	Detail
	Usage:	Optional
	Max Use:	1
	Purpose:	To identify the specific monetary balances associated with a particular account
	Syntax Notes:
	Semantic Notes:
	Comments:
Notes:		Required	
		BAL~CD~BD~325.67
BAL~CD~BD~-250.00

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	Attributes
Must Use	BAL01	951	Balance Type Code	M		ID 1/2	
	Code indicating the type of balance	
 	CD		Cycle to Date	
	Denotes balance data associated with defined periods	
	Denotes balance data associated with defined periods	
Must Use	BAL02	522	Amount Qualifier Code	M		ID 1/3	
	Code to qualify amount	
 	BD		Balance Due	
Must Use	BAL03	782	Monetary Amount	M		R 1/18	
	Monetary amount	
	On an initial 248, this is the amount that the billing party will no longer pursue collections for.

On a cancellation 248, this is the same amount provided on the original 248 (do not reverse the signs).

A negative amount indicates that the non-billing party has been overpaid and is responsible for reimbursing the customer.

	Segment:	DTP Date or Time or Period {Date Changes are Written Off Billing Party Books)
	Position:	120
	Loop:	DTP        Optional
	Level:	Detail
	Usage:	Optional
	Max Use:	1
	Purpose:	To specify any or all of a date, a time, or a time period
	Syntax Notes:
	Semantic Notes:	1	DTP02 is the date or time or period format that will appear in DTP03.
	Comments:
Notes:		Required for an original 248 (BHT02 = 22)
Not used for cancellation 248 (BHT02 = 01)
	
		DTP~630~D8~19990226	

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	Attributes
Must Use	DTP01	374	Date/Time Qualifier	M		ID 3/3	
	Code specifying type of date or time, or both date and time	
 	630		Account Closed	
	Date the account was written off.	
Must Use	DTP02	1250	Date Time Period Format Qualifier	M		ID 2/3	
	Code indicating the date format, time format, or date and time format	
 	D8		Date Expressed in Format CCYYMMDD	
Must Use	DTP03	1251	Date Time Period	M		AN 1/35	
	Expression of a date, a time, or range of dates, times or dates and times	

	Segment:	SE Transaction Set Trailer
	Position:	180
	Loop:
	Level:	Detail
	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~28~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