Hi,   Sorry if I was unclear, I have verified that everything works as it should in Financials ERP UI. The problem only occurs when we book a journal via the integration, before updating we could enter the segment value as follows: "segmentId": "3", "segmentValue": "32"   After your update, we need pad the segmentvalue "segmentId": "3", "segmentValue": "  32"   We have updated our integration to do this now and updated all our customers with a new version so the problem is no longer critical. ... View more

Hi,   After some more testing, we can state that the problem only applies to journal transaction, if we book with the same values on the supplier invoice, it works with these values: "segmentId": "3", "segmentValue": "32" The proposal  with zeros as padding does not work: "segmentId": "3", "segmentValue": "3200" On the other hand, it works if we pad with spaces: "segmentId": "3", "segmentValue": "  32"   Code parts should work in the same way regardless of whether it is journal transaction or supplier invoice? ... View more

Hi, After a lot of investigation, we have come to the following conclusion. Before the update, it was possible to book on a code part that did not contain all the characters. Examples: Default Code parts: 0-00-0000-00000 Works in UI: 0-00-0000-45 (works also via API, if the two char value is last in the code part) Works in UI: 0-00-32-00000 (the value 32 does not work via API after update)         This works { "operation": "Insert", "lineNumber": {}, "accountNumber": { "value": "5800" }, "subaccount": [ { "segmentId": "1", "segmentValue": "1" }, { "segmentId": "2", "segmentValue": "00" }, { "segmentId": "3", "segmentValue": "0000" }, { "segmentId": "4", "segmentValue": "45" } ], "debitAmountInCurrency": { "value": 189.41 }, "vatCodeId": { "value": "01" }   This does not work: { "operation": "Insert", "lineNumber": {}, "accountNumber": { "value": "5800" }, "subaccount": [ { "segmentId": "1", "segmentValue": "1" }, { "segmentId": "2", "segmentValue": "00" }, { "segmentId": "3", "segmentValue": "32" }, { "segmentId": "4", "segmentValue": "00000" } ], "debitAmountInCurrency": { "value": 189.41 }, "vatCodeId": { "value": "01" }     ... View more

Hi,   We rewrote our integration last night according to your recommendation and have now updated the integration for all our customers, it seems to be working fine. But we have a large number of cases to solve with our customers regarding bookings that were made until we got our new solution in place.   /anders ... View more

Hi, Do you continue to look on your side at what may have happened? Even if we manage to make the changes on our side, we have a large number of customers who have problems and who were affected yesterday without us making any change.   /anders ... View more

Hi,   We have missed that functionality, I will look at it immediately   /anders ... View more

Hi, We can't o that, we need to know what referenceNumber we got on the booking. Since we just get an empty response on successful booking we need to fetch the booking we just made and verify the result.  We can't do that if we don't now the referenceNumber.   /anders ... View more

We are using  https://integration.visma.net/API/controller/api/v1/numberSequence/APBILL To get lastNbr and we are using the result + 1  as referenceNumber on the supplier Invoice booking, booking works but the Invoice gets another referenceNumber.   /anders  ... View more

Hi, Yes, it has always worked fine for several years, looks like it started around lunchtime yesterday We currently have about 180 companies affected by this problem and we have not made any changes to our side.   /anders ... View more