SSIS Software Specification - MinnesotaSSIS Software Specification Title IV-E Abstract Report – Proofing Messages Designer: Theresa Hill Project Manager: Kate Stolpman Last Updated:

SSIS Software Specification

Title IV-E Abstract Report – Proofing Messages

Designer: Theresa Hill

Project Manager: Kate Stolpman

Last Updated: August 22, 2013

Revision History

Revision Revision Description Updated by Date

Original Original Document for the Quarter 1, 2012 report,

release v12.1

Theresa Hill 03/08/12

1 v12.1

Proofing Message #1216 (Local Agency is

not the COFR) - Add Rock County to the

Lincoln/Lyon/Murray (SWHHS) region

(CNTY_CD = 88) using the new multi-county

tables (PR #12-0223-1839-24)

v12.2

Proofing Message #1101 (Court Ordered

Before Best Interest Date) - Exclude

Placements that started on or before

3/27/2000 from this message (PR #12-

0307-1652-08)

Proofing Message #1206 (Negative

Modification – IV-E Reimbursable is No) –

updated long message (PR #12-0327-1647-

53)

Child Count Proofing – change IV-E Eligibility

messages (1150, 1151, 1152, and 1153 to

warnings (PR# 12-0413-1341-51)


2 v12.3

Add Payment Proofing error message #1247

(Service Dates more than 13 Months after

Warrant / Eff Date) (PR #12-0416-0842-36)

Proofing Message #1201 (IV-E Reimbursable

is No) – Do not display if the payment is for

the discharge date (PR #12-0412-1530-16)

v12.4

Added Claimed Payment Proofing section


3 v13.1

Child Count Proofing – Add error messages

#1123 (No Title IV-E Maintenance

Agreement for Supervising Tribe) and #1124

(No Corrections Umbrella or Title IV-E

Maintenance Agreement) (PR# 12-1212-

1659-26)


Revision Revision Description Updated by Date

4 v13.2

Updated messages:

Changed #1151, #1152, and #1160 to

use the new MAXIS IV-E Eligibility and

Reimbursability test results fields (PR

#13-0107-1711-04)

Change the message text and logic of

proofing messages #1191, #1192, and

#1204 for the IV-E Group Provider

Rate tables (PR #13-0107-1745-36)

Change proofing messages #1123 &

#1124 to use the new Supervising

Agency "Effective Date" field (PR #13-

0124-1900-24)

Changed proofing message #1216 (Local

Agency is not the COFR) to use new field

label (PR #13-0222-1542-32)

New warning messages:

#1147 – Extension Review is Overdue

Extended (PR #13-0111-1551-58)

#1148 (Educational Transportation for

Ages 19-20) (PR #12-0625-1400-59)

#1207 (EFC-SIL - One Day Payment)

(PR #13-0111-1504-45)

New error messages:

#1154 (Not IV-E Eligible – Inconclusive)

(PR #13-0107-1725-38)

#1157 (Service Dates before IV-E

Eligibility Begins) (PR #13-0107-1715-

16)

#1197 (Invalid Tribe on License) (PR

#13-0118-1310-51)

Changed Standard Criteria for Child Count

Proofing - removed criteria that a payment

is not claimed (PR #13-0211-1334-34)


5 V13.3

New error message #1250 (Exclusion Exists)

(PR #13-0531-1514-17)


Table of Contents

SECTION ONE: PROOFING MESSAGES .......................................................................... 1 1.0 Introduction ...................................................................................................... 1 1.1 Payment Proofing ............................................................................................... 2

1.1.1 Standard Criteria for Payment Proofing......................................................... 3 1.1.2 Payment Proofing Message Summary ........................................................... 4

1.1.2.1 #107 - Estimated DOB ......................................................................... 8 1.1.2.2 #1018 – No PMI # ............................................................................... 9 1.1.2.3 #1100 – Court Ordered – No Best Interest Date .................................... 10 1.1.2.4 #1101 – Court Ordered Before Best Interest Date .................................. 11 1.1.2.5 #1102 – Voluntary – No Best Interest by Day 180 ................................. 12 1.1.2.6 #1103 – Voluntary – Best Interest after Day 180 ................................... 13 1.1.2.7 #1104 – Reasonable Efforts is Overdue ................................................ 15 1.1.2.8 #1110 – Age over Maximum ............................................................... 17 1.1.2.9 #1120 – No Continuous Placement ...................................................... 18 1.1.2.10 #1121 – Service Dates Partially Within a Continuous Placement .............. 19 1.1.2.11 #1122 – Multiple Continuous Placements .............................................. 20 1.1.2.12 #1123 – No Title IV-E Maintenance Agreement for Supervising Tribe ....... 21 1.1.2.13 #1124 – No Corrections Umbrella or Title IV-E Maintenance Agreement ... 23 1.1.2.14 #1125 – Supervising Agency must be the Tribe ..................................... 25 1.1.2.15 #1130 – No DOC Assessment .............................................................. 26 1.1.2.16 #1131 – Higher DOC Points Paid .......................................................... 27 1.1.2.17 #1132 – Lower DOC Points Paid .......................................................... 29 1.1.2.18 #1133 – No DOC Assessment – Zero Points Paid ................................... 31 1.1.2.19 #1134 – Duplicate DOC Assessments ................................................... 32 1.1.2.20 #1140 – Not Eligible for Extended Foster Care ....................................... 33 1.1.2.21 #1141 – No Foster Care Extension Condition ......................................... 34 1.1.2.22 #1143 – Extension Condition Needed Through the Service End Date ........ 35 1.1.2.23 #1144 – EFC-SIL – Invalid Service ....................................................... 37 1.1.2.24 #1145 – EFC-SIL – Invalid Placement Setting........................................ 38 1.1.2.25 #1146 – EFC-SIL – Client Under 18 ...................................................... 39 1.1.2.26 1147 – Extension Review is Overdue .................................................... 40 1.1.2.27 #1148 – Educational Transportation for Ages 19-20 ............................... 42 1.1.2.28 #1150 – No MAXIS IV-E Eligibility Information ...................................... 43 1.1.2.29 #1151 – Not IV-E Eligible – Denied ...................................................... 44 1.1.2.30 #1152 – Not IV-E Eligible – Closed ...................................................... 45 1.1.2.31 #1153 – No IV-E Eligibility for the Cont Placement #.............................. 46 1.1.2.32 #1154 – Not IV-E Eligible – Inconclusive .............................................. 47 1.1.2.33 #1155 - VPA Date Mismatch ................................................................ 48 1.1.2.34 #1156 - Best Interest Date Mismatch ................................................... 49 1.1.2.35 #1157 – Service Dates before IV-E Eligibility Begins .............................. 50 1.1.2.36 #1160 – Not IV-E Reimbursable .......................................................... 51 1.1.2.37 #1161 – No IV-E Reimbursability for One Year ...................................... 52 1.1.2.38 #1162 – No IV-E Reimbursability for Nine Months .................................. 53 1.1.2.39 #1170 - Invalid Special Cost Code ....................................................... 55 1.1.2.40 #1171 – No Maintenance Claim – Additional Cost .................................. 56 1.1.2.41 #1172 – No Maintenance Claim – Admin ............................................... 57 1.1.2.42 #1173 – No Maintenance Claim – Difficulty of Care (DOC) ...................... 58 1.1.2.43 #1174 – No Maintenance Claim – Adjustment of DOC ............................ 59 1.1.2.44 #1175 – Service Dates Invalid with Maintenance Claim – Additional Cost .. 61 1.1.2.45 #1176 – Service Dates Invalid with Maintenance Claim - Admin .............. 63

1.1.2.46 #1177 – Service Dates Invalid with Maintenance Claim - Difficulty of Care

(DOC)............................................................................................... 64 1.1.2.47 #1178 – Service Dates Invalid with Maintenance Claim - Adjustment of

DOC ................................................................................................. 65 1.1.2.48 #1179 – Initial Clothing – Invalid Service Dates .................................... 67 1.1.2.49 #1180 – Group Provider – Invalid IV-E Service Type .............................. 68 1.1.2.50 #1181 – Invalid BRASS Service ........................................................... 69 1.1.2.51 #1190 – No License # on Payment ...................................................... 70 1.1.2.52 #1191 – No Effective IV-E Provider Rate ............................................... 71 1.1.2.53 #1192 – Invalid IV-E Sub Code ........................................................... 73 1.1.2.54 #1193 – License Status must be Granted ............................................. 74 1.1.2.55 #1194 – Facility Type not 001, OSH or OT2 .......................................... 75 1.1.2.56 #1195 – License Record does not exist for Bus Org ................................ 77 1.1.2.57 #1196 – Service Dates not Valid with License Dates ............................... 78 1.1.2.58 #1197 – Invalid Tribe on License ......................................................... 80 1.1.2.59 #1201 – IV-E Reimbursable is No ........................................................ 82 1.1.2.60 #1202 – Service Dates too Old to Claim ............................................... 83 1.1.2.61 #1203 – Negative Modification too Old to Claim ..................................... 84 1.1.2.62 #1204 – Basic Per Diem does not Match Approved Per Diem ................... 86 1.1.2.63 #1205 – Unit Type not Valid ................................................................ 88 1.1.2.64 #1206 – Negative Modification – IV-E Reimbursable is No ....................... 89 1.1.2.65 #1207 – EFC-SIL - One Day Payment ................................................... 91 1.1.2.66 #1210 – No IV-E Placement ................................................................ 93 1.1.2.67 #1211 – Service Dates Partially Within a Placement ............................... 94 1.1.2.68 #1212 – Multiple Placements ............................................................... 95 1.1.2.69 #1213 – Multiple Bus Orgs on Placement History ................................... 97 1.1.2.70 #1214 – Placement Bus Org Different than Payment .............................. 98 1.1.2.71 #1215 – Courtesy Supervision is not IV-E Reimbursable ......................... 99 1.1.2.72 #1216 – Local Agency is not the COFR ............................................... 100 1.1.2.73 #1217 – Overlapping Location or Absence .......................................... 102 1.1.2.74 #1220 – Authority is Protective Hold .................................................. 104 1.1.2.75 #1221 – No Voluntary or Court Ordered Authority ............................... 105 1.1.2.76 #1222 – Authority Effective Date more than a Month Before Continuous

Placement Start Date ....................................................................... 106 1.1.2.77 #1230 – Service Invalid for Rule Code ................................................ 107 1.1.2.78 #1231 – Rule 4 – Invalid Special Cost Code ........................................ 108 1.1.2.79 #1232 – Special Cost Code 14 - Invalid Rule Code ............................... 109 1.1.2.80 #1240 – Warrant / Eff Date before Service End Date ............................ 110 1.1.2.81 #1241 – Initial Clothing - Warrant / Eff Date before Service End Date .... 111 1.1.2.82 #1242 – Service Start and End Dates not in the Same Month ................ 112 1.1.2.83 #1243 – Another Claim Already Exists ................................................ 113 1.1.2.84 #1244 – EFC-SIL – Another Claim Already Exists ................................. 115 1.1.2.85 #1245 –Discharge Date is not Reimbursable ....................................... 116 1.1.2.86 #1246 – Units do not Match the Days of Service .................................. 117 1.1.2.87 #1247 – Service Dates more than 13 Months after Warrant / Eff Date .... 118 1.1.2.88 #1250 – Exclusion Exists .................................................................. 119

1.2 Claimed Payment Proofing .............................................................................. 120 1.2.1 Standard Criteria for Claimed Payment Proofing ........................................ 121 1.2.2 Claimed Payment Proofing Message Summary ........................................... 122

1.2.2.1 #1123 – No Title IV-E Maintenance Agreement for Supervising Tribe ..... 125 1.2.2.2 #1124 – No Corrections Umbrella or Title IV-E Maintenance Agreement . 126 1.2.2.3 #1193 – License Status must be Granted ........................................... 126

1.3 Child Count Proofing ....................................................................................... 127

1.3.1 Standard Criteria for Child Count Proofing ................................................. 128 1.3.2 Child Count Proofing Message Summary ................................................... 130

1.3.2.1 #1150 – No MAXIS IV-E Eligibility Information .................................... 131 1.3.2.2 #1151 – Not IV-E Eligible - Denied..................................................... 131 1.3.2.3 #1152 – Not IV-E Eligible - Closed ..................................................... 132 1.3.2.4 #1153 – No IV-E Eligibility for the Cont Placement #............................ 133 1.3.2.5 #1154 – Not IV-E Eligible – Inconclusive ............................................ 134 1.3.2.6 #1157 – Service Dates before IV-E Eligibility Begins ............................ 134 1.3.2.7 #1301 – ICWA Indicator is Blank ....................................................... 135

RELATED DOCUMENTS ............................................................................................ 137

SS Title IV-E Abstract Report - Proofing Messages.docm

Last Updated: 08/22/13 Title IV-E Abstract Report

Proofing Messages

Page 1 of 139

SECTION ONE: PROOFING MESSAGES

1.0 Introduction

This document contains detailed information for all payment proofing messages for the Title

IV-E Abstract Report, which contains the follow proofing tabs:

Payment Proofing – displays non-reimbursable payments with error messages

indicating the reason a IV-E Claim cannot be created and payments claimed on the

selected report with warning messages identifying potentially incorrect information

and situations which may cause future payments to be non-reimbursable.

Claimed Payment Proofing - displays payments with IV-E Claims with error messages

indicating the reason the payment is no longer reimbursable.

Child Count Proofing - displays payments with error messages indicating the reason

the payment cannot be included in the Child Counts and payments counted on the

selected report with warning messages identifying potentially incorrect information.

Child Count Proofing and Claimed Proofing use a subset of the messages used for Payment

Proofing. The Standard Criteria for Proofing is different for each type of proofing.



Proofing Messages

Page 2 of 139

1.1 Payment Proofing

The following figure shows an example of the Payment Proofing screen for a Title IV-E

Abstract Report.

Figure 1-1: Payment Proofing Screen



Proofing Messages

Page 3 of 139

1.1.1 Standard Criteria for Payment Proofing

Listed below is the standard criteria for payment proofing. Payment proofing displays for

payments that meet these criteria along with the error conditions defined for the proofing

message. A payment can have multiple proofing messages.

Exceptions for messages that ignore one or more standard criteria are noted in the “Error

Condition” section of the message. For example, message #107, Estimated DOB, overrides

the standard criteria that the Person has an Actual DOB.

Criteria Details Ref

"Warrant / Eff Date" is between the

Report Payment Dates

PYMT_DT between Report Payment Start

Date and Report Period End Date

1.0

"Service Start Date" is >= Report

Service Start Date

PYMT_SVC_START_DT >= Report

Service Start Date

2.0

"Payment Status" is "Paid" PYMT_STATUS_CD = 'PD' 3.0

A IV-E Claim does not exist for the

Payment

(select count(*)

from IVE_ABSTRACT_CLAIM C

where PAYMENT_ID = C.PAYMENT_ID )

= 0

4.0

IV-E Reimbursable = "Yes" IVE_REIMB_IND = 'Y' 5.0

A Person is selected on the Payment PAYMENT.PERSON_ID =

PERSON.PERSON_ID

6.0

"Service" is a Reimbursable Service ServiceCode in (‘171’, ‘180’, ‘181’, ‘183’,

‘185’, ‘188’, ‘214’, ‘483’)

7.0

The Person has a PMI # (except edits

specifically for a claimable record with no

"PMI #" or where specifically excluded)

PERSON.PMI is not null 8.0

The Person has an Actual DOB (except

edits specifically for a claimable record

with no "Actual Date of Birth" or where

specifically excluded)

PERSON.BIRTH_DT is not null 9.0

“Payment Type” is one of the following

Code Description

1 Payment Request

2 Posted Payment

3 Correcting Entry Adjustment

PYMT_TYPE_CD in (‘1’, ’2’, ’3’) 10.0



Proofing Messages

Page 4 of 139


The Net Amount > 0 PAYMENT.PYMT_PAID_AMT +

(select nvl(sum(PYMT_PAID_AMT),0)

from PAYMENT P

where P.ORIG_PAYMENT_ID =

PAYMENT_ID

and P.PYMT_TYPE_CD in

(‘4’,’5’,’6’,’7’,’8’)

and P.PYMT <= Report Period End

Date

) > 0

11.0

An Exclusion for the Title IV-E Abstract

Report does not exist for the Payment

(select count(*)

from EXCL_PYMT_XREF X

where PAYMENT_ID = X.PAYMENT_ID

and EXCL_MODULE_CD = '01'

) = 0

12.0

Table 1-1: Payment Proofing Criteria

1.1.2 Payment Proofing Message Summary

The table below lists the Payment Proofing checkboxes and messages.

Checkbox

Label

Message

# Description

Claim

Warnings

1132 Lower DOC Points Paid

1133 No DOC Assessment – Zero Points Paid

1147 Extension Review is Overdue

1148 Educational Transportation for Ages 19-20

1162 No IV-E Reimbursability for Nine Months

1204 Basic Per Diem does not Match Approved Per Diem

1207 EFC-SIL – One Day Payment

1217 Overlapping Location or Absence

1222 Authority Effective Date more than a Month Before

Continuous Placement Start Date

Client 107 Estimated DOB

1018 No PMI #

1110 Age over Maximum



Proofing Messages

Page 5 of 139

Checkbox

Label

Message

# Description

Continuous

Placement

1120 No Continuous Placement

1121 Service Dates Partially Within a Continuous Placement

1122 Multiple Continuous Placements

1123 No Title IV-E Maintenance Agreement for Supervising Tribe

1124 No Corrections Umbrella or Title IV-E Maintenance Agreement

1125 Supervising Agency must be the Tribe

Court Actions 1100 Court Ordered – No Best Interest Date

1101 Court Ordered Before Best Interest Date

1102 Voluntary – No Best Interest by Day 180

1103 Voluntary – Best Interest after Day 180

1104 Reasonable Efforts is Overdue

DOC 1130 No DOC Assessment

1131 Higher DOC Points Paid

1134 Duplicate DOC Assessments

Exclusions 1250 Exclusion Exists

Extended

Foster Care

1140 Not Eligible for Extended Foster Care

1141 No Foster Care Extension Condition

1143 Extension Condition Needed Through the Service End Date

1144 EFC-SIL – Invalid Service

1145 EFC-SIL – Invalid Placement Setting

1146 EFC-SIL – Client Under 18

IV-E Eligibility 1150 No MAXIS IV-E Eligibility Information

1151 Not IV-E Eligible – Denied

1152 Not IV-E Eligible - Closed

1153 No IV-E Eligibility for the Cont Placement #

1154 Not IV-E Eligible – Inconclusive

1155 VPA Date Mismatch

1156 Best Interest Date Mismatch

1157 Service Dates before IV-E Eligibility Begins

IV-E

Reimbursability

1160 Not IV-E Reimbursable

1161 No IV-E Reimbursability for One Year



Proofing Messages

Page 6 of 139

Checkbox

Label

Message

# Description

IV-E Service

Type

1170 Invalid Special Cost Code

1171 No Maintenance Claim – Additional Cost

1172 No Maintenance Claim – Admin

1173 No Maintenance Claim – Difficulty of Care (DOC)

1174 No Maintenance Claim – Adjustment of DOC

1175 Service Dates Invalid with Maintenance Claim – Additional

Cost

1176 Service Dates Invalid with Maintenance Claim - Admin

1177 Service Dates Invalid with Maintenance Claim – Difficulty of

Care (DOC)

1178 Service Dates Invalid with Maintenance Claim - Adjustment of

DOC

1179 Initial Clothing – Invalid Service Dates

1180 Group Provider – Invalid IV-E Service Type

1181 Invalid BRASS Service

License # / IV-

E Sub Code

1190 No License # on Payment

1191 No Effective IV-E Provider Rate

1192 Invalid IV-E Sub Code

1193 License Status must be Granted

1194 Facility Type not 001, OSH or OT2

1195 License Record does not exist for Bus Org

1196 Service Dates not Valid with License Dates

1197 Invalid Tribe on License

Other 1201 IV-E Reimbursable is No

1202 Service Dates too Old to Claim

1203 Negative Modification too Old to Claim

1205 Unit Type not Valid

1206 Negative Modification – IV-E Reimbursable is No



Proofing Messages

Page 7 of 139

Checkbox

Label

Message

# Description

Placement 1210 No IV-E Placement

1211 Service Dates Partially within a Placement

1212 Multiple Placements

1213 Multiple Bus Orgs on Placement History

1214 Placement Bus Org Different than Payment

1215 Courtesy Supervision is not IV-E Reimbursable

1216 Local Agency is not the COFR

Placement

Authority

1220 Authority is Protective Hold

1221 No Voluntary or Court Ordered Authority

Rule Code 1230 Service Invalid for Rule Code

1231 Rule 4 – Invalid Special Cost Code

1232 Special Cost Code 14 - Invalid Rule Code

Service Dates 1240 Warrant / Eff Date before Service End Date

1241 Initial Clothing - Warrant / Eff Date before Service End Date

1242 Service Start and End Dates not in the Same Month

1243 Another Claim Already Exists

1244 EFC-SIL – Another Claim Already Exists

1245 Discharge Date is not Reimbursable

1246 Units do not Match the Days of Service

1247 Service Dates more than 13 Months after Warrant / Eff Date

Table 1-2: Payment Proofing Messages



Proofing Messages

Page 8 of 139

1.1.2.1 #107 - Estimated DOB

Checkbox Label Client Message # 107

Description Estimated DOB

Rule Client must have an Actual DOB

Severity Error Navigates

To

Client node container (Person

Screen) Navigation Hint Client

Short Message "Est. date of birth" ([@ClientEDOB]).

Example Client: "Est. date of birth" (09/01/1997).

Long Message The client has an estimated date of birth. The client must have an

actual date of birth.

Parameters @ClientEDOB = PERSON.ESTIMATED_BIRTH_DT, formatted as

mm/dd/yyyy

Error Condition

Exclude the following standard criteria from this edit:

The Person has a PMI # – display the message regardless of

whether the client has a PMI

The Person has an Actual DOB

Display when client does not have an actual date of birth

PERSON.BIRTH_DT is null



Proofing Messages

Page 9 of 139

1.1.2.2 #1018 – No PMI #


Description No PMI #

Rule Client must have a PMI number


To



Short Message No PMI #.

Example Client: No PMI #.

Long Message The client does not have a Person Master Index (PMI) number in SSIS.

The client must have a PMI #.

Parameters None

Error Condition


The Person has a PMI #

The Person has an Actual DOB – display the message regardless

of whether the client has an Actual Date of Birth or an Estimated

Date of Birth

Display when the client does not have a PMI number

PERSON.PMI is null for PAYMENT.PERSON_ID



Proofing Messages

Page 10 of 139

1.1.2.3 #1100 – Court Ordered – No Best Interest Date

Checkbox Label Court Actions Message # 1100

Description Court Ordered – No Best Interest Date

Rule If the Initial Placement Authority = “Court Ordered,” a Best Interest

Statement is required.


To

Client | Court Actions node

container Navigation Hint Court Actions

Short Message A “Best Interest Statement” is required for a “Court Ordered”

placement.

Example Continuous Placement: A “Best Interest Statement” is required for a

“Court Ordered” placement.

Long Message

The “Initial Placement Authority” is “Court Ordered” and a “Best

Interest Statement” does not exist for the Continuous Placement. The

earliest Court record with the “Continuous Placement” selected on the

Child Findings tab must have the “Best Interest Statement” equal “Yes”

and a value in the corresponding “Date” field.

Parameters None

Error Condition

Display when all of the following conditions are true:

A Continuous Placement exist for the service dates

ValidContPlcmt for PYMT_SVC_START_DT through

PYMT_SVC_END_DT

The “Initial Placement Authority” is “Court Ordered”

ValidPlaceAuth and PLACE_AUTH_CD = ‘2’

A Best Interest Statement does not exist for the Continuous

Placement

not exists (select *

from COURT_DETAIL CD

where BEST_INTEREST_IND = 'Y'

and BEST_INTEREST_DT is not null

and CD.CONTPLCMT_ID = CONTPLCMT_ID)



Proofing Messages

Page 11 of 139

1.1.2.4 #1101 – Court Ordered Before Best Interest Date


Description Court Ordered Before Best Interest Date

Rule If the Initial Placement Authority = “Court Ordered,” the “Effective

Date” must be on or after the “Initial Best Interest Date”


To



Short Message The "Effective Date" ([@COEffDt]) of a Court Ordered placement must

be on or after the Best Interest Date ([@BestIntDt]).

Example Court Actions: The “Effective Date” (06/05/2011) of a Court Ordered

placement must be on or after the Best Interest Date (06/15/2011).

Long Message

The “Initial Placement Authority” for this Continuous Placement is

“Court Ordered.” The earliest Best Interest “Date” on the Child

Findings tab of the Court Detail record is after the Placement Authority

“Effective Date.”

Parameters @COEffDt = trunc(PLACE_AUTH_EFF_DT)

@BestIntDt = COURT_DETAIL.BEST_INTEREST_DT

Error Condition




PYMT_SVC_END_DT



The Initial Best Interest Statement is after the “Effective Date”

of the “Court Ordered” authority

trunc(PLACE_AUTH_EFF_DT) <

(select min(BEST_INTEREST_DT)





The “Continuous Placement Start Date” is after 03/27/2000

(added in v12.2, PR #12-0307-1704-54)

trunc(CONTPLCMT_START_DT) >

to_date(‘03/27/2000’, ’mm/dd/yyyy’)



Proofing Messages

Page 12 of 139

1.1.2.5 #1102 – Voluntary – No Best Interest by Day 180


Description Voluntary – No Best Interest by Day 180

Rule If the Initial Placement Authority = “Voluntary,” a Best Interest

Statement is required for service dates after the BestIntReqdDate.


To



Short Message The service dates are after the 180th day ([@BestIntDueDt]) of a

Voluntary placement and a “Best Interest Statement” does not exist.

Example

Court Actions: The service dates are after the 180th day (06/05/2011)

of a Voluntary placement and a “Best Interest Statement” does not

exist.

Long Message

The “Initial Placement Authority” is “Voluntary” and a “Best Interest

Statement” does not exist for the Continuous Placement. The “Best

Interest Statement” must be “Yes” and the “Date” on the Child Findings

tab of a Court Detail record must be on or before the 180th day of the

Continuous Placement to claim IV-E for service dates after the 180th

day.

Parameters @BestIntDueDt = BestIntReqdDate

Error Condition




PYMT_SVC_END_DT

The “Initial Placement Authority” is “Voluntary”


The service dates are after the BestIntReqdDate

PYMT_SVC_END_DT > BestIntReqdDate

A Best Interest Statement does not exist








Proofing Messages

Page 13 of 139

1.1.2.6 #1103 – Voluntary – Best Interest after Day 180


Description Best Interest after Day 180

Rule If the Initial Placement Authority = “Voluntary,” the Best Interest

Statement must be dated on or before the BestIntReqdDate. If not,

service dates after the BestIntReqdDate are not IV-E reimbursable.


To



Short Message The initial “Best Interest Statement” ([@InitBestIntDt]) must be on or

before the 180th day ([@BestIntDueDt]) of the Continuous Placement.

Example

Court Actions: The initial “Best Interest Statement” (06/12/2011) must

be on or before the 180th day (06/05/2011) of the Continuous

Placement.

Long Message

The “Initial Placement Authority” is “Voluntary” and the service dates

are after the 180th day of the Continuous Placement. The “Best

Interest Statement” must be “Yes” and the “Date” must be on or before

the 180th day on the Child Findings tab of a Court Detail record to

claim IV-E for service dates after the 180th day.

Parameters @InitBestIntDt = COURT_DETAIL.BEST_INTEREST_DT

@BestIntDueDt = BestIntReqdDate



Proofing Messages

Page 14 of 139

Error Condition




PYMT_SVC_END_DT



The service dates are after the BestIntReqdDate

PYMT_SVC_END_DT > BestIntReqdDate

A Best Interest Statement exists that is dated after the

BestIntReqdDate

(select min(BEST_INTEREST_DT)




and CD.CONTPLCMT_ID = CONTPLCMT_ID

and BEST_INTEREST_DT > BestIntReqdDate

) returns a record

A Best Interest Statement on or before the BestIntReqdDate

does not exist


from COURT_DETAIL CD2




and BEST_INTEREST_DT <= BestIntReqdDate)



Proofing Messages

Page 15 of 139

1.1.2.7 #1104 – Reasonable Efforts is Overdue


Description Reasonable Efforts is Overdue

Rule Reasonable efforts to finalize permanency are required within 14

months of the continuous placement start date, and every 12 months

thereafter.


To



Short Message A “Reasonable efforts to finalize permanency plan” is overdue.

Example Court Actions: A “Reasonable efforts to finalize permanency plan” is

overdue.

Long Message

The service dates are more than 14 months after the Continuous

Placement “Start Date.” The “Reasonable efforts to finalize

permanency plan made” on the Child Findings tab on the Court Detail

record for the Continuous Placement must be “Yes” and the “Date” no

more than 12 months before the service dates to claim IV-E.

Reimbursability will resume on the first of the month in which the

reasonable efforts to finalize statement is completed.

Parameters None



Proofing Messages

Page 16 of 139

Error Condition

Determine the date to use for comparison:

If PYMT_SVC_START_DT <= Report Period End Date

CompareDate = PYMT_SVC_START_DT

Otherwise (future dates)

CompareDate = Report Period End Date




PYMT_SVC_END_DT

The IV-E Service Type is “Maintenance” or “Basic Maintenance”

ValidIV-EServiceType and IVE_SVC_TYPE_CD in (‘A’, ‘E’)

The CompareDate is more than 14 months after the continuous

placement start date

CompareDate >

last_day(add_months(trunc(CONTPLCMT_START_DT),

14))

A reasonable efforts to finalize permanency date does not exist

within the 12 months prior to the CompareDate

select count(*)


where REAS_EFF_PERM_IND = 'Y'


and trunc(CD.REAS_EFF_PERM_DT, ‘month’) between

CompareDate and trunc(add_months(CompareDate,-

12), ‘month’)

= 0



Proofing Messages

Page 17 of 139

1.1.2.8 #1110 – Age over Maximum


Description Age over Maximum

Rule The client must be under age 21 (service dates starting 10/01/10) or

under age 19 (service dates before 10/01/10).


To



Short Message Age ([@ClientAge]) on the “Service End Date” must be under

[@OverMax].

Example Client: Age (21) on the “Service End Date” must be under 21.

Long Message IV-E Eligibility ends when the client turns [@OverMax].

Parameters

@ClientAge =

CalculatedAge for PYMT_SVC_START_DT

@OverMax =

If PYMT_SVC_START_DT >= ‘10/01/2010’

@OverMax = 21

If PYMT_SVC_START_DT < ‘10/01/2010’

@OverMax = 19

Error Condition

Display when either of the following set of conditions are true:

Service dates on or after 10/01/10:

PYMT_SVC_START_DT >= ‘10/01/2010’

Client is 21 or over on the “Service End Date”

CalculatedAge for PYMT_SVC_END_DT >= 21

Service dates before 10/01/10:

PYMT_SVC_START_DT < ‘10/01/2010’





Proofing Messages

Page 18 of 139

1.1.2.9 #1120 – No Continuous Placement

Checkbox Label Continuous Placement Message # 1120

Description No Continuous Placement

Rule A Continuous Placement must exist for the service dates.


To

Client | Permanency |

Continuous Placements node

container Navigation Hint Continuous Placement

Short Message A Continuous Placement does not exist for the service dates.

Example Continuous Placement: A Continuous Placement does not exist for the

service dates.

Long Message

A Continuous Placement does not exist anytime during the service

dates. A Continuous Placement must exist with a "Start Date" that is

on or before the "Service Start Date" and a "Discharge Date" that is

blank or is on or after the "Service End Date."

Parameters None

Error Condition

Display when the following condition is true:

A Continuous Placement does not exist for the service dates

Not ValidContPlcmt for PYMT_SVC_START_DT through

PYMT_SVC_END_DT

The service dates are not within the effective dates of a

Continuous Placement:


from CONTPLCMT C

where C.PERSON_ID = PERSON_ID

and (

PYMT_SVC_START_DT between

trunc(CONTPLCMT_START_DT) and

nvl(trunc(CONTPLCMT_END_DT), SYSDATE + 365)

or

trunc(CONTPLCMT_START_DT) between

PYMT_SVC_START_DT and PYMT_SVC_END_DT

))



Proofing Messages

Page 19 of 139

1.1.2.10 #1121 – Service Dates Partially Within a Continuous

Placement


Description Service Dates Partially Within a Continuous Placement

Rule The service dates must be completely within a Continuous Placement.

Exclude the Payment if the service dates are partially within a

Continuous Placement.


To




Short Message The service dates must be completely within a Continuous Placement.

Example Continuous Placement: The service dates must be completely within a


Long Message

The service dates are partially within a Continuous Placement. A

Continuous Placement must exist with a "Start Date" that is on or

before the "Service Start Date" and a "Discharge Date" that is blank or

is on or after the "Service End Date."

Parameters None

Error Condition




PYMT_SVC_END_DT

The service dates are partially within the effective dates of a

Continuous Placement:

(select COUNT(*)

from CONTPLCMT C


and (

(PYMT_SVC_START_DT between


nvl(trunc(CONTPLCMT_END_DT), SYSDATE +365)

or


PYMT_SVC_START_DT and PYMT_SVC_END_DT)

)

) = 1



Proofing Messages

Page 20 of 139

1.1.2.11 #1122 – Multiple Continuous Placements


Description Multiple Continuous Placements

Rule Exclude the Payment if another Continuous Placement exists anytime

during the service dates.


To




Short Message More than one Continuous Placement exists during the service dates.

Example Continuous Placement: More than one Continuous Placement exists


Long Message

A single Continuous Placement must exist with a "Start Date" that is on

or before the "Service Start Date" and a "Discharge Date" that is blank

or is on or after the "Service End Date."

Parameters None

Error Condition




PYMT_SVC_END_DT

More than one Continuous Placement exists sometime during

the service dates:

(select count(*)

from CONTPLCMT C


and (



nvl(trunc(CONTPLCMT_END_DT), SYSDATE + 365)

)

or


PYMT_SVC_START_DT and PYMT_SVC_END_DT

)

) > 1



Proofing Messages

Page 21 of 139

1.1.2.12 #1123 – No Title IV-E Maintenance Agreement for

Supervising Tribe


Description No Title IV-E Maintenance Agreement for Supervising Tribe

Rule Exclude the Payment if all of the following are true:

The Supervising Agency = “Tribal social services”

The local agency is not a tribe

A Title IV-E Maintenance Agreement does not exist for the

service dates with the Supervising "Tribe"

The service dates are on or after the Supervising Agency

"Effective Date" (Added, v13.2, PR #13-0124-1900-24)


To

Client | Permanency | Continuous

Placements | effective Continuous

Placement record Navigation Hint Continuous

Placement

Short Message A Title IV-E Maintenance Agreement does not exist for the Supervising

Tribe ([@Tribe]).

Example Continuous Placement: A Title IV-E Maintenance Agreement does not

exist for the Supervising Tribe (Leech Lake Band of Ojibwe).

Long Message

The “Supervising Agency” on the Continuous Placement is “Tribal social

services.” A Title IV-E Maintenance Agreement with the supervising

“Tribe” must be in effect for the service dates. Title IV-E Maintenance

Agreements are entered in the SSIS Administration application under

Tools | County Preferences | Title IV-E.

Parameters @Tribe = CODE.DESCRIPTION for CONTPLCMT.SUP_TRIBE_CD



Proofing Messages

Page 22 of 139

Error Condition


A Continuous Placement exists for the service dates


PYMT_SVC_END_DT


SYSTEM_CONTROL.CNTY_CD not in (‘A4’,’B2’)


CONTPLCMT.SUP_AGCY_CD=‘3’


"Effective Date"

PYMT_SVC_END_DT >= CONTPLCMT.SUP_AGCY_EFF_DT

A Title IV-E Maintenance Agreement does not exist with the

“Supervising” Tribe on the Continuous Placement for service

dates on or after the Supervising Agency "Effective Date"


from IVE_MNT_AGR MA

where MA.MNT_AGR_WITH_CD = ‘2’

and MA.SUP_TRIBE_CD = CONTPLCMT.SUP_TRIBE_CD

and greatest(PYMT_SVC_START_DT,

CONTPLCMT.SUP_AGCY_EFF_DT) >=

MA.MNT_AGR_EFF_DT

and PYMT_SVC_END_DT <= NVL(MNT_AGR_END_DT,

PYMT_SVC_END_DT) )



Proofing Messages

Page 23 of 139

1.1.2.13 #1124 – No Corrections Umbrella or Title IV-E Maintenance

Agreement


Description No Corrections Umbrella or Title IV-E Maintenance Agreement

Rule Exclude the Payment if the Supervising Agency = “Corrections” and

neither of the following exist for the service dates:

A Title IV-E Maintenance Agreement with Corrections

A Title IV-E Corrections Umbrella record


"Effective Date" (Added, v13.2, PR #13-0124-1900-24)


To




Placement

Short Message A Corrections Umbrella or Title IV-E Maintenance Agreement for

Corrections does not exist.

Example Continuous Placement: A Corrections Umbrella or Title IV-E

Maintenance Agreement for Corrections does not exist.

Long Message

The “Supervising Agency” on the Continuous Placement is

“Corrections.” A Title IV-E Maintenance Agreement or Corrections

Umbrella must be in effect for the service dates. Title IV-E

Maintenance Agreements and Corrections Umbrellas are entered in the

SSIS Administration application under Tools | County Preferences |

Title IV-E.

Parameters None



Proofing Messages

Page 24 of 139

Error Condition




PYMT_SVC_END_DT


SYSTEM_CONTROL.CNTY_CD not in (‘A4’,’B2’)

The Supervising Agency = “Corrections”

CONTPLCMT.SUP_AGCY_CD=‘2’


"Effective Date"

PYMT_SVC_END_DT >= CONTPLCMT. SUP_AGCY_EFF_DT

A Title IV-E Maintenance Agreement does not exist with

Corrections for the service dates


from IVE_MNT_AGR

where MNT_AGR_WITH_CD = ‘1’

and greatest(PYMT_SVC_START_DT,


MNT_AGR_EFF_DT

and PYMT_SVC_END_DT <= nvl(MNT_AGR_END_DT,

PYMT_SVC_END_DT) )

A Title IV-E Corrections Umbrella record does not exist for

service dates on or after the Supervising Agency "Effective

Date"


from IVE_UMB_CNTY

where greatest(PYMT_SVC_START_DT,


CORR_UMB_CNTY_EFF_DT

and PYMT_SVC_END_DT <=

nvl(CORR_UMB_CNTY_END_DT,

PYMT_SVC_END_DT) )



Proofing Messages

Page 25 of 139

1.1.2.14 #1125 – Supervising Agency must be the Tribe


Description Supervising Agency must be the Tribe

Rule If the local agency is a tribe, the Supervising Agency on the Continuous

Placement must be “Tribal social services” and the “Tribe” must be the

local agency.


To




Placement

Short Message The supervising “Tribe” ([@Tribe]) must be the local agency.

Example

If another Tribe is selected:

Continuous Placement: The supervising “Tribe” (Mille Lacs Band of

Chippewa Indians) must be the local agency.

If “County Social Services” or “Corrections” is selected:

Continuous Placement: The supervising “Tribe” (No tribe selected)

must the local agency.

Long Message The “Supervising Agency” on the Continuous Placement must be “Tribal

social services” and the supervising “Tribe” must be the local agency.

Parameters

If CONTPLCMT.SUP_TRIBE_CD is valued

@Tribe = CODE.DESCRIPTION for CONTPLCMT.SUP_TRIBE_CD

Otherwise

@Tribe = “No tribe selected”

Error Condition




PYMT_SVC_END_DT

If the local agency is “Leech Lake Band of Ojibwe”

SYSTEM_CONTROL.CNTY_CD = ‘A4’

The “Supervising Agency” <> “Tribal social services”

CONTPLCMT.SUP_AGCY_CD <> ‘3’

or the “Tribe” <> “Leech Lake Band of Ojibwe”

CONTPLCMT.SUP_TRIBE_CD <> ‘TMD’

If the local agency is “White Earth Band of Ojibwe”

SYSTEM_CONTROL.CNTY_CD =’B2’

The “Supervising Agency” <> “Tribal social services”

CONTPLCMT.SUP_AGCY_CD <> ‘3’

or the “Tribe” <> “White Earth Band of Ojibwe”

CONTPLCMT.SUP_TRIBE_CD = ‘TMG’



Proofing Messages

Page 26 of 139

1.1.2.15 #1130 – No DOC Assessment

Checkbox Label DOC Message # 1130

Description No DOC Assessment

Rule Exclude the Payment if “DOC points” has a value > 0 and a DOC

Assessment does not exist for the service dates.


To

Client | DOC Assessment node

container Navigation Hint DOC

Short Message A DOC Assessment does not exist for the service dates.

Example DOC: A DOC Assessment does not exist for the service dates.

Long Message

A DOC Assessment must exist with an “Effective Date” that is on or

before the “Service Start Date” when “DOC Points” on the Payment is

greater than 0.

Parameters None

Error Condition


“DOC Points” on the Payment is > 0

PAYMENT.PYMT_DOC_PTS > 0

A DOC Assessment does not exist with an effective on or before

the service dates


from DOC_ASSESS DA

where DA.PERSON_ID = PERSON_ID

and DA.DOC_EFF_DT <= PYMT_SVC_START_DT)



Proofing Messages

Page 27 of 139

1.1.2.16 #1131 – Higher DOC Points Paid


Description Higher DOC Points Paid

Rule Exclude the Payment if the “DOC points” on the Payment is more than

the DOC Assessment.


To

Client | DOC Assessment | effective

DOC Assessment Navigation Hint DOC

Short Message The total “DOC Points” paid ([@PayDOC]) is over the assessed “DOC

Points” ([@AssessedDOC]) for the service dates.

Example DOC: The total “DOC Points” paid (120) is over the assessed “DOC

Points” (102) for the service dates.

Long Message

A DOC Assessment must exist with an “Effective Date” that is on or

before the “Service Start Date” and “DOC Points” greater than or equal

to the “DOC Points” on the Payment. "DOC Points" over the assessed

"DOC Points" are not IV-E reimbursable. You may need to split the

Payment to claim only the assessed "DOC Points."

Parameters @PayDOC = DOCPointsPaid (defined below in Error Condition)

@AssessedDOC = DOC_ASSESS.DOC_POINTS

Error Condition


IV-E Service Type is Maintenance, Difficulty of Care (DOC), or

Adjustment of DOC

ValidIV-EServiceType

and IVE_SVC_TYPE_CD in (‘A’, ‘F’, ‘G’)

“DOC Points” on the Payment is > 0




Proofing Messages

Page 28 of 139

Error Condition

(continued)

If the IV-E Service Type is ‘G’ (Adjustment of DOC), calculate

the Total DOC Points by adding DOC Points on existing claims

with the DOC Points on the Payment

If IV-E Service Type = ‘G’

DOCPointsPaid = PAYMENT.PYMT_DOC_PTS +

sum (select CLM_DOC_PTS

from IVE_ABSTRACT_CLM C

where PERSON_ID = C.PERSON_ID

and (PYMT_SVC_START_DT between

C.CLM_SVC_START_DT and

C.CLM_SVC_END_DT

or PYMT_SVC_END_DT between

C.CLM_SVC_START_DT and

C.CLM_SVC_END_DT)

and C.SVC_BUS_ORG_ID =

PAYMENT.SVC_BUS_ORG_ID

and C.IVE_SVC_TYPE_CD in (‘A’, ’F’, ‘G’)

and CLM_AMT > 0

and NotBackedOut)

otherwise

DOCPointsPaid = PAYMENT.PYMT_DOC_PTS

One or more DOC Assessments exist for the service dates and

the Payment “DOC Points” is more than the DOC Assessment

select DOC_ASSESS_ID, nvl(DA.DOC_POINTS,225)

from DOC_ASSESS DA


and DA.DOC_EFF_DT <= PYMT_SVC_START_DT

and DA.DOC_EFF_DT = (select max(DA2.DOC_EFF_DT)

from DOC_ASSESS DA2

where DA2.PERSON_ID = PERSON_ID

and DA2.DOC_EFF_DT <= PYMT_SVC_START_DT)

and DA.DOC_ASSESS_DT =

(select max(DA3.DOC_ASSESS_DT)

from DOC_ASSESS DA3


and DA3.DOC_EFF_DT = DA.DOC_EFF_DT)

and DOCPointsPaid > DA.DOC_POINTS

and rownum = 1

Note: If multiple DOC Assessment records have the same Assessment

Date and Effective Date, this message is displayed if the Payment

“DOC Points” is more than any of the DOC Assessments



Proofing Messages

Page 29 of 139

1.1.2.17 #1132 – Lower DOC Points Paid

Checkbox Label Claim Warnings Message # 1132

Description Lower DOC Points Paid

Rule Display a warning if “DOC points” on the Payment is less than the DOC

Assessment.

Severity Warning Navigates

To

Client | DOC Assessment | effective

DOC Assessment Navigation Hint DOC

Short Message The Payment “DOC Points” ([@PayDOC]) is less than the assessed

“DOC Points” ([@AssessedDOC]) for the service dates.

Example Warning - DOC: The Payment “DOC Points” (92) is less than the

assessed “DOC Points” (102) for the service dates.

Long Message

Verify the DOC Assessment with the most recent “Effective Date” prior

to the service dates is correct. If needed, create a Payment for the

difference in the number of "DOC Points" paid and the number

assessed and select “Difficulty of Care Adjustment” on the “Special

Cost Code” field.

Parameters @PayDOC = PAYMENT.PYMT_DOC_PTS

@AssessedDOC = DOC_ASSESS.DOC_POINTS



Proofing Messages

Page 30 of 139

Error Condition

Exclude the following standard criteria from this edit

A IV-E Claim does not exist for the Payment


The Payment has been claimed on the current Title IV-E

Abstract Report

exists (select *


where C.PAYMENT_ID = PAYMENT_ID

and C.STATE_RPT_ID = STATE_RPT_ID)

“DOC Points” on the Payment has a value

PAYMENT.PYMT_DOC_PTS is not null

One or more DOC Assessments exist for the service dates and

the Payment “DOC Points” is less than the DOC Assessment

select DOC_ASSESS_ID, nvl(DA.DOC_POINTS,225)

from DOC_ASSESS DA



and DA.DOC_EFF_DT =

(select max(DA2.DOC_EFF_DT)

from DOC_ASSESS DA2





from DOC_ASSESS DA3



and PAYMENT.DOC_POINTS < DA.DOC_POINTS

and rownum = 1

Note: If the payment was claimed and a DOC Assessment record is

added with the same Assessment Date and Effective Date, this

message is displayed if the Payment “DOC Points” is less than any of

the DOC Assessments



Proofing Messages

Page 31 of 139

1.1.2.18 #1133 – No DOC Assessment – Zero Points Paid


Description No DOC Assessment – Zero Points Paid

Rule A DOC Assessment must be completed within 30 days of placement.

Display a warning if “DOC points” on the payment is zero and a DOC

Assessment does not exist for the service dates.


To



Short Message “DOC Points” is zero and a DOC Assessment does not exist for the

service dates.

Example Warning - DOC: “DOC Points” is zero and a DOC Assessment does not

exist for the service dates.

Long Message A DOC Assessment should be completed within 30 days of a child’s

placement in foster care.

Parameters None

Error Condition





Abstract Report

exists (select *




“DOC Points” on the Payment = 0

PAYMENT.PYMT_DOC_PTS = 0

or the Service is “188 - Supervised independent living (18-20)”

and the IV-E Service Type = ‘A’

ServiceCode = ‘188’

and ValidIV-EServiceType and IVE_SVC_TYPE_CD = ‘A’)

A DOC Assessments does not exist with an effective on or

before the Payment "Service Start Date"


from DOC_ASSESS DA


and DA.DOC_EFF_DT <= PYMT_SVC_START_DT)



Proofing Messages

Page 32 of 139

1.1.2.19 #1134 – Duplicate DOC Assessments


Description Duplicate DOC Assessments

Rule Exclude the Payment if multiple DOC Assessment records have the

same Assessment Date and Effective Date.


To



Short Message Multiple DOC Assessments have the same “Assessment Date”

([@AssessDate]) and “Effective Date” ([@EffDate]).

Example DOC: Multiple DOC Assessments have the same “Assessment Date”

(03/01/2010) and “Effective Date” (02/20/2010).

Long Message

Only one DOC Assessment record should exist for the “Assessment

Date” / “Effective Date.” You may need to delete one of the records or

correct one or both of the records.

Parameters @AssessDate = DOC_ASSESS.DOC_ASSESS_DT

@EffDate = DOC_ASSESS.DOC_EFF_DT

Error Condition


“DOC Points” on the Payment > 0


or the Service is “188 - Supervised independent living (18-20)”

and the IV-E Service Type = ‘A’


and ValidIV-EServiceType and IVE_SVC_TYPE_CD = ‘A’)

Two or more DOC Assessments exist for the service dates with

the same Assessment Date and Effective Date

select DOC_EFF_DT, DOC_ASSESS_DT

from DOC_ASSESS DA



and DA.DOC_EFF_DT =


from DOC_ASSESS DA2





from DOC_ASSESS DA3



) returns more than one row



Proofing Messages

Page 33 of 139

1.1.2.20 #1140 – Not Eligible for Extended Foster Care

Checkbox Label Extended Foster Care Message # 1140

Description Not eligible for extended foster care

Rule Exclude Payments with Extended Eligibility = “No” because a “Not

eligible” foster care extension condition exists for the service dates.

Severity Error

Navigates

To



Placement record | Foster Care Extension

tab | Extension Conditions tab | effective

Extension Condition record

Navigation Hint Continuous

Placement

Short Message “Not eligible-no foster care extension condition applies” for the service

dates.

Example Continuous Placement: “Not eligible-no foster care extension condition

applies” for the service dates.

Long Message

The foster care extension condition indicates the child is not eligible for

IV-E. A valid foster care extension condition must exist for children

ages 18, 19 and 20.

Parameters None

Error Condition




PYMT_SVC_END_DT

Service dates are on or after 10/01/10

PYMT_SVC_START_DT >= 10/01/2010

The client is 18 or over on the Payment “Service End Date”


The Continuous Placement has a foster care extension condition

of “Not eligible-no foster care extension condition applies”

FC_EXTENSION.CONTPLCMT_ID = CONTPLCMT_ID

and FC_EXTENSION_CD = ‘01’

The Payment “Service End Date” is on or after the effective date

of the Extension Condition

PYMT_SVC_END_DT >= FC_EXT_EFF_DT



Proofing Messages

Page 34 of 139

1.1.2.21 #1141 – No Foster Care Extension Condition


Description No foster care extension condition

Rule Exclude Payments with Extended Eligibility = “No” because a foster

care extension condition does not exist for the service dates.

Severity Error

Navigates

To



Placement record | Foster Care

Extension tab Navigation Hint

Continuous

Placement

Short Message The client is [@ClientAge] and no Foster Care Extension Conditions

exist.

Example Continuous Placement: The client is 18 and no Foster Care Extension

Conditions exist.

Long Message A valid Foster Care Extension Condition must be in effect on or before

the client’s 18th birthday.

Parameters @ClientAge =

CalculatedAge for PYMT_SVC_END_DT

Error Condition




PYMT_SVC_END_DT



Client is 18 or over on the “Payment Service End Date”


A foster care extension condition does not exist for the

Continuous Placement, excluding a “Not Eligible” condition.


from FC_EXTENSION FC

where FC.CONTPLCMT_ID = CONTPLCMT_ID

and (FC_EXTENSION_CD <> ‘01’

or (FC_EXTENSION_CD = ‘01’ and

PYMT_SVC_END_DT >=FC_EXT_EFF_DT)))



Proofing Messages

Page 35 of 139

1.1.2.22 #1143 – Extension Condition Needed Through the Service

End Date


Description Extension Condition Needed Through the Service End Date

Rule Exclude Payments with Extended Eligibility = “No” because the service

dates are partially within a foster care extension condition.

Severity Error

Navigates

To



Placement record | Foster Care Extension

tab Navigation Hint

Continuous

Placement

Short Message A Foster Care Extension Condition must be in effect from the client’s

18th birthday through the “Service End Date.”

Example Continuous Placement: A Foster Care Extension Condition must be in

effect from the client’s 18th birthday through the “Service End Date.”

Long Message

More than one Foster Care Extension Condition can exist as long as

there is not a gap in the effective dates of the conditions. If the child

re-entered care after his or her 18th birthday, a Foster Care Extension

Condition must be in effect from the Continuous Placement “Start Date”

through the “Service End Date.”

Parameters None



Proofing Messages

Page 36 of 139

Error Condition




PYMT_SVC_END_DT





One or more valid Foster Care Extension Conditions for the

FCExtensionReqdDate through the Service End Date do not

exist

not (ValidFCExtension for FCExtensionReqdDate through

PYMT_SVC_END_DT)

The FCExtensionReqdDate through the Service End Date are

partially within the effective dates of a foster care extension

condition (except a “Not eligible” condition):

exists (select *



and FC_EXTENSION_CD <> ‘01’

and (FCExtensionReqdDate between FC_EXT_EFF_DT and

nvl(FC_EXT_END_DT, PYMT_SVC_END_DT)

or FC_EXT_EFF_DT between FCExtensionReqdDate and

PYMT_SVC_END_DT))

A “Not Eligible” foster care extension condition does not exist for

the service dates.




and FC_EXTENSION_CD = ‘01’

and FC_EXT_EFF_DT <= PYMT_SVC_END_DT)



Proofing Messages

Page 37 of 139

1.1.2.23 #1144 – EFC-SIL – Invalid Service


Description EFC-SIL – Invalid Service

Rule If the client is in a IV-E Placement - EFC-SIL, the Service must be

“188 - Supervised independent living (18-20).”


To selected Payment

Navigation Hint Payment

Short Message

The “Service” ([@SvcCode] - [@SvcDescription]) must be “188 -

[@188SvcDescription]” when the Placement “Setting” is

“[@SettingDescr].”

Example

Payment: The “Service” (181 - Child family foster care) must be “188 -

Supervised independent living (18-20)” when the Placement “Setting”

is “Supervised independent living.”

Long Message Payments for youth in a “Supervised independent living” setting can

only be claimed to IV-E when the “Service” is 188.

Parameters

@SvcCode = ServiceCode

@SvcDescription = ServiceDescription

@188SvcDescription = Current Service Description for Service 188

@SettingDescr = CODE.DESCRIPTION for LOC_SETTING_CD

Error Condition


The Service is not “188 - Supervised independent living (18-

20)”

ServiceCode <> ‘188’

The client is in an IV-E Placement - EFC-SIL

(select *

from PLCMT_LOC L, PLCMT_LOC_HIST H

where L.PLCMT_LOC_ID = H.PLCMT_LOC_ID

and L.PERSON_ID = PAYMENT.PERSON_ID

and LOC_REASON_CD not in (‘04’,’12’,’14’)

and LOC_SETTING_CD = ‘07’

and PYMT_SVC_START_DT >= trunc(LOC_START_DT)

and PYMT_SVC_END_DT <= trunc(nvl(LOC_END_DT,

sysdate + 365))

and PYMT_SVC_START_DT >= trunc(H.LOC_EFF_DT)

and rownum = 1

) returns a row



Proofing Messages

Page 38 of 139

1.1.2.24 #1145 – EFC-SIL – Invalid Placement Setting


Description EFC-SIL – Invalid Placement Setting

Rule If the Service is “188 - Supervised independent living (18-20),” the

client must be in a IV-E Placement - EFC-SIL.


To


Placements/Locations/Absences

| effective Placement record Navigation Hint Placement

Short Message The “Setting” ([@SettingDescr]) must be “Supervised independent

living” when the “Service” is “188 - [@188SvcDescription].”

Example

Placement: The “Setting” (Foster family home - relative) must be

“Supervised independent living” when the “Service” is “188 -

Supervised independent living (18-20).”

Long Message Payments for “Service” 188 can only be claimed to IV-E when the youth

is in a “Supervised independent living” setting.

Parameters @SettingDescr = CODE.DESCRIPTION for LOC_SETTING_CD

@188SvcDescription = Current Service Description for Service 188

Error Condition


A IV-E Placement exists for the service dates

ValidIV-E PlacementandHistory for

PYMT_SVC_START_DT through PYMT_SVC_END_DT

The Service is “188 - Supervised independent living (18-20)”


The client is not in an EFC-SIL Placement Setting

LOC_SETTING_CD <> ’07’



Proofing Messages

Page 39 of 139

1.1.2.25 #1146 – EFC-SIL – Client Under 18


Description EFC-SIL – Client Under 18

Rule If Rule Code = “SIL,” the client must be between 18 and 20 on the

service dates.


To



Short Message Age ([@ClientAge]) must be 18 or over when the “Service” is “188 -

[@SvcDescription].”

Example Client: Age (17) must be 18 or over when the “Service” is “188 -

Supervised independent living (18-20).”

Long Message “Service” 188 is only valid for clients who are 18, 19, or 20 living in a

“Supervised independent living” setting.

Parameters @ClientAge = CalculatedAge for PYMT_SVC_START_DT


Error Condition




Client is under 18 on the “Service Start Date”

CalculatedAge for PYMT_SVC_START_DT < 18



Proofing Messages

Page 40 of 139

1.1.2.26 1147 – Extension Review is Overdue


Description Extension Review is Overdue

Rule An Extension Review must be completed every 6 months

(Added in v13.2, PR #13-0111-1551-58)


To

Client | Permanency | Continuous Placements

| effective Continuous Placement record |

Foster Care Extension tab Navigation Hint Continuous

Placement

Short Message A Foster Care Extension Review is overdue.

Example Warning - Continuous Placement: A Foster Care Extension Review is

overdue.

Long Message A Foster Care Extension Review must be completed every 6 months.

Parameters None



Proofing Messages

Page 41 of 139

Error Condition


If PYMT_SVC_START_DT <= Report Period End Date

CompareDate = PYMT_SVC_START_DT






The Payment has been claimed on the current Title IV-E Abstract

Report

exists (select * from IVE_ABSTRACT_CLAIM C





PYMT_SVC_END_DT





The CompareDate is more than 6 months after the client's 18th

birthday or the Continuous Placement “Start Date” if the client

re-entered foster care after their 18th birthday

CompareDate > add_months(FCExtensionReqdDate, 6)

An Extension Review does not exist within the 6 months prior to

the CompareDate

(select count(*)

from FC_EXT_REVIEW FCE

where FCE.CONTPLCMT_ID = CONTPLCMT_ID

and FCE.FC_EXT_REVIEW_DT between

add_months(CompareDate,-6) and CompareDate)= 0



Proofing Messages

Page 42 of 139

1.1.2.27 #1148 – Educational Transportation for Ages 19-20


Description Educational Transportation for Ages 19-20

Rule Educational Transportation is only reimbursable through high school.

(Added in v13.2, PR #12-0625-1400-59)


To selected Payment


Short Message Educational Transportation for Age ([@ClientAge]) must be for high

school.

Example Warning - Payment: Educational Transportation for Age (19) must be

for high school.

Long Message

IV-E reimbursement for Educational Transportation is only available

through high school. Post-secondary Educational Transportation is not

IV-E reimbursable.

Parameters @ClientAge = CalculatedAge for PYMT_SVC_END_DT

Error Condition





Abstract Report






PYMT_SVC_END_DT

The IV-E Service Type is “Educational Transportation”

ValidIV-EServiceType and IVE_SVC_TYPE_CD = 'T'





Proofing Messages

Page 43 of 139

1.1.2.28 #1150 – No MAXIS IV-E Eligibility Information

Checkbox Label IV-E Eligibility Message # 1150

Description No MAXIS IV-E Eligibility information

Rule Exclude the Payment if a MAXIS IV-E eligibility record does not exist for

the service dates


To

Client | Client Eligibility Log |

IV-E Eligibility node container Navigation Hint Client Eligibility

Short Message No IV-E Eligibility information from MAXIS.

Example Client Eligibility: No IV-E Eligibility information from MAXIS.

Long Message

The client must be IV‑E eligible based on the MAXIS IV‑E eligibility

information to claim IV-E. No IV-E Eligibility information from MAXIS

exists for this child.

Parameters None

Error Condition


A MAXIS IV-E Eligibility record does not exist for the person


from DI_CHILD_ELIG E

where E.PERSON_ID = PERSON_ID

and E.ELIG_BEGIN_DT is not null

and BENEFIT_YR_MONTH is not null

and DATA_TYPE = ‘ELIG')



Proofing Messages

Page 44 of 139

1.1.2.29 #1151 – Not IV-E Eligible – Denied


Description Not IV-E Eligible - Denied

Rule Exclude the Payment if the MAXIS IV-E eligibility is Denied

(v13.2, changed to use the test results field (PR #13-0107-1711-04))


To

Client | Client Eligibility Log | IV-E

Eligibility | effective IV-E Eligibility record Navigation Hint Client Eligibility

Short Message IV-E Eligibility for the Continuous Placement has been denied.

Example Client Eligibility: IV-E Eligibility for the Continuous Placement has been

denied.

Long Message The client must be IV-E eligible based on the MAXIS IV-E Eligibility

information to claim IV-E.

Parameters None

Error Condition




PYMT_SVC_END_DT

A MAXIS IV-E Eligibility record exists for the “Cont Placement #”

(select *



and E.CONTPLCMT_ID = CONTPLCMT_ID


and DATA_TYPE = ‘ELIG'

order by BENEFIT_YR_MONTH desc, TIMESTAMP_DT desc,

DI_CHILD_ELIG_ID desc)

Use the results from the first row returned

The MAXIS IV-E Eligibility for the Continuous Placement is

“Denied”

E.IVE_ELIGIBLE_CD = '5'



Proofing Messages

Page 45 of 139

1.1.2.30 #1152 – Not IV-E Eligible – Closed


Description Not IV-E Eligible – Closed

Rule Exclude the Payment if the MAXIS IV-E eligibility is Closed prior to the

service dates

(v13.2, changed to use the test results field (PR #13-0107-1711-04))


To



Short Message IV-E Eligibility closed ([@EligEndDt]) prior to the “Service End Date.”

Example Client Eligibility: IV-E Eligibility closed (04/01/2010) prior to the

“Service End Date.”

Long Message

The client must be IV-E eligible on the service dates based on the

MAXIS IV-E Eligibility information. If IV-E Eligibility closed during the

service dates, you can split the Payment to claim through the IV-E

Eligibility end date.

Parameters @EligEndDt = E.ELIG_END_DT

Error Condition




PYMT_SVC_END_DT


(select *




and PYMT_SVC_START_DT >= E.ELIG_BEGIN_DT







“Closed”:


The Payment “Service End Date” is after the “Elig End” date

PYMT_SVC_END_DT > E.ELIG_END_DT



Proofing Messages

Page 46 of 139

1.1.2.31 #1153 – No IV-E Eligibility for the Cont Placement #


Description No IV-E Eligibility for the Cont Placement #

Rule Exclude the Payment if the “Cont Placement #” on the MAXIS IV-E

Eligibility record and the Continuous Placement in SSIS do not match


To



Short Message No IV-E Eligibility information for the Continuous Placement, “Cont

Placement #” ([@ContPlcmtID]), “Start Date” ([@ContPlcmtStart]).

Example

Client Eligibility: No IV-E Eligibility information for the Continuous

Placement, “Cont Placement #” (123456789), “Start Date”

(06/11/2011).

Long Message

IV-E Eligibility information from MAXIS exists for this child, either for

another Continuous Placement or the “Cont Placement #” on the MAXIS

record does not match the Continuous Placement in SSIS.

Parameters @ContPlcmtID = CONTPLCMT_ID

@ContPlcmtStart = trunc(CONTPLCMT_START_DT)

Error Condition




PYMT_SVC_END_DT

A MAXIS IV-E Eligibility record exists for the person

exists (select *



and ELIG_BEGIN_DT is not null



The “Cont Placement #” on the MAXIS IV-E Eligibility record

does not match the Continuous Placement in SSIS





and ELIG_BEGIN_DT is not null





Proofing Messages

Page 47 of 139

1.1.2.32 #1154 – Not IV-E Eligible – Inconclusive


Description Not IV-E Eligible – Inconclusive

Rule Exclude the Payment if the MAXIS IV-E eligibility is Inconclusive

Note: Eligibility Test Results are inconclusive when the End Date is

valued and none of the tests failed or a test failed and there is no End

Date.

(Added in v13.2, PR#13-0107-1725-38)


To



Short Message IV-E Eligibility for the Continuous Placement is inconclusive.

Example Client Eligibility: IV-E Eligibility for the Continuous Placement is

inconclusive.

Long Message IV-E eligibility results could not be determined based on the MAXIS IV-E

Eligibility information. The client must be IV-E eligible to claim IV-E.

Parameters None

Error Condition




PYMT_SVC_END_DT


(select *










“Inconclusive”




Proofing Messages

Page 48 of 139

1.1.2.33 #1155 - VPA Date Mismatch


Description VPA Date Mismatch

Rule Exclude the Payment if the “Effective Date” of the Voluntary Placement

Authority and the MAXIS “Voluntary Plcmt. Agmt.” date do not match


To



Short Message

The “Voluntary plcmt agmt” from MAXIS ([@MAXISVPADt]) does not

match the “Effective Date” of the Voluntary Authority

([@SSISVolEffDt]).

Example

Client Eligibility: The “Voluntary plcmt agmt” from MAXIS (06/04/2011)

does not match the “Effective Date” of the Voluntary Authority

(04/06/2011).

Long Message

The IV-E Eligibility information from MAXIS indicates the child is eligible.

The “Voluntary plcmt agmt” from MAXIS must match the “Effective

Date” of the Voluntary Authority.

Parameters @MAXISVPADt = E.VOL_PLCMT_AGRMT_DT

@SSISVolEffDt = trunc(PLACE_AUTH_EFF_DT)

Error Condition




PYMT_SVC_END_DT

The client is IV-E Eligible

IV-EEligibleClient for PYMT_SVC_START_DT through

PYMT_SVC_END_DT



The MAXIS “Voluntary plcmt agmt” date does not match the

“Effective Date” of the Voluntary Placement Authority

E.VOL_PLCMT_AGRMT_DT is null

or E.VOL_PLCMT_AGRMT_DT <>

trunc(PLACE_AUTH_EFF_DT)



Proofing Messages

Page 49 of 139

1.1.2.34 #1156 - Best Interest Date Mismatch


Description Best Interest Date Mismatch

Rule Exclude the Payment if the Best Interest Date and the MAXIS “Best

Interest Stmt.” date do not match


To



Short Message The “Best interest stmt” from MAXIS ([@MAXISBestIntDt]) does not

match SSIS ([@SSISBestIntDt]).

Example Client Eligibility: The “Best interest stmt” from MAXIS (06/20/2011)

does not match SSIS (06/22/2011).

Long Message

The IV-E Eligibility information from MAXIS indicates the child is eligible.

The “Best interest stmt” from MAXIS must match the earliest Best

Interest Date for the Continuous Placement.

Parameters @MAXISBestIntDt = E.BEST_INTEREST_DT

@SSISBestIntDt = CD.BEST_INTEREST_DT

Error Condition




PYMT_SVC_END_DT



PYMT_SVC_END_DT

A Best Interest Date exists for the Continuous Placement

select min(BEST_INTEREST_DT)





One of the following is true:

The MAXIS “Best interest stmt” date does not match the

“Initial Best Interest Date” in SSIS

E.BEST_INTEREST_DT is not null

and E.BEST_INTEREST_DT <> CD.BEST_INTEREST_DT



and E.BEST_INTEREST_DT is null



Proofing Messages

Page 50 of 139

1.1.2.35 #1157 – Service Dates before IV-E Eligibility Begins


Description Service Dates before IV-E Eligibility Begins

Rule Exclude the Payment if the "Service Start Date" is before IV-E eligibility

starts.

(Added in v13.2, PR#13-0107-1715-16)


To



Short Message The "Service Start Date" is before IV-E Eligibility begins

([@EligBeginDt]).

Example Client Eligibility: The "Service Start Date" is before IV-E Eligibility

begins (06/23/2012).

Long Message The client must be IV-E eligible on the service dates based on the

MAXIS IV-E Eligibility information to claim IV-E.

Parameters @EligBeginDt = E.ELIG_BEGIN_DT

Error Condition




PYMT_SVC_END_DT


select *




and E.ELIG_BEGIN_DT is not null



and rownum = 1

order by BENEFIT_YR_MONTH desc,

TIMESTAMP_DT desc, DI_CHILD_ELIG_ID desc

Client's IV-E Eligibility Test Result is "Eligible" or "Eligible

(closed)"

E.IVE_ELIGIBLE_CD in ('1','4')

The Payment "Service Start Date" is before the "Elig. Begin" date

PYMT_SVC_START_DT < E.ELIG_BEGIN_DT



Proofing Messages

Page 51 of 139

1.1.2.36 #1160 – Not IV-E Reimbursable

Checkbox Label IV-E Reimbursability Message # 1160

Description Not IV-E Reimbursable

Rule Exclude the Payment if IV-E Reimbursability for the service dates

indicates the client is not reimbursable.

(v13.2, changed to test results field, PR #13-0107-1711-04)


To


IV-E Reimbursability | effective

IV-E Reimbursability record Navigation Hint Client Eligibility

Short Message Not IV-E reimbursable on the service dates.

Example Client Eligibility: Not IV-E reimbursable on the service dates.

Long Message

IV-E Reimbursability results from MAXIS indicate the child is not IV-E

reimbursable because the “Duplicate assistance,” “Reasonable efforts to

finalize permanency plan,” or “Maintenance Agreement” test failed.

Parameters None

Error Condition




PYMT_SVC_END_DT



PYMT_SVC_END_DT

A MAXIS IV-E Reimbursability record exists for the “Cont

Placement #” and service dates

select IVE_REIMB_CD

from DI_CHLD_MNTH_RMB R

where R.PERSON_ID = PERSON_ID

and R.CONTPLCMT_ID = CONTPLCMT_ID

and to_date(R.REIMB_YR_MONTH, ’yyyymm’) =

trunc(PYMT_SVC_START_DT, 'month')

order by TIMESTAMP_DT desc


The IV-E Reimbursability Test Result indicates the client is "Non

reimbursable"

IVE_REIMB_CD = '1'

For SIL payments that cross months, display this message if a

MAXIS IV-E Reimbursability record exists with a test that fails in

any of the service months



Proofing Messages

Page 52 of 139

1.1.2.37 #1161 – No IV-E Reimbursability for One Year

Checkbox Label IV-E Reimbursability Message # 1161

Description No IV-E Reimbursability for One Year

Rule Exclude the Payment if MAXIS IV-E Reimbursability information has not

been received within the 12 months prior to the service dates


To


IV-E Reimbursability node

container Navigation Hint Client Eligibility

Short Message No IV-E Reimbursability from MAXIS in the year prior to the service

dates.

Example Client Eligibility: No IV-E Reimbursability from MAXIS in the year prior

to the service dates.

Long Message

IV-E cannot be claimed until reimbursability results are received from

MAXIS. Reimbursability results must be certified in MAXIS before they

are sent to SSIS.

Parameters None

Error Condition


If PYMT_SVC_END_DT <= Report Period End Date

CompareDate = PYMT_SVC_END_DT






PYMT_SVC_END_DT



PYMT_SVC_END_DT

Service dates are more than one year after the Continuous

Placement Start Date

CompareDate >


12))

A MAXIS IV-E Reimbursability does not exist within 12 months

of the service dates:

select count(*)




and to_date(R.REIMB_YR_MONTH,’yyyymm’) >=

add_months(trunc(CompareDate,‘month’),-12)) = 0



Proofing Messages

Page 53 of 139

1.1.2.38 #1162 – No IV-E Reimbursability for Nine Months


Description No IV-E Reimbursability for Nine Months

Rule Display a warning if if MAXIS IV-E Reimbursability information has not

been received within the 9 months prior to the service dates


To


IV-E Reimbursability node

container Navigation Hint Client Eligibility

Short Message No IV-E Reimbursability from MAXIS in the nine months prior to the

service dates.

Example Warning - Client Eligibility: No IV-E Reimbursability from MAXIS in the

nine months prior to the service dates.

Long Message

After one year, IV-E cannot be claimed until reimbursability results are

received from MAXIS. Reimbursability results must be certified in

MAXIS before they are sent to SSIS.

Parameters None



Proofing Messages

Page 54 of 139

Error Condition




If PYMT_SVC_END_DT <= Report Period End Date

CompareDate = PYMT_SVC_END_DT





Abstract Report

(select count(*)



and C.STATE_RPT_ID = STATE_RPT_ID ) > 0



PYMT_SVC_END_DT



PYMT_SVC_END_DT

Service dates are more than nine months after the Continuous


CompareDate >


9))

A reimbursability record does not exist within 9 months of the

service dates:

(select count(*)




and to_date( R.REIMB_YR_MONTH, ’yyyymm’) >=

add_months(trunc(CompareDate,‘month’),-9)

) = 0



Proofing Messages

Page 55 of 139

1.1.2.39 #1170 - Invalid Special Cost Code

Checkbox Label IV-E Service Type Message # 1170

Description Invalid Special Cost Code

Rule Exclude the Payment if a IV-E Service Type cannot be assigned

because the Special Cost Code is not IV-E reimbursable.


To selected Payment


Short Message

The “Special Cost Code” ([@SpecCostCode] – [@SpecCodeDescription])

is not IV-E reimbursable with “Service” ([@SvcCode] -

[@SvcDescription]).

Example

Payment: The “Special Cost Code” (01 – Initial Clothing) is not IV-E

reimbursable with “Service” (214 – Other childcare).

Payment: The “Special Cost Code” (03 - Transportation, non-medical)

is not IV-E reimbursable with “Service” (181 – Child family foster care).

Long Message The “Special Cost Code” must be valid with the “Service” to claim IV-E.

Parameters

@SpecCostCode =SPECIAL_COST.SPC_CODE for

PAYMENT.SPECIAL_COST_ID

@SpecCostCode =SPECIAL_COST.SPC_DESC for

PAYMENT.SPECIAL_COST_ID

@SvcCode = ServiceCode


Error Condition


A “IV-E Service Type” cannot be assigned

Not ValidIV-EServiceType

“Special Cost Code” has a value

PAYMENT.SPECIAL_COST_ID is not null



Proofing Messages

Page 56 of 139

1.1.2.40 #1171 – No Maintenance Claim – Additional Cost


Description No Maintenance Claim – Additional Cost

Rule Exclude the Payment if the IV-E Service Type is Initial Clothing,

Childcare Costs, or Educational Transportation and a Maintenance

Claim does not exist anytime during the service dates.


To selected Payment


Short Message “[@IVESvcTypeDesc]” must have a “Maintenance” claim that includes

the service dates.

Example Payment: “Initial Clothing” must have a “Maintenance” claim that

includes the service dates.

Long Message

The service dates must be equal to or completely within the service

dates of a IV-E Claim for “Maintenance” or “Basic Maintenance.” A

“Maintenance” or “Basic Maintenance” claim does not exist for the

service dates.

Parameters @IVESvcTypeDesc = CODE.DESCRIPTION for IVE_SVC_TYPE_CD

Error Condition


IV-E Service Type is Initial Clothing, Childcare Costs, or

Educational Transportation


and IVE_SVC_TYPE_CD in (‘B’, ‘C’, ‘T’)

A Maintenance Claim does not exist during any part of the

service dates




and (PYMT_SVC_START_DT between C.CLM_SVC_START_DT

and C.CLM_SVC_END_DT

or C.CLM_SVC_START_DT between


and C.IVE_SVC_TYPE_CD in (‘A’, ‘E’)

and NotBackedOut)



Proofing Messages

Page 57 of 139

1.1.2.41 #1172 – No Maintenance Claim – Admin


Description No Maintenance Claim – Admin

Rule Exclude the Payment if the IV-E Service Type is Admin and a

Maintenance Claim does not exist with the same service dates.


To selected Payment


Short Message “[@IVESvcTypeDesc]” must have a “Maintenance” claim for the same

service dates.

Example Payment: “Rule 4 Administration and Training” must have a

“Maintenance” claim for the same service dates.

Long Message

The service dates must be equal to the service dates of a IV-E Claim for

“Maintenance” or “Basic Maintenance.” A “Maintenance” or “Basic

Maintenance” claim does not exist for the service dates.


Error Condition


IV-E Service Type is Rule 4 Placing Agency's Administrative Fee

ValidIV-EServiceType and IVE_SVC_TYPE_CD = ‘D’

A Maintenance Claim does not exist with the same service

dates









and C.RULE_CD <> (‘SIL’)

and NotBackedOut)



Proofing Messages

Page 58 of 139

1.1.2.42 #1173 – No Maintenance Claim – Difficulty of Care (DOC)


Description No Maintenance Claim – Difficulty of Care (DOC)

Rule Exclude the Payment if the IV-E Service Type is “Difficulty of Care

(DOC)” and a “Basic Maintenance” claim does not exist with the same

service dates for the same vendor.


To selected Payment


Short Message “[@IVESvcTypeDesc]” must have a “Basic Maintenance” claim for the

same service dates and “Service Vendor.”

Example Payment: “Difficulty of Care (DOC)” must have a “Basic Maintenance”

claim for the same service dates and “Service Vendor.”

Long Message

Both the service dates and the service vendor must match a IV-E Claim

for “Basic Maintenance.” A “Basic Maintenance” claim does not exist

for the service dates and “Service Vendor.”


Error Condition


IV-E Service Type is Difficulty of Care (DOC)

ValidIV-EServiceType and IVE_SVC_TYPE_CD = ‘F’

A “Basic Maintenance” claim does not exist with the same

service dates and service vendor








and C.SVC_BUS_ORG_ID = PAYMENT.SVC_BUS_ORG_ID

and C.IVE_SVC_TYPE_CD = ‘E’

and NotBackedOut)



Proofing Messages

Page 59 of 139

1.1.2.43 #1174 – No Maintenance Claim – Adjustment of DOC


Description No Maintenance Claim – Adjustment of DOC

Rule Exclude the Payment if the IV-E Service Type is Adjustment of DOC and

a “Maintenance” claim or a “Basic Maintenance” and “Difficulty of Care

(DOC)” claim does not exist for the service dates with the same

vendor.


To selected Payment


Short Message “[@IVESvcTypeDesc]” must have a “Maintenance” claim for the same

service dates and “Service Vendor.”

Example Payment: “Adjustment of DOC” must have a “Maintenance” claim for

the same service dates and “Service Vendor.”

Long Message

Both the service dates and the service vendor must match a IV-E Claim

for “Maintenance” or both a “Basic Maintenance” and “DOC only” claim.

A “Maintenance” or both a “Basic Maintenance” and “DOC only” claim

do not exist for the service dates and “Service Vendor.”




Proofing Messages

Page 60 of 139

Error Condition


IV-E Service Type is Adjustment of DOC

ValidIV-EServiceType and IVE_SVC_TYPE_CD = ‘G’

A “Maintenance” claim does not exist that covers the service

dates for the same vendor









and C.IVE_SVC_TYPE_CD = ‘A’


and NotBackedOut)

Both a “Basic Maintenance” claim and a “Difficulty of Care

(DOC)” claim do not exist for the service dates and vendor

(select count(*)




C.CLM_SVC_START_DT and C.CLM_SVC_END_DT




and C.IVE_SVC_TYPE_CD in (‘E’,’F’)

and NotBackedOut)

< 2



Proofing Messages

Page 61 of 139

1.1.2.44 #1175 – Service Dates Invalid with Maintenance Claim –

Additional Cost


Description Service Dates Invalid with Maintenance Claim – Additional Cost

Rule Exclude the Payment if the IV-E Service Type is Initial Clothing,

Childcare Costs, or Educational Transportation and the service dates

are partially within the service dates of a Maintenance Claim.


To

Client | Fiscal Details | IV-E

Claims node container Navigation Hint Claim

Short Message “[@IVESvcTypeDesc]” service dates are partially within one or more

“Maintenance” claims.

Example Claim: “Initial Clothing” service dates are partially within one or more


Long Message The service dates must be equal to or completely within the service

dates of a IV-E Claim for “Maintenance” or “Basic Maintenance.”




Proofing Messages

Page 62 of 139

Error Condition


IV-E Service Type is Initial Clothing, Childcare Costs, or



and IVE_SVC_TYPE_CD in (‘B’, ‘C’, ‘T’)

A Maintenance Claim exists during part of the service dates

exists (select *








and NotBackedOut)

The service dates are not completely within the dates of the

Maintenance Claim




and PYMT_SVC_START_DT between C.CLM_SVC_START_DT


and PYMT_SVC_END_DT between C.CLM_SVC_START_DT



and NotBackedOut)



Proofing Messages

Page 63 of 139

1.1.2.45 #1176 – Service Dates Invalid with Maintenance Claim -

Admin


Description Service Dates Invalid with Maintenance Claim - Admin

Rule Exclude the Payment if the IV-E Service Type is “Rule 4 Placing

Agency's Administrative Fee” and the service dates are partially within

the service dates of a Maintenance Claim.


To





Example Payment: “Rule 4 Placing Agency’s Administrative Fee” service dates

are partially within one or more “Maintenance” claims.

Long Message The service dates must be equal to the service dates of a IV-E Claim for

“Maintenance” or “Basic Maintenance.”


Error Condition


IV-E Service Type is Rule 4 Placing Agency's Administrative Fee

ValidIV-EServiceType and IVE_SVC_TYPE_CD = ‘D’

A Maintenance Claim exists during part of the service dates

exists (select *









and NotBackedOut)

A Maintenance Claim does not exist with the same service

dates




and PYMT_SVC_START_DT = C.CLM_SVC_START_DT

and PYMT_SVC_END_DT = C.CLM_SVC_END_DT



and NotBackedOut)



Proofing Messages

Page 64 of 139


Difficulty of Care (DOC)


Description Service Dates Invalid with Maintenance Claim - Difficulty of Care (DOC)

Rule Exclude the Payment if the IV-E Service Type is “Difficulty of Care

(DOC)” and the service dates are partially within the service dates

of a “Basic Maintenance” claim for the same vendor.


To




“Basic Maintenance” claims.

Example Claim: “Difficulty of Care (DOC)” service dates are partially within one

or more “Basic Maintenance” claims.

Long Message Both the service dates and the “Service vendor” must match a IV-E

Claim for “Basic Maintenance.”


Error Condition


IV-E Service Type is Difficulty of Care (DOC)

ValidIV-EServiceType and IVE_SVC_TYPE_CD = ‘F’

A “Basic Maintenance” exists during part of the service dates

exists (select *









and NotBackedOut)

A “Basic Maintenance” does not exist with the same service

dates




and PYMT_SVC_START_DT = C.CLM_SVC_START_DT

and PYMT_SVC_END_DT = C.CLM_SVC_END_DT



and NotBackedOut)



Proofing Messages

Page 65 of 139


Adjustment of DOC


Description Service Dates Invalid with Maintenance Claim - Adjustment of DOC

Rule Exclude the Payment if the IV-E Service Type is Adjustment of DOC and

the service dates are partially within a Maintenance Claim for the

same vendor.


To





Example Claim: “Adjustment of DOC” service dates are partially within one or

more “Maintenance” claims.

Long Message Both the service dates and the service vendor must match a IV-E Claim

for “Maintenance” or both a “Basic Maintenance” and “DOC only” claim.


Error Condition


IV-E Service Type is Adjustment of DOC

ValidIV-EServiceType and IVE_SVC_TYPE_CD = ‘G’

A “Maintenance” claim or both a “Basic Maintenance” claim and

a “Difficulty of Care (DOC)” claim exist during part of the

service dates for the same vendor

(select *








and C.IVE_SVC_TYPE_CD in (‘A’, ‘E’, ‘F’)


and NotBackedOut)

returns one or more records

If one record is returned:

C.IVE_SVC_TYPE_CD = ‘A’

If more than one record is returned:

C.IVE_SVC_TYPE_CD = ‘E’ on one record

C.IVE_SVC_TYPE_CD = ‘F’ on the other record



Proofing Messages

Page 66 of 139

Error Condition

(continued)

A “Maintenance” claim does not exist that covers the service

dates for the same vendor




and PYMT_SVC_START_DT >= C.CLM_SVC_START_DT

and PYMT_SVC_END_DT <= C.CLM_SVC_END_DT


and C.IVE_SVC_TYPE_CD = ‘A’


and NotBackedOut)

Both a “Basic Maintenance” claim and a “Difficulty of Care

(DOC)” claim do not exist for the service dates and vendor

(select count(*)



and PYMT_SVC_START_DT >= C.CLM_SVC_START_DT

and PYMT_SVC_END_DT <= C.CLM_SVC_END_DT


and C.IVE_SVC_TYPE_CD in (‘E’,’F’)

and NotBackedOut

) < 2



Proofing Messages

Page 67 of 139

1.1.2.48 #1179 – Initial Clothing – Invalid Service Dates


Description Initial Clothing – Invalid service dates

Rule Exclude the Payment if the IV-E Service Type is Initial Clothing and the

service dates are not completely with the first 60 days of the



To selected Payment


Short Message “[@IVESvcTypeDesc]” service dates must be within the first 60 days of

the Continuous Placement ([@ContPlcmtStart] – [@ClothingEnd]).

Example Payment: “Initial Clothing” service dates must be within the first 60

days of the Continuous Placement (06/05/2011 – 08/03/2011).

Long Message

The service dates are not completely within the first 60 days of the

Continuous Placement. Clothing purchased prior to the Continuous

Placement “Start Date” or after the first 60 days is not IV-E

reimbursable.

Parameters

@IVESvcTypeDesc = CODE.DESCRIPTION for IVE_SVC_TYPE_CD


@ClothingEnd = trunc(CONTPLCMT_START_DT) + 59

Error Condition




PYMT_SVC_END_DT

IV-E Service Type is Initial Clothing

ValidIV-EServiceType and IVE_SVC_TYPE_CD = ‘B’

The service dates are not completely within the first 60 days of

the Continuous Placement

PYMT_SVC_END_DT > trunc(CONTPLCMT_START_DT) + 59



Proofing Messages

Page 68 of 139

1.1.2.49 #1180 – Group Provider – Invalid IV-E Service Type


Description Group Provider – Invalid IV-E Service Type

Rule Exclude the Payment if the Provider Type is Group and the IV-E Service

Type is not Maintenance, Initial Clothing, or Educational Transportation.


To selected Payment


Short Message The “Service Vendor has a “Provider Type” of “Group,” which is not

valid for “[@IVESvcTypeDesc].”

Example Payment: The “Service Vendor has a “Provider Type” of “Group,” which

is not valid for “Childcare Costs.”

Long Message The "IV-E Service Type" must be "Maintenance," "Initial Clothing," or

"Educational Transportation" for group providers.


Error Condition

Display the message when all of the following are true:

IV-E Service Type is not Maintenance, Initial Clothing, or



and IVE_SVC_TYPE_CD not in (‘A’, ‘B’, ‘T’)

A Rule Code can be assigned

ValidRuleCode

Provider Type = ‘Group’

ValidProviderType and PROVIDER_TYPE_CD = ‘G’



Proofing Messages

Page 69 of 139

1.1.2.50 #1181 – Invalid BRASS Service


Description Invalid BRASS Service

Rule The “Service” must be a Reimbursable Service.

IV-E Service Type is based on the Payment’s “Service” and “Special

Cost Code.” Exclude the Payment if a IV-E Service Type cannot be

assigned because the “Service” is not a Reimbursable Service.


To selected Payment


Short Message The “Service” is not IV-E reimbursable.

Example Payment: The “Service” is not IV-E reimbursable.

Long Message The “Service” must be 171, 180, 181, 183, 185, 188, 214, or 483 to

claim IV-E.

Parameters None

Error Condition


Payment meets the standard criteria for records on proofing,

except the "Service" is not a Reimbursable Service

ServiceCode not in (‘171’, ‘180’, ‘181’, ‘183’, ‘185’, ‘188’,

‘214’, ‘483’)



Proofing Messages

Page 70 of 139

1.1.2.51 #1190 – No License # on Payment

Checkbox Label License # / IV-E Sub Code Message # 1190

Description No License # on Payment

Rule Unless the Reported License is assigned by the generate process, the

Payment must have a “License #.”


To selected Payment


Short Message The “License #” must have a value.

Example Payment: The “License #” must have a value.

Long Message The Service Vendor’s “License #” must be entered on the Payment to

claim IV-E.

Parameters None

Error Condition


The “License #” on the Payment does not have a value

PAYMENT.PROV_LIC_NUM is null

The IV-E Service Type is not Initial Clothing, Childcare Costs,



and IVE_SVC_TYPE_CD not in (‘B’, ‘C’, ‘T’)


20)”




Proofing Messages

Page 71 of 139

1.1.2.52 #1191 – No Effective IV-E Provider Rate


Description No Effective IV-E Provider Rate

Rule Exclude the Payment if the “License #” and "IV-E Sub Code" exist on

the IV-E Group Provider table, but a IV-E Group Rate record for

the service dates does not exist.

(v13.2, changed to use new IV-E Group Provider Rates instead of

the IV-E Rate Bulletin, PR #13-0107-1745-36)


To selected Payment


Short Message The service dates must be within the effective dates of a Title IV-E

Provider Rate for the “License #” / ”IV-E Sub Code.”

Example Payment: The service dates must be within the effective dates of a

Title IV-E Provider Rate for the “License #” / ”IV-E Sub Code.”

Long Message

The “License #” / “IV-E Sub Code” exists in the Title IV-E Group

Providers table, but a valid Title IV-E Group Rates record for the service

dates does not exist.

Parameters None



Proofing Messages

Page 72 of 139

Error Condition







20)”


The “License #” and “IV-E Sub Code” exists on the IV-E Group

Providers table

exists (select *

from DI_IVE_PROV_LIC

where PROV_LIC_NUM =

upper(trim(PAYMENT.PROV_LIC_NUM)))

and nvl(IVE_SUB_CD,’blank’) =

nvl(PAYMENT.IVE_SUB_CD,’blank’))

The service dates are not within the effective dates of a IV-E

Group Rates record for the “License #” and “IV-E Sub Code”


from DI_IVE_PROV_LIC PL,

DI_IVE_LIC_RATE LR

where PL.DI_IVE_PROV_LIC_ID = LR.DI_IVE_PROV_LIC_ID

and PL.PROV_LIC_NUM =

upper(trim(PAYMENT.PROV_LIC_NUM))

and nvl(PL.IVE_SUB_CD,’blank’) =

nvl(PAYMENT.IVE_SUB_CD,’blank’)

and PYMT_SVC_START_DT >= LR.EFF_DT

and PYMT_SVC_END_DT <= LR.EXP_DT

and LR.EFF_DT <> LR.EXP_DT

and (LR.APPR_PER_DIEM > 0

or LR.APPR_IVE_MTN_PCNT > 0))



