Hi all,    I'm investigating options in to create an aging overview (accounts receivable and payable) using the Visma.net API. I would like to minimize the number of requests to the minimum to speed up performance. Do you have any suggestions or ideas on how to implement this? I've included a sample screenshot of how this report should be created. Thus, the information that we would need is as follows:  - Open amount per debtor / creditor per period, split by the number of due days.    Joining endpoints or doing any transformations on the original data is no problem. Hoping someone can help me out!    Regards,   Daan   Sample image    ... View more

Hi,   Our application involves an incremental load of all JournalTransactions. In order to do this, we use a datetime variable which is saved after each request, and used in each get request to retrieve new or updated batches. However, there currently is no way to delete batches from the existing dataset since we can not retrieve this information.    In order to do so, we would like to incorporate some kind of logic in order to retrieve an overview of deleted batchnumbers, preferably per year. Would that be possible?    Regards,   Daan  ... View more

In order to extend the functionalities of our Visma integration, we would like to create an opening balance per customer for specific accounts. For example: in order to identify intercompany transactions, we would like to create an opening balance which is split to different debtors for specific accounts (e.g. 1300 - Debtors).   Right now we use the endpoint GeneralLedgerBalance but this endpoint does not support any other dimensions thant account. Would someone be able to advise me: - Which endpoint to use?  - Which logic to use?    An important assumption is to limit the amount of requests to the lowest as possible.    Kind regards,    Daan  ... View more