Release Notes Documentation Unable to release voided purchase credit note that was re-opened In the documents flow where a purchase credit note was; 1. Pre-booked 2. Voided 3. Re-opened into balanced state 4. Releasing the document gave an error "subaccount cannot be empty" This has now been fixed, and purchase credit notes that have been re-opened can be pre-booked and/or released via both UI and API.     API - Due dates for breaking changes Release Notes Documentation Due Deprecated parameters on  GET Packagingtype endpoint In version 10.43.0 we have introduced pagination to enhance API performance and usability. As part of this update, the following parameters have been marked as deprecated: -GeaterThanValue -numberToRead -skipRecordsThis -orderBy These parameters will be removed in 6 months, at which point this update will result in a breaking change to the API. Please update your integrations accordingly to accommodate this change before the due date.   Deprecated parameter releasedBatch on  JournalTransactionV2 GET In version 10.39.0 we have introduced a new parameter, status, to filter on different statuses on journal transactions and marked releasedBatch  as deprecated. We will remove releasedBatch parameter on May 13th 2025.  May 13, 2025 Planned removal of Sales Order API endpoints We plan to be functionally complete by Q1-2025 (31st of March 2025), end of life date for the endpoints will be announced at a later point. A number of Sales Order API endpoints will be removed as a part of the transition to the next generation ERP. The following API endpoints will be removed: GET /controller/api/v1/salesorder/{orderNbr} GET /controller/api/v1/salesorder/{orderType}/{orderNbr} GET /controller/api/v1/salesorder/{orderType}/{orderNbr}/rotrut GET /controller/api/v1/salesorder GET /controller/api/v1/salesorder/{orderType}/{orderNbr}/commissions POST /controller/api/v1/salesorder POST/controller/api/v1/salesorder/{saleOrderNumber}/action/cancelSalesOrder POST/controller/api/v1/salesorder/{salesOrderNumber}/action/reopenSalesOrder PUT /controller/api/v1/salesorder/{orderNbr} GET /controller/api/v1/salesorderbasic/{orderNbr} GET /controller/api/v1/salesorderbasic/{orderType}/{orderNbr} GET /controller/api/v1/salesorderbasic POST /controller/api/v1/salesorderbasic PUT /controller/api/v1/salesorderbasic/{orderNbr} POST /controller/api/v2/salesorderbasic POST /controller/api/v2/salesorder POST /controller/api/v2/salesorder/{saleOrderNumber}/action/cancelSalesOrder POST/controller/api/v2/salesorder/{salesOrderNumber}/action/reopenSalesOrder All functionality currently missing in the new Sales Order Service API will be added before these endpoints are removed. The list of affected endpoints might also be extended, so pay attention to future updates. For more information on how to use the Visma.net ERP Sales Order Service, please visit: https://community.visma.com/t5/News-in-Developers-Visma-net/Getting-started-with-the-first-neXtGen-s... Swagger for Visma.net.ERP.SalesOrder.API https://salesorder.visma.net/swagger/index.html   ... View more

