|
Hi Vishwas
I think the solution for 1 would work for now, although I do think a unique number just adding up would also make it clear, thats what accountants/auditors like. To know for sure no transactions are skipped/missed etc. But for the time being this would work.
on 2, a stretchy report can work, but would mean a lot of extra work in the implementation for people wanting to use it, because you lose a lot of the power of the API endpoint around selection of dates, offices etc etc, and making that in a stretchy report gets quite messy (because all params are mandatory then). And I firmly believe that this will be a requirement that will come back very often, as it is the key starting point for doing any reconciliation of accounts by an accountant. Therefore it makes sense for me to add it to the journal endpoint.
In terms of the actual work to be done, we have one of our guys ready to pick this up once we agree on the best approach
|