Drop-In Childcare Checkout and Daily Reconciliation
- At each drop-in checkout, confirm the visit, check the actual duration, apply any eligible pack, review the bill, and record the true payment status.
- An invoice, a successful payment and a bank deposit are different events, so never mark a visit paid just because an invoice exists or a payment was attempted.
- In the fictional day, $70 of new charges splits into $55 paid and $15 pending, and a $10 payment on an older visit brings receipts to $65.
- Keep original arrival and departure times, and correct a disputed timestamp only through an authorized, documented process, never to produce a desired bill.
A reliable drop-in checkout connects the actual visit, the applicable charge, any pack entitlement and the payment result. At the end of the day, staff should be able to explain each completed visit without treating an invoice, a successful payment and a bank deposit as the same event.
Use the workflow below to build a desk checklist and a daily exception log. All visits and amounts in the worked example are fictional. Apply your own disclosed pricing, payment and record-correction procedures.
Keep pickup and payment tasks distinct
Follow your center's established child-release and authorized-pickup procedure first. A billing question must not become a substitute for verifying who is collecting a child, and staff should maintain supervision while administrative questions are resolved.
Once the actual departure is confirmed, the attendance record needs the correct time and visit. Avoid closing the wrong sibling's visit or recording the expected due-out time as though it were the actual departure.
Bloomily for drop-in centers connects checkout invoicing with time stayed, card charging after pickup and visit-pack balances. Those capabilities still need a clearly defined operating process, particularly when a timestamp or charge is disputed.
Agree on hourly billing rules before reviewing the arithmetic
Your checkout reviewer should be able to find the current version of the rate policy. It needs to explain the unit charged, any minimum or rounding rule, what a pack covers, and which additional items require separate payment.
There is no single billing increment to assume. For example, Giggles publishes a first-hour minimum and later fifteen-minute increments, while Bloomily describes billing for time stayed. A provider's policy is an example, not a rule for every center or a feature every system supports.
Preserve actual arrival and departure times even if the selected pricing policy transforms that duration into billable units. Changing a timestamp to produce a desired bill makes the attendance record harder to trust.
Use a five-step checkout review
Confirm the visit
Match the correct child, date, location and open visit. If there are duplicate or overlapping records, have the designated person investigate rather than guessing which one to close.
Check actual duration
Review the recorded arrival and departure. If a time needs correction, document the evidence and follow your authorized correction process. Keep the original value and the reason available where your system permits.
Apply the eligible offer
Check whether the family is using an hour pack, visit pack, membership benefit or ordinary visit rate. Confirm eligibility and the remaining entitlement before applying it. A pack purchase and a pack redemption are separate events. If the offer itself is unclear, start with how to define prepaid hours and visit packs.
Review the bill
Check the care charge and any separately authorized items against the published policy. Make sure a manually added amount has not duplicated an automatic charge.
Record the payment result
Use the status shown by the payment system: paid, pending, failed, or another accurate state. Do not mark a visit paid merely because an invoice exists or a payment was attempted.
For an unresolved result, assign an owner and a next check. Before retrying a payment, verify that the previous attempt did not succeed or remain in progress through the approved billing process.
Worked example: a fictional day of drop-in checkouts
Assume a fictional center charges $20 per hour using actual minutes, with no minimum charge in this example. Visit B uses one eligible prepaid visit entitlement that covers its full stay. There are no additional items, processing fees or taxes in the example.
| Visit | Actual time | Duration | Checkout outcome |
|---|---|---|---|
| A | 9:10–10:40 a.m. | 90 minutes | $30 paid |
| B | 10:05 a.m.–12:05 p.m. | 120 minutes | One pack visit used |
| C | 11:15 a.m.–noon | 45 minutes | $15 pending |
| D | 12:30–1:45 p.m. | 75 minutes | $25 paid |
For Visit D, the calculation is:
75 ÷ 60 × $20 = $25
Suppose someone initially entered 2 p.m. as the departure. That would produce a 90-minute, $30 charge under the example policy. Correcting it requires checking the real departure, recording the authorized correction and addressing any resulting bill difference. It does not justify silently replacing a paid transaction.
The day's new charges payable outside packs total:
$30 + $15 + $25 = $70
Of that amount, $55 is paid and $15 is pending. One prepaid visit was also used. Report that redemption separately rather than counting the original pack purchase again as money collected today.
Daily reconciliation: separate today's visits from today's money
Now imagine the center also collects $10 against an older unpaid visit.
Today's successful receipts become $65: $55 for today's visits plus $10 for an earlier one. Today's newly payable charges remain $70. Those numbers answer different questions, so they do not need to match.
Use three short views:
- Completed visits and their charges or pack use
- Payment results, including payments relating to older visits
- Unresolved items requiring a named reviewer
Bank deposits form another view. Payment timing, processing deductions and adjustments can affect how receipts appear in the bank. Use the processor's records and your bookkeeping process to reconcile deposits; this desk worksheet is not a replacement for accounting reconciliation.
Build an exception log that helps the next person act
A useful exception has an owner and a specific unresolved question.
| Visit reference | Issue | Current state | Next action |
|---|---|---|---|
| C | Payment has no final result | Pending in payment system | Billing lead checks status |
| D | Departure time challenged | Evidence under review | Authorized reviewer confirms time |
| E | Pack eligibility unclear | No adjustment approved | Manager checks published offer |
These are fictional examples; Visit E is an additional visit not shown in the day's table. Keep actual family and payment information in a restricted-access record. Do not place card details, private messages or identifiable child records in a public spreadsheet or training handout.
Close an exception only when its outcome is recorded. “Asked the manager” describes an action, not the final result. Open items that carry over should also appear in the drop-in staff shift handover.
Give families an explanation they can check
When the amount is questioned, explain the components before repeating the total.
Original wording to adapt:
“For the visit on [date], our record shows [arrival] to [departure], or [duration]. We applied [published rate or pack rule]. The care charge is [amount], with [any approved separate items] listed separately. The payment currently shows [verified status]. We are reviewing [specific question], and [role] will follow up through [channel].”
Avoid inventing a completion time for the review. If the family provides evidence of a different time, route it to the authorized reviewer and preserve the conversation.
Test a complete checkout day in a demo
Use Bloomily's drop-in workflow to discuss one ordinary checkout, one eligible pack visit and one unresolved payment. Ask how your team would find each record and review a correction. Confirm the supported workflow rather than assuming every exception will resolve automatically.