Change Tracking - Release Date: 9/23/2026
See who changed what on a class, and when. Kangarootime has added a Change Tracking tab on the class view that logs every change made to that class's values, so if you're trying to figure out, for example, when the default casual fee changed, or who was assigned on a given day, this is where to look.
The tab shows a list of events; click any event to see the full details.
A couple of things to know:
- Existing classes start with an empty history: Tracking only begins once the feature is turned on for that class, nothing retroactive.
- The first tracked event includes a staff snapshot: The first time an event is recorded for a class, we capture the currently assigned staff as a "Staff Assigned" event. This just gives us a baseline to track changes against going forward. For new classes, this happens right at creation.
Change Details breaks down into three sections: Who, What, When. The What section shows the change name plus a field count (e.g. "Updated · 3 fields"), and for each changed field you'll see a small label with the value shown as old value → new value. Cleared or unset values show as an em dash (—).
Custom Billing Cycles - Release Date: 9/23/2026
Many childcare and before & after businesses offer programming where billing differs by term (ex. summer camps have irregular sessions, tuition schedules shift with the school calendar, and some centers bill in patterns that don't map to any standard template.) Custom Billing Cycles let administrators define billing periods entirely on their own terms, building a cycle out of individually configured periods instead of picking from preset options.
How it works:
- Create a Custom Billing Cycle from Billing > Settings. It appears alongside weekly and monthly cycles and can be scoped to specific business units or schools.
- Add individual Billing Periods to the cycle by defining each period with a date range of care being billed (Starts / Ends), plus a Bill date (Will Be Sent On) and a Due date (Will Be Due On).
- Mix and match period lengths. Periods don't need a consistent length or cadence; a center could run a 30-day period followed by two 7-day periods to transition from a monthly spring schedule into weekly summer sessions.
Built-in safeguard: Expiration Warnings
Since custom cycles are built period-by-period rather than auto-generating, a center could run out of defined periods and leave a stretch of time unbilled. To prevent that, each cycle is flagged before it happens:
- Expiring Soon — the cycle's last defined period is coming up; it's time to add more.
- Expired — the cycle has no remaining periods and needs immediate attention.
Both statuses surface directly on the Billing Settings list, so admins can catch gaps before they turn into missed bills.
For optimal performance, use Custom Billing Cycles in conjunction with Per Week and Per Month fees.