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

2. Reporting Requirements 1.Call Forms  Form #3 – Accident Year 1997 – 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 2005 (Individual insurers may vary)

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

8. Reporting Requirements 2001 Exposures (Insurers may vary) BI Claimants (Insurers may vary)

9. 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)

10. 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

11. 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 after 7/1/1999* * This is when the definition of the Verbal Threshold changed.

13. Reporting Requirements How are Reportable Claims Identified? Reportable Claimants should be reported consistent with the settling of the claim. “Moving Day” “Grandma”

14. Reporting Requirements 2.Due Dates: to ISO (other than CAIP) or AIPSO (CAIP only) Account QuarterDue Date First QuarterMay 15 Second QuarterAugust 15 Third QuarterNovember 15 Fourth QuarterFebruary 15

15. Quality Reviews 1.Use of the Data 2.Financial Impact on Companies 3.Cost of Late, Erroneous Data 4.Detecting Errors at the Call Form Level

16. Quality Reviews 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

17. Quality Reviews 2.Financial Impact on Companies - The magnitude of the financial transactions: –$ 13 million every quarter via the monthly payments and quarterly disbursements (the provisional transactions) –$ 650 million every year via the Annual Cash Settlement true-up

18. Quality Reviews 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!

19. Quality Reviews 3.Cost of Errors, Late 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

20. Quality Reviews 3.Cost of Errors, Late Data (cont.) Putting just 3 BI claims in the wrong threshold column can cost $ 70,000 Putting just 3 BI claims vs. zero threshold insureds in the wrong territory can cost $ 50,000

21. Quality Reviews 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

22. Quality Reviews 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

23. Quality Reviews 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?

24. Quality Reviews 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?

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

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

27. Quality Reviews 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

28. Quality Reviews 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%

29. Quality Reviews Company A: Earned Exposures by Quarter

30. Quality Reviews Company B: Earned Exposures by Quarter

31. Quality Reviews 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

32. Quality Reviews Company A: BI Claimants by Quarter

33. Quality Reviews Company B: BI Claimants by Threshold and Quarter

34. Quality Reviews 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

35. Quality Reviews Company B: Verbal and Reportable Claimants by Threshold and Quarter

36. Quality Reviews 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?

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

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

39. Quality Reviews 4.Detecting Errors at the Call Form Level (cont.) Visual Checks by Territory – Possible Problem areas:  Large change in Exposures by Qtr.  Exposures in Other Than Current Qtr.

40. Quality Reviews 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

41. Quality Reviews 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

42. Quality Reviews

43. 4.Detecting Errors at the Call Form Level (cont.) Checks that could help:  Completeness  Other Existing Internal Data  Special Reports

44. Summary Poor data quality can have a large, hidden impact on your company’s bottom line With a reasonable effort you can help ensure that your company is properly assessed and reimbursed