Common use of Usage To Be Transmitted Clause in Contracts

Usage To Be Transmitted. 7.1.1 The following messages recorded by BellSouth will be transmitted to <<customer_name>>: Customer usage data for flat rated local call originating from <<customer_name>>’s End User lines (1FB or 1FR). The EODUF record for flat rate messages will include: Date of Call From Number To Number Connect Time Conversation Time Method of Recording From ▇▇▇ Rate Class Message Type Billing Indicators ▇▇▇▇ to Number 7.1.2 BellSouth will perform duplicate record checks on EODUF records processed to Optional Daily Usage File. Any duplicate messages detected will be deleted and not sent to <<customer_name>>. 7.1.3 In the event that <<customer_name>> detects a duplicate on Enhanced Optional Daily Usage File they receive from BellSouth, <<customer_name>> will drop the duplicate message (<<customer_name>> will not return the duplicate to BellSouth).

Usage To Be Transmitted. 7.1.1 The following messages recorded by BellSouth ▇▇▇▇▇▇▇▇▇ will be transmitted to <<customer_name>>: Customer usage data for flat rated local call originating from <<customer_name>>’s End User lines (1FB or 1FR). The EODUF record for flat rate messages will include: Date of Call From Number To Number Connect Time Conversation Time Method of Recording From ▇▇▇ Rate Class Message Type Billing Indicators ▇▇▇▇ Bill to Number 7.1.2 BellSouth will perform duplicate record checks on EODUF records processed to Optional Daily Usage File. Any duplicate messages detected will be deleted and not sent to <<customer_name>>. 7.1.3 In the event that <<customer_name>> detects a duplicate on Enhanced Optional Daily Usage File they receive from BellSouth, <<customer_name>> will drop the duplicate message (<<customer_name>> will not return the duplicate to BellSouth).