TRRP Plan CYCLE Using File Transfer Protocol FTP

1
TRRP Plan CYCLEUsing File Transfer Protocol
(FTP)

• NFIP Bureau and Statistical
• Agent
• 6/2003

2
Data is posted to the FTP Site
Post Cycle
Pre Cycle
NFIP Front End Balancing
Cycle Ends
TRRP Cycle Overview
Cycle
Pre Cycle
Data is Run (Cycle Starts)
Errors Are Generated
Cycle
Rejects Are Generated
Cycle
3
Data is Posted on the FTP Site
TRRP Cycle Overview
(1) Company posts monthly financial data on the
FTP Site. (2) Company posts monthly transaction
data as described in the TRRP Plan.
4
Data is Posted to the FTP Site
Pre Cycle
NFIP Front End Balancing
TRRP Cycle Overview
(1) Data is examined for record counts and
dollar amounts. (2) Discrepancies will cause the
data to be rejected. (3) When this occurs the
BFSC department notifies the WYO company
accounting contact.
5
Pre Cycle
Data is Posted to the FTP Site
NFIP Front End Balancing
TRRP Cycle Overview
Pre Cycle
Data is Run (Cycle Starts)
(1) Reformat and pre-process. (2) Load policy
transactions to the policy database. (3) Load
claims transactions to the claims database. (4)
Process edits.
6
Pre Cycle
Data is Posted the FTP Site
NFIP Front End Balancing
TRRP Cycle Overview
Pre Cycle
Data is Run (Cycle Starts)
(1) NFIP will produce Reject data
information and generate reports. (2)
Reports are generated and are posted to
the FTP Site for companies vendors to
retrieve
Cycle
Rejects Are Generated
7
Policy Rejects
8
Rejects

• Rejects can occur on transactions such as an
  11A, a 17A, a 20A etc.
• If this occurs the entire transaction will be
  rejected
• Rejected transaction resides on Reject Master
  File
• Nothing processes to the databases
• Rejects are removed by resubmitting the
  corrected
• transaction with the reject control number
• included

9
Common Data Elements Causing Policy Rejects
Most policy transactions reject because of
invalid or incorrect data in the following fields

• Endorsement Effective Date
• PR009010
• PR009030
• PR009050
• Policy Effective Date
• PR007050
• PR007060
• PR007070

10
Common Data Elements Causing Policy Rejects
(continued)

• Policy Number
• PR004030
• PR004040
• PR004050
• PR004070
• PR004100
• PR006030
• Policy Termination Date
• PR059040

11
Common Reasons for Many Policy Rejects

• Incorrect Sort Sequence Key
• Submission of a cancellation and renewal in the
  same
• cycle for the same policy
• Submission of a policy correction transaction to
  change
• policy dates and an endorsement in the same
  cycle
• for the same policy
• Incorrect policy dates reported (gap in term
  periods)

12
Common Reasons for Many Policy Rejects (continued)

• Changing policy numbers on archived policies
• Correcting/removing rejects using policy
  correction txn
• Spaces or zeros submitted for Endorsement
  Effective Date
• Attempting to reinstate an active policy
• Attempting to cancel a policy that has already
  been archived
• or cancelled

13
Loss Rejects
14
Common Data Elements Causing Loss Rejects
Date of Loss

• CR066050 - Date of Loss is not on file for the
  policy
• CR066030 - Claim already on file for this policy
  and DOL

15
Common Reasons for Many Loss Rejects

• Loss transaction (other than open) was submitted
  but the
• loss was not on file
• Open Claim/Loss (31) transaction was submitted
  when an
• open transaction had already been submitted for
  the loss
• Claim/Loss transaction was submitted when there
  was no
• policy on file for the loss

16
(1) Generate monthly, historical, fiscal
and financial recon and variance
reports. (2) Provide reports to BFSC (3)
Generate error tapes/reports and
management information reports. (4) Data
is posted on the FTP site (5) Tapes and
reports sent by overnight mail to WYO
Companies/Vendors.
Pre Cycle
Data is Posted to the FTP
NFIP Front End Balancing
TRRP Cycle Overview
Pre Cycle
Data is Run (Cycle Starts)
Errors Are Generated
Cycle
Rejects Are Generated
Cycle
17
Policy Errors
18
Errors

• Errors can be transactional or data element based
• Transactional - Submitting a closed
  transaction on a
• closed loss
• Data Element - Invalid CWOP code
• Data submitted in error will be processed and an
  error