Proofing Messages

Page 73 of 139

1.1.2.53 #1192 – Invalid IV-E Sub Code


Description Invalid IV-E Sub Code

Rule Exclude the Payment if the “License #” exists, but the but the “IV-E

Sub Code” is invalid because of one of the following:

• The Payment’s “IV-E Sub Code” is blank and the License # on

the IV-E Group Provider table has a “IV E Sub Code”

• The Payment’s “IV-E Sub Code” does not exist for the License #

on the IV-E Group Provider table

(v13.2, changed to use new IV-E Group Provider Rates instead of

the IV-E Rate Bulletin, PR #13-0107-1745-36)


To selected Payment


Short Message The “IV-E Sub Code” does not match the "License #" on the Title IV-E

Group Providers table.

Example Payment: The “IV-E Sub Code” does not match the "License #" on the

Title IV-E Group Providers table.

Long Message

Either the Payment “IV-E Sub Code” is blank and the “License #” needs

a “IV-E Sub Code” or the “IV-E Sub Code” does not exist for the

“License #” in the Title IV-E Group Providers table.

Parameters None

Error Condition







20)”


The License # exists on the IV-E Group Providers table

exists (select *




A IV-E Provider Rate record for the service dates does not

exist for the “License #” and “IV-E Sub Code”


from DI_IVE_PROV_LIC PL

where PL.PROV_LIC_NUM =


nvl(PL.IVE_SUB_CD,’blank’) =




Proofing Messages

Page 74 of 139

1.1.2.54 #1193 – License Status must be Granted


Description License Status must be Granted

Rule The “Status” of the license must be “Granted”


To

Bus Org | Licenses | effective

License record Navigation Hint License

Short Message The “License Status” ([@LicStat]) must be “Granted.”

Example License: The “License Status” (Pending) must be “Granted.”

Long Message The “Status” of the Service Vendor’s “License #” is not “Granted.”

Parameters @LicStat = CODE.DESCRIPTION for LICENSE_STAT_CD

Error Condition







20)”


