Compliance IL444-3455
Validation Checks by Instafill.ai
1
Required Parent/Guardian Identity Fields Completed
Validate that the applicant’s first name, last name, date of birth, and sex selection (male/female) are provided, and that the parent/guardian name appears where required (top of each page in the form set). These fields establish the primary case identity and are needed for eligibility determination and record matching. If missing or illegible/blank, the submission should be flagged as incomplete and returned for correction.
2
Address Completeness and Illinois Address Format Validation
Check that the home address includes street, city, state, and ZIP code, and that the state is a valid two-letter code (typically IL for Illinois). Validate ZIP code format (5 digits or ZIP+4) and ensure apartment number is present when indicated. Address accuracy is critical for notices, CCR&R routing, and cross-database verification. If invalid, the system should reject the address and require correction before processing.
3
Phone Number and Email Format Validation
Validate that at least one reachable phone number is provided (home, mobile, or alternate) and that all phone numbers follow a valid US format (10 digits, optional extension). If an email address is provided, validate it against standard email syntax rules. Reliable contact information is necessary to resolve missing documentation and prevent processing delays. If validation fails, prompt the applicant to correct the format or provide an alternate contact method.
4
Optional SSN Field Rules (Parent/Children) and Placeholder Handling
If a Social Security Number is entered for a parent or child, validate it is exactly 9 digits (or formatted as XXX-XX-XXXX) and not an obviously invalid value (e.g., all zeros). If not provided, ensure the field is blank or explicitly marked as 'N/A' per form instructions, and do not treat it as a required field. This prevents data-entry errors while respecting that SSNs are optional for eligibility. If an SSN is partially entered or malformed, the submission should be flagged for correction to avoid mismatches in verification.
5
Other Benefits Case Number and County Field Consistency
When a TANF/SNAP/Medical Assistance case number is provided, validate it matches expected numeric/alpha format and that a county is selected/entered. County and case number are used for cross-program verification and routing. If a case number is present but county is missing (or vice versa where required by workflow), the system should request completion or confirm the applicant is not applying with an existing case.
6
Work Information Completeness Per Job (Applicant and Other Parent)
If the applicant (or other parent) indicates they are working or lists a number of jobs greater than zero, require completion of employer name, job title, employer address, start date, pay amount, pay frequency, and typical hours/days per week for each job. Also require at least one work schedule example (FROM/TO with days) or a clear explanation that the schedule varies. This information drives eligibility and authorized care hours. If any required job fields are missing for a declared job, the application should be marked incomplete.
7
Employment Pay Rate and Pay Frequency Logical Validation
Validate that exactly one pay basis is selected (per year/per month/per hour) and that the numeric amount is positive and within reasonable bounds (e.g., not negative, not zero when working is claimed). Validate that a pay frequency is selected (weekly, every two weeks, twice per month, or 'other' with explanation). Correct pay structure is necessary to compute monthly income consistently. If multiple bases are selected or none are selected, the system should require correction before income calculations proceed.
8
Date Field Format and Chronology Validation (DOB, Job Start, Term Dates, Provider Start)
Validate all dates are in MM/DD/YYYY format and represent real calendar dates. Enforce logical chronology: job start dates cannot be in the future (unless explicitly allowed by policy), school term start must be on/before term end, and provider care start date should not be unreasonably far in the past relative to application submission. Date accuracy is essential for eligibility windows and verification. If dates are invalid or inconsistent, the system should block submission or route to exception review.
9
School/Training Section Conditional Requirements
If the applicant (or other parent) answers 'Yes' to attending school/training/TANF-required activity, require the education/training type selection, school/program name, address/phone (if captured), term start/end dates, and a completed school schedule (FROM/TO with days) or documented explanation of variability. If 'No' is selected, ensure school fields are blank or 'N/A' to avoid contradictory data. This ensures the activity requirement for eligibility is properly documented. If conditional fields are missing, the application should be returned as incomplete.
10
Other Parent/Stepparent Household Presence and Activity Consistency
If the applicant indicates the other parent/stepparent lives in the home, require completion of that person’s identity fields (name, DOB, phone) and their work and/or school/training status details. If they are neither working nor in school/training, require a non-empty explanation of why they cannot care for the children. Program rules require both adults in a two-parent household to meet activity requirements or provide an acceptable exception. If the section is incomplete or contradictory, the case should be flagged for follow-up and may be denied if not resolved.
11
Family Size and Household Member Listing Reconciliation
Validate that the declared 'My family size' equals the count of individuals listed across the applicant, other parent (if in home), children, and any additional household members included in family size. Ensure no duplicate persons are listed and that each listed person has required attributes (name, DOB, relationship, sex, ethnic origin where required). Family size directly affects income eligibility thresholds and copayment calculations. If counts do not reconcile, the system should require correction or route to manual review.
12
Child Eligibility Age and Special Condition Validation
Validate each child’s date of birth and compute age; flag children age 13 or older for additional required documentation indicators (court supervision or medical documentation of incapacity) per program rules. Also ensure each child needing assistance is explicitly listed in the 'I need child care assistance for the following children' section. This prevents authorizing care for ineligible ages without required exceptions. If an over-age child is included without exception documentation, the application should be flagged and not approved until resolved.
13
Ethnic Origin Coding and Multi-Code Format Validation
Validate that each child has an ethnic origin entry using only the allowed codes (1–6) and that multi-code entries follow the specified format (e.g., '3-1', '3-2', '3-5' when Hispanic is selected along with race). This is required for federal reporting and data quality. If codes are missing or outside the allowed set, the system should prompt correction rather than silently accepting invalid values.
14
Child Care Provider Identification and Tax ID Requirement
Require a provider name and either an IDHS Provider Registration Number or a valid tax identifier (SSN/FEIN/Gov’t unit code) as indicated by the provider type. Validate SSN/FEIN formats (SSN 9 digits; FEIN 9 digits, often formatted XX-XXXXXXX) and ensure only one identifier type is selected/filled unless policy allows multiple. Provider identification is mandatory for payment and W-9/Comptroller setup. If missing or invalid, the application cannot proceed to authorization and should be returned.
15
Provider Type vs Licensing Fields Consistency
Validate that the selected provider type (licensed center/home/group home, license-exempt relative/non-relative, etc.) is consistent with the licensing information provided. If a licensed type is selected, require license number, capacity, expiration date, and hours of operation; if license-exempt is selected, ensure licensing fields are blank and that required household member listing is completed when care is in provider’s home. This prevents misclassification that could bypass required checks or apply wrong rate rules. If inconsistent, route to correction or manual review.
16
Child Care Schedule Integrity and School-Time Exclusion
For each child listed under a provider, validate that FROM/TO times are present for any day care is requested, that times are in a valid AM/PM format, and that FROM is earlier than TO. If the child attends school, require school hours and validate that requested child care hours do not overlap with school hours (per certification that care does not include school time). Schedule accuracy is essential for determining authorized hours and preventing improper payments. If overlaps or invalid time ranges are detected, the system should flag the schedule and require correction.
17
Monthly Income Totals and Non-Negative Amount Validation
Validate that all income entries are numeric currency amounts (or 'N/A' where allowed), non-negative, and that the subtotal equals the sum of lines 1–6. Validate that child support paid is entered as a non-negative amount and is subtracted correctly from the subtotal to produce the total monthly income, and that housing cash assistance is captured separately and not included in total family income. Accurate income math is central to eligibility and copayment determination. If calculations do not reconcile, the system should recalculate and/or require applicant confirmation before submission.
18
Required Signatures and Dates Present (Parent and Provider)
Require the parent/guardian signature and date in Section 8 and the child care provider signature and date in Section 7; if an other parent signature line is present and the other parent is part of the household/case, require their signature per policy/workflow. Validate signature dates are present and in valid date format. Signatures are legal attestations and authorizations for verification and payment processing. If missing, the application should be rejected as incomplete and not processed.