• will be generated
• Errors are removed by submitting the appropriate
• correction transaction

19
Common Data Elements Causing Policy Errors
Flood Risk Zone - PL021040
Reasons for error

• Flood Risk Zone does not correspond with Risk
  Rating
• Method, Program Type, Building/Contents
  Deductibles
• and Community Number
• Flood Risk Zone not reported

20
Premium Calculation Elements

• Policy Term Indicator
• Community Number
• Total Bldg/Cont Coverage
• Risk Rating Method

• CRS Credit Percentage
• New/Renewal Indicator
• Elevated Building Indicator
• Original Construction Date

21
Common Data Elements Causing Policy Errors
Base Flood Elevation (BFE) - PL049030 Lowest
Floor Elevation (LFE) - PL048030 Elevation
Difference - PL036040
Reasons for error

• Values submitted for BFE/LFE and Elev Diff do
  not compute
• If any are set to default values then all must
  be set to the
• default values or an error will be generated
• Misalignment of data reported in fields
• Spaces or zeros reported instead of asterisks

22
Common Data Elements Causing Policy Errors
Deductible - Building/Contents PL029040,
PL030030, PL029060, PL030060
Reasons for error

• Specific data elements do not coordinate (Flood
  Risk Zone,
• Risk Rating Method, Post-Firm Indicator)
• Spaces or zeros reported instead of asterisks

23
Common Data Elements Causing Policy Errors
CRS Classification Credit Percentage - PL139040
Reasons for error

• Related to Flood Risk Zone and Community Number
• WYO reported CRS credit does not match NFIP
  calculated
• CRS credit
• Spaces or zeros reported instead of asterisks

24
Common Data Elements Causing Policy Errors
Flood Risk Zone - PL021040
Reasons for error

• Flood Risk Zone does not correspond with Risk
  Rating
• Method, Program Type, Building/Contents
  Deductibles
• and Community Number
• Flood Risk Zone not reported

25
Common Data Elements Causing Policy Errors
Total Premium Refund - PL061050
Reasons for error

• Incorrect premium refund based upon
• Specific cancellation reason code
• Cancellation date
• Policy term/dates
• Computation of full refund vs. pro-rata refunds
  as defined
• in the TRRP Plan

26
Common Data Elements Causing Policy Errors
Total Calculated Premium - PI040030
Reasons for error

• Federal Policy Fee should not be included in the
  calculation
• On transactions 11 and 17, minimum premium
  is either
• 50 (policies effective prior to 05/01/1998)
  or
• 55 (policies effective on or after
  05/01/1998)
• Minimum premium should be calculated as
  endorsement
• premium minus (Community Probation Surcharge
  ICC
• Premium)

27
Common Data Elements Causing Policy Errors
Total Calculated Premium - PL040040, PL040050
Reasons for error

• Miscalculation of premium based on
  Building/Contents
• Coverage (1 and 3 year terms, FPF not included)
• Miscalculation of premium on PRP policies based
  on
• Building/Contents Coverage (FPF is not
  included)
• Discrepancy between WYO company rates and NFIP
• system rates

28
Common Data Elements Causing Policy Errors
Total Calculated Premium - PL040040,
PL040050 (continued)
Reasons for error

• Incorrect use of Post-Firm/Pre-Firm rates
• Early submission of monthly policy transactions
  prior to the
• implementation of a Rate and Rule project
• Incorrect rating elements reported on the policy
  transaction

29
Common Data Elements Causing Policy Errors
Street Address - PL011040
Reasons for error

• Improper use of blanks/zeros instead of
  asterisks to clear
• an address line
• Changing the Name or Descriptive Information
  Indicator
• from D to N without clearing address line 1
• Reporting the same address information on
  Address Line
• 1 and 2
• Submitting address information on different
  address lines
• in different WYO cycles

30
Common Data Elements Causing Policy Errors
Risk Rating Method - PL041060, PL041080
Reasons for error

• Risk Rating Method of 4, 6, 8, A, 1 or
  2 and specific
• rating elements do not coordinate together
• Misalignment of data reported in fields

31
Common Data Elements Causing Policy Errors
Diagram Number - PL160020 Lowest Adjacent Grade -
PL161020, PL161030 Elevation Certificate Date -
PL174030 Elevation Certificate Indicator -
PI126020 Original Construction Date - PI034020
Reasons for error

• Entire date is not reported by WYO company or
  Century
• is not completed (99 vs. 1999)
• Incorrect date format submitted (04151999 vs.
  19990415)
