Enrollment Software and Reporting for Child Care Operators

Key Takeaways

• A dashboard shows what the software was configured to display, not independently verified revenue.
• Raw spreadsheet exports with a field dictionary and an effective date are worth more than any summary screen.
• Tie the billing ledger to bank deposits, payroll, filed returns, and the licensing roster before pricing anything.
• Strip child and family identifiers first; coded identifiers answer nearly every question a buyer needs answered early.
• Subscription assignment, data ownership, and administrator access are closing-checklist items, not IT trivia.

Six numbers the system is asked to keep separate

Most reporting disputes in a child care transaction come from blending measures that describe different things. Licensed capacity is the maximum the regulator authorized under stated conditions. Configured capacity is what the current room layout could physically hold. Staffed capacity is what the actual staffing plan and the applicable state ratios allow the center to open. Enrollment headcount counts distinct children under contract. Enrollment FTE normalizes those contracts for schedule under a method someone chose. Attendance counts children who were present, and collected cash counts money that cleared the bank.

A center can be full against staffed capacity while two licensed rooms sit dark. It can report rising headcount while FTE falls because five-day contracts were replaced with three-day contracts. Any report that does not say which of the six it measures is not yet usable, and the fix is a written definition rather than a longer report.

The export request list

Export	Fields that make it usable	What it supports	Frequent failure
Child roster, de-identified	Coded child ID, room, age band, start date, end date, status, payer type	Headcount and FTE by month	Withdrawn children left in active status
Schedule and room history	Contracted days, hours, effective-date ranges, transfers between rooms	FTE method and age-mix analysis	Only the current schedule is stored, so history is lost
Billing ledger	Invoice date, service period, gross charge, discount type, credit, refund, write-off	Gross-to-net revenue bridge	Invoice date and service period treated as interchangeable
Payments and aging	Payment date, method, processor batch, applied invoice, balance buckets	Cash tie-out and collection quality	Processor fees netted invisibly inside deposits
Subsidy module	Authorization dates, authorized units, copay, claim, remittance, recoupment	Payer-mix and timing analysis	Claims that cannot be reproduced from attendance
Attendance and check-in	Check-in and check-out stamps, authorized pickup, absence codes	Ratio testing and meal-claim support	Attendance presented as enrollment
Users and permissions	Named user, role, last login, creation date, deactivation date	Access audit and log credibility	One shared director login used by several people
Audit log	Actor, timestamp, record changed, prior value, new value	Confidence in every other export	Log retention shorter than the review period

Treat the table as a starting request, not a universal checklist. A single-site private-pay preschool and a subsidy-heavy center with a food program will need different files, and some centers keep part of this on paper or in a separate accounting package. What matters is that the reviewer can name which file supports which number.

Define the FTE method before quoting an FTE number

Here is an illustrative center with 96 contracted children. Sixty-two hold five-day contracts, eighteen hold three-day contracts, and sixteen hold two-day contracts. Using a straightforward weighting of 1.0 for five days, 0.6 for three days, and 0.4 for two days, enrollment FTE is 62 + 10.8 + 6.4, or 79.2. Against licensed capacity of 112, licensed utilization is 70.7 percent. Against staffed capacity of 94 seats, staffed utilization is 84.3 percent. Both percentages are correct and they describe very different investment cases.

The weighting above is a convention, not a rule, and other reasonable methods use contracted hours or billed days. The obligation is disclosure: state the weights, the measurement date, whether unpaid or noticed-out children are included, and which denominator is in use. A buyer who receives one percentage with no denominator should ask for the other. Related mechanics for the waitlist side of the same system are covered in enrollment and waitlist management.

Reconcile the ledger to the bank

A gross-to-net bridge is the fastest way to find out whether the system and the financial statements describe the same business. Take a trailing twelve months from the billing ledger and work down. In an illustrative example, gross charges posted total $1,412,600. Subtract sibling, staff, and promotional discounts of $58,900, credits and refunds of $11,400, and write-offs of $9,200, which leaves net billings of $1,333,100. Cash applied inside the system is $1,318,400, so accounts receivable grew by $14,700 over the period. Deposits traced to the merchant processor and subsidy remittances come to $1,309,700, leaving $8,700 unexplained.

That $8,700 is the interesting part. Processor fees netted at the batch level, a December deposit that cleared in January, a family paying by check outside the portal, and a refund issued from the operating account rather than the processor all produce exactly this shape of gap. None of them is alarming on its own. A gap that cannot be decomposed at all is a different matter, because it usually means the ledger is not the system of record and something else is. The figures here are constructed to show the method; they are not a benchmark, and no national dataset supports a normal size for that residual.

