If you're like me and this issue was holding up going live with an integration, I've changed back to the old VNI authentication for just this endpoint, which works as expected. ... View more

I have the exact same issue and error, and have been trying to get this working for the last week.   When I change the API authentication back to the older VNI authentication, using the exact same body other than the different bearer token and including ipp-company-id headers, it works fine. But using the new Visma Connect Authentication I get this error "Error creating supplierInvoice. No access to branch 101". I am able to GET data without issue, just cant POST to this endpoint.   As such, this implies its not a user permission issue (as it works using old authentication under my same user account), but rather an issue with the permission / scope of the Visma Connect authentication. Perhaps its not respecting the vismanet_erp_service_api:create scope in the token request? The token request does respond with that scope confirmation though:  "scope": "vismanet_erp_service_api:create vismanet_erp_service_api:read vismanet_erp_service_api:update" ... View more