Release Notes Documentation Warehouse can be incorrectly updated through  PUT v1/salesorder/[salesordernbr] even if it has quantity shipped on the current line  Earlier, warehouse could be incorrectly updated on the orderline through PUT v1/salesorder/[salesordernbr] even if it has quantity shipped on the current line. This has now been fixed. Implement support for delivery address line 3 in POST and PUT v1/shipment -endpoints Implemented support for delivery address line 3 in endpoints POST v1/shipment and PUT v1/shipment/[shipmentnumber] Improve performance for GET v1/shipment and GET v1/shipment/[shipmentNbr] endpoints. Improve performance for GET v1/shipment and GET v1/shipment/[shipmentNbr] endpoints. Improve performance for GETs in /v1/purchaseorder and /v1/purchaseorderbasic endpoints Improved performance for GET in /v1/purchaseorder and GET /v1/purchaseorderbasic endpoints     API - Due dates for breaking changes Release Notes Documentation Due Deprecated parameters on  GET Packagingtype endpoint In version 10.43.0 we have introduced pagination to enhance API performance and usability. As part of this update, the following parameters have been marked as deprecated: -GeaterThanValue -numberToRead -skipRecordsThis -orderBy These parameters will be removed in 6 months, at which point this update will result in a breaking change to the API. Please update your integrations accordingly to accommodate this change before the due date.   Deprecated parameter releasedBatch on  JournalTransactionV2 GET In version 10.39.0 we have introduced a new parameter, status, to filter on different statuses on journal transactions and marked releasedBatch  as deprecated. We will remove releasedBatch parameter on May 13th 2025.  May 13, 2025 Planned removal of Sales Order API endpoints We plan to be functionally complete by Q1-2025 (31st of March 2025), end of life date for the endpoints will be announced at a later point. A number of Sales Order API endpoints will be removed as a part of the transition to the next generation ERP. The following API endpoints will be removed: GET /controller/api/v1/salesorder/{orderNbr} GET /controller/api/v1/salesorder/{orderType}/{orderNbr} GET /controller/api/v1/salesorder/{orderType}/{orderNbr}/rotrut GET /controller/api/v1/salesorder GET /controller/api/v1/salesorder/{orderType}/{orderNbr}/commissions POST /controller/api/v1/salesorder POST/controller/api/v1/salesorder/{saleOrderNumber}/action/cancelSalesOrder POST/controller/api/v1/salesorder/{salesOrderNumber}/action/reopenSalesOrder PUT /controller/api/v1/salesorder/{orderNbr} GET /controller/api/v1/salesorderbasic/{orderNbr} GET /controller/api/v1/salesorderbasic/{orderType}/{orderNbr} GET /controller/api/v1/salesorderbasic POST /controller/api/v1/salesorderbasic PUT /controller/api/v1/salesorderbasic/{orderNbr} POST /controller/api/v2/salesorderbasic POST /controller/api/v2/salesorder POST /controller/api/v2/salesorder/{saleOrderNumber}/action/cancelSalesOrder POST/controller/api/v2/salesorder/{salesOrderNumber}/action/reopenSalesOrder All functionality currently missing in the new Sales Order Service API will be added before these endpoints are removed. The list of affected endpoints might also be extended, so pay attention to future updates. For more information on how to use the Visma.net ERP Sales Order Service, please visit: https://community.visma.com/t5/News-in-Developers-Visma-net/Getting-started-with-the-first-neXtGen-service-Visma-net-ERP/ba-p/401436 Swagger for Visma.net.ERP.SalesOrder.API https://salesorder.visma.net/swagger/index.html     ... View more

 API - Due dates for breaking changes Release Notes Documentation Due Deprecated parameters on GET Packagingtype endpoint  In version 10.43.0 we have introduced pagination to enhance API performance and usability. As part of this update, the following parameters have been marked as deprecated: -GeaterThanValue -numberToRead -skipRecordsThis -orderBy These parameters will be removed in 6 months, at which point this update will result in a breaking change to the API. Please update your integrations accordingly to accommodate this change before the due date.   Deprecated parameter releasedBatch on  JournalTransactionV2 GET In version 10.39.0 we have introduced a new parameter, status, to filter on different statuses on journal transactions and marked releasedBatch  as deprecated. We will remove releasedBatch parameter on May 13th 2025.  May 13, 2025 Planned removal of Sales Order API endpoints We plan to be functionally complete by Q1-2025 (31st of March 2025), end of life date for the endpoints will be announced at a later point. A number of Sales Order API endpoints will be removed as a part of the transition to the next generation ERP. The following API endpoints will be removed: GET /controller/api/v1/salesorder/{orderNbr} GET /controller/api/v1/salesorder/{orderType}/{orderNbr} GET /controller/api/v1/salesorder/{orderType}/{orderNbr}/rotrut GET /controller/api/v1/salesorder GET /controller/api/v1/salesorder/{orderType}/{orderNbr}/commissions POST /controller/api/v1/salesorder POST /controller/api/v1/salesorder/{saleOrderNumber}/action/cancelSalesOrder POST/controller/api/v1/salesorder/{salesOrderNumber}/action/reopenSalesOrder PUT /controller/api/v1/salesorder/{orderNbr} GET /controller/api/v1/salesorderbasic/{orderNbr} GET /controller/api/v1/salesorderbasic/{orderType}/{orderNbr} GET /controller/api/v1/salesorderbasic POST /controller/api/v1/salesorderbasic PUT /controller/api/v1/salesorderbasic/{orderNbr} POST /controller/api/v2/salesorderbasic POST /controller/api/v2/salesorder POST /controller/api/v2/salesorder/{saleOrderNumber}/action/cancelSalesOrder POST/controller/api/v2/salesorder/{salesOrderNumber}/action/reopenSalesOrder All functionality currently missing in the new Sales Order Service API will be added before these endpoints are removed. The list of affected endpoints might also be extended, so pay attention to future updates. For more information on how to use the Visma.net ERP Sales Order Service, please visit: https://community.visma.com/t5/News-in-Developers-Visma-net/Getting-started-with-the-first-neXtGen-s... Swagger for Visma.net.ERP.SalesOrder.API https://salesorder.visma.net/swagger/index.html     ... View more

