We used to have this feature. The programming improved the database design by changing from payments and receipts being in the same table to payments in one table and receipts in another table. This meant that the code to convert receipts and payments to each other had to go away.
However, I hope @lubos will consider reimplementing. The conversion need would be fulfilled even if some data is lost in the conversion due to some columns not having a corresponding column in the other table.
Some uses of this feature:
A user starts entering a payment and has everything filled out, then realizes he/she is filling out a receipt. Instead of starting over, the user clicks “change to payment” and then “create.”
A user is reconciling. The user discovers that the mistake is that a receipt was entered as a payment. The user clicks “edit,” then “change to receipt.”
A business purchases, then later returns for a full refund. To record the refund, the user clones the purchase, adds “Returned” to the comment, then clicks “change to receipt.”
Maybe this feature is already on the to-do list?
Anybody else see this as a beneficial productivity feature?