The License # does not exist on the IV-E Group Providers

table (v13.2, changed to use new tables instead of the IV-E

Rate Bulletin, PR #13-0107-1745-36)





The “Status” of the License # is not “Granted”

(select PROV_LID_DETAIL_ID, LICENSE_STAT_CD

from PROV_LIC_DETAIL

where BUS_ORG_ID = PAYMENT.SVC_BUS_ORG_ID

and PROV_LIC_NUM =


and PYMT_SVC_START_DT >= PROV_LIC_START_DT

and PYMT_SVC_END_DT <= PROV_LIC_END_DT

and LICENSE_STAT_CD <> ‘1’

and rownum = 1

) returns a record



Proofing Messages

Page 75 of 139

1.1.2.55 #1194 – Facility Type not 001, OSH or OT2


Description Facility Type not 001, OSH or OT2

Rule The “IV-E Facility Type” on the license record must be ‘001’, ‘OSH’ or

‘OT2’


To



Short Message The “IV-E Facility Type” ([@LicFacilType]) must be 001, OSH, OT2 for

licenses not on the Title IV-E Group Providers table.

Example

License: The “IV-E Facility Type” (022 - Rule 22 Transitional Living

Facility (MN DHS)) must be 001, OSH, OT2 for licenses not on the Title

IV-E Group Providers table.

Long Message

The “License #” does not exist on the Title IV-E Group Providers table.

The “IV-E Facility Type” for family foster homes must be “001 - Rule 1

Family Foster Home (MN DHS),” “OSH - Out-of-state FFH,” or “OT2 -

Tribally approved American Indian FFH.”

Parameters @LicFacilType= CODE.DESCRIPTION for FACILITY_TYPE_CD



Proofing Messages

Page 76 of 139

Error Condition






The Service is not “188 - Supervised independent living (18-20)”



table (v13.2, changed to use new tables instead of the IV-E Rate

Bulletin, PR #13-0107-1745-36)





The “IV-E Facility Type” is not 001, OSH or OT2

(select PROV_LIC_DETAIL_ID, FACILITY_TYPE_CD



and PROV_LIC_NUM =




and nvl(FACILITY_TYPE_CD,’-99’) not in (‘001’, ‘OSH’,

‘OT2’)

and rownum = 1

) returns a record



Proofing Messages

Page 77 of 139

1.1.2.56 #1195 – License Record does not exist for Bus Org


Description License Record does not exist for Bus Org

Rule A License record must exist for the Service Vendor and License number

on the Payment


To

Bus Org | Licenses node

container Navigation Hint License

Short Message The “License #” does not exist for the “Service Vendor.”

Example License: The “License #” does not exist for the “Service Vendor.”

Long Message The Service Vendor’s license record was changed or deleted after the

Payment was created.

Parameters None

Error Condition







20)”







where PROV_LIC_NUM=


The “License #” on the Payment has a value

PAYMENT.PROV_LIC_NUM is not null

A License record does not exist for the Service Vendor and

License #




and upper(PROV_LIC_NUM) =

upper(PAYMENT.PROV_LIC_NUM))



