Currently, if a revenue record is in an existing Revenue Update Batch, and changes are made to the revenue record outside of that batch, those changes are going to be reverted when the Revenue Update Batch gets committed.

To prevent changes from unknowingly being overwritten, I would like to suggest that if a revenue record is in an uncommitted Revenue Update Batch, the revenue record should get 'locked' down similar to how recurring gift records are when a payment for that recurring gift is sitting in an uncommitted batch. That would allow users to be aware of the uncommitted batch and can either make the change to the revenue record in the RUB or they will know to make the change later, after the batch has been committed.