• Misalignment of data reported in field
• Lower case characters

32
Loss Errors
33
Most Common Data Elements Causing Loss Errors
CL077075 - Bldg Claim Payment Exceeds Bldg Pay
Limit
Reasons for error

• 90 of all CL077075 errors are due to improper
  use of
• the following calculation
• Building Damage - Building Deductible Expense
  of
• Temporary Flood Protection Building Payment
  Limit
• Use of incorrect deductible
• ACV loss with RCV damages reported or
• RCV loss with ACV damages reported

How to Fix It

• Payment Correction (64) transaction
• Recovery After Final Payment (52) transaction
• General Correction (61) transaction

34
Most Common Data Elements Causing Loss Errors
CL078065 - Cont Claim Payment Exceeds Cont Pay
Limit
Reasons for error

• Most CL078065 errors are due to improper use of
• the following calculation
• Contents Damage - Contents Deductible Expense
  of
• Contents Removal Contents Payment Limit
• Use of incorrect deductible

How to Fix It

• Payment Correction (64) transaction
• Recovery After Final Payment (52) transaction
• General Correction (61) transaction

35
Most Common Data Elements Causing Loss Errors
CL066070 - The loss was closed. Incorrect txn
type.
Reasons for error
Occurs when one of the following transactions
are submitted against a closed loss

• Change Reserve (37) transaction
• Partial Payment (40) transaction
• Close Claim/Loss (43) transaction
• Close Claim/Loss Without Payment (46) transaction

How to Fix It
Any activity against the policy or loss will
remove the error as long as the error does not
occur again.
36
Most Common Data Elements Causing Loss Errors
CL077035 - Bldg Claim Payment and no Bldg Case
Reasons for error
Final Payment Indicator was reported as A (no
case) and payments were reported.
How to Fix It
Submit a General Correction (61) transaction
with a Y or an N in the final payment
indicator.
37
Most Common Data Elements Causing Loss Errors
CL081040 - Conflicting CWOP Reason - Contents
Reasons for error
Final Payment Indicator was reported as A (no
case) and Claims Closed Without Payment Reason
was reported.
How to Fix It
Submit a General Correction (61) transaction with
a Y or an N in the final payment indicator.
38
Most Common Data Elements Causing Loss Errors
CL077060 - Bldg Claim Payment Exceeds Total Amt
of Ins CL078055 - Cont Claim Payment Exceeds
Total Amt of Ins
Reasons for error
Total Claim Payments cannot exceed Total
Insurance
How to Fix It

• Submit a Payment Correction (64) transaction.
• Submit a Recovery after Final Payment (52)
  transaction

39
Most Common Data Elements Causing Loss Errors
CL130030 - Both Bldg Claim Payments and CWOP
Reported
Reasons for error
Both payments and a CWOP reason were reported.
Only one of those fields should have been
reported.
How to Fix It
Remove the Claim Closed Without Payment Reason -
Bldg by submitting a General Correction (61)
transaction with asterisks in the CWOP reason
for building.
40
Most Common Data Elements Causing Loss Errors
CL066045 - Date of Loss not within a policy term.
Reasons for error

• Date of Loss must be within a term for the
  policy
• Policy cancelled mid-term (prior to the date of
  loss)
• Renewal did not process

How to Fix It

• If cancelled, all loss payments must be
  recovered
• If renewal never processed, renewal must be
  submitted

41
Most Common Data Elements Causing Loss Errors
CL073030 - Closed a claim w/payment w/o reporting
damage
Reasons for error

• Building Damage must be reported when claims
  payments
• are reported
• If loss closed without payment and damage is
  less than
• deductible, Building Damage must be reported.

How to Fix It
Submit a General Correction (61) transaction with
the building damage amount reported.
42
(1) No information goes out to the
companies. (2) System backups are made. (3)
Companies should prepare reject and error
correction information for submission
with next months data. (4) Re-Edits may be
run at this point
Data is posted to the FTP Site
Pre Cycle
NFIP Front End Balancing
Cycle Ends
TRRP Cycle Overview
Cycle
Pre Cycle
Data is Run (Cycle Starts)
Errors Are Generated
Rejects Are Generated
Cycle
Cycle
43
Post Cycle
Pre Cycle
Tapes Submitted To NFIP
NFIP Front End Balancing
Cycle Ends
TRRP Cycle Overview
Cycle
Pre Cycle
Tape Run Process (Cycle Starts)
Errors Are Generated
Rejects Are Generated
Rejects Are Generated
Cycle
Cycle