Proofing Messages

Page 78 of 139

1.1.2.57 #1196 – Service Dates not Valid with License Dates


Description Service Dates not Valid with License Dates

Rule The service dates must be within the effective dates of the license

record for the Bus Org


To



Short Message The service dates must be within the License effective dates

([@StartDate] – [@EndDate]).

Example The service dates must be within the License effective dates

(06/01/2010 – 05/31/2011).

Long Message The effective dates of the License must cover the service dates to claim

IV-E.

Parameters @StartDate = PROV_LIC_START_DT

@EndDate = PROV_LIC_END_DT



Proofing Messages

Page 79 of 139

Error Condition







20)”









The License record exists for the Bus Org

(select PROV_LIC_DETAIL_ID, PROV_LIC_START_DT,

PROV_LIC_END_DT




upper(PAYMENT.PROV_LIC_NUM)

and rownum = 1

) returns a row

The service dates are not within the License effective dates





upper(PAYMENT.PROV_LIC_NUM)


and PYMT_SVC_END_DT <= PROV_LIC_END_DT)



Proofing Messages

Page 80 of 139

1.1.2.58 #1197 – Invalid Tribe on License


Description Invalid Tribe on License

Rule If the Rule Code = OT2 (Tribally licensed/approved family foster

home), the "Tribe" on the license record must have a value other than

