|
>>get a lot of questions both from our own accountant and from the people using the accounting stuff around the transaction_id's.
We originally have two Id's for accounting
1) A Transaction Id: This is unique in the context of a transaction, a auto generated Id for manual transactions or the transaction Id for loan/savings coupled with another another discriminator of the entity type which makes this transaction.
To make things simpler, we can prepend the entity type as a part of the transaction Id too so loans would be 1_transactionId and for savings would be 2_transactionId and no changes for manual entries.
Would this work for you?
2) A Entry Id: This is unique for each journal entry i.e the autogenerated Id of the journal entry table
>> but I do think that the payment detail fields also should be available as part of the journal API. The reason for this is that it makes it much easier to reconcile transactions
I was thinking of adding a new stretchy report for the same. Not too sure about the need for making any code modifications to the same
|