Visma.net Financials API updates for version 8.73.0 (November 2021)

[#1]

Release date for 8.73.0 version has been planned as 09/11/2021
Release plan & date may vary. We will keep you informed of any changes. This thread will be updated regularly up until the point of version-release.

Release Notes	Documentation
Support correction of sales invoice by API endpoint	Correction of sales invoices by a new API endpoint POST customerinvoice/{SalesInvoiceNumber}/action/correct is now supported with same functionality as we have for this feature in the UI. There is now a new way of correcting invoices, which requires fewer steps to update/correct an invoice than the previous standard reversal process. You can find the "Correct invoice" feature under the Actions drop-down list button in the Sales invoices (AR301000) window. When using the "Correct invoice" feature, the system will automatically create a copy of the original invoice that can be further edited. In the background, when releasing this new invoice, the system will automatically create a sales credit note for the original invoice and will match it against the chosen invoice to be corrected. As a note the original invoice will remain in status Open until the new corrected document will be finally released, but will not  be included in the payment process. Correcting of invoices with lines from the Shipments (SO302000) or Sales orders (SO301000) windows is currently not supported.
No webhook notification when sales invoice status changed to "Closed"	Earlier, there was no webhook notification when the status of an invoice was changed to "Closed" in Visma.net ERP. This has now been fixed.

Due dates for breaking changes

First announcement: Visma.net Financials API updates for version 8.61.0 (August 2021)

Release Notes	Documentation	Due
Breaking change on Currency endpoint	The PUT, POST and GET v1/currency/ExchangeRates methods are deprecated and will be removed on January 11th, 2021. Start using the new methods under v2/currencyRate.	Jan 11, 2021
Breaking change on GeneralLedgerTransactions	To improve the performance of GeneralLedgerTransactions endpoint, there are now three new flags to allow users to retrieve extended data only if necessary: expandBranchInfo, expandAccountInfo, includeTransactionBalance. To ensure the API compatibility, the flags were set to True by default, but they will be switched to False by November 16th 2021. Please verify swagger documentation and if you consider the extended data is necessary, set the flags to True for your calls.	Nov 16, 2021
Breaking changes on Budget endpoint	From January 18th 2022, the following breaking changes will be committed on GET method of the Budget endpoint:  - 'Branch' and 'Ledger' filters will become mandatory. Now they are specified to be mandatory by documentation, but it is not enforced by implementation.  - 'FinancialYear' filter will become mandatory  - Now, the branch filter requires being specified either by branch full name (example: BranchID - BranchName), either by branch ID surrounded by quotation marks. It will be simplified to require the branch ID without any other marks.	Jan 18, 2022