the following:

• T99 Unknown tribe

• TUC Unknown Chippewa

• TUS Unknown Sioux

(Added in v13.2, PR#13-0118-1310-51)


To



Short Message The licensing “Tribe” ([@Tribe]) must be a known tribe to claim IV-E.

Example License: The licensing “Tribe” (Unknown tribe) must be a known tribe

to claim IV-E.

Long Message

The “IV-E Facility Type” is “[@FacilityType].” To claim IV-E, the "Tribe"

on the License record must be a valid tribe.

Example:

The “IV-E Facility Type” is “Tribally licensed/approved family foster

home.” To claim IV-E, the "Tribe" on the License record must be a

valid tribe.

Parameters

@Tribe = CODE.DESCRIPTION for RACE_SUBGRP_CD =

PROV_LIC_DETAIL.TRIBE_CD

@FacilityType =

CODE.DESCRIPTION for PROV_LIC_DETAIL.FACILITY_TYPE_CD



Proofing Messages

Page 81 of 139

Error Condition







20)”


The Rule Code is OT2 (Tribally licensed/approved family foster

home)

ValidRuleCode and RULE_CD = 'OT2'

The “Tribe” is blank or an Unknown Tribe

(select PROV_LIC_DETAIL_ID, TRIBE_CD







and LICENSE_STAT_CD = ‘1’

and (TRIBE_CD is null or TRIBE_CD in ('T99', 'TUC',

'TUS')

and rownum = 1

) returns a record



Proofing Messages

Page 82 of 139

1.1.2.59 #1201 – IV-E Reimbursable is No

Checkbox Label Other Message # 1201

Description IV-E Reimbursable is No

Rule “IV-E Reimbursable” on the Payment must be “Yes.”


To selected Payment


Short Message “IV-E Reimbursable” is “No” and the client is IV-E eligible and IV-E

reimbursable.

Example Payment: “IV-E Reimbursable” is “No” and the client is IV-E eligible

and IV-E reimbursable.

Long Message Verify “IV-E Reimbursable” = “No” is accurate for this Payment.

Parameters None

Error Condition


IV-E Reimbursable = "Yes"


IV-E Reimbursable = No

IVE_REIMB_IND = 'N'

A IV-E Service Type can be assigned




PYMT_SVC_END_DT

The client is IV-E Eligible during the service dates


PYMT_SVC_END_DT

The client is IV-E Reimbursable during the service dates

IV-EReimClient for PYMT_SVC_START_DT through

PYMT_SVC_END_DT

The service dates are not for the discharge date (added in

v12.3, PR #12-0412-1530-16)

PYMT_SVC_START_DT = PYMT_SVC_END_DT

and PYMT_SVC_START_DT =

CONTPLCMT.CONTPLCMT_END_DT



Proofing Messages

Page 83 of 139

1.1.2.60 #1202 – Service Dates too Old to Claim


Description Service Dates too Old to Claim

Rule The service dates on the Payment must be within eight quarters of

the Report Period End Date.


To selected Payment


Short Message The service dates are too old to claim.

Example Payment: The service dates are too old to claim.

Long Message The service dates on the Payment cannot be more than eight quarters

before the report end date.

Parameters None

Error Condition


Payment meets the standard criteria for records on proofing

except the service dates are more than eight quarters prior to

the Report Period End Date

PYMT_SVC_START_DT < Report Service Start Date



Proofing Messages

Page 84 of 139

1.1.2.61 #1203 – Negative Modification too Old to Claim


Description Negative Modification too Old to Claim

Rule The "Service Start Date" must be on or after the Report Service Start

Date and the “Warrant / Eff Date” on both the Original Payment and

the Negative Payment Modification must be within five quarters


To selected Payment


Short Message This [@PaymentType] is too old to claim. Report the paid “Amount” as

a IV-E Recovery.

Example Payment: This Cancellation (Recovery) is too old to claim. Report the

paid “Amount” as a IV-E Recovery.

Long Message

The amount of this Payment must be reported as a IV-E Recovery

because the service dates are more than eight quarters before the

report end date or the original Payment was made more than five

quarters before the report end date.

Parameters @PaymentType = CODE.DESCRIPTION for PYMT_TYPE_CD



Proofing Messages

Page 85 of 139

Error Condition

The standard criteria for records on proofing is ignored for this edit


The Payment Type is a Negative Payment Modification

Code Description

4 Adjustment Reversal

5 Refund

6 Recovery

7 Cancellation (Refund)

8 Cancellation (Recovery)

The "Warrant / Eff Date" is between the Report Payment

Dates

PYMT_DT between Report Payment Start Date and

Report Period End Date

The Payment has not been claimed



where PAYMENT_ID = C.PAYMENT_ID)


IVE_REIMB_IND = 'Y'

The Original Payment has been claimed

exists (select *


where C.PAYMENT_ID = ORIG_PAYMENT_ID)

The "Service Start Date" is before the Report Service Start

Date

PYMT_SVC_START_DT < Report Service Start Date

or

The Original Payment was made more than five quarters ago

(select PYMT_DT

from PAYMENT P

where P.PAYMENT_ID = ORIG_PAYMENT_ID)

< Report Payment Start Date



Proofing Messages

Page 86 of 139

1.1.2.62 #1204 – Basic Per Diem does not Match Approved Per

Diem


Description Basic Per Diem does not Match Approved Per Diem

Rule Display a warning if the per diem does not match the approved per

diem and the Rule Code is not SIL.

For Rule Codes 1, OSH, OT2 and SIL, the approved per diem applies to

an age range. In the significant birthday month, counties can pay the

per diem for either lower or the higher age.

For all other Rule Codes, the approved per diem is in the IV-E Group

Provider Rates.

(v13.2, use IV-E Group Provider Rates, PR #13-0107-1745-36)


To selected Payment


Short Message The “[@PerDiemLabel]” ([@PymtPerDiem]) does not match the

approved per diem ([@ApprovedPerDiem]).

Example

Warning - Payment: The “Basic Per Diem” ($32.50) does not match the

approved per diem ($24.63).

Warning - Payment: The “Rate” ($132.50) does not match the

approved per diem ($124.63).

Long Message

The rate on the Payment may be incorrect. If the “License #” / “IV-E

Sub Code” is on the Title IV-E Group Providers table, the wrong “License

#” / “IV-E Sub Code” may have been selected.

Parameters

If the Rule Code is ‘1’, ‘OSH’ or ‘OT2’

@PerDiemLabel = “Basic Per Diem”

@PymtPerDiem = PYMT_PER_DIEM formatted as currency

@ApprovedPerDiem = PD.DAILY_BASIC_RATE formatted as

currency

Otherwise

@PerDiemLabel = “Rate”

@PymtPerDiem = PYMT_RATE formatted as currency

@ApprovedPerDiem = RB.APPR_PER_DIEM formatted as currency

Error Condition





Report






Proofing Messages

Page 87 of 139

Error Condition

(continued)



The Special Cost Code on the Payment is not ‘17’ (Rule 5 room

and board)

PAYMENT.SPECIAL_COST_ID <> ‘17’


ValidRuleCode

The Rule Code is not SIL (Supervised Independent Living)

RULE_CD <> ‘SIL’

If the Rule Code is ‘1’, ‘OSH’ or ‘OT2’

RULE_CD in (‘1’, ‘OSH’, ‘OT2’)

“Basic Per Diem” has a value

PAYMENT.PYMT_PER_DIEM is not null

The “Basic Per Diem” does not match the approved per diem

select PD.DAILY_BASIC_RATE

from CFC_BASIC_PER_DIEM PD

where (YEAR = to_char(PYMT_SVC_END_DT, 'yyyy')

and (CalculatedAge for

trunc(PYMT_SVC_START_DT,’month’) between

PD.AGE_LOW and nvl(PD.AGE_HIGH,99)

or CalculatedAge for last_day(PYMT_SVC_END_DT)

between PD.AGE_LOW and nvl(PD.AGE_HIGH,99))

Display the message if the “Basic Per Diem” does not match

the value on any of the records returned (If the client has a

significant birthday during the service dates, the approved

per diem will change and two records may be returned)

PYMT_PER_DIEM <> PD.DAILY_BASIC_RATE

For all other Rule Codes

RULE_CD not in (‘1’, ‘OSH’, ‘OT2’)

The “Rate” does not match the approved per diem

select APPR_PER_DIEM

from DI_IVE_PROV_LIC PL,

DI_IVE_LIC_RATE LR

where PL.DI_IVE_PROV_LIC_ID =

LR.DI_IVE_PROV_LIC_ID

and PL.PROV_LIC_NUM = upper(trim(PAYMENT.

PROV_LIC_NUM))

nvl(PL.IVE_SUB_CD,’blank’) =


and PYMT_SVC_START_DT >= LR.EFF_DT

and PYMT_SVC_END_DT <= LR.EXP_DT

Display the message if the “Rate” does not match the value

on the record returned.

PYMT_RATE <> APPR_PER_DIEM



Proofing Messages

Page 88 of 139

1.1.2.63 #1205 – Unit Type not Valid


Description Unit Type not Valid

Rule The Unit Type must be one of the following:

Day

Daily rate, live-in

Daily rate, cert. facility


To selected Payment


Short Message The “Unit Type” must be “Day,” “Daily rate, live-in,” or “Daily rate,

cert. facility.”

Example Payment: The “Unit Type” must be “Day,” “Daily rate, live-in,” or

“Daily rate, cert. facility.”

Long Message The “Unit Type” must be per day to claim IV-E.

Parameters None

Error Condition


The IV-E Service Type is Maintenance, Rule 4 Placing Agency’s

Administrative Fee, Basic Maintenance, Difficulty of Care (DOC),

or Adjustment of DOC

ValidIV-EServiceType and IVE_SVC_TYPE_CD in (‘A’, ‘D’,

‘E’, ‘F’, ‘G’)


20)”


The Unit Type is not valid for IV-E Claiming

UNIT_TYPE_CD not in (‘07’, ‘08’,’31’)



Proofing Messages

Page 89 of 139

1.1.2.64 #1206 – Negative Modification – IV-E Reimbursable is No


Description Negative Modification – IV-E Reimbursable is No

Rule If the Original Payment was claimed and reimbursed, Negative

Payment Modifications should, generally, also be claimed.


To selected Payment


Short Message “IV-E Reimbursable” is “No” and the original Payment has been

claimed.

Example “IV-E Reimbursable” is “No” and the original Payment has been

claimed.

Long Message

If the full amount of the IV-E Claim for the original Payment was

reimbursed, this Payment Modification should also be claimed by

changing “IV-E Reimbursable” to “Yes.”

Parameters None



Proofing Messages

Page 90 of 139

Error Condition

The standard criteria for records on proofing is ignored for this edit


The Payment Type is a Negative Payment Modification

Code Description

4 Adjustment Reversal

5 Refund

6 Recovery

7 Cancellation (Refund)

8 Cancellation (Recovery)

IV-E Reimbursable = "No"

IVE_REIMB_IND = 'N'

The "Warrant / Eff Date" is between the Report Payment

Dates

PYMT_DT between Report Payment Start Date and

Report Period End Date

The “Service Start Date" is on or after the Report Service

Start Date

PYMT_SVC_START_DT >= Report Service Start Date

The Payment has not been claimed

not exists (select * from IVE_ABSTRACT_CLAIM C


The Original Payment has been claimed

exists (select *


where C.PAYMENT_ID = ORIG_PAYMENT_ID)

The Original Payment was made within the last five quarters

(select PYMT_DT

from PAYMENT P

where P.PAYMENT_ID = ORIG_PAYMENT_ID)

>= Report Payment Start Date



Proofing Messages

Page 91 of 139

1.1.2.65 #1207 – EFC-SIL - One Day Payment


Description EFC-SIL - One Day Payment

Rule Display a warning if the Rule Code is SIL, the payment is for one day,

and the rate is more than the allowable per diem.

(Added in v13.2, 13-0111-1504-45)


To selected Payment


Short Message EFC-SIL service for one day and the “Amount” ([@Amount]) is more

than allowable per diem ([@AllowablePerDiem]).

Example Warning - Payment: EFC-SIL service for one day and the “Amount”

($132.50) is more than allowable per diem ($28.04).

Long Message

The allowable per diem is the approved per diem

([@ApprovedPerDiem]) plus the DOC rate ([@DOCRate]) for the

assessed "DOC Points" ([@AssessedPoints]). IV-E reimbursement for

EFC-SIL is based on the allowable per diem for the day of service.

Example:

The allowable per diem is the approved per diem ($25.84) plus the

DOC rate ($0.22) for the assessed "DOC Points" (10). IV-E

reimbursement for EFC-SIL is based on the allowable per diem for

the day of service.

Parameters

@Amount = PYMT_PAID_AMT, formatted as currency

@AllowablePerDiem = AllowablePerDiem (see logic below), formatted

as currency

@ApprovedPerDiem = ApprovedPerDiem (see logic below), formatted

as currency

@DOCRate = DOCRate (see logic below), formatted as currency

@AssessedPoints = AssessedPoints (see logic below)

Error Condition





Abstract Report




The IV-E Service Type is “Maintenance”

ValidIV-EServiceType and IVE_SVC_TYPE_CD = ‘A’





Proofing Messages

Page 92 of 139

Error Condition

(continued)

The Payment is for one day of service

PYMT_SVC_START_DT = PYMT_SVC_END_DT

The “Amount” is more than the allowed per diem

PYMT_PAID_AMT > AllowablePerDiem

AllowablePerDiem =

ApprovedPerDiem + (DOCRate * AssessedPoints)

ApprovedPerDiem =

select PD.DAILY_BASIC_RATE

from CFC_BASIC_PER_DIEM PD


and CalculatedAge for last_day(PYMT_SVC_END_DT)

between PD.AGE_LOW and nvl(PD.AGE_HIGH,99)

DOCRate =

select POINT_RATE

from DOC_PT_RATE


AssessedPoints =

select nvl(DA.DOC_POINTS,225)

from DOC_ASSESS DA



and DA.DOC_EFF_DT =


from DOC_ASSESS DA2

where DA2.PERSON_ID = DA.PERSON_ID




from DOC_ASSESS DA3

where DA3.PERSON_ID = DA.PERSON_ID


order by DOC_ASSESS_DT desc)

AssessedPoints = nvl(DA.DOC_POINTS,225) on first record

returned or 0 if no records are returned



Proofing Messages

Page 93 of 139

1.1.2.66 #1210 – No IV-E Placement

Checkbox Label Placement Message # 1210

Description No IV-E Placement

Rule A IV-E Placement must exist for the service dates.


To



node container Navigation Hint Placement

Short Message No IV-E Placement for the service dates.

Example Placement: No IV-E Placement for the service dates.

Long Message

A IV-E Placement does not exist anytime during the service dates. A

IV-E Placement must exist with a "Start Date" that is on or before the

"Service Start Date" and an "End Date" that is blank or is on or after

the "Service End Date."

Parameters None

Error Condition


The IV-E Service Type is Maintenance

ValidIV-EServiceType and IVE_SVC_TYPE_CD in (‘A’, ’E’)

A IV-E Placement does not exist anytime during the service

dates




and PAYMENT.PERSON_ID = L.PERSON_ID

and L.LOC_REASON_CD not in (‘04’, ’12’, ’14’)

and H.LOC_SETTING_CD in (‘01’, ‘02’,

‘03’,‘04’,‘05’,‘06’,‘07’,‘09’,‘10’,‘11’)


trunc(L.LOC_START_DT) and

nvl(trunc(L.LOC_END_DT), SYSDATE + 365)

or trunc(L.LOC_START_DT) between

PYMT_SVC_START_DT and PYMT_SVC_END_DT))



