For a value class, comparisons for equality should be based on state, not on identity
Closure of an account includes the current day as well
Bump to next version already
API for forecasting closures of individual accounts
forecasting is based on current plan
forecasting is based on current state of account
test for forecast service will require date utilities as well
Extraction of factory method yields more readable tests
In case a  transaction has been planned  to occur before today, assume that it either happened or has been planned anew. Either way, the forecast should ignore them
forecast should not take into account any part of the plan which will take place after the forecast day
method under test is invoked in assertion
If a non-continuous transaction is planned to occur between today and forecast date, the service should forecast that it happens for the specified amount. Exception is if a transaction took already place which matches the planned transaction, in that case it should be ignored
protected pointless as no subclasses are modelled
Out-of-the box implementation yields identity, which is unimportant for a value object
Test assumption explicitly
adjust to domain language
Clarify role of account in tests. Missing distinction between creditor and debitor role lead to incorrect test cases
Implement forecast service for non-continuous planned transactions
filtering could likewise be provided by container class as well
Similar behavior for continuous transaction if it will occur completely between now and forecast