There are a couple ways I can see this being done, both of which have some element of messiness involved.
The first keeps everything in a single table, but is slightly messy from a data structure standpoint. Long story short, add new dummy bookings to each week/month that have a specific name like “FUNDED HOURS”, setting the hours appropriately for how much is funded for that week/month. In your {Total} formula field, look for this name and multiply the normal calculation by -1, which will reduce the weekly and monthly totals appropriately. Something like this:
IF(Name="FUNDED HOURS", -1, 1) * Hours * Rate
A much more complex setup involves adding more tables for tracking the funded hours per month per pupil, more linking, summarizing in a table other than [Bookings], etc. A bit “cleaner” from a data structure standpoint, but more complex to use, though some aspects of its usage might be made easier using automation (Zapier/Integromat).
Firstly, thanks for the detailed reply Justin. Much appreciated.
Both are good, workable solutions. I had already gone down the Integromat route of moving the data into a new table but the first solution sounds like a better option and gave me another idea.
I could have a status of each booking that can be changed to “Funded” and zero’s the cost. I’ll have to look at how I manage the depletion of the total funded hours but is sounds easy enough. Failing that I’ll automate a “Dummy” entry with the funded hrs value as you said
I might also continue with the Integromat option too as a kind of month end procedure where I flatten the data and make it static for reporting and archiving .
Thanks again