Release Notes Documentation Pagination support added to GET PackagingType Endpoint The PackagingType endpoint now supports pagination through the introduction of pageSize and pageNumber parameters. GET v2/salesorders - missing contactId in response Added missing contactId in response for GET v2/salesOrders - endpoint Fields "currencyOverride" & "currencyRateOverride" exposed in GET Supplier endpoint Now, you have available "currencyOverride" & "currencyRateOverride" fields in GET Supplier.     API - Due dates for breaking changes Release Notes Documentation Due Deprecated parameters on GET Packagingtype endpoint  In version 10.43.0 we have introduced pagination to enhance API performance and usability. As part of this update, the following parameters have been marked as deprecated: -GeaterThanValue -numberToRead -skipRecordsThis -orderBy These parameters will be removed in 6 months, at which point this update will result in a breaking change to the API. Please update your integrations accordingly to accommodate this change before the due date.   Deprecated parameter releasedBatch on  JournalTransactionV2 GET In version 10.39.0 we have introduced a new parameter, status, to filter on different statuses on journal transactions and marked releasedBatch  as deprecated. We will remove releasedBatch parameter on May 13th 2025.  May 13, 2025 Planned removal of Sales Order API endpoints We plan to be functionally complete by Q1-2025 (31st of March 2025), end of life date for the endpoints will be announced at a later point. A number of Sales Order API endpoints will be removed as a part of the transition to the next generation ERP. The following API endpoints will be removed: GET /controller/api/v1/salesorder/{orderNbr} GET /controller/api/v1/salesorder/{orderType}/{orderNbr} GET /controller/api/v1/salesorder/{orderType}/{orderNbr}/rotrut GET /controller/api/v1/salesorder GET /controller/api/v1/salesorder/{orderType}/{orderNbr}/commissions POST /controller/api/v1/salesorder POST /controller/api/v1/salesorder/{saleOrderNumber}/action/cancelSalesOrder POST/controller/api/v1/salesorder/{salesOrderNumber}/action/reopenSalesOrder PUT /controller/api/v1/salesorder/{orderNbr} GET /controller/api/v1/salesorderbasic/{orderNbr} GET /controller/api/v1/salesorderbasic/{orderType}/{orderNbr} GET /controller/api/v1/salesorderbasic POST /controller/api/v1/salesorderbasic PUT /controller/api/v1/salesorderbasic/{orderNbr} POST /controller/api/v2/salesorderbasic POST /controller/api/v2/salesorder POST /controller/api/v2/salesorder/{saleOrderNumber}/action/cancelSalesOrder POST/controller/api/v2/salesorder/{salesOrderNumber}/action/reopenSalesOrder All functionality currently missing in the new Sales Order Service API will be added before these endpoints are removed. The list of affected endpoints might also be extended, so pay attention to future updates. For more information on how to use the Visma.net ERP Sales Order Service, please visit: https://community.visma.com/t5/News-in-Developers-Visma-net/Getting-started-with-the-first-neXtGen-s... Swagger for Visma.net.ERP.SalesOrder.API https://salesorder.visma.net/swagger/index.html     ... View more

Release Notes Documentation New API filter parameters for all customer endpoints used for different customer document types  We have added new filter parameters in the following API endpoints: CustomerInvoice, CustomerCreditnote, CustomerDebitnote, CustomerOverdueCharge, Cashsale, CustomerWriteoff. These filter parameters are: branch, docDate, docDateCondition, financialPeriod, customer, documentDueDate, documentDueDateCondition Also new filter parameters in CustomerPayment endpoint: branch, docDate, docDateCondition, financialPeriod New client id: "Branch cannot be found in the system" -error  API calls made with a new client ID not yet registered into database of the company - Unable to locate the access for the branches directly after. This has now been fixed and the cache will be automatically refreshed after a new client id is registered as a user.     API - Due dates for breaking changes Release Notes Documentation Due Deprecated parameter releasedBatch on  JournalTransactionV2 GET In version 10.39.0 we have introduced a new parameter, status, to filter on different statuses on journal transactions and marked releasedBatch  as deprecated. We will remove releasedBatch parameter on May 13th 2025.  May 13, 2025 Planned removal of Sales Order API endpoints We plan to be functionally complete by Q1-2025 (31st of March 2025), end of life date for the endpoints will be announced at a later point. A number of Sales Order API endpoints will be removed as a part of the transition to the next generation ERP. The following API endpoints will be removed: GET /controller/api/v1/salesorder/{orderNbr} GET /controller/api/v1/salesorder/{orderType}/{orderNbr} GET /controller/api/v1/salesorder/{orderType}/{orderNbr}/rotrut GET /controller/api/v1/salesorder GET /controller/api/v1/salesorder/{orderType}/{orderNbr}/commissions POST /controller/api/v1/salesorder POST /controller/api/v1/salesorder/{saleOrderNumber}/action/cancelSalesOrder POST/controller/api/v1/salesorder/{salesOrderNumber}/action/reopenSalesOrder PUT /controller/api/v1/salesorder/{orderNbr} GET /controller/api/v1/salesorderbasic/{orderNbr} GET /controller/api/v1/salesorderbasic/{orderType}/{orderNbr} GET /controller/api/v1/salesorderbasic POST /controller/api/v1/salesorderbasic PUT /controller/api/v1/salesorderbasic/{orderNbr} POST /controller/api/v2/salesorderbasic POST /controller/api/v2/salesorder POST /controller/api/v2/salesorder/{saleOrderNumber}/action/cancelSalesOrder POST/controller/api/v2/salesorder/{salesOrderNumber}/action/reopenSalesOrder All functionality currently missing in the new Sales Order Service API will be added before these endpoints are removed. The list of affected endpoints might also be extended, so pay attention to future updates. For more information on how to use the Visma.net ERP Sales Order Service, please visit: https://community.visma.com/t5/News-in-Developers-Visma-net/Getting-started-with-the-first-neXtGen-service-Visma-net-ERP/ba-p/401436 Swagger for Visma.net.ERP.SalesOrder.API https://salesorder.visma.net/swagger/index.html       ... View more

