[Version 12] [Proposal] Changing the Cancellation Workflow

[wale]

Well, you might need to clarify your definition of ‘immutability’. The ERPNext system as it currently stands doesn’t have transaction immutability because we’re still able to make all traces of a transaction disappear by Cancelling and Deleting. Thankfully though we’re expecting real immutability to ship with V12. Pls see thread below for reference:

[discussion] Immutable Ledger

Dear all, We are proposing a major change in the way the accounting ledgers work in ERPNext. Please review and comment [Proposal] Immutable Ledger · Issue #11782 · frappe/erpnext · GitHub Discussion In most accounting systems, the ledger is immutable. If a cancellation or adjustment has to be made, it has to be as a new entry that reverses or changes the impact of a previous entry. Here are some problems related to this: Forward posting is computationally expensive. In stock, where valuat…

If your concern however is about the ‘Revert’ option being a threat to immutability when it does come in V12 then there’s no need to worry at all

1. Immutability is more about the ledger than the doc itself. Reverting creates reverse ledger entries as opposed to deleting the existing ones which is in line with the philosophy of immutability

2. For ease of reference, the team has suggested an option of adding a ‘Revision’ property to the DocType which will basically serve the same purpose as the current suffix naming system. This means when a document gets Reverted once for example, there’ll be a number 1 in the ‘Revision’ field. If it gets Reverted three times, there’ll be a figure 3 in the ‘Revision’ field

When there’s a figure in the ‘Revision’ field, you should be able to inspect the audit trail by simply clicking on the ‘View => Accounting Ledger’ button. This should bring up all ledger entries for the document including the reversals

Hope this helps clarify things

Cheers