Hello. Currently, this is also valid on the following fields for the API transactions with released "Supplier/Purchase Invoice" documents. Purchase (Supplier) Invoice header  -Payment Ref No -Due Date -Cash Discount Date Financial Details [Payment Information] -Charge Bearer -Priority -Payment reporting code -Payment Message -Pay date -Payment Location -Payment Method -Cash Account -Approved for payment (paySelected)   As aforementioned, values can be set by sending FT=1 parameter in the request URL as a workaround at the moment. PUT:   https://integration.visma.net/API/controller/api/v1/supplierInvoice/<InvoiceNumber>?FT=1   { "paySelected": { "value": true } } ... View more

Hello,   One currency ID can only have one exchange rate with the same Currency / Currency  Type / Effective Date / Currency Rate at the same time. In this way, as it mentioned above, this can be fetched via  e.g. https://integration.visma.net/API/controller/api/v1/currency/exchangerates/EUR/2021-03-22 Currency exchange rates can be recorded any time for a particular currency. Each record contains the date when the rate becomes effective. When the next record for the same rate type is entered, the rate value becomes a historical rate and can be used as the effective rate for operations that take place between the two dates. Historical rates are stored in the database for all the financial years defined in the system. We do not recommend that you change the value of the exchange rate if any transactions were based on the historical rate. You can use the historical rates for entering back-dated transactions and for calculating realized and unrealized gains and losses. ... View more

Hello,    This feature is currently available on the following endpoints, so please make sure you are using the "overrideNumberseries" on POST CustomerInvoice V2. POST Customer POST CustomerDebitNote V2 POST SalesOrder POST Supplier POST Journal Transaction V2 POST PurchaseOrder POST Supplier Invoice POST CustomerCreditNote V2 POST CustomerInvoice V2 Visma.net Financials API updates for version 8.25 (September 2020) Override number series for POST CustomerInvoice V2 You are now able to override the number series of a customer invoice by specifying the field overrideNumberSeries=true when creating a customer invoice. This functionality has to be enabled in the Number series (CS201010) window by selecting option Allow manual numbering on imports. You also can specify a longer customer invoice number when using overrideNumberSeries than what is specified in number series for customer invoice.  1-Set Allow manual numbering on imports = true on the UI 2-Set "overrideNumberSeries": { "value": true }, 3-Add  "referenceNumber": { "value": "string" }, ... View more

Hello Tomi,    This improvement request is in our backlog and the posted "Idea" can be found at Webhook subscription for Purchase receipt Please feel free to add comment and give kudos which will eventually help our development team with prioritization during the sprint planning. Thanks. ... View more

Hello Mathias, Could you please send us your integration's API Client ID that is used while generating the token ? You can send this to developersupport@visma.com    CompanyName seems to be "Skal", could you confirm ?  Thanks. ... View more

Hi, At the moment, none of the wenhook events supports deletion. You can post it in the Idea's part of the forum if you would like to see this implemented.  ... View more

Hi, Inventory does nos have kitAssembly or stockComponent allocations, what are you trying to do via that endpoint? As far as we can see, both your images are from kitAssembly, is this correct?   Kitassembly does not have stockComponent allocations exposed for post/put via the API currently: Please create a post in the Ideas section of the forum. Please describe your use case as well as possible. This allows others to vote for your suggeston, which in turn influences the assessment and implementation process.  ... View more

Hi, Currently there does not seem to be a solution for this implemented.  We would recommend that you post the suggestion to implement this in the Ideas section.  ... View more

Ok, good to hear it is solved. Yes, we agree that the error seems to be missrepresenting the issue.  ... View more

Visma.net ERP version 8.33 will be released 19/01  22:30 CET. There will be short downtime between 22:30 and 00:30 This is because we have an issue with the upgrade process that prevents us from upgrading databases without downtime. In the coming releases this will be resolved. status.visma.com will be updated accordingly.  We will keep you informed of any changes. Scheduled Maintenance for Visma.net ERP Visma.net Financials API updates for version 8.33.0 (January 2021) ... View more