Easy oversight, I did not notice that you had written the field that way either. Glad that it works.  ... View more

Hi, So this is a Get? Is the field filled in the UI? Was it posted via the API, if so, please share the JSON so we can test it on our end. If it was posted via the UI, please send a screenshot of the order.   ... View more

Hi, What endpoint are you calling? Please provide the full URL as well as the full JSON when you are creating a post. Thank you.  ... View more

Hi, Depending on the type of transactions you are looking for there might be some webhooks you are interested in, for example: salesorder_changed purchaseorder_changed arinvoice_changed You can read about how to set this up here: Visma.net ERP API Webhooks Setup API & ERP UI (Event - Subscription - Notification)   If you want to use JournalTransactions, we would recommend that you check the endpoint with the "LastModifiedDateTime" & "LastModifiedDateTimeCondition", where you get the result since the last time you checked:   Update: In JournalTransactions/V2, there is no need to specify the condition, it is set ">=" by default, the usage with the condition still applies to other endpoints.    Example: GET  v2/journalTransactions?LastModifiedDateTime=2021-06-10   This would return only the transactions that have been modified since 2021-06-10.   Parameter usage:   LastModifiedDateTime=time As of today Filtering Parameters does not accept certain characters such as W-Z These are the formats for Filtering *2001-01-01 *2001-01-01 13:13:13 *2001-01-01 13:13:13.133 LastModifiedDateTimeCondition=Operator Supported comparative operators for LastModifiedDateTime Conditions on filtering  > - Greater than < - Less than <= - Less than or equal to >= - Greater than or equal to   ... View more

Hi, The invoice printed should be printed as per the settings on the customer(ScreenId=AR303000):   We were not able to reproduce this with the standard dutch template, neither via the API or the UI, in both cases the date was printed as d/m/yyyy:   Could you please have a look at this setting and send us screenshots of the invoice printed in the UI and via the API? If you do not want to post it here, you can send it in an email to developersupport@visma.com.   Thank you.  ... View more

We can confirm even sending the minimum fields result in the same error: {     "landedCost": [         {             "operation": "Insert",             "landedCostCode": {                 "value": "TESTCODE"             },             "supplierID": {                 "value": "50000"             },             "purchaseInvoiceNbr": {                 "value": "SupRef"             },             "locationId": {                 "value": "Main"             },             "description": {                 "value": "Test"             }         }     ] }   It has been reported to the development team. Thank you.  ... View more

Hi, I would recommend having a look at this article, it goes over how tax zones, categories and id's combine to set the rate: TaxID '01' cannot be found in the system   Please let us know if you are still struggling after checking it out. ... View more

Hi, We're having a look at this and will get back to you. ... View more

Hi, We have asked the development team for another update on this case. We recommend that you lift this with your partner service as well. ... View more

Hi, When using the print operations the standard template for the document is used. Have you tried printing the same report from a different company? Is it only for this company you get this format? ... View more

Hi, You need to tick the box for "Webhook notifications" on the customers: ... View more

Hi, Currently, there is no parameter exposed for the status. We have a case in the backlog for this.   Voting/Commenting on this case can be done here: Expose Supplier Invoice Document "Status" as a filtering parameter via "SupplierInvoice" Endpoint   There is no way to filter for when an incoive has been closed, if this is a functionality you need, please create a post in the Ideas part of the forum.  ... View more

Hi, There are cases for this in the current backlog: Create/Update CustomerSalesPrice API, Vendor Sales Price endpoint   If you need this functionality, we recommend that you go to those Ideas and vote for them.   Thank you.  ... View more

Hi, Apart from the values being available in the segment keys subaccount window(ScreenId=CS202000&DimensionID=SUBACCOUNT): Please also make sure that the subaccount is setup in ScreenId=GL203000: ... View more

As Florian mentioned, please include the value of your subaccount as such: Also, the document type should be "Invoice":   Please correct this and let us know if you are still having issues.   Thank you. ... View more

That sounds like a good idea, if this is an improvement you'd like to see. Please post it in the "Ideas" part of the forum.  ... View more

Hi, We have asked for an update regarding this case. If this is something you need, we recommend that you vote for this idea.  ... View more

Hi Marius, As this is an improvement and there are currently high priority cases ahead of it in the backlog, there is no current date planned for this. Here is the Idea's post for the case: Expose "paymentDetails" from Supplier -> Locations To help with prioritising the case, you can vote for the Idea. Further progress will be posted in the Idea post.    Thank you.  ... View more

This is currently in the backlog. ... View more

Could you please send us your api client ID and the company ID to developersupport@visma.com ... View more

Hi, We tried on our end and have no issues getting the PDF via postman or swagger. Error code 5102 is usually a network issue and should be retried. How often are you seeing this? Does it always happen to the same invoices? ... View more