I've reproduced the error in a private browser, which has no native cookies or cache.
It can be reproduced by setting a future date on any customer statement and then using the print preview.
The problem persists and is not related to an invalid cookie or cache.
