Error Codes 1-25
Error 1
Center License is Missing
The center does not have a license on-file in the Manage Center Information License/Schedule tab.
Error 2
Meals Were Claimed on Dates that Fall Before this Center's CACFP Original Start Date (Or Date is Missing)
The center claimed meals on a date that is before the date entered in the Original Start Date box in the Manage Center Information General tab, or this box is blank.
Error 3
Meal Claimed Before Center's CACFP Allowed Start Date
The center claimed a meal before the date entered in the Allowed Start Date box in the Manage Center Information General tab. Policy C.4 controls whether KidKare checks this date and whether the meal is disallowed or warned.
Error 4
Meal Claimed Before Center's CACFP Current Start Date
The center claimed a meal before the date entered in the Current Start Date box in the Manage Center Information General tab. Policy C.5 controls whether KidKare checks this date and whether the meal is disallowed or warned.
Error 5
Meals Were Claimed on Dates that Fell After This Center's Current End Date
The center claimed a meal after the date entered in the Current End Date box in the Manage Center Information General tab. Policy C.6 controls whether KidKare checks this date and whether the meal is disallowed or warned.
Error 6
Meals Were Claimed on Dates that Fall Before This Center's License Start Date
The center claimed a meal before the date entered in the License Start Date box in the Manage Center Information License/Schedule tab. Any meals claimed before this date are always disallowed, unless you do not enter a date in the License Start Date box.
Error 7
Meals Were Claimed on Dates that Fall After This Center's License End Date
The center claimed a meal after the date entered in the License End Date box in the Manage Center Information License/Schedule tab. Policy C.3 controls whether KidKare checks this date and whether meals or disallowed, warned, or warned for several months before being disallowed.
Error 8
Meals Were Claimed on Dates that Fall After the Center's Removal/Withdrawal Date
The center claimed a meal after the date entered in the Withdrawal Date box when you withdrew them from your agency. Meals claimed after this date are automatically disallowed.
Error 10
Meals Claimed on Dates After Center's Fire Inspection Certification Expired
The center claimed a meal after the date entered in the Fire box in the Manage Center Information General tab. This error is also generated if you checked the Fire box and did not provide an expiration date.
Error 11
Meals Claimed on Dates After Center's Health Inspection Certification Expired
The center claimed a meal after the date entered in the Health box in the Manage Center Information General tab. This error is also generated if you checked the Health box and did no provide an expiration date.
Error 12
Meals Claimed on Dates After Center's Sanitation Inspection Certification Expired
The center claimed a meal after the date entered in the Sanitation box in the Manage Center Information General tab. This error is also generated if you checked the Sanitation box and did not provide a date.
Error 13
Center is not Approved to Serve Meals on a Day of the Week When Meals Were Served
The center claimed a meal for a day of the week for which they are not approved, according to your selections in the Manage Center Information License/Schedule window. Policy C.1 controls whether these meals are warned or disallowed.
Error 14
Center is not Approved to Offer a Particular Meal that was Served
The center claimed a meal for which they are not approved, according to your selections in the Manage Center Information License/Schedule window. Policy C.2 controls whether these meals are warned or disallowed.
Error 15
A Menu was Recorded, but no Children were Recorded in Attendance
This error is generated as a warning message when menus are planned, but no meal counts are marked for the planned menus.
Note: This error also displays on the Center Error report, even though it is only a warning. This is to highlight any potential data entry errors for the center. For example, they may have forgot to record attendance.
Error 16
No Foods Were Served but Child(ren) Were in Attendance for the Given Meal(s) for the Listed Age Group
This error disallows children when menus are recorded, assuming that menu edit checks are not skipped per Policy M.02. Menus must be recorded specific to the child's age group, so the disallowance may apply to one age group and not others.
Error 17
The Food Cannot be Served to Children of Given Age
This error disallows meals with bad foods recorded, assuming menu edit checks are not skipped per Policy M.02. In most cases, unapproved foods cannot be selected when setting up menus, but if a food was previously approved and then changed to unapproved, those menus can theoretically get reused, and the meal would receive this error.
For more information about managing foods, see Food Tool.
Error 18
The Food is Not Recommended for Children of Given Age
This warning is generated if a center serves a food that is allowed but is set to Warn, assuming menu edit checks aren't skipped per Policy M.02. For more information about managing foods, see Food Tool.
Error 19
The Food Cannot be Served to Children of that Age Group at the Given Meal Type
This error is generated when a center serves a food at a meal for which the food is not approved, assuming menu edit checks aren't skipped per Policy M.02. For example, if a center serves potatoes at Breakfast, but potatoes are not approved for Breakfast, this error displays on the OER. In most cases, centers cannot select foods at meals for which they aren't approved, but if a food was previously approved and then changed to unapproved, those meals can be reused, and this error would display.
For more information about managing foods, see Food Tool.
Error 20
The Food is Not Approved as Given Meal Component Type at Non-Infant Meal
This error is generated when a food is marked but is not approved, assuming menu edit checks aren't skipped per Policy M.02. In most cases, centers cannot select unapproved foods when setting up menus, but if a food was previously approved and then changed to unapproved, those menus can theoretically get reused and the meal would receive this error.
For more information about managing foods, see Food Tool.
Error 21
A Meal Component was Missing from the Non-Infant Meal
This error is generated when Breakfast, Lunch, or Dinner is missing one or more components, assuming menu edit checks aren't skipped per Policy M.02.
Error 22
At Least Two Valid Foods Must be Served at Snacks
This error is generated when a snack does not have at least two valid components, assuming menu edit checks aren't skipped per Policy M.02.
Error 23
Snacks Cannot Include only Milk and Juice, Another Food Must be Present
This error is generated when a snack only has a milk and a juice, assuming menu edit checks aren't skipped per Policy M.02.
Error 24
The Same Food was Served Twice in the Same Meal
This error is generated if a center serves the same item twice in one meal, assuming menu edit checks aren't skipped per Policy M.02. This is common when serving the same fruit/vegetable item twice, or when serving something like baked beans as a meat and as a fruit/vegetable.
Error Codes 26-50
Error 27
Two Juices Were Served at the Meal(s)
This error is generated if two juices are served as the fruit/vegetable/juice component at Lunch/Dinner, assuming menu edit checks aren't skipped per Policy M.02.
Error 28
A Juice was Served at the Given Meal(s)
This error is generated if a juice is served at Lunch or Dinner, assuming menu edit checks aren't skipped per Policy M.02. This error is also subject to Policy M.03.
Error 29
An "Other" Food was Served in the Given Meal. Verify Nutritional Components
This error generates a warning if a center serves a food described in Other food, such as Other Bread, assuming menu edit checks aren't skipped per Policy M.02. This error is also subject to Policy M.05b.
Error 33
Snacks Served to 8-11 Month-Old Infants Require Either Juice or Formula/Breast Milk to be Served
This error is generated if a center serves an infant snack without the required components, assuming menu edit checks aren't skipped per Policy M.02.
Error 38
A Meal Component was Missing from the Infant Meal
This error is generated when Breakfast, Lunch, or Dinner is missing one or more components, assuming menu edit checks aren't skipped per Policy M.02.
Error 39
A Dr's Statement has not Been Received for the Special Diet Child(ren) Served During the Month
This error is generated when a child is marked as having special diet in the Manage Child Information Child tab, but the Diet Statement on File box is not checked. This error is subject to Policy D.05.
Error 40
Special Diet Statement on File for Given Child(ren) is Expired
This error is generated when a child is marked as having a special diet in the Manage Child Information Child tab, but the child is claimed on dates that fall after the date entered in the Diet Expiration Date box (in the same tab) or if the Diet Expiration Date box is blank. This error is subject to Policy D.06.
Error 41
The Child was not Yet Enrolled as of Meal Date
This error is generated if a child is claimed on dates that come before the Original Enrollment Form Date/First Day in Care date (or the first of the month, depending on policy). This error is subject to Policy D.20.
This edit check is skipped for At-Risk centers and the At-Risk portion of a claim for regular centers that also operate At-Risk programs.
Error 42
The Child is Not Yet Born as of Meal Date(s)
This error is generated if a child's birth date falls after a meal date. This typically would only happen if data is changed for a child after the child has been claimed.
Error 43
The Child was Claimed After the Child was Withdrawn from Care
This error is generated if a child is claimed after the date on which they were withdrawn from care. When withdrawing children, you enter an effective date, which is the last date a child can be claimed (if Policy F.6 is set to Enrolled and Policy F.6c is set to N or Not Set).
Children stay in the system when being withdrawn. Instead of being removed, they are changed to Withdrawn status. This error is generated for all non-At-Risk meals if a child is claimed after the child's withdrawal effective date. This edit check is skipped for At-Risk-only centers and emergency shelters.
Error 44
A Pending Child was Claimed — No Signed Enrollment is on File
This error is generated when a center claims a pending child. Pending children are disallowed by default. These are children who were enrolled by centers, but who have not yet been activated (by the sponsor or by the center, subject to Policy F.2b). If you set Policy D.19 to Yes, this error does not generate for pending children unless Policy F.4 is also set to Yes. If this is the case, the child is disallowed by Error 62.
This edit check is skipped for At-Risk meals for dual-licensed centers.
Error 45
The Child is Older than the Center's License Allows
This error is generated if the center claims a child who is over the age of 13 as of the claimed date. Migrant workers' children and children marked as special needs are exempt from this requirement. Also, children in At-Risk programs are allowed until they turn 18 as of the beginning of the school year (so they could be claimed at 19 in some cases).
Error 46
The Special Needs Child is Older than the State's Max Allowable Age for Special Needs Children on the Given Meal Dates
This error is generated if a special needs child is older than the state-defined policy for maximum age. There is no limit by default, but some states restrict participation to those under 18.
Error 47
Special Needs Child was Claimed, but Documentation is not On-File
This error is generated if a special needs child is claimed and the child is over the age of 13. This error is subject to Policy D.07 if the Special Needs Statement on File box is not checked in the Manage Child Information Child tab.
Error 48
The Migrant Child is Over 15 Years of Age
This error is generated if a center claims a migrant worker's child who is over the age of 15 as of the claimed date.
This edit check is skipped for At-Risk centers/the At-Risk portion of a claim for regular centers that also operate At-Risk programs.
Error 49
A Child was Served After the Child's Enrollment Expiration Date was Reached
This error is generated if a child is claimed after the enrollment expiration date or after the current expiration date, subject to Policy D.01. The child is also excluded from counts if Policy F.6 is set to Enrolled or if Policy F.6c is set to N.
This edit check is skipped for At-Risk centers/the At-Risk portion of a claim for regular centers that also operate At-Risk programs. The Enrollment Expiration Date and Current Enrollment Date values are set in the Manage Child Information Child tab, subject to Policies D.01a - D.01d. If Use History is enabled, the Enrollment Expiration Gap and Gap Effective Date values are used.
Error 50
School Aged Child Served a Meal when Child Should Have Been in School
This error is generated if a child is determined to be school-aged and is served an AM Snack or Lunch on a weekday, subject to Policy D.02. This edit check is skipped if you indicate that the child is out of school for that day (check the Sick or Sch Out box in the Record Daily Attendance + Meal Counts window, or use the Manage School Calendar). Using the Manage School Year for At Risk calendar has no impact on this edit check.
Each state has its own logic for determining what defines a school-aged child. For example, this could be children five (5) years of age and older as of the date of the meal. KidKare has been configured with rules specific to your state(s). Typically, but not always, you can also overrule this setting by designating a child as School Aged (and sometimes as participating in Kindergarten) via the Type/Level drop-down menu in the Manage Child Information Child tab.
Error Codes 51-73
Error 51
Child Served More than 2 Meals & a Snack or 2 Snacks & a Meal
This error is generated if a child is served more meals/snacks than is allowed in a given day. KidKare disallows snacks before a meal, and it disallows Breakfast before Lunch or Dinner to maximize the amount of money received.
Error 52
Meal Over Capacity
This error is generated if more children are claimed at a meal than are allowed based on the Cap value recorded in the Manage Center Information License/Schedule tab. It disallows children in excess of capacity unless you check the Waiver box in the License/Schedule tab. If this box is checked, this is only a warning.
Error 53
For-Profit Center Does not Have at Least 25% Free or Reduced
Any center that is not specifically designated with a profit status of Non-Profit (set in the Manage Center Information General tab) is subjected to this edit check. When determining which children factor into analysis, the system uses the same rules as to whether a child is participating. The relevant policies include:
-
F.4
-
F.6
-
F.6b
-
F.7
-
D.20
-
D.19
-
D.01
Policies F.5 and F.7b can also play a role.
This edit check is skipped for At-Risk-only centers and emergency centers.
Error 54
Child Birth Date is Missing
This error is generated for any child who does not have a date of birth on file.
Error 55
No Blended Rate is on File for This Center
If Policy F.1 uses a blended rate (i.e., not Actuals), the system requires you to have calculated blended rates at least one time before processing the claim. This can happen automatically if you check the Calculate Blended Rates While Processing box in the Process Claims window. This can also happen if you use the Calculate Blended Rates function.
If neither has ever been done for a center, the system does not know what rates to apply to the claim, and this error is generated.
Error 56
Child Enrollment Date is Missing
This error is generated for any child who is missing an Original Enrollment Form Date/First Day in Care date in the Manage Child Information General tab.
Error 58
A Child was Claimed at a Meal that is not Approved on the Child's Enrollment Form/File
This error is generated for children claimed for a meal that isn't checked in the Manage Child Information Child tab, subject to Policy D.04.
This edit check is skipped for At-Risk only centers, emergency shelters, and At-Risk meals for children enrolled in dual-licensed centers.
Error 59
A Child was Claimed on a Day of Week that is not Approved on the Child's Enrollment Form/File
This error is generated for children claimed for a day that isn't checked in the Manage Child Information Child tab, subject to Policy D.03.
This edit check is skipped for At-Risk only centers, emergency shelters, and At-Risk meals for children enrolled in dual-licensed centers.
Error 60
Quantity of Food Prepared was not Recorded with the Menu
The system can be configured to allow users to record actual quantities prepared/offered at any given meal service via Policy D.01. This error is generated for any meal where a food doesn't have prepared/offered quantities recorded, subject to Policies M.01b and/or M.01c. Note that this error does not indicate any kind of adequate value has been recorded for these quantities, only that these quantities were not recorded at all. This edit check is skipped if Policy M.02 is set to Y.
Error 61
No Receipts are on File for Center This Month
This error is generated as a warning message only to remind you to enter receipts (if it is part of your process). This warning also displays on the Center Error report by default. The reason for this is to remind the center in case they forgot to send in receipts.
Error 62
Child is Missing an F/R/P Application
If Policy F.4 is set to Yes, this error is generated for children who do not have a F/R/P Reimbursement Level specified in the Manage Child Information Oversight tab. If Policy F.4 is not set to Yes, these children are assumed to be at Paid status.
This edit check is skipped for At-Risk-only centers, emergency shelters, and At-Risk meals for children enrolled in dual-licensed centers, as these children are always reimbursed at the Free level.
Error 63
Block Claim Detected
This error is generated if a block claim pattern is identified in the claim. A block claim is any claim where the same number of children are served any given meal or snack for 15 consecutively claimed days. When block claims are detected, sponsoring organizations/back offices must perform a site visit within 60 days to verify that information submitted for the center is accurate.
Error 64
Meal Disallowed by Monitor
This error is generated for any meals claimed within a range of meals disallowed by the Monitor during a a center review.
Error 65
Count of Children Served in Review File is Different than Count as Recorded by Center
When you record a review in KidKare, you document the number of children served at the meal being reviewed. This error can be generated if this count is different than the count of children as determined when comparing the totals from Record Daily Attendance + Meal Counts. It is always a warning if the monitor sees more children than were recorded by the center.
It can disallow or warn children claimed in excess of the monitor's count, as determined by Policy R.2.
Error 66
Foods Seen by Monitor were Different than Foods Recorded by Center
When you record a review in KidKare, you can document what foods the monitor saw were offered by the center. If these foods are different than the foods found in Record Menus, this error can be generated as a disallowance or a warning, subject to Policy R.3.
This edit check is not performed if no information is recorded in the Review or if Policy M.02 is set to Y.
Error 67
Child not Participating in CACFP has been Removed from Claim Totals
You can enroll children who are specifically designated as not participating in the CACFP. Policy D.10 will enable the Participates box in the Manage Child Information Oversight tab. Children who do not have this box checked will specifically be excluded from claim totals, and, unless Policy D.10b is set to Yes, these children are also excluded from any FRP participation counts/blended rates.
This edit check is skipped for At-Risk-only centers and the At-Risk potion of a claim for regular centers that operate At-Risk programs (and these children are reimbursed).
Error 68
School Aged Child Served Breakfast without Documentation
This error is generated if a school-aged child is served Breakfast and does not have a check in the School Aged Documentation box in the Manage Child Information Oversight tab. This is subject to state policies (some states require special documentation for school aged children who are served breakfast) and Policy D.18.
Error 69
Child Claimed after IEF Expired. Child Reimbursed as Paid, Regardless of Classification
You can configure KidKare to record an Income Eligibility Expiration Date that is distinct from the enrollment form. Normally, this isn't necessary, as the enrollment and income eligibility forms are received/updated simultaneously. However, if you need to record distinct dates, you can do so via Policy F.8. This will enable an IEF Expiration date box in the Manage Child Information Oversight tab.
If a child is claimed in a month in which this date expires (unless the date expires on the last day of the month), that entire month and any month thereafter, the child is treated as Paid, regardless of what FRP Reimbursement Level the child has.
This may be changed subject to update guidance from the USDA, such as that the child keeps their existing FRP Reimbursement Level for the month in which the IEF expires and reverts to Paid only in subsequent months.
This edit check is skipped for At-Risk-only centers or the At-Risk portion of a claim for regular centers that also operate At-Risk programs, as all At-Risk children are classified as Free.
This warning also displays on the Center Error report by default. This is to remind centers to get new income eligibility forms.
Error 70
Child's In/Out Times Indicate Child Not Present at Meal
This error is generated if a child's In/Out times don't cover the time of meal service, subject to Policy L.4. For example, a Breakfast may be scheduled for 8AM - 9AM, but the child does not arrive until 11:00AM and is marked at Breakfast. In/Out time data is entered via the Record Daily Attendance + Meal counts function. If the Skip box is checked for the child, this edit check is skipped.
This error can sometimes also be generated when there is bad meal time data in the Manage Center Information License/Schedule tab. For example, lunch times starting at 11:30PM or ending at 12:30AM can generate erroneous messages on the OER.
Error 71
A Meal was Claimed for a Meal Missing a Start/End Time Pair in the Center's File
This error is generated any time a meal doesn't have a properly defined starting and ending time in the Manage Center Information License/Schedule tab, subject to Policy L.4.
Error 72
Child's In/Out Times were Missing or Incomplete for the Day
This error is generated if a child is noted as In, but does not have an Out time (or vice versa) recorded in the Record Daily Attendance + Meal Counts window, subject to Policy L.4. If the Skip box is checked for the child, this edit check is skipped.
Error 73
Child wasn't Claimed for a Meal, but In/Out Times Show Child was Present During Meal Service
If Policy L.4 is set to Yes, this error will list any child not marked as served at a meal, but who should have been, based on the child's In/Out times as entered for the day. For example, if a child has an In/Out pair of 7:00AM - 4:00PM, Breakfast is noted as being served from 8:00AM - 9:00AM, and the child isn't marked as present in the Record Daily Attendance + Meal Counts window, the child is listed here. This error is a warning only, since it indicates possible accidental under-counting.
This warning is listed on the Center Error report by default. This is to highlight any potential data entry errors to the center.
Error Codes 74-100
Errors 74-76, 80, 84-86, & 90
Meal Over Age Group Capacity
Some states require age group-specific capacity checking. If your state does require this, additional capacity fields display in the Manage Center Information License/Schedule tab. For example, you may have an Inf, Tod, Pre, or Sch field to record specific capacity values.
When recording age group-specific capacities, the system allows you to designate that groups can be combined for capacity purposes by including a negative sign for the capacity value. For example, a license may indicate that a total of 20 infants and toddlers and 30 preschoolers and school-age children can be recorded, for a total of 50 children overall. You would document this as follows:
|
Inf
|
Tod
|
Pre
|
Sch
|
Cap
|
|
20
|
20
|
30
|
30
|
50
|
Error 77
The Child was Claimed After Previous Enrollment Expired and Before New Enrollment Became Effective
The process of using historic data, controlled by Policy D.22, makes it possible for agencies to track a gap in enrollment periods, where one year's enrollment form expires and a month passes before a new one is received. This gap is visible by accessing the Manage Child Information window and selecting the relevant historic claim month. The Old Dates section displays, as does a value for the old enrollment's Expiration. Compare this to the new Current Enrollment Form date.
This error is generated for any dates claimed in between those two values.
Error 78
Quantity of Food Prepared was Less Than Quantity Required
This error is controlled by Policy M.01d (assuming Policy M.02 is set to Y) and only works properly if users are allowed to record actual quantities offered/prepared is less than the value required as computed by KidKare. This error is generated if the value users record in Record Menus for actual quantities offered/prepared is less than the value required as computed by KidKare.
To compare the two values, print the Menu Production Record and compare the Quantity Needed Per Actual Attendance field with the Actual Qty Prepared field. The Actual Qty Prepared field represents the value a user entered and must be higher than the value in the Quantity Needed Per Actual Attendance field.
Error 79
Quantity of Food Prepared was Recorded with a Measurement Type Inconsistent with the Quantity Required
This error is generated when the quantity measurement type entered by the user cannot be compared against the the quantity as computed by KidKare. This is typically the result of user error. For example, someone may have recorded that they served four gallons of ground beef, when they meant to enter pounds. This error is controlled by the following policies: M.01, M.01d, and M.02.
Error 81
No Infant Form on File
This error is generated if an infant is claimed and the Infant Form on File box is not checked in the Manage Child Information Child tab, subject to Policy D.24.
Error 82
A Withdrawn Child is Claimed Prior to the Date of Withdrawal, but the Child was Never Activated Before Being Withdrawn
This error is generated when a withdrawn child who was never activated is claimed prior to the withdrawal date. For example, a center enrolls a child and the sponsor never activates the child. The center begins claiming the pending child, but the child withdraws from care a few days later. So, the center withdraws the pending child and designates a withdrawal date as the last date the child was in care. When the center submits their claim, the child is claimed prior to the withdrawal date, but was never activated.
If you've received a valid enrollment for for the child and want to activate them, use the Activate New Children function to do so. Ensure you check the Include Withdrawn Children Who Were Never Activated box.
Error 83
Menu Notes/Comments Have Been Supplied
This warning is generated if infant/non-infant special notes are added to Record Menus. This is to advise you to look at the notes. This warning is not generated if Policy M.05 is set to Y. To review menu notes, click the Reports menu, select Menus, and click Menu Notes Report.
Error 87
Milk Audit Resulted in Milk Shortage
This error is generated in the event that Milk Audit edit checks are set to warn or disallow via Policy M.06, and milk audit disallowances are set to be applied using a monthly percentage and not to specific meals via Policy M.06f. It notes a shortage and a the number of meals disallowed as a result. For more information about the milk audit, see Milk Audit .
Error 88
For-Profit Center Does not Have at Least 25% Free or Reduced (At-Risk Still Allowed)
This is a variation of Error 53. This variation occurs if a dual child care center + At-Risk facility is prevented from filling the child care center claim only.
Error 89
Review Checked for Over Capacity
This error is generated on the claim if you checked the Over Capacity box in the Meals tab when editing a review.
Error 91
Infant Served Whose Parent Refuses Food
In most cases, infants can be reimbursed regardless of whether the parent brings food or not. This is because the labor involved with providing breast milk to infants is such that USDA policy reimburses the meals. However, Policy D.27 allows you to configure KidKare to disallow reimbursement for any infant for whom the parent refused the food offered by the center. You can apply this to an infant of any age or to infants that are 8-11 months old, since younger infants only require breast milk or formula.
Error 92
A Pending Child was Claimed—No Signed Enrollment is on File—But the Child has an F/R/P Application
This error is generated if a Pending child who does not have a FRP reimbursement level set is claimed, but only if Policy F.5b is set to including Pending children in the rate for the claim (as Paid).
The error behavior seems to be the opposite of error language. Contact KidKare support if you receive this error at support@kidkare.com.
Error 93
This error is exactly like Error 92, except it applies to children who were withdrawn and never activated.
Error 94
A Child has Neither an Enrollment Form nor an F/R/P Application on File
This error is generated if a child is Pending and the child does not have an FRP reimbursement level set, but only if Policy F.4 is set to B (Both — No App & No Enrollment).
Error 95
At-Risk children served outside of the school year.
This error is generated when an At-Risk child is served an At-Risk meal on a date prior to the school Start Date, or after the school End Date set on the Manage School Calendar screen for the specified child or center, school, district, or for all children, all centers. To view or edit the At)Risk Program school dates, go to Menus/Attendance > Manage School Calendar.
Error 96
At-Risk children served more than 1 meal & 1 snack.
This error is generated if an At-Risk center claims more than one meal and one snack per day to an At-Risk child outside of regular school hours during the school year.
Error 97
At-Risk children served a meal when child should have been in school.
This error is generated if a child has been fed a meal during normal school hours during the school year and a School Out designation has not been created for that day on the Manage School Calendar for the specific child or center, school, district, or all children, all centers.
To resolve this, mark school out on the days the At-Risk children are not attending school. See Manage School Out Days.
Error 98
Food was Claimed on a Date that Fell After the Food's Effective End Date
This error is generated when foods are claimed after their effective End dates. These foods are automatically disallowed. For more information about managing your foods, see Manage Your Food List.
Error 99
Food was Claimed on a Date that Fell Before the Food's Effective Start Date
This error is generated when foods are claimed before their effective start date. These foods are disallowed. For more information about managing your foods, see Manage Your Food List.
Error 100
At Least 1 Serving of Bread/Alternate Per Day Must be Whole Grain-Rich
This error is generated if none of the bread/alternate servings for a given day were marked as whole grain-rich. The meal pattern requires that at least one serving of bread/alternate must be whole grain-rich. Policy E.3 determines whether this error is generated as a warning or a disallowance. The meal with the lowest reimbursement will be the meal with an error. For example, a snack will be found in error before meals, and breakfasts will be found in error before lunches and dinners. Only those meals and snacks that included a bread/alternate are included.
Error Codes 101-112
Error 101
A Particular Type of Food was Served too Often. Consider Other Foods for a Better Variety
This error is generated if food served violates a food rule you have set up. Each of your food rules can be set to warn or disallow. For more information about managing food rules, see Create Food Rules.
Error 102
An Insufficient Combination of Foods were Served at the Given Meal(s)
This error is generated if food served violates a food combination rule you have set up. Each of your food rules can be set to warn or disallow. For more information about managing food rules, see Create Food Rules.
Error 103
A Meal was Served in which Two or More components May Have Been Provided by the Parent
This error is generated if an infant's record indicates that the parent supplies formula/food and the center serves a meal that contains two or more meal components (excluding formula/breast milk). Policy D.27b determines whether this error is generated as a warning or as a disallowance.
Error 104
The Child's Infant Feeding Form Indicates Parent Supplies Formula and Food
This error is generated if an infant's record indicates that the parent supplies formula/food and the center serves a meal that contains two or more meal components (excluding formula/breast milk). Policy D.27b determines whether this error is generated as a warning or as a disallowance.
Error 105
Juice Cannot Be Served More than Once per Day to Non-Infants
This error is generated if a center serves juice to non-infants twice in a day. Policy M.14 determines whether this error is generated as a warning or as a disallowance.
Error 106
Some children claimed have a current enrollment form date that is in a future month. These children may not be included in the OER counts.
This error is generated if policy D.20b is set to Y, policy F.6 is set to Enrolled, and policy F.6c is set to Y, children who's enrollment form date is set after the last day of the claim month.
Error 107
Grains Without an Ounce Equivalent Calculation Were Claimed
This error is generated if you have enabled ounce equivalents (policy M.17) and a site claims a Bread/Alt that does not have an ounce equivalents calculation saved to the food list. This is a warning only and does not impact claims reimbursement.
Error 108
Infant Cereal Without an Ounce Equivalent Calculation Were Claimed
This error is generated if you have enabled ounce equivalents (policy M.17) and a site claims an Infant Cereal that does not have an ounce equivalents calculation saved to the food list. This is a warning only and does not impact claims reimbursement.
Error 109
The Child is Younger Than the Center License Allows
This error is generated if a site claims a participant that is younger than the center's license allows. This edit check references the license Starting Age in the Manage Center Information License/Schedule tab.
Error 110
Infant previously served developmental foods was not served solid foods.
This error is generated if an infant is marked as developmentally ready for solid foods and is served solid foods in a prior claim months, but is not served solid foods during the current claim month.
Error 111
Insufficient foods served for developmentally ready infants.
This error is generated if an infant is marked as developmentally ready for solid foods, but is not served enough meal components for a specific meal. This error only appears when policy M19 is set to disallow.
Error 112
Quantity of food prepared was less than quantity required for infants.
This error is generated if the actual quantities served to an infant are insufficient based on their age, if they are developmentally ready for solid foods, and the USDA meal pattern requirements for infants. This error will occur no matter how policy M16 is set.