Record change history

[zkatai]

It would be good to have a change history for the records (transactions)

When I enter a transaction, it receives a transaction number, however it happens that later it needs to change several times (mostly with transfers from one account to another ) It would be a great help to see somekind of transaction history (record creation date, original values, change date, new value...) I know, it makes the database bigger, so it should be an optional setting, if the user wants to record changes or not.

[MartinArmstrong]

When I enter a transaction, it receives a transaction number, however it happens that later it needs to change several times (mostly with transfers from one account to another )

I think you are not using MMEX correctly.

Each time you make transfer from one account to another, it should be a new transaction. You should not ever be modifying an existing transaction (except to correct a mistake). Each transaction in MMEX represents a single real world deposit, withdrawal, or transfer of money on a particular date. There should be no history of changes to a single transaction.

[zkatai]

Yes, it is possible, that I not use it correctly... You are right, that a transaction should not be changed, as that is a real transaction which should not be changed.
As a new user I do not have the full knowledge of all the functionalities of this program to set up everything before I record transactions in the program. As I have more and more data recorder in the program, in certain cases as I see reports, I found out, that certain transaction should be changed because in the future I would like to see them differently show up on my reports.
Either I create a new category ( split a category, add subcategories...or something what was recorded as cost, and it would be better to see as asset..so I go back to change these transactions...)
Also in certain cases - when when I go through on a bank statement, and record transaction - certain transaction is not categorised, or need to revise later to find out exactly where should it be categorised, so temporarily I record it as a transfer to a "need to chak later" account, ( and later I sort it out ) So basically these are the cases when it would be a help for me to see transaction history there.

[MartinArmstrong]

Also in certain cases - when when I go through on a bank statement, and record transaction - certain transaction is not categorised, or need to revise later to find out exactly where should it be categorised, so temporarily I record it as a transfer to a "need to check later" account, ( and later I sort it out ) So basically these are the cases when it would be a help for me to see transaction history there.

You should not be temporarily setting a deposit or withdrawal transaction as a transfer to mark it as "need to check later" because MMEX already provides a means of setting the Status of transactions to:
- Unreconciled
- Reconciled
- Follow-up
- Void
- Duplicate

I would advise you to look at section 6 the Help.
Specifically:
6.1 Transaction Status
6.4 Reconciling and Balancing Transactions
6.5. Flagging transactions for follow up

You could also enter text in the Notes to indicate why you need to follow up on a transaction.

Attached is an example of three transactions with statuses of Reconciled, Follow-up, and Unreconciled.

For the use case you have described, I do not believe you need a 'transaction history' facility.