Proofing Messages

Page 94 of 139

1.1.2.67 #1211 – Service Dates Partially Within a Placement


Description Service Dates Partially Within a Placement

Rule The service dates must be completely within a IV-E Placement.

Exclude the Payment if the service dates are partially within a IV-E

Placement.


To




Short Message The service dates must be within a IV-E Placement.

Example Placement: The service dates must be within a IV-E Placement.

Long Message

The service dates are partially within a IV-E Placement. A IV-E

Placement must exist with a "Start Date" that is on or before the

"Service Start Date" and an "End Date" that is blank or is on or after

the "Service End Date."

Parameters None

Error Condition




A IV-E Placement does not exist for the service dates

Not ValidIV-EPlacement for PYMT_SVC_START_DT

through PYMT_SVC_END_DT

The service dates are partially within the effective dates of a

IV-E Placement:

exists (select *



and L.PERSON_ID = PAYMENT.PERSON_ID



‘03’,‘04’,‘05’,‘06’,‘07’,‘09’,‘10’,‘11’)


trunc(L.LOC_START_DT) and

nvl(trunc(L.LOC_END_DT), SYSDATE + 365)

or trunc(L.LOC_START_DT) between


and not PYMT_SVC_START_DT between LOC_START_DT

and nvl(LOC_END_DT,sysdate + 365)

and PYMT_SVC_END_DT between LOC_START_DT and

nvl(LOC_END_DT,sysdate + 365))



Proofing Messages

Page 95 of 139

1.1.2.68 #1212 – Multiple Placements


Description Multiple Placements

Rule Exclude the payment if another Placement Location exists anytime



To




Short Message More than one IV-E Placement exists during the service dates.

Example Placement: More than one IV-E Placement exists during the service

dates.

Long Message

A single IV-E Placement must exist with a "Start Date" that is on or

before the "Service Start Date" and an "End Date" that is blank or is on

or after the "Service End Date."

Parameters None



Proofing Messages

Page 96 of 139

Error Condition





ValidIV-EPlacement for PYMT_SVC_START_DT through

PYMT_SVC_END_DT

A IV-E Placement exists for the Service Vendor



The Payment service dates are not for one day and they do

not match the Placement’s start or end date

PYMT_SVC_START_DT <> PYMT_SVC_END_DT

and PYMT_SVC_END_DT <> LOC_START_DT

and PYMT_SVC_END_DT <> LOC_END_DT

The Reason is not “Behavioral consequences - less than 30

days”

LOC_REASON_CD <> ‘03’

An overlapping Placements exists, ignoring a “Start Date” or

“End Date” overlap

SelectedPlacement = IV-EPlacementResults.PLCMT_LOC_ID

(select count(*)

from PlacementResultSet

where PLCMT_LOC_ID <> SelectedPlacement

and LOC_START_DT <> PYMT_SVC_END_DT

and nvl(LOC_END_DT, sysdate + 365) <>

PYMT_SVC_START_DT

and LOC_REASON_CD not in (‘03’, ‘04’,’12’,’14’)

and LOC_SETTING_CD in (‘01’, ‘02’, ‘03’, ‘04’, ‘05’, ‘06’,

‘07’, ‘09’, ‘10’, ‘11’, ‘12’, ‘16’)

) > 0



Proofing Messages

Page 97 of 139

1.1.2.69 #1213 – Multiple Bus Orgs on Placement History


Description Multiple Bus Orgs on Placement History

Rule Exclude the Payment if another History record with a different Bus Org

exists with an Effective Date that is between the Effective Date of the

matching Bus Org and the payment’s Service End Date.


To




Short Message The “Bus org/provider” changed during the service dates.

Example Placement: The “Bus org/provider” changed during the service dates.

Long Message A Placement History record exists for another “Bus org/provider” with

an “Effective Date” during the Payment service dates.

Parameters None

Error Condition





20)”




PYMT_SVC_END_DT




A History record for another Bus Org exists

SelectedLOC_ID = IV-EPlacementResults.PLCMT_LOC_ID

SelectedHIST_ID =

IV-EPlacementResults.PLCMT_LOC_HIST_ID

SelectedEFF_DT = IV-EPlacementResults.LOC_EFF_DT

(select count(*)

from IV-EPlacementResults

where PLCMT_LOC_ID = SelectedLOC_ID

and PLCMT_LOC_HIST_ID <> SelectedHIST_ID

and LOC_EFF_DT >= SelectedEFF_DT

and BUS_ORG_ID <> PAYMENT.SVC_BUS_ORG_ID

) > 0



Proofing Messages

Page 98 of 139

1.1.2.70 #1214 – Placement Bus Org Different than Payment


Description Placement Bus Org Different than Payment

Rule The Bus Org on the Placement Location must match the Service Vendor

on the Payment.


To


Placements/Locations/Absences | selected

Placement/Location/Absence record Navigation Hint Placement

Short Message The “Service Vendor” does not match the Placement “Bus org/provider”

([@PlcmtBusOrg]).

Example Placement: The “Service Vendor” does not match the Placement “Bus

org/provider” (John & Mary Smith).

Long Message The “Bus org/provider” on the Placement record must match the

“Service Vendor” on the Payment.

Parameters @PlcmtBusOrg = BUS_ORG.BUS_NAME for H.BUS_ORG_ID

Error Condition





20)”




PYMT_SVC_END_DT

The IV-EPlacementsResults (from ValidIV-EPlacement) does

not contain a History record for the Payment’s Service Vendor

with an effect date prior to the service dates

Not ValidIV-E PlacementandHistory for




Proofing Messages

Page 99 of 139

1.1.2.71 #1215 – Courtesy Supervision is not IV-E Reimbursable


Description Courtesy Supervision is not IV-E Reimbursable

Rule Placements for the purpose of Courtesy Supervision (“Did another

agency or state place this child – courtesy supervision by the county?”

= “Yes”) cannot be claimed by the supervising agency.


To




Short Message Courtesy supervision is not IV-E reimbursable.

Example Placement: Courtesy supervision is not IV-E reimbursable.

Long Message

Placements for the purpose of courtesy supervision (“Did another

agency or state place this child – courtesy supervision by the county?”

= “Yes”) cannot be claimed by the supervising agency and will not be

included in child counts.

Parameters None

Error Condition




A IV-E Placement does not exist for the service dates

Not ValidIV-EPlacement for PYMT_SVC_START_DT


A IV-E Placement exists for the service dates with Courtesy

Supervision = ‘Yes’

(select L.PLCMT_LOC_ID, H.PLCMT_LOC_ID



and PAYMENT.PERSON_ID = L.PERSON_ID

and L.COURTESY_SUPVN_IND = ‘Y’



‘03’,‘04’,‘05’,‘06’,‘07’,‘09’,‘10’,‘11’)

