Broadband Customer Reporting – XML Release 2 Issue 16.8a

Column Title Possible Entries Format ExplanationReceived DateDateBlankDD/MM/YYYYHH:MM:SSThe date and time that the order was received onthe BT back end systems.Blank – the order is in a very early stage ofRejected ReasonAlready Provided / DuplicateEnd User post code is invalidEnd User Telephone numberunknownIncompatible Rented ProductsNumber served by non BroadbandExchangeIncomplete CRFInsufficient Address DetailsIncorrect order type requestedNo Current BT ServiceLine loss/length out of limitsEU and VP not served via the sameexchange.Alphanumeric255 Char MaxReview Date DD/MM/YYYYHH:MM:SSService ID FT or FTIP or BBIP or BBVS or BBDSand 9 numbersAlphanumeric30 Char Maxprogression on BT systemsThe reason for rejections of an order submitted byCRF (additionally see cancellation reasons).Already provided/duplicate – Telephone numberalready has service or current order in progress forrequested service.End user postcode is invalid - Where the post codegiven on the CRF is incorrect.End user telephone number unknown – Telephonenumber unknown or not matched to address/postcode supplied.Incompatible rented products – Telephone numbersupplied has existing incompatible products.Number served by non Broadband Exchange -Exchange serving the telephone line is not enabledfor the requested service.Incomplete CRF - Details on the CRF do not satisfythe criteria required for BT to process the order e.g.End User name is missing.Insufficient address details - Address details on theCRF do not satisfy the criteria required for BT toprocess the order.Incorrect order type requested - SP has selected thewrong order type e.g. provision instead ofconversion.No current BT service – No current BT PSTNservice at requested location.The unique identifier of the service.It never changes.