I have to agree with John Francis. A "stand alone" monthly cash flow forecast lacks integrity. It really needs to be linked to a forecast of P&L and balance sheet, and should take into account invoicing dates, profile of debtors collection, etc. I would suggest that a "stand alone" cash flow forecast could be done alongside the monthly forecast (that would be linked to monthly P&L and balance sheet forecasts) but should be a daily forecast, as this would highlight any problems that may occur during the month. For example, if all your receipts come in at the month end and your payments go out during the month, there may well be an overdrawn situation during the month, even though the month end forecast appears to be well in credit.
Please can you explain precisely what you mean by "hashing".
Totally agree with you, Tedbuck.
I was reading the article and decided to post a comment that it will defeat the objective of increasing the Treasury net "take" for exactly the reasons you have outlined above.
Would it not be easier to use the ranking function, then if two values in the list are, in fact, the same, they will have the same ranking, which is arguably better than ranking Kiwi 3rd and Bananas 4th merely bacause Kiwis appear in your list after Bananas.
The formula that I would enter in cell E2 on your example would be:
=Rank (B2,B$2:B$11,0), then copy the formula down column E.
I would then simply sort the list by reference to the rank value in column E.
However, I can see that COUNTIF would be useful to use if you wanted to identify genuine duplicated data so it can be removed.