and PYMT_SVC_START_DT >= trunc(H.LOC_EFF_DT)

and (PYMT_SVC_START_DT

between trunc(L.LOC_START_DT)

and nvl(trunc(L.LOC_END_DT), SYSDATE + 365)

or trunc(L.LOC_START_DT)

between PYMT_SVC_START_DT

and PYMT_SVC_END_DT)

and rownum = 1

) returns a row



Proofing Messages

Page 100 of 139

1.1.2.72 #1216 – Local Agency is not the COFR


Description Local Agency is not the COFR

Rule Create claims only for children for whom the local agency is the "Agency

of Financial Responsibility."

(Changed in v13.2 to use new field label, PR #13-0222-1542-32)


To




Short Message The local agency is not the “Agency of Financial Responsibility”

([@COFR]) on the “Workgroup” selected on the placement.

Example

Placement: The local agency is not the “Agency of Financial

Responsibility” (Ramsey) on the “Workgroup” selected on the

placement.

Long Message Placement costs are only IV-E reimbursable if the local agency is the

“Agency of Financial Responsibility.”

Parameters @COFR = CODE.DESCRIPTION for CNTY_CD =

WORKGROUP.CNTY_FIN_RESP_CD



Proofing Messages

Page 101 of 139

Error Condition






PYMT_SVC_END_DT


ValidIV-E PlacementandHistory for PYMT_SVC_START_DT


The "Agency of Financial Responsibility” on the Workgroup

record for the Placement Location History is not the local agency,

or for regions, a county within the region:

SWHHS (88)

Description Code

Lincoln 41

Lyon 42

Murray 51

Pipestone 59

Redwood 64

Rock 67

F/M (92)

Description Code

Faribault 22

Martin 46

LocalAgency = SYSTEM_CONTROL.CNTY_CD

SelectedPlacement = IV-EPlacementResults.PLCMT_LOC_ID

(select * from IV-EPlacementResults

where PLCMT_LOC_ID = SelectedPlacement

and ((LocalAgency not in (‘88’, ’92’)

and CNTY_FIN_RESP_CD <> LocalAgency)

or (LocalAgency = ‘88’

and CNTY_FIN_RESP_CD not in (‘41’, ‘42’, ‘51’,’67’))

or (LocalAgency = ‘92’

and CNTY_FIN_RESP_CD not in (‘22’, ‘46’))

)) returns a row



Proofing Messages

Page 102 of 139

1.1.2.73 #1217 – Overlapping Location or Absence


Description Overlapping Location or Absence

Rule Display a warning if a Location or Absence exists for more than 14 days

anytime during the service dates.


To




Short Message Another Location or Absence exists for more than 14 days during the

service dates.

Example Warning - Placement: Another Location or Absence exists for more

than 14 days during the service dates.

Long Message

IV-E reimbursement is only allowable for up to 14 days when a child is

temporarily absent, but the child's placement continues with the same

provider.

Parameters None



Proofing Messages

Page 103 of 139

Error Condition





Report

(select count(*)



and C.STATE_RPT_ID = STATE_RPT_ID

) > 0





PYMT_SVC_END_DT

A IV-E Placement History record exists for the Service Vendor or

the Rule Code is ‘SIL’

ValidIV-E PlacementandHistory for PYMT_SVC_START_DT


The Payment service dates are not for one day and they do

not match the Placement’s start or end date

PYMT_SVC_START_DT <> PYMT_SVC_END_DT

and PYMT_SVC_END_DT <> LOC_START_DT

and PYMT_SVC_END_DT <> LOC_END_DT

The Reason is not “Behavioral consequences - less than 30

days”

LOC_REASON_CD <> ‘03’

A Location or Absence exists for more than 14 days during the

service dates

(select PLCMT_LOC_ID

from PlacementResultSet

where (LOC_REASON_CD in (‘03’, ‘04’,’12’,’14’)

or LOC_SETTING_CD not in (‘01’, ‘02’, ‘03’, ‘04’, ‘05’,

‘06’, ‘07’, ‘09’, ‘10’, ‘11’, ‘12’,‘16’))

and nvl(LOC_END_DT, sysdate) - LOC_START_DT + 1 >

14

and rownum = 1

) returns a row



Proofing Messages

Page 104 of 139

1.1.2.74 #1220 – Authority is Protective Hold

Checkbox Label Placement Authority Message # 1220

Description Authority is Protective Hold

Rule Exclude the Payment if the Placement Authority is ‘Protective hold.’

Severity Error

Navigates To



Placement record | Authority tab |

effective Placement Authority record Navigation Hint

Continuous

Placement

Short Message The “Authority” is “[@AuthDescr]” during the service dates.

Example Continuous Placement: The “Authority” is “Protective hold” during the

service dates.

Long Message Payments for “Protective hold” cannot be claimed to IV-E and will not

be included in child counts.

Parameters @AuthDescr = CODE.DESCRIPTION for PLACE_AUTH_CD

Error Condition




PYMT_SVC_END_DT

A “Court Ordered” or “Voluntary Placement Authority does not

exist with an effective date on or before the “Service Start Date”

Not ValidPlaceAuth for PYMT_SVC_START_DT through

PYMT_SVC_END_DT

A “Protective hold” Placement Authority exists with an effective

date on or before the “Service Start Date”

(select CONTPLCMT_AUTH_ID, PLACE_AUTH_CD

from CONTPLCMT_AUTH A

where A.CONTPLCMT_ID = CONTPLCMT_ID

and PLACE_AUTH_CD = ‘3’

and trunc(PLACE_AUTH_EFF_DT) <= PYMT_SVC_START_DT)




Proofing Messages

Page 105 of 139

1.1.2.75 #1221 – No Voluntary or Court Ordered Authority

Checkbox Label Placement Authority Message # 1221

Description No Voluntary or Court Ordered Authority

Rule Exclude the Payment if a “Voluntary” or “Court Ordered” Placement

Authority does not exist with an “Effective Date” that is on or before

the service dates.


To



Placement record | Authority tab Navigation Hint Continuous

Placement

Short Message No “Authority” exists for the service dates.

Example Continuous Placement: No “Authority” exists for the service dates.

Long Message A “Voluntary” or “Court Ordered” Placement Authority with an

“Effective Date” that is on or before the service dates is required.

Parameters None

Error Condition




PYMT_SVC_END_DT

A Placement Authority does not exist with an effective date on

or before the “Service Start Date”


from CONTPLCMT_AUTH A

where A.CONTPLCMT_ID = CONTPLCMT_ID

and trunc(PLACE_AUTH_EFF_DT) <=

PYMT_SVC_START_DT)



Proofing Messages

Page 106 of 139

1.1.2.76 #1222 – Authority Effective Date more than a Month

Before Continuous Placement Start Date


Description Authority Effective Date more than a Month Before Continuous


Rule The child must be placed within a reasonable amount of time after the

effective date of the Voluntary agreement or the Court Order.

Severity Warning

Navigates

To



Placement record | Authority tab | effective

Placement Authority record Navigation Hint

Continuous

Placement

Short Message

The “Effective Date” ([@AuthEffDate]) of the Placement Authority is

more than one month before the Continuous Placement “Start Date”

([@ContPlcmtStart]).

Example

Warning - Continuous Placement: The “Effective Date” (06/05/2011) of

the Placement Authority is more than one month before the Continuous

Placement “Start Date” (07/15/2011).

Long Message Verify that the "Effective Date" of the Placement Authority is correct.

Parameters @AuthEffDate = PLACE_AUTH_EFF_DT, formatted as mm/dd/yyyy

@ContPlcmtStart = CONTPLCMT_START_DT, formatted as mm/dd/yyyy

Error Condition





Report

exists (select *






PYMT_SVC_END_DT

A “Court Ordered” or “Voluntary” Placement Authority exists with

an effective date on or before the “Service Start Date”

ValidPlaceAuth for PYMT_SVC_START_DT through

PYMT_SVC_END_DT

The “Effective Date” of the Initial Placement Authority if more

than one month before the Continuous Placement “Start Date”

ValidPlaceAuth.PLACE_AUTH_EFF_DT <

add_months(ValidContPlcmt.CONTPLCMT_START_DT,-1)



Proofing Messages

Page 107 of 139

1.1.2.77 #1230 – Service Invalid for Rule Code

Checkbox Label Rule Code Message # 1230

Description Service Invalid for Rule Code

Rule The Service must be valid for the Rule Code. Exclude the Payment if

the Service is not valid with the Rule Code.


To selected Payment


Short Message The “Service” is not valid with the “Rule Code” ([@RuleCd] -

[@RuleCodeDescr]).

Example Payment: The “Service” is not valid with the “Rule Code” (TR - Tribally

licensed/approved child residential facility).

Long Message

The “Rule Code” is based on the “License #” / “IV-E Sub Code.” Each

“Rule Code” is only valid with certain Services. The "Service" must be

one of the following with this “Rule Code:” ([@SvcList]).

Parameters

@RuleCd = RULE_CD

@RuleCdDescr = CODE.DESCRIPTION for RULE_CD

@SvcList = List of valid Services for the Rule Code

Error Condition


A “IV-E Service Type” can be assigned”



ValidRuleCode

The Service is not valid with the Rule Code

Rule Code Valid Services

1 180, 181, 214

4 180, 181

5 483

8 171, 183

22 171, 183

31 183, 185

CP 185

OSF 183, 185, 483

OSH 180, 181, 214

OT2 180, 181, 214

TR 171, 183

SIL 188



Proofing Messages

Page 108 of 139

1.1.2.78 #1231 – Rule 4 – Invalid Special Cost Code


Description Rule 4 – Invalid Special Cost Code

Rule If Rule Code = 4, the Payment's Special Cost Code must = “14 - Rule 4

Admin (Intake and Planning).”


To selected Payment


Short Message The “Special Cost Code” must be “14 – [@SpecialCostDescr]” on Rule 4

payments.

Example Payment: The “Special Cost Code” must be “14 - Rule 4 admin (intake

and planning)” on Rule 4 payments.

Long Message

The “Rule Code” is “Child placing agency (Rule 4)” for the “License #” /

“IV-E Sub Code” on the Payment. The “Special Cost Code” must be

“14” to claim IV-E.

Parameters @SpecialCostDescr = SPC_DESC for SPC_CODE = ‘14’

Error Condition


A “IV-E Service Type” can be assigned”


The Rule Code is ‘4’

ValidRuleCode and RULE_CD = ‘4’

The Special Cost Code on the Payment is not ‘14’ (Rule 4 admin

(intake and planning))

PAYMENT.SPECIAL_COST_ID <> ‘14’



Proofing Messages

Page 109 of 139

1.1.2.79 #1232 – Special Cost Code 14 - Invalid Rule Code


Description Special Cost Code 14 - Invalid Rule Code

Rule If the Special Cost Code must = “14 - Rule 4 Admin (Intake and

Planning),.” the Rule Code must be 4 (Child placing agency (Rule 4))


To selected Payment


Short Message

The “Rule Code” ([@RuleCode] – [@RuleCodeDescr]) must be “Child

placing agency (Rule 4)” when the “Special Cost Code” is “14 –

[@SpecialCostDescr].”

Example

Payment: The “Rule Code” (5 – Child residential facility - MH cert.)

must be “Child placing agency (Rule 4)” when the “Special Cost Code”

is “14 – Rule 4 admin (intake and panning).”

Long Message “Special Cost Code” (14) can only be claimed when the “License #” /

“IV-E Sub Code” on the Payment is for a Rule 4 child placing agency.

Parameters

@RuleCode = RULE_CD

@RuleCodeDescr = CODE.DESCRIPTION for RULE_CD

@SpecialCostDescr = SPC_DESC for SPC_CODE = ‘14’

Error Condition


The Rule Code is not ‘4’

ValidRuleCode and RULE_CD <> ‘4’

The Special Cost Code on the Payment is ‘14’

SPC_CODE for PAYMENT.SPECIAL_COST_ID = ‘14’



Proofing Messages

Page 110 of 139

1.1.2.80 #1240 – Warrant / Eff Date before Service End Date

Checkbox Label Service Dates Message # 1240

Description Warrant / Eff Date before Service End Date

Rule The “Warrant / Eff Date” must be after the “Service End Date” unless

the Payment is for EFC-SIL Maintenance, Child Care, Educational

Transportation or Initial Clothing.


To selected Payment


Short Message The “Warrant / Eff Date” must be after the “Service End Date.”

Example Payment: The “Warrant / Eff Date” must be after the “Service End

Date.”

Long Message The service must be provided before the Payment is made for

Maintenance, DOC and Rule 4 costs to claim IV-E.

Parameters None

Error Condition


The IV-E Service Type is not Initial Clothing, Child Care or


ValidIV-EServiceType and IVE_SVC_TYPE_CD not in

(‘B’,‘C’,’T’)


20)”


The “Warrant / Eff Date” is on or before the “Service End Date”

PYMT_DT <= PYMT_SVC_END_DT



Proofing Messages

Page 111 of 139

1.1.2.81 #1241 – Initial Clothing - Warrant / Eff Date before

Service End Date


Description Initial Clothing - Warrant / Eff Date before Service End Date

Rule The “Warrant / Eff Date” on an Initial Clothing Payment must be on or

after the “Service End Date”


To selected Payment


Short Message Initial clothing “Warrant / Eff Date” must be on or after the “Service

End Date.”

Example Payment: Initial clothing “Warrant / Eff Date” must be on or after the

“Service End Date.”

Long Message

The service dates for initial clothing Payments should match the receipt

dates. Initial clothing is only reimbursable when paid after the clothing

is purchased.

Parameters None

Error Condition


The IV-E Service Type is Initial Clothing

ValidIV-EServiceType and IVE_SVC_TYPE_CD = ‘B’

The “Warrant / Eff Date” is before the “Service End Date”

PYMT_DT < PYMT_SVC_END_DT



Proofing Messages

Page 112 of 139

1.1.2.82 #1242 – Service Start and End Dates not in the Same

Month


Description Service start and end dates not in the same month

Rule The service dates must be within the same calendar month unless the

Payment is for EFC-SIL maintenance.


To selected Payment


Short Message The “Service Start Date” and “Service End Date” must be within the

same month.

Example Payment: The “Service Start Date” and “Service End Date” must be

within the same month.

Long Message The service dates must be within the same calendar month unless the

Payment is for EFC-SIL maintenance.

Parameters None

Error Condition


The Payment is not an EFC-SIL maintenance Payment


and not (ServiceCode <> ‘188’

and IVE_SVC_TYPE_CD = ‘A’)

The service dates are not within the same calendar month:

trunc(PYMT_SVC_START_DT, ‘month’) <>

trunc(PYMT_SVC_END_DT, ‘month’)



Proofing Messages

Page 113 of 139

1.1.2.83 #1243 – Another Claim Already Exists


Description Another Claim Already Exists

Rule Exclude the Payment if a claim exists with the same IV-E Service Type

and overlapping service dates


To


Claims | selected Claim Navigation Hint Claim

Short Message A ”[@IVESvcType]” claim ([@ClmStartDt] - [@ClmEndDt]) already

exists for the service dates.

Example Claim: A ”Maintenance” claim (06/01/2011 – 06/30/2011) already

exists for the service dates.

Long Message The service dates cannot overlap the service dates of another IV-E

Claim for the same “IV-E Service Type.”

Parameters


@ClmStartDt = C.CLM_SVC_START_DT

@ClmEndDt = C.CLM_SVC_END_DT



Proofing Messages

Page 114 of 139

Error Condition


The IV-E Service Type is Maintenance, Rule 4 Placing Agency's

Administrative Fee, Basic Maintenance or Difficulty of Care

(DOC)

ValidIV-EServiceType and IVE_SVC_TYPE_CD in

(‘A’,’D’,’E’,’F’)


20)”


Another claim with the same IV-E Service Type exists anytime

during the service dates

(select C.IVE_ABSTRACT_CLAIM_ID,

C.CLM_SVC_START_DT. C.CLM_SVC_END_DT







and (C.IVE_SVC_TYPE_CD = IVE_SVC_TYPE_CD

or (C.IVE_SVC_TYPE_CD = ‘A’ and

IVE_SVC_TYPE_CD = ‘E’)

or (C.IVE_SVC_TYPE_CD = ‘E’ and

IVE_SVC_TYPE_CD = ‘A’))

and CLM_AMT > 0

and rownum = 1

and NotBackedOut

) returns a row



Proofing Messages

Page 115 of 139

1.1.2.84 #1244 – EFC-SIL – Another Claim Already Exists


Description EFC-SIL – Another Claim Already Exists

Rule For EFC-SIL Payments, the service dates for IV-E Service Type “A”

(Maintenance) cannot overlap the service dates of another

Maintenance Claim for another Provider Type.


To


Claims | selected Claim Navigation Hint Claim

Short Message A ”[@IVESvcType]” claim ([@ClmStartDt] - [@ClmEndDt]) already

exists with “Provider Type” of “[@ProvType].”

Example Claim: A ”Maintenance” claim (06/01/2011 – 06/30/2011) already

exists with “Provider Type” of “Family.”

Long Message

The service dates of an EFC-SIL “Maintenance” claim cannot overlap

the service dates of another “Maintenance” claim for a “Family” or

“Group” Provider Type.

Parameters


@ClmStartDt = C.CLM_SVC_START_DT

@ClmEndDt = C.CLM_SVC_END_DT

@ProvType = CODE.DESCRIPTION for C.PROVIDER_TYPE_CD

Error Condition



ValidIV-EServiceType and IVE_SVC_TYPE_CD = ‘A’



Another claim with the same IV-E Service Type exists anytime

during the service dates

(select C.IVE_ABSTRACT_CLAIM_ID, C.PROVIDER_TYPE_CD,

C.CLM_SVC_START_DT. C.CLM_SVC_END_DT








and RULE_CD <> ‘SIL’

and CLM_AMT > 0

and rownum = 1

and NotBackedOut

) returns a row



Proofing Messages

Page 116 of 139

1.1.2.85 #1245 –Discharge Date is not Reimbursable


Description Discharge Date is not Reimbursable

Rule The Continuous Placement “Discharge Date” cannot be claimed.


To selected Payment


Short Message The Continuous Placement “Discharge Date” ([@EndDt]) cannot be

claimed.

Example The Continuous Placement “Discharge Date” (06/24/2011) cannot be

claimed.

Long Message Only the Continuous Placement "Start Date" is eligible for IV-E

reimbursement.

Parameters @EndDt = CONTPLCMT_END_DT

Error Condition




PYMT_SVC_END_DT

The Payment’s “Service End Date” = the Continuous Placement

“Discharge Date”

PYMT_SVC_END_DT = trunc(CONTPLCMT_END_DT)



Proofing Messages

Page 117 of 139

1.1.2.86 #1246 – Units do not Match the Days of Service


Description Units do not Match the Days of Service

Rule The number of units must correspond to the service dates. Exclude

the Payment if the Units are not equal to the number of days of

service.


To selected Payment


Short Message The “Units” ([@Units]) must match the number of days of service

([@DaysSvc]).

Example Payment: The “Units” (30) must match the number of day of service

(31).

Long Message Verify the dates of service are accurate and correct the service dates or

the "Units" to claim IV-E.

Parameters @Units = PYMT_UNITS

@DaysSvc = PYMT_SVC_END_DT – PYMT_SVC_START_DT + 1

Error Condition


The IV-E Service Type is Maintenance, Rule 4 Placing Agency’s

Administrative Fee, Basic Maintenance, Difficulty of Care (DOC),

or Adjustment of DOC


and IVE_SVC_TYPE_CD in (‘A’, ‘D’, ‘E’, ‘F’, ‘G’)


20)”


The Unit Type is valid for IV-E

UNIT_TYPE_CD in (‘07’, ‘08’,’31’)

The number of units is not equal the number of days of service

PYMT_SVC_END_DT – PYMT_SVC_START_DT + 1 <>

PYMT_UNITS



Proofing Messages

Page 118 of 139

1.1.2.87 #1247 – Service Dates more than 13 Months after Warrant

/ Eff Date


