Hi all,   We POST a supplierinvoice (See POSTSupplierInvoice.json).   The invoice has the status "In Balance" in which we can perform a PUT to modify the paySelected property of the SupplierInvoice (See PUTSupplierInvoice.json).   When we "Release" the invoice via de release endpoint, the SupplierInvoice has the status 'Open'.    When we want to perform a PUT to modify the paySelected property, we get the following error:   { "message": "Error updating supplier invoice. Invoice 200054 cannot be updated because it is already Released." }   I also tried to perform a PUT with only the PaySelected, but the same error occurs.   Now comes the interesting part: When I open the SupplierInvoice in Financials, I can adjust the PaySelected combobox and save the SupplierInvoice! So there is a difference between the User Interface and the API.   Best regards!         ... View more

We POST a SupplierInvoice with a different percentage (60% in this example) as which is filled on the Supplier card.   This is the JSON:     { "documentType": { "value": "Invoice" }, "date": { "value": "2020-02-01" }, "financialPeriod": { "value": "202002" }, "supplierReference": { "value": "1985011" }, "description": { "value": "Memo/5001" }, "supplierNumber": { "value": "243234" }, "currencyId": { "value": "EUR" }, "paymentRefNo": { "value": "1985001" }, "creditTermsId": { "value": "14" }, "cashDiscountDate": { "value": "2020-02-01" }, "branchNumber": { "value": "OrgWater" }, "taxCalculationMode": { "value": "TaxSetting" }, "supplierTaxZone": { "value": "NL" }, "applyRetainage": { "value": true }, "taxDetailLines": [{ "taxId": { "value": "3 " }, "taxableAmount": { "value": 100.00 }, "vatAmount": { "value": 21.00 } }], "invoiceLines": [{ "operation": "Insert", "lineNumber": { "value": 1 }, "transactionDescription": { "value": "Memo/5001" }, "quantity": { "value": 0 }, "costInCurrency": { "value": 100.00 }, "accountNumber": { "value": "4610" }, "vatCodeId": { "value": "1" }, "retainagePct": { "value": 60 }, "curyRetainageAmt": { "value": 60 }, "branchNumber": { "value": "OrgWater" }, "projectId": { "value": "X" } }] }     But the API still applies the percentage from the Supplier?   ... View more

Hi,   For example: A customer is processing a Purchase Invoice, with the following data:   - Supplier Number: 3366 - Invoice Number: 19852231   How can we check via the API if this Invoice Number is already in the administration?    I see this GET:     But the Invoice Number is not the actual Invoice Number, but the Entrynumber.     ... View more

Post a supplier with a supplier number with leading spaces can not be used anymore. "1234" works, but " 1234" cannot be used anymore. https://integration.visma.net/API/controller/api/v1/supplier { "number" : { "value" : " 1234" }, "name" : { "value" : "Elvy" } } ... View more

Hi,   I want to add a receipt line using the API: supplierInvoice. Using the UI, I have 150 items. I select the line:   I then adjust the quantity to 4 pieces. Works perfectly.   Using the API i can use: "addPOReceiptLines": [{"poReceiptNumber": {"value": "000002"},"poReceiptLineNumber": {"value": 1}}] But then all the 150 items are used, i cannot adjust anything, because all functionality is done by the API.   Can you help me how i should do this using the API ?   Thanks ... View more

Hi,   We want to send a purchase invoice to Visma Approval via de API. Is there an import for sending a purchase invoice to Approval after we POSTED the purchase invoice? ... View more

Hi,   As far as we can see we can only download the SubAccount. Is it also possible to download all the Segment values?   Because we now have an issue that we want to select a Segment value which is not available in the SubAccount, because the Segment key has not checked 'Validate'   ... View more

We can set the checkbox 'Validate' to a segment key:     How can we retrieve this via de API? Because when we GET the subaccounts, the property Validate is not in de segment tree:   ... View more

After receiving an token using: https://community.visma.com/t5/Knowledge-base-in-Developers/OAuth-2-0-Authorization-Flow/ta-p/270859   i.e. https://integration.visma.net/API/resources/oauth/authorize?client_id=xxxxxx&redirect_uri=https%3A%2F%2FVismanet.xxxxnl&scope=financialstasks&response_type=code&state=ElvyDSxxxxx&force_login=1   and then   code=a6d426fd-9bd6-4af8-bf33-6b6751a46c89&client_id=xxxxx&client_secret=yyyyyy &redirect_uri=https://Vismanet.xxxxx.nl&scope=financialstasks&grant_type=authorization_code   {"token":"xxxxxxxxxxxxxxxxxxxxx","token_type":"bearer","scope":"financialstasks"}   somewhere along testing (after 1 hour i guess) it becomes invalid. How can we refresh the token ?   Thanks. ... View more