Hi, You should have a look at the article linked in your other post as well as the charts of accounts. Does the account have a Tax category set?: We would also recommend that you try to recreate the same transaction manually in the UI. ... View more

Hi, Have a look at your segment keys and values for subaccount(ScreenId=CS203000&DimensionID=SUBACCOUNT&SegmentID=x), these are the values returned by the API. Click ion the segment ID to find the segment values. Apart from this, have you had a look at this article:  TaxID '01' cannot be found in the system ... View more

Hi, As far as we have been able to see this also happens in the UI. We would recommend that you get in contact with your partner service regarding this as it's a feature of the system and not a bug in the API. ... View more

Hi, We are aware and are looking into it: https://status.visma.com/incidents/xj1qjw02p3w4 ... View more

Hi, Yes that is correct, please let us know if you run in to any issues.  ... View more

There is no direct action for the supplierInvoices. But you can get the attachments for the invoice with the attachmentID on the supplierInvoice and then get by id via the "Attachment" endpoint. ... View more

I'm guessing based on the postcode that what you want is: Country: GB County: Oxfordshire City: Goring ... View more

Hi, There were some fields causing issues in your payload, for example the "accountUsedForPayment" was left empty, and the "county" field was incorrect.  With the payload below we were able to create the supplier, please try this: {     "number": {         "value": "1"     },     "name": {         "value": "Simplehuman"     },     "status": {         "value": "Active"     },     "documentLanguage": {         "value": "en-GB"     },     "supplierClassId": {         "value": "20"     },     "overrideWithClassValues": false,     "currencyId": {         "value": "EUR"     },     "vatRegistrationId": {         "value": "GB 831 1308 70"     },     "corporateId": {         "value": "831 1308 70"     },     "mainAddress": {         "value": {             "addressLine1": {                 "value": "5 Thames Court, High Street, Goring-on-Thames"             },             "addressLine2": {                 "value": "5 Thames Court, High Street, Goring-on-Thames"             },             "postalCode": {                 "value": "RG8 9AQ"             },             "city": {                 "value": "Oxfordshire"             },             "countryId": {                 "value": "GB"             },             "county": {                 "value": "Oxfordshire"             }         }     }, } ... View more

Hi, We are aware of the issue and were investigating it, you can follow the status here: https://status.visma.com/incidents/lp6cykqwk9jq ... View more

There was an incident related to the VNI service: https://status.visma.com/incidents/9v8w5nmk77n6 ... View more

Hi, What type of app is it? If it's tenant based you need to have someone with the "Integration Administrator" role add the app by for example invite codes.  Are you getting the correct token?   ... View more

Hi, We will not shut down your integrations now, we advise you as mentioned to contact your Business Unit if you are not ready. For the issue you receive, could you please list when they are happening and we can bring it up with development. Are there any of those issues that are not related to the initial on-boarding of new clients to the developer portal? Thank you.   ... View more

Please have a look at the segment key setup for your subaccounts(ScreenId=CS202000&DimensionID=SUBACCOUNT): The issue might be that there is some validation that is not properly done in V2 as well. Thank you. ... View more

Is it happening to clients that have been onboarded for longer than 24 hours or only for newly onboarded clients? Could you send us some examples of the issues with time stamp and requestId if possible.  Thank you.  ... View more

Hi, Most likely the company you are sending requests to have subaccounts required, and the subaccounts that are set up on the item you are using has a default value set that is shorter than the subaccounts that have been set up. ... View more

Hi, is this still happening? ... View more

Hi, For the incident where this error occurs after the initial request with a Service type token the status remains the same. The development team is still working on resolving the root cause, which seems to be that the user that is created after the initial request is not shared to the cache of all servers fast enough. When subsequent requests are sent, the loadbalancer might route it to a server where this user is not yet properly set up.     ... View more

Hi, In that case you don't have automatic numbering on your SO's, please disregard my comment about the field and include it in your request. Thank you.  ... View more

Hi, There were a couple of issues with your JSON: Ordertype SO does not support the "orderID" field It's not possible to set discountCode, discountPercent and discountAmount in the same request This will still generate an issue if you try to create a shipment from this as it has no warehouse, for more information on how the drop-ship flow works i Visma.Net, please have a look at this article: Create a drop-ship order flow   Try using the JSON below:   { "type": "SO", "date": "2023-12-14T00:00:00", "requestOn": "0001-01-01T00:00:00", "cancelBy": "0001-01-01T00:00:00", "description": "Prog-It testi", "status": "Open", "customer": { "id": "10001", "order": "10905" }, "shipping": { "scheduledDate": "0001-01-01T00:00:00", "contact": { "name": "JSC Tehnoinform" }, "intrastatTransactionTypeId": 0, "residentialDelivery": false, "saturdayDelivery": false, "insurance": false, "priority": 0 }, "orderLines": [ { "inventoryId": "nonstocktest", "description": "Coated Paper Stocklot", "unitOfMeasure": "STK", "quantity": 23.762, "unitCost": 0, "unitPrice": 855, "undershipThreshold": 0, "overshipThreshold": 100, "shipDate": "0001-01-01T00:00:00", "requestDate": "0001-01-01T00:00:00", "note": "Coated Paper Stocklot, 35 RO, 0 PX, 23762 KG NET/23762 KG GROSS, 48101300 CUSTOM CODE", "hasManualPrice": true, "commissionable": false, "supplierPrice": 0 } ], "useReplacementCostForMarginAndProfit": false, "originalOrderId": "10905" }     ... View more

What type of application/authentication are you intending to set up?  ... View more

Hi, There is an issue with the link that you posted yesterday, could you please compare your calls to these examples: Authorize: GET https://connect.visma.com/connect/authorize ?client_id=ClientID &response_type=code &scope=openid &redirect_uri=http://localhost &code_challenge=iMnq5o6zALKXGivsnlom_0F5_WYda32GHkxlV7mq7hQ &code_challenge_method=S256 Token: curl --request POST --url https://connect.visma.com/connect/token --header 'content-type: application/x-www-form-urlencoded' --data 'grant_type=authorization_code &redirect_uri=http://localhost &code=94c99b73c13c1e39f7b0a7d259628338 &client_id=ClientID &code_verifier=verifier' ... View more