Hi Allan!   I see that there has been some small changes on the two latest releases, but I'm not sure if it is the reason why your customers are suddenly experiencing more issues. I've checked with our developer team and only that comes in mind to have smaller updates in the PUT request. Unfortunately there is no 100% guarantee that this will work. You could also try to do this manually in the UI until the next release.   - Suzdar ... View more

Hi,    That seems to be exactly whats happening, that also explains why some orders works and some dont.  Thank you. ... View more

Hi, Thank you.   Yes, I have tried that. I get a 204 response but the transfer number field is not updated/populated on the inventory receipt, so no luck there either.   Example: PUT: https://integration.visma.net/API/controller/api/v1/inventoryReceipt/2700193 Headers: { Accept: application/json Authorization: <hidden> Accept-Encoding: gzip Accept-Encoding: deflate Request-Id: |mNxxPaa2S54=.73b6c807_5. Content-Type: application/json; charset=utf-8 Content-Length: 38 } {"transferNumber":{"value":"2700188"}} Response: 204 No Content Headers: { Date: Fri, 25 Aug 2023 14:50:32 GMT Server: Nginx Strict-Transport-Security: max-age=31536000; includeSubDomains Strict-Transport-Security: max-age=31536000; includeSubDomains ipp-request-id: f8e62102-bed6-49b2-96e7-fc42bdce0789 X-Content-Type-Options: application/json Pragma: no-cache X-Handled-By: Visma-PX.Export/AuthenticationManagerModule Referrer-Policy: origin-when-cross-origin VnfInstanceId: ERP_SE_DEMO_0017 Cache-Control: no-cache X-XSS-Protection: 1;mode=block Set-Cookie: <crumbs>; path=/; secure; expires=Thu, 24-Aug-2023 14:50:31 GMT; HttpOnly Expires: -1 }   ... View more