Comment 8 for bug 1858448

I realize a fix is in progress for implementing options 2 and 3, but I would have voted for option 1 to resolve this issue.

I don't agree that the aging process assumes you are essentially done with the data. Circulations get aged, but reports continue to be run off that data, so it would make sense that aged payment data should still allow for reporting.

If the fields specified in the bug description were restored, all the needed data for cash reports and other reporting would be retained in the aged tables. There would be no need to age payments on a different schedule than circs, and no need for a global flag.

If adding these columns is a needed improvement, why not take that approach now?