|
Hi Vishwas,
I was not intending the notes, 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. On top of that with the current situation where we do not have any unique identifier for a journal transaction it is very hard for end users to reconcile and understand the workings of this. Although I would agree that we can pull this out using the existing info in the API, or using a run report, we currently want to display this information as part of a journals overview, where you pull out 50 to 100 journals at a time based on some search parameters. Doing an extra call for each of these won't be acceptable in terms of performance, and a run report will significantly limit the search possibilities.
Therefore my preference would be to make this available as part of the endpoint anyway to make it a lot easier to reconcile individual transactions within a loan or savings (or across multiple loans and savings when the same cheque was linked to multiple payments).
As a second point on this area: I get a lot of questions both from our own accountant and from the people using the accounting stuff around the transaction_id's. People expect one unique identifier for each journal booking. Currently there isn't one, because the transaction_id can be duplicated where one is linked to a loan and the other to a savings with the same transaction_id but they have completely different clients, products etc. In order to make this more clear to end users I would really like to clean this up and get one unique ID in. The other relations back to the loan and savings can of course still be there.
|