Since upgrading to Service Pack 8, users may experience the error: "Object reference not set to an instance of an object." when editing a posted payment. It seems the cause is batch allowing invalid finder numbers. Then when it is in the system and edited, it looks up the finder number information and cannot find it so it is failing. In previous versions batch prevented the invalid finder numbers.
We're currently evaluating this issue for a fix in a future patch or service pack.
Steps to Duplicate
1. Create an effort with a finder number range quantity of 1 2. Add a segment with criteria so that 0 records will be in your segment. 3. Activate your effort 4. Add an Enhanced Revenue Batch and enter a constituent, then add a source code, appeal, effort that would have been used in this effort 5. Add the finder number to this row in batch (the finder number that would have been in this efforts range) 6. It will let you commit the batch and does not give the invalid finder number error 7. Next, if you try to edit the payment it will not let you