NJAIRE Data Reporting

1. NJAIRE Data Reporting Overview of Current Reporting Requirements Quality Reviews

2. Reporting Requirements Call Forms Form #3 – Accident Year 1998 – 2000, for policies issued or renewed before 7/1/1999 Form #4 – Accident Year 1999 – present, for policies issued or renewed on or after 7/1/1999

3. Reporting Requirements Sample Form:

4. Reporting Requirements Call Forms – Required Data Earned Exposures by Threshold and Territory - Current Account Quarter Only, in Car Years

5. Reporting Requirements Earned Exposures by Threshold and Accident Year (Individual insurers may vary)

6. Reporting Requirements Exposure Thresholds for Accident Year 2006 (Individual insurers may vary)

7. Reporting Requirements Exposure Thresholds for Accident Year 2006 Individual Company (Actual Data: Minimum 10,000 Exposures)

8. Reporting Requirements Exposure Thresholds for Accident Year 2006 Individual Company (Actual Data: Minimum 10,000 Exposures)

9. Reporting Requirements Call Forms – Required Data BI Paid Claimants by Insured Threshold by Territory and Accident Year

10. Reporting Requirements 2002 • Exposures (Insurers may vary) • BI Claimants (Insurers may vary)

11. Reporting Requirements Call Forms – Required Data (cont.) Reportable Claim Loss Amounts and Claimants by Territory and Accident Year Loss Adjustment Expenses for Reportable Claims, Allocated and Unallocated (separately or combined)

12. Reporting Requirements A Reportable Claim is . . . One that could not be made had the claimant selected the Verbal Threshold (Tort Limitation) , and One where the claimant had the Zero Dollar Threshold (No Tort Limitation) and the insured selected the Verbal Threshold …the basis for establishing NJAIRE

13. Reporting Requirements How are Reportable Claims Identified? Via the proper Reportable Claim Determination Form: Policies issued or renewed before 7/1/1999* Policies issued or renewed on or after7/1/1999* * This is when the definition of the Verbal Threshold changed.

14. Reporting Requirements Reportable Claims to Verbal BI by Accident Year (Individual insurers may vary)

15. Reporting Requirements Reportable Claims to Verbal BI Accident Year 2002 (Individual Insurers may vary)

16. Reporting Requirements Loss Severities by Year (Individual insurers may vary)

18. Reporting Requirements How are Reportable Claims Identified? Reportable Claimants should be reported consistent with the facts involved in the settling of the claim.

19. Reporting Requirements Due Dates: to ISO (other than CAIP) or AIPSO (CAIP only)

20. Quality Reviews Use of the Data Financial Impact on Companies Cost of Late, Erroneous Data Detecting Errors at the Call Form Level

21. 1. Use of the Data The Call Form data is used to calculate: the “pot” of losses to be reimbursed each company’s assessment each company’s reimbursement, plus its share of investment income each company’s share of the NJAIRE administrative expenses

22. 2. Financial Impact on Companies The magnitude of the financial transactions: $ 11 million every quarter via the monthly payments and quarterly disbursements (the provisional transactions) $ 550 million every year via the Annual Cash Settlement true-up

23. 3. Cost of Late, Erroneous Data The costs can be significant: Late Data - $ 50 per work day Resubmissions - $ 250 per quarter Undetected Data Errors – can be over $1,000,000!

24. 3. Cost of Late, Erroneous Data (cont.) How can it be that much? The ultimate Annual Cash Settlement formula assesses and reimburses based on BI claims: by threshold, territory & accident year BI claims in the wrong place have a real financial impact

25. 3. Cost of Late, Erroneous Data (cont.) Putting just 3 BI claims in the wrong threshold column can cost $ 60,000 Putting just 3 BI claims vs. zero threshold insureds in the wrong territory can cost $ 50,000

26. 4. Detecting Errors at the Call Form Level What is done today? ISO performs high level data checks upon receipt and in the financial transaction process Companies are contacted regarding unusual data

27. 4. Detecting Errors at the Call Form Level (cont.) AIPSO performs completeness checks and detailed checks on claim samples in the compliance audit process This covers about 10 companies per year

28. 4. Detecting Errors at the Call Form Level (cont.) The ISO and AIPSO checks alone cannot catch everything What can companies do? What kind of reviews will be useful?

29. 4. Detecting Errors at the Call Form Level (cont.) What types of errors are commonly made? How many can be caught by expending a reasonable amount of company resources?

30. 4. Detecting Errors at the Call Form Level (cont.) Common errors: Exposures: car months, written, cumulative, threshold BI Claims: threshold, territory

31. 4. Detecting Errors at the Call Form Level (cont.)

32. 4. Detecting Errors at the Call Form Level (cont.) Common errors: Reportables: claims included ALAE, ULAE: reported separately and combined

33. 4. Detecting Errors at the Call Form Level (cont.)

34. 4. Detecting Errors at the Call Form Level (cont.) Review needs: “Spreadsheet” Current & Previous Quarter’s Data Knowledge about your company About 15 minutes per quarter

35. Sample Spreadsheet(Exhibit C of handout)

36. 4. Detecting Errors at the Call Form Level (cont.) Exposures by threshold Data needed: Statewide totals General expectation: Volume +/-5% Zero Dollar Exposures as % of total +/-2%

37. 4. Detecting Errors at the Call Form Level (cont.) CompanyA: Earned Exposures by Quarter

38. 4. Detecting Errors at the Call Form Level (cont.) Company B: Earned Exposures byQuarter

39. 4. Detecting Errors at the Call Form Level (cont.) BI Paid Claims by Threshold Data needed: Statewide, all years General expectation: Similar volume, allowing for credibility, yrs included Claim Frequencies/Threshold similar, averaging 0.5-1.5 per 100 car years

40. 4. Detecting Errors at the Call Form Level (cont.) CompanyA: BI Claimants by Quarter

41. 4. Detecting Errors at the Call Form Level (cont.) CompanyB: BI Claimants by Threshold and Quarter

42. 4. Detecting Errors at the Call Form Level (cont.) Reportable Losses & Claims Data needed: Statewide, all years General expectations: Pct. of Verbal: 4-28%, avg. 15% Avg. Loss: $3-15,000, avg. $7,500

43. 4. Detecting Errors at the Call Form Level (cont.) CompanyB: Verbal and Reportable Claimants by Threshold and Quarter

44. 4. Detecting Errors at the Call Form Level (cont.) Loss Adjustment Expenses Data needed: Statewide by year General expectation: 5-35% of Reportable Losses, note: may lag Company Methodology: Formula?

45. 4. Detecting Errors at the Call Form Level (cont.) More difficult errors to detect: Territory errors Completeness

46. 4. Detecting Errors at the Call Form Level (cont.) Checks that could help: Territory: Additional proofreading, if posting numbers Visual checks

47. 4. Detecting Errors at the Call Form Level (cont.) Visual Checks by Territory – Possible Problem areas: Large change in Exposures by Quarter Exposures in Other Than Current Accident Year for the Current Quarter

48. 4. Detecting Errors at the Call Form Level (cont.) Visual Checks by Territory – Possible Problem areas: Zero Exposures > Verbal Exposures Claims vs. Zero > Claims vs. Verbal

49. 4. Detecting Errors at the Call Form Level (cont.) Visual Checks by Territory – Possible Problem areas: Reportable Claims > Claims vs. Verbal Reportable Losses w/o Reportable Claims, and vice-versa

50. 4. Detecting Errors at the Call Form Level (cont.)