Description Service Dates more than 13 Months after Warrant / Eff Date

Rule The “Warrant / Eff Date” can be up to 13 months before the “Service

End Date” for EFC-SIL Maintenance, Child Care and Educational

Transportation.


To selected Payment


Short Message The “Service End Date” is more than 13 months after the “Warrant / Eff

Date.”

Example Payment: The “Service End Date” is more than 13 months after the

“Warrant / Eff Date.”

Long Message

The “Warrant / Eff Date” can be up to 13 months before the “Service

End Date” for EFC-SIL Maintenance, Child Care and Educational

Transportation.

Parameters None

Error Condition


A IV-E Service Type can be assigned



and the IV-E Service Type is Maintenance or the IV-E Service

Type is Child Care or Educational Transportation

(ServiceCode = ‘188’ and IVE_SVC_TYPE_CD = ‘A’)

or IVE_SVC_TYPE_CD in (‘C’,’T’)

The “Service End Date” of more than 13 months after the

“Warrant / Eff Date”

PYMT_SVC_END_DT > add_months(PYMT_DT,13)



Proofing Messages

Page 119 of 139

1.1.2.88 #1250 – Exclusion Exists

Checkbox Label Exclusions Message # 1250

Description Exclusion Exists

Rule Create claims only for payments where an Exclusion for the Title IV-E

Abstract Report does not exist

(Added in v13.3, PR#13-0531-1514-17)


To selected Payment


Short Message An Exclusion for the Title IV-E Abstract Report exists.

Example Payment: An Exclusion for the Title IV-E Abstract Report exists.

Long Message IV-E Claims are not created when an Exclusion record for the Title IV-E

Abstract Report exists for the payment.

Parameters None

Error Condition


The Person has a PMI # – display the message regardless of

whether the client has a PMI

The Person has an Actual DOB


An Exclusion for the Title IV-E Abstract Report does not exist

for the Payment

Display when an Exclusion for the Title IV-E Abstract Report exists for

the Payment

exists (select '*'






Proofing Messages

Page 120 of 139

1.2 Claimed Payment Proofing

The following figure shows an example of the Claimed Payment Proofing screen for a Title

IV-E Abstract Report.

Figure 1-2: Claimed Payment Proofing Screen



Proofing Messages

Page 121 of 139

1.2.1 Standard Criteria for Claimed Payment Proofing

Listed below is the standard criteria for Claimed Payment Proofing. Claimed Payment

Proofing displays for payments that meet these criteria along with the error conditions

defined for the proofing message. A payment can have multiple proofing messages.





"Warrant / Eff Date" is between the

Report Payment Dates

PYMT_DT between Report Payment Start

Date and Report Period End Date

1.0

"Service Start Date" is >= Report

Service Start Date

PYMT_SVC_START_DT >= Report

Service Start Date

2.0

A IV-E Claim exists for the Payment (select C.IVE_ABSTRACT_CLM_ID

from IVE_ABSTRACT_CLM C


returns a row

3.0

The Person has a PMI # (except for

edits specifically for a claimable record

with no "PMI #" or where specifically

excluded)

PERSON.PMI is not null 4.0

The Person has an Actual DOB (except

for edits specifically for a claimable

record with no "Actual Date of Birth" or

where specifically excluded)

PERSON.BIRTH_DT is not null 5.0


Code Description

1 Payment Request

2 Posted Payment


PYMT_TYPE_CD in (‘1’, ’2’, ’3’) 6.0

The net Claim Amount is > 0 C.CLM_AMT +

(select nvl(sum(C2.CLM_AMT),0)

from IVE_ABSTRACT_CLM C2

where C2.ORIG_IVE_CLM_ID =

C.IVE_ABSTRACT_CLM_ID

) > 0

7.0

An Exclusion for the Title IV-E

Abstract Report does not exist for the

Payment

(select count(*)




) = 0

8.0

Table 1-3: Claimed Payment Proofing Criteria



Proofing Messages

Page 122 of 139

1.2.2 Claimed Payment Proofing Message Summary

The table below shows the checkboxes for Claimed Payment Proofing and the messages

included for each checkbox.

Checkbox

Label

Message

# Description


1018 No PMI #


Continuous

Placement





(Warning)

1124 No Corrections Umbrella or Title IV-E Maintenance

Agreement (Warning)


Court Actions 1100 Court Ordered – No Best Interest Date

1101 Court Ordered Before Best Interest Date

1102 Voluntary – No Best Interest by Day 180

1103 Voluntary – Best Interest after Day 180

1104 Reasonable Efforts is Overdue

DOC 1130 No DOC Assessment

1131 Higher DOC Points Paid

1134 Duplicate DOC Assessments


Extended

Foster Care




1144 EFC-SIL – Invalid Service

1145 EFC-SIL – Invalid Placement Setting

1146 EFC-SIL – Client Under 18



Proofing Messages

Page 123 of 139

Checkbox

Label

Message

# Description

IV-E Eligibility 1150 No MAXIS IV-E Eligibility Information

1151 Not IV-E Eligible – Denied

1152 Not IV-E Eligible - Closed

1153 No IV-E Eligibility for the Cont Placement #

1154 Not IV-E Eligible – Inconclusive

1155 VPA Date Mismatch

1156 Best Interest Date Mismatch

1157 Service Dates before IV-E Eligibility Begins

IV-E

Reimbursability

1160 Not IV-E Reimbursable

IV-E Service

Type

1171 No Maintenance Claim – Additional Cost

1172 No Maintenance Claim – Admin

1173 No Maintenance Claim – Difficulty of Care (DOC)

1174 No Maintenance Claim – Adjustment of DOC

1175 Service Dates Invalid with Maintenance Claim – Additional

Cost

1176 Service Dates Invalid with Maintenance Claim - Admin

1177 Service Dates Invalid with Maintenance Claim – Difficulty of

Care (DOC)

1178 Service Dates Invalid with Maintenance Claim - Adjustment

of DOC

1179 Initial Clothing – Invalid Service Dates

License # / IV-

E Sub Code

1191 No Effective IV-E Provider Rate

1192 Invalid IV-E Sub Code

1193 License Status must be Granted (Warning)

1194 Facility Type not 001, OSH or OT2

1195 License Record does not exist for Bus Org

1196 Service Dates not Valid with License Dates

1197 Invalid Tribe on License



Proofing Messages

Page 124 of 139

Checkbox

Label

Message

# Description



1212 Multiple Placements

1213 Multiple Bus Orgs on Placement History

1214 Placement Bus Org Different than Payment


1216 Local Agency is not the COFR

Placement

Authority



Service Dates 1245 Discharge Date is not Reimbursable

Table 1-4: Claimed Payment Proofing Messages

All Claimed Payment Proofing messages are errors with the exception of messages #1123,

#1124 and #1193, which are warnings in Claimed Payment Proofing, but are errors in

Payment Proofing. Because of this, these warning messages are defined in this section.

See the Section 1.1, “Payment Proofing” for details for messages not defined in this section.



Proofing Messages

Page 125 of 139

1.2.2.1 #1123 – No Title IV-E Maintenance Agreement for

Supervising Tribe


Description No Title IV-E Maintenance Agreement for Supervising Tribe

Rule Exclude the Payment if



A Title IV-E Maintenance Agreement does not exist for the

service dates with the “Supervising” Tribe


To




Placement

Short Message A Title IV-E Maintenance Agreement does not exist for the Supervising

Tribe ([@Tribe]).

Example Continuous Placement: A Title IV-E Maintenance Agreement does not

exist for the Supervising Tribe (Leech Lake Band of Ojibwe).

Long Message

The “Supervising Agency” on the Continuous Placement is “Tribal social

services.” A Title IV-E Maintenance Agreement with the supervising

“Tribe” must be in effect for the service dates. Title IV-E Maintenance

Agreements are entered in the SSIS Administration application under

Tools | County Preferences | Title IV-E.

Parameters See Section 1.1.2.12, “#1123 – No Title IV-E Maintenance Agreement

for Supervising Tribe,” on page 21 in Section 1.1, “Payment Proofing”

for Parameter and Error Condition information. Error Condition



Proofing Messages

Page 126 of 139

1.2.2.2 #1124 – No Corrections Umbrella or Title IV-E Maintenance

Agreement


Description No Corrections Umbrella or Title IV-E Maintenance Agreement

Rule Exclude the Payment if the Supervising Agency = “Corrections” and

neither of the following exist for the service dates:

A Title IV-E Maintenance Agreement with Corrections

A Title IV-E Corrections Umbrella record


To




Placement

Short Message A Corrections Umbrella or Title IV-E Maintenance Agreement for

Corrections does not exist.

Example Continuous Placement: A Corrections Umbrella or Title IV-E

Maintenance Agreement for Corrections does not exist.

Long Message

The “Supervising Agency” on the Continuous Placement is

“Corrections.” A Title IV-E Maintenance Agreement or Corrections

Umbrella must be in effect for the service dates. Title IV-E

Maintenance Agreements and Corrections Umbrellas are entered in the

SSIS Administration application under Tools | County Preferences |

Title IV-E.

Parameters See Section 1.1.2.13, “#1124 – No Corrections Umbrella or Title IV-E

Maintenance Agreement,” on page 2321 in Section 1.1, “Payment

Proofing” for Parameter and Error Condition information. Error Condition

1.2.2.3 #1193 – License Status must be Granted


Description License Status must be Granted

Rule The “Status” of the license must be “Granted”


To



Short Message The “License Status” ([@LicStat]) must be “Granted.”

Example License: The “License Status” (Pending) must be “Granted.”

Long Message The “Status” of the Service Vendor’s “License #” is not “Granted.”

Parameters See Section 1.1.2.54, “#1193 – License Status must be Granted,” on

page 74 in Section 1.1, “Payment Proofing” for Parameter and Error

Condition information. Error Condition



Proofing Messages

Page 127 of 139

1.3 Child Count Proofing

The following figure shows an example of the Child Count Proofing screen for a Title IV-E

Abstract Report.

Figure 1-3: Child Count Proofing Screen



Proofing Messages

Page 128 of 139

1.3.1 Standard Criteria for Child Count Proofing

Listed below is the standard criteria for child count proofing. Child count proofing displays

for payments that meet these criteria along with the error conditions defined for the

proofing message. A payment can have multiple proofing messages.




(Changed in v13.2 to remove standard criteria that a payment is not claimed. Child Counts

are recalculated for the past five quarters, so a claimed payment may no longer be counted

because of a change to the client's information (PR #13-0211-1334-34).


A Maintenance Payment exists

Service Special Cost Code

IV-E

Service

Type

171, 180,

181, 183,

185, 483,

188

Blank A

188 16 - EFC-SIL - Additional

maintenance expenses

A

483 17 – Rule 5 Room &

Board Only

A

180 or

181

11 - Foster Care

Maintenance Only - Basic

E

1.0

"Warrant / Eff Date" is on or before the Report

Period End Date

PYMT_DT <= Report Period End

Date

2.0

The service dates are between the Report

Payment Start Date – 1 month and Report

Period End Date – 1 month

For example,

Report Period = Q1 2011 (1/1/11–3/31/11)

Service dates include 12/1/09–2/28/11


add_months(Report Payment

Start Date,-1) and

add_months(Report Period End

Date,-1)

3.0

"Payment Status" is "Paid" PYMT_STATUS_CD = 'PD' 4.0


Code Description

1 Payment Request

2 Posted Payment


PYMT_TYPE_CD in (‘1’, ’2’, ’3’) 5.0



Proofing Messages

Page 129 of 139


A IV-E Claim does not exist for the Payment (select count(*)


where PAYMENT_ID =

C.PAYMENT_ID

) = 0

6.0

The Net Amount > 0 PAYMENT.PYMT_PAID_AMT +

(select sum(PYMT_PAID_AMT)

from PAYMENT P

where P.ORIG_PAYMENT_ID =

PAYMENT_ID

and P.PYMT_TYPE_CD in

(‘4’,’5’,’6’,’7’,’8’)

and P.PYMT <= Report

Period End Date

) > 0

7.0

A Person is selected on the Payment PAYMENT.PERSON_ID =

PERSON.PERSON_ID

8.0

The Person has an Actual DOB PERSON.BIRTH_DT is not null 9.0

An Exclusion for the Title IV-E Abstract Report

does not exist for the Payment

(select count(*)


where PAYMENT_ID =

X.PAYMENT_ID


) = 0

10.0

Table 1-5: Child Count Proofing Criteria



Proofing Messages

Page 130 of 139

1.3.2 Child Count Proofing Message Summary

The table below shows the checkboxes for Child Count Payment Proofing and the messages

included for each checkbox.

Checkbox

Label

Message

# Description



Continuous

Placement





1124 No Corrections Umbrella or Title IV-E Maintenance Agreement


Child Count

Warnings

1301 ICWA Indicator is Blank


Extended

Foster Care




IV-E Eligibility 1150 No MAXIS IV-E Eligibility Information (Warning)

1151 Not IV-E Eligible – Denied (Warning)

1152 Not IV-E Eligible – Closed (Warning)

1153 No IV-E Eligibility for the Cont Placement # (Warning)

1154 Not IV-E Eligible – Inconclusive (Warning)

1157 Service Dates before IV-E Eligibility Begins (Warning)




Placement

Authority



Table 1-6: Child Count Proofing Messages

All Child Count Proofing messages, except #1301, “ICWA Indicator is Blank,” are also

included in Payment Proofing. Message #1301 is defined in this section. The messages in

the IV-E Eligibility checkbox are warnings in Child Count Proofing, but are errors in Payment

Proofing. Because of this, the warning messages are defined in this section.

See the Section 1.1, “Payment Proofing” for details for messages not defined in this section.



Proofing Messages

Page 131 of 139

1.3.2.1 #1150 – No MAXIS IV-E Eligibility Information


Description No MAXIS IV-E Eligibility information

Rule Count the child only on the Total Children in Placement / Total Indian

Children in Placement lines if a MAXIS IV-E eligibility record does not

exist for the service dates


To



Short Message No IV-E Eligibility information from MAXIS.

Example Warning - Client Eligibility: No IV-E Eligibility information from MAXIS.

Long Message

The client must be IV‑E eligible based on the MAXIS IV‑E eligibility

information to claim IV-E. No IV-E Eligibility information from MAXIS

exists for this child.

Parameters None

Error Condition See Section 1.1.2.28, "#1150 – No MAXIS IV-E Eligibility Information",

on page 43 for Error Condition information.

1.3.2.2 #1151 – Not IV-E Eligible - Denied


Description Not IV-E Eligible - Denied


Children in Placement lines if the MAXIS IV-E eligibility is Denied


To



Short Message IV-E Eligibility for the Continuous Placement has been denied.

Example Warning - Client Eligibility: IV-E Eligibility for the Continuous Placement

has been denied.

Long Message The client must be IV-E eligible based on the MAXIS IV-E Eligibility

information to claim IV-E.

Parameters None

Error Condition See Section 1.1.2.29, “#1151 – Not IV-E Eligible – Denied,” on page 44

in Section 1.1, “Payment Proofing” for Error Condition information.



Proofing Messages

Page 132 of 139

1.3.2.3 #1152 – Not IV-E Eligible - Closed


Description Not IV-E Eligible – Closed


Children in Placement lines if the MAXIS IV-E eligibility is Closed prior

to the service dates.


To



Short Message IV-E Eligibility closed ([@EligEndDt]) prior to the “Service End Date.”

Example Warning - Client Eligibility: IV-E Eligibility closed (04/01/2010) prior to

the “Service End Date.”

Long Message

The client must be IV-E eligible on the service dates based on the

MAXIS IV-E Eligibility information. If IV-E Eligibility closed during the

service dates, you can split the Payment to claim through the IV-E

Eligibility end date.

Parameters @EligEndDt = E.ELIG_END_DT

Error Condition

See Section 1.1.2.30, “#1152 – Not IV-E Eligible – Closed,” starting on

page 45 in Section 1.1, “Payment Proofing” for Error Condition

information.



Proofing Messages

Page 133 of 139

1.3.2.4 #1153 – No IV-E Eligibility for the Cont Placement #


Description No IV-E Eligibility for the Cont Placement #


Children in Placement lines if the “Cont Placement #” on the MAXIS IV-

E Eligibility record and the Continuous Placement in SSIS do not match


To



Short Message No IV-E Eligibility information for the Continuous Placement, “Cont

Placement #” ([@ContPlcmtID]), “Start Date” ([@ContPlcmtStart]).

Example

Warning - Client Eligibility: No IV-E Eligibility information for the

Continuous Placement, “Cont Placement #” (123456789), “Start Date”

(06/11/2011).

Long Message

IV-E Eligibility information from MAXIS exists for this child, either for

another Continuous Placement or the “Cont Placement #” on the MAXIS

record does not match the Continuous Placement in SSIS.

Parameters @ContPlcmtID = CONTPLCMT_ID


Error Condition

See Section 1.1.2.31, “#1153 – No IV-E Eligibility for the Cont

Placement #,” on page 46 in Section 1.1, “Payment Proofing” for Error

Condition information.



Proofing Messages

Page 134 of 139

1.3.2.5 #1154 – Not IV-E Eligible – Inconclusive


Description Not IV-E Eligible – Inconclusive


Children in Placement lines if the MAXIS IV-E eligibility is Inconclusive

Note: Eligibility Test Results are inconclusive when the End Date is

valued and none of the tests failed or a test failed and there is no End

Date.

(Added in v13.2, PR#13-0107-1725-38)


To



Short Message IV-E Eligibility for the Continuous Placement is inconclusive.

Example Warning - Client Eligibility: IV-E Eligibility for the Continuous Placement

is inconclusive.

Long Message IV-E eligibility results could not be determined based on the MAXIS IV-E

Eligibility information. The client must be IV-E eligible to claim IV-E.

Parameters None

Error Condition See Section 1.1.2.32, "#1154 – Not IV-E Eligible – Inconclusive" on

page 47 for Error Condition information.

1.3.2.6 #1157 – Service Dates before IV-E Eligibility Begins


Description Service Dates before IV-E Eligibility Begins


Children in Placement lines if the Payment "Service Start Date" is before

IV-E eligibility starts.

(Added in v13.2, PR#13-0107-1715-16)


To



Short Message The "Service Start Date" is before IV-E Eligibility begins

([@EligBeginDt]).

Example Warning - Client Eligibility: The "Service Start Date" is before IV-E

Eligibility begins (06/23/2012).

Long Message The client must be IV-E eligible on the service dates based on the

MAXIS IV-E Eligibility information to claim IV-E.

Parameters @EligBeginDt = E.ELIG_BEGIN_DT

Error Condition See Section 1.1.2.35, "#1157 – Service Dates before IV-E Eligibility

Begins" on page 50 for Error Condition information.



Proofing Messages

Page 135 of 139

1.3.2.7 #1301 – ICWA Indicator is Blank

Checkbox Label Child Count Warnings Message # 1301

Description ICWA Indicator is Blank

Rule Count the child on ICWA lines only if “Qualifies under ICWA” is Yes


To



Short Message “Qualifies under ICWA” does not have a value.

Example Warning - Client: “Qualifies under ICWA” does not have a value.

Long Message

The child will not be included in the Indian Child counts. A child is only

included in the Indian Child counts when “Qualifies under ICWA” is

“Yes.”

Parameters None

Error Condition


“Qualifies under ICWA” is blank

PERSON.ICWA_IND is null



Proofing Messages

Page 137 of 139

RELATED DOCUMENTS

Following is a list of documents related to this software specification.

Document Information

SS Title IV-E Abstract Report.docm Information about the user interface and

design of the Title IV-E Abstract Report

SS Title IV-E Abstract Report – Detail

Requirements.docm

Detailed requirements for the Title IV-E

Abstract Report

SSIS Message Infrastructure.docx Information about the framework for

proofing



Proofing Messages

Page 139 of 139

End of Title IV-E Abstract Report – Proofing Messages

SSIS Software Specification - MinnesotaSSIS Software Specification Title IV-E Abstract Report – Proofing Messages Designer: Theresa Hill Project Manager: Kate Stolpman Last Updated:

Documents