We have this issue too. We do the following:   create an empty purchase receipt: {  "receiptType": {  "value": "PoReceipt"  },  "supplierId": {  "value": "C00059"  },  "date": {  "value": "2025-01-31"  } } After doing this we get a purchasereceipt number which is not visible in the Visma UI. Correct?   create a purchase orderline by using linenumber from purchaseorder {     "purchaseOrderLines": [         {             "orderNbr": "PO11250001",             "lines": [                 {                     "lineNbr": "1"                 }             ]         }     ] }   Linenumber 1 in the purchaseorder exists but we are getting error: {     "message": "Error adding purchase orders to receipt: Purchase order line 1 could not be found for order number PO11250001 " } ... View more

i Got it working my local cashe where playing a trick on me Ctrl+Shift+R got it working. have u seem my question regarding findings in regards to warehouse and toWarehouse filtes ?  it seems like toWarehouse filter only works if used WITH warehouse and not alone  is this intended ?  ... View more

We also need crossReference for POST, in the current API and NextGen.   ... View more

Thanks for the update Magnus. Hope it will go to development plan soon.  ... View more

Thank you for the information. This will be investigated. ... View more

We're experiencing the same issue across several customers / companies ... View more

We have asked the team for an update on a possible ETA. Information will be posted in the Idea's thread when we have more information. If you have any concerns regarding the time to implement this, we recommend that you contact your partner service.  ... View more

Thanks for the information Kjetil. ... View more

Hei Erik, no problem 🙂 Might be related to the Non-stock item's properties so if you could share the details of the Purchase Order / Receipt and the Inventory via developersupport@visma.com after testing then we can check this out together again. Cheers !   ... View more

Hi, Please follow this status page: https://status.visma.com/incidents/8b8nvbg7fqjm   This is currently being investigated. ... View more

Please send the API Client ID  & Approximate Date/Time of the request/s to developersupport@visma.com   Could you please make sure that there are invoices in the company matching with the specified lastModifiedDateTime&lastModifiedDateTimeCondition ? ... View more

Hi Kjetil, Just wanted to update you, the case has been picked up from the backlog and has been assigned to a developer. Thank you for your patience.  ... View more

Hi  Not as far as I can see. ... View more

Today between 10:34 - 10:44 one of our nodes experienced a misconfiguration which led to routes of endpoints being not available on that node. This was quickly discovered and fixed. Sorry for any inconvenience. ... View more

We have scaled out the application further, please let us know if you are still having issues. We are still investigating the cause for this.  ... View more

This issue has been planned to be fixed in 8.48 version. Visma.net Financials API updates for version 8.48.0 (May 2021)  ... View more

This is the information that we received from the infrastructure team about how that specific exception is built. If there are inconsistencies in the scenarios of when the exception thrown, please inform us on the followed steps before you've received the response so that we can check this out in detail. ... View more

Last reported connection problem was at 9:12 so it is resolved. ... View more

Thank you for checking. I'll create a new thread with a different issue when adding lines "manually".  ... View more

Thank you, regarding the confirmation it's also confirmed it happened in the GUI and it will be reported accordingly.   ... View more

Thank you for confirming it works, please let us know if you have any other issues. ... View more

As far as we can see, nothing out of the ordinary occured this morning. We can see some 502's in the logs, but more then usual. How many 502's were you getting? Was this under a longer period or just around 7.30? ... View more