Run the same discipline against filed tax returns and the payroll register. Revenue per the return should be reachable from net billings with identified reconciling items, and the payroll register should support the staffing that the attendance and ratio reports imply. Tuition mechanics behind the discount and write-off lines are covered in tuition pricing and collections.

Audit the user list before trusting the log

The access review takes an hour and changes how much weight every other export deserves. Pull the user list and set it beside the current payroll roster. Former employees with active credentials, a shared director login used by three people, and an administrator count in double digits at a single site are all common and all reduce attribution. Ask who can edit a posted invoice, change a historical rate, or delete an attendance record, and whether those actions appear in the audit log with the prior value preserved.

Check the log's retention window against the review period. A system that keeps ninety days of change history cannot corroborate a twenty-four-month billing trend, and that limitation should be written down rather than discovered late. Multi-factor authentication, where the vendor offers it, is worth confirming for administrator accounts specifically.

De-identify before anything leaves the building

Transaction materials should use coded identifiers. Child names, birth dates, home addresses, family contact details, medical and immunization records, custody documents, incident narratives, and staff background-check results have no place in a general diligence file, and almost every enrollment or billing question can be answered without them. An NDA allocates contractual risk between the parties; it does not satisfy privacy, security, or retention duties, and it does not make a spreadsheet of family phone numbers appropriate to circulate.

Retention is genuinely local. State licensing rules set how long attendance, immunization, incident, and personnel records must be kept and where they must be available, and a subsidy contract or food-program agreement may impose its own period. Some states also address what happens to those records when a program changes hands or closes. Confirm the current requirement with the licensing agency and counsel rather than accepting the software's default retention setting as the legal answer. The federal licensing-regulation database maintained by the Administration for Children and Families is a starting point for locating the governing state text, not a substitute for it.

Read the vendor contract as a transfer document

The subscription is a contract that has to survive the deal. Look for assignment and change-of-control language, the current term and auto-renewal date, per-site or per-child pricing that changes when a new entity signs, termination rights, and any transfer or setup fee. Confirm in writing who owns the historical data, what export formats are available on exit and in what timeframe, which subprocessors touch family information, and how the vendor handles a security incident.

Sequence matters at closing. If the buyer's entity needs its own subscription, someone has to decide when the historical data migrates, who keeps read access during the transition, and how families experience the change to billing and check-in. A center that cannot bill on day one after closing has a working-capital problem, not a software problem, and it is avoidable with two weeks of planning.

Where reporting quietly misstates the business

Certain errors recur often enough to be worth testing directly. Waitlist rows counted inside an enrollment report. A single status value used for both contracted and pending families. Attendance substituted for enrollment in a month with heavy illness. Subsidy children billed at the posted private rate in the system while the state reimburses a different amount, so the ledger overstates realizable revenue. Registration fees and tuition deposits posted as earned revenue in the month received rather than across the service period. Sibling discounts applied manually and inconsistently across two front-desk staff.

Food-program records deserve a separate pass where the center participates. Claimed meals should be reproducible from attendance and production records, and reimbursement is a program payment governed by current federal and state rules rather than unrestricted margin. Subsidy timing follows the state plan, and federal policy in this area changed in 2026, so the current state payment practice controls rather than an older federal mandate. Detail on that payer is in analyzing subsidy revenue.

What this changes in price and terms

Good reporting does not earn a higher multiple by itself, and no public dataset supports one. What it changes is the range of outcomes a buyer has to price around. Clean, reconcilable exports shorten diligence, reduce the size of the holdback a cautious buyer asks for, and make a lender's file easier to approve. Weak records push the negotiation toward escrow, longer verification periods, or a working-capital true-up after closing.

Three items usually belong in the purchase agreement rather than in a spreadsheet: the treatment of prepaid tuition and deposits held at closing, responsibility for subsidy recoupments relating to pre-closing periods, and who bears the cost if the historical data cannot be migrated. Counsel should draft those provisions against the actual ledger balances, which is why the reconciliation work comes first. The broader sequence is laid out in the due diligence checklist.

Related

• Verifying enrollment and tuition
• Child care due diligence checklist
• Enrollment and waitlist management in diligence
• Tuition pricing and collections
• Analyzing subsidy revenue
• Child care center valuation
• Documents needed to sell
• FTE enrollment defined
• Contact Jason Taken