Custom childcare benefit hours app
Appfront builds apps that let childcare organisations record the hours per child per month as actually used, compile the childcare benefit return from them and show parents what was submitted. With contract hours, extra days, swapped days and closure days in one system, and every correction traceable, so the annual statement and the monthly data submission match what was actually provided.
What is a childcare benefit hours reporting app?
A childcare benefit hours reporting app tracks, per child per month, how many hours of care were used: the contracted hours, the extra days that were requested and approved, the swapped days, the closure days and the days that were cancelled. From this come the statement sent to the Dutch Tax and Customs Administration (Toeslagen) and the annual statement for the parent. In the portal, the parent sees per month what has been reported, and a later correction is a new statement with the reason attached.
Without such an app, the contracted hours sit in the placement system, the extra days in emails, the swapped days on the group and the cancellations in a supplier's app. At the end of the month, the administration pieces it all together, and in January a parent phones because their annual statement does not match what they thought they had used. A difference between the statement and reality is a problem for the parent when it comes to their benefit, and therefore a problem for you.
We build this as a custom solution because hours policy differs from one organisation to the next. Whether a swapped day counts, how extra days are charged, whether closure days are passed on and how a host-parent agency processes the host parent's hours are all set out in your terms. The app should follow those rules and connect to your planning and your invoicing, not impose a standard arrangement.
Hours per child per month
Contracted hours, extra days, swapped days, closure days and cancellations according to your terms, per child and per month, drawn from the planning and the group.
Statement and annual statement
The monthly statement for the data submission and the annual statement for the parent, both drawn from the same hours, with the version and date attached.
Parents can follow along
In the portal, the hours reported each month with the breakdown alongside, so the question in January no longer comes up.
How we build your childcare benefit hours reporting app
We start with your hours policy and the sources the hours currently come from. The monthly calculation rule follows from that.
How contracted hours, extra days, swapped days and closure days count for you, where they are currently recorded, and how the statement and annual statement are currently produced. We recalculate a few months to check.
The monthly calculation rule from your terms, with the hours drawn from the planning and the group, and extra days and swapped days handled as requests with approval.
The monthly statement and the annual statement drawn from the hours, with version and date, and the portal in which the parent sees the breakdown each month.
Corrections as a new statement with a reason, integrations with invoicing and planning, and the history per child. After that, we take over management of the app.
What a childcare benefit hours reporting app actually does
The components below appear at almost every childcare organisation. Which ones you need depends on your hours policy and the systems you already use.
Hours rules
Your terms as a calculation rule: what counts, what does not, and how extra days, swapped days and closure days are processed, per type of care.
Hours registration per child
Per child per month, the hours from the contract, extra days, swapped days and cancellations, with the source for each line.
Requests and approval
Extra days and swapped days as a request from the parent, approved by the group or the planning team, and then added to the hours.
Statement and annual statement
The monthly statement and the annual statement per child, drawn from the same hours, with the version, date and breakdown attached.
Parent portal
Per month, the hours reported and the breakdown, the annual statement as a download, and a button to ask a question.
Corrections with history
A correction is a new statement with a reason; the old one stays visible, so the parent and Toeslagen see the same series.
Who we build a childcare benefit hours reporting app for
The app is intended for organisations where the hours come from too many sources and where the statement and parents' questions currently take up too much of the administration's time.
Day nurseries
Contracted hours per day, extra days and swap days per child. A monthly calculation rule replaces the hunt for the right figures.
Out-of-school care
School weeks, holiday weeks and training days, each with their own hours. The rules per period live in the app, not in the planner's head.
Childminder agencies
The childminder's hours per child, checked by the parent and processed by the agency. The app makes that chain traceable.
Organisations with multiple locations
One hours policy, multiple locations with their own groups. The statement is produced in the same way everywhere.
Test your idea first: a working prototype in 1 day
With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.
View OneDayBuild →Technology and integrations
This page is about hours per child and the statement. For staffing and the staff-to-child ratio in a group, see our page on staff-to-child ratio calculation and staffing, and for time tracking in general, our page on time tracking software. You can read about our approach on custom software development.
For linking the contract, invoice and statement in the back office, there is our software for contracts, invoices and hours statements.
Why Appfront for your childcare benefit hours statement app?
A statement is only correct if the hours come from a single calculation rule and the parent can see them. That is what we build on.
Your terms as a rule
What counts and what doesn't is set out in your terms. We translate them into a single calculation rule and check it against a few months of past data, so the statement matches what you have agreed.
One source for the statement and the annual statement
The monthly statement and the annual statement come from the same hours. Two statements that differ are exactly what gets parents calling.
Corrections without confusion
A correction is a new statement with a reason, and the parent sees both. This keeps the series that the Tax and Customs Administration sees identical to the parent's.
Security and privacy in a childcare benefit hours statement app
The app contains data on children and parents. Access is arranged by role: a parent sees only their own children, the group sees the children in the group, and the administration sees everything. Data is retained for as long as the law and the benefit rules require, and no longer.
Statements are stored immutably with a version and date; a correction is a new version with a reason and a reference to the old one. If a parent or the Tax and Customs Administration asks a question, you can look up what was submitted when, and why.
Frequently asked questions about a childcare benefit hours statement app
Questions that childcare organisations ask before getting started.
It records the hours used per child per month according to your terms, compiles the monthly statement and the annual statement from them, shows the parent in a portal what has been submitted and makes every correction traceable. The hours come from your planning and the group; the statement is sent to the data submission in the required format.
That depends on your terms and on the benefit rules. At the start we record how you handle them, and the app applies that rule in the same way everywhere. Whether a specific rule complies with the benefit rules is a question for your adviser; what we guarantee is that the app applies it consistently.
Yes, per month in the portal, with the breakdown: contracted hours, extra days, swap days, absences. The annual statement is available as a download. That is why the question no longer comes up in January: the parent has been able to see it all year.
A correction is a new declaration with the reason attached; the original stays visible. The parent sees both, and the new declaration goes to the data submission. This keeps the series at the Tax Administration (Toeslagen) identical to the one in the portal, and you can look up later what was corrected and when.
Yes. The childminder registers hours per child, the parent checks them, and the agency processes them into the declaration. Every step is traceable, and the declaration comes from the same rule as for a day nursery.
Yes. The contracted hours and attendance come from your planning system, invoicing uses the same hours, and the declaration comes from the app. We integrate with the packages you use; the app does not become a second placement system.
Then we update the calculation rule with an effective date. Declarations from before that date stay calculated as they were, so an annual statement for an earlier year does not change. You can look up in the app which rule applied when.
Your hours declaration from a single calculation rule?
Send us your terms on hours, swap days and closing days, and tell us which planning system you use. We will recalculate one month and show you what the declaration and the parent portal look like.