User is attempting to resequence a check from a prior fiscal year and selects to void the old check.  Check would not resequence and the original check was voided.  If you process the same transaction but do NOT void the old check the resequence works.  

We think this problem stems from the re-sequencing process being a little to aggressive about handling messages from ModelContext. The DisbursementResequencer consumes all message available from ModelContext, thus an exception is never thrown by the ModelErrorsAspect when we come out of the transaction for the call to the DisbursementService. We need to restructure this code so errors and warnings that occurred for the void/re-sequencing process are left in the context so the appropriate exception is thrown and the transaction is rolled back. This should also cause the appropriate message to be displayed in the UI...although this display/handling of messages also need to be reviewed as part of this issue.