Release Notes Documentation "Reverse and Apply to Memo" action on CustomerInvoice endpoint to trigger creation and automatic application of a credit note There is a new action "Reverse and Apply to Memo" in the CustomerInvoice endpoint, which triggers creation and automatic application of a credit note to a sales invoice. This is the same functionality as in the user interface. Release invoice endpoint not working properly  When using the "controller/api/v1/supplierInvoice/[invoicerefnbr]/action/release" API call, the system allowed you to release the same invoice several times creating multiple general ledger batches for the same document. Now the issue has been fixed, and the release invoice action will be locked during the process, and you will no longer be allowed to trigger the same action from different windows or tools multiple times. ... View more

In order to be able to add a new "Contact" to a Supplier or Customer via Visma.net ERP API, we can use the POST - Contact Endpoint.  Visma.net ERP API - Endpoint Documentation     Visma.net Financials ERP - Contact Module - ScreenID=CR302000     The connection between Supplier / Customer and Contact will be established by "businessAccount" field which is available in the POST - Contact DTO. "businessAccount": { "value": "string"   We need to set POST - Contact:"businessAccount" field's value with the "Customer ID" or "Supplier ID" depending on where you'd like to assign the "Contact". 1) POST Contact Endpoint (Sample payload) https://integration.visma.net/API/controller/api/v1/contact { "active": { "value": true }, "title": { "value": "Doctor" }, "firstName": { "value": "Crowley" }, "lastName": { "value": "Ozy" }, "position": { "value": "Position" }, "businessAccount": { "value": "Supplier or Customer ID" }, "sameAsAccount": { "value": false }, "address": { "value": { "addressLine1": { "value": "A1" }, "addressLine2": { "value": "A2" }, "addressLine3": { "value": "A3" }, "postalCode": { "value": "1313" }, "city": { "value": "test" }, "countryId": { "value": "01" }, "county": { "value": "02" } } }, "email": { "value": "test@gmail.com" }, "web": { "value": "web" }, "phone1": { "value": "0002" }, "phone2": { "value": "56565655" }, "phone3": { "value": "656565" }, "fax": { "value": "65656565" }, "contactMethod": { "value": "Any" }, "doNotCall": { "value": true }, "doNotFax": { "value": true }, "doNotEmail": { "value": true }, "doNotMail": { "value": true }, "noMassMail": { "value": true }, "noMarketing": { "value": true } }   2) Financials ERP UI Output Customer: Supplier: ... View more

Release Notes Documentation A new field “Tax total” has now been exposed via the GET  ExpenseReceipt endpoint DTO A new field “Tax total” is now available in the response body for the ExpenseReceipt endpoint with the GET operations. ... View more

Release Notes Documentation New POST operations on Expense Claim endpoint: put On hold, Submit, Send to approval There is a new improvement on the Expense Claim endpoint. Third party integrators are now able to submit, send to approval and put On hold expense claim using the following new POST operations on the Expense Claim endpoint: - POST /api/v1/expenseClaim/{expenseClaim}/action/hold; - POST /api/v1/expenseClaim/{expenseClaim}/action/submit; - POST /api/v1/expenseClaim/{expenseClaim}/action/approval ... View more