API - Due dates for breaking changes Release Notes Documentation Due Deprecated parameter releasedBatch on  JournalTransactionV2 GET In version 10.39.0 we have introduced a new parameter, status, to filter on different statuses on journal transactions and marked releasedBatch  as deprecated. We will remove releasedBatch parameter on May 13th 2025. May 13, 2025 Planned removal of Sales Order API endpoints We plan to be functionally complete by Q1-2025 (31st of March 2025), end of life date for the endpoints will be announced at a later point. A number of Sales Order API endpoints will be removed as a part of the transition to the next generation ERP. The following API endpoints will be removed: GET /controller/api/v1/salesorder/{orderNbr} GET /controller/api/v1/salesorder/{orderType}/{orderNbr} GET /controller/api/v1/salesorder/{orderType}/{orderNbr}/rotrut GET /controller/api/v1/salesorder GET /controller/api/v1/salesorder/{orderType}/{orderNbr}/commissions POST /controller/api/v1/salesorder POST/controller/api/v1/salesorder/{saleOrderNumber}/action/cancelSalesOrder POST/controller/api/v1/salesorder/{salesOrderNumber}/action/reopenSalesOrder PUT /controller/api/v1/salesorder/{orderNbr} GET /controller/api/v1/salesorderbasic/{orderNbr} GET /controller/api/v1/salesorderbasic/{orderType}/{orderNbr} GET /controller/api/v1/salesorderbasic POST /controller/api/v1/salesorderbasic PUT /controller/api/v1/salesorderbasic/{orderNbr} POST /controller/api/v2/salesorderbasic POST /controller/api/v2/salesorder POST /controller/api/v2/salesorder/{saleOrderNumber}/action/cancelSalesOrder POST/controller/api/v2/salesorder/{salesOrderNumber}/action/reopenSalesOrder All functionality currently missing in the new Sales Order Service API will be added before these endpoints are removed. The list of affected endpoints might also be extended, so pay attention to future updates. For more information on how to use the Visma.net ERP Sales Order Service, please visit: https://community.visma.com/t5/News-in-Developers-Visma-net/Getting-started-with-the-first-neXtGen-service-Visma-net-ERP/ba-p/401436 Swagger for Visma.net.ERP.SalesOrder.API https://salesorder.visma.net/swagger/index.html     ... View more

The new base URL is now available at https://api.finance.visma.net. The deadline for the breaking changes is three months from now (Deadline: 10.06.2025).   Since the old URL will still be available for some time, the documentation will not be updated at this moment.    The original post has been updated.   Examples of these changes:   Old Base URL New Base URL GET https://integration.visma.net/API/controller/api/v1/account GET https://api.finance.visma.net/v1/account POST https://integration.visma.net/API/controller/api/v2/customerinvoice   POST https://api.finance.visma.net/v2/customerinvoice   ... View more

An upcoming webinar will focus on the breaking changes mentioned in this article. This session will address any questions you may have about the new API management. To participate, please register using the form linked below. Once the webinar date is confirmed, all registered attendees will receive an email with event details and an access link. We hope to see you there! Register for the webinar here: End of VNI - webinar ... View more