New rule/task "APA SHORT BEDROOM TAX NO DHP" would use the following 2-tier SQL solution to identify cases for staff intervention but replacing the existing quite generic APA short tasks with a very specific description of the problem and clear path to solution for busy frontline staff. (1) Compare the expected gross monthly rent 'X' versus the monthly APA payment received 'Y' as a percentage shortfall and where this equals exactly 14.0% or 25.0% it is recognised as bedroom tax (2) Where bedroom tax is in play, are there any DHP payments/credits being received onto rent account? Y = no action required as shortfall being met. N = generate task. This idea leans into the wish for the guess work to be taken out of frontline hands. This rule/task would tackle a common collection issue in a very specific/tailored way providing an intervention prompt where the next steps are crystal clear. 'Spoon-feeding' frontline staff if you like with a suggested course of action. Yes, it won't capture all bedroom tax shortfalls (only those 'clean' ones that exactly = 14.0% or 25.0%) but others can still be picked up by the existing generic APA short rules. The ask here represents pretty basic SQL which can be easily pulled in a report but I feel this is the sort of development work Mobysoft should be delivering to help make UC casework as meaningful and palatable as possible for frontline staff.