New validation error on POST /v2/customerinvoices - RotReducedInvoicingPropertyName
In order to fix a bug and align to the behaviour inside eAccounting the API will now return a
2000 - DataModelValidationErrorwhen usingPOST /v2/customerinvoiceswith a setRotPropertyTypebut emptyRotReducedInvoicingPropertyName.
Backorder:
If an existing order has a delivered quantity that is smaller than the ordered quantity, this endpoint will take the order id and automatically create a backorder for the remaining amount. The order must be in status shipped or invoiced and may not have an existing backorder already.
Changelog
Address properties on v2/customerinvoices are not read-only anymore.
Changelog
InvoiceAddress1, InvoiceAddress2, InvoicePostalCode, InvoiceCity, InvoiceCountryCode, DeliveryCustomerName, DeliveryAddress1, DeliveryAddress2, DeliveryPostalCode, DeliveryCity and DeliveryCountryCode can now be set using POST v2/customerinvoices endpoint.eAccounting has been extended with some article updates and additions. They are all related to stock and stock handling. There's a few updates to the API related to this aswell:
Changelog
IsStock on v2/articlesStockLocationReference on v2/articlesFreightCosts on v2/articlesFreightCostsManuallyChangedUtc on v2/articlesUpdateStockPrices on v2/articlesBarcodes on v2/articlesStockValue on v2/articlesActivatedModules property on v2/companysettingsRead more about these at the API Reference
The patch verb was released a few months back in our Sandbox environment together with some experimental endpoints. After further investigation and self assessment we decided to postpone the PATCH verb implementation in the production environment in order to implement a solution that alligns more with the industry standards and with the quality and structure that the Visma eAccounting API has.
We are very grateful for all your feedback, please don't hesitate to contact us with more. Reach out to us either by sending an email to [email protected] or post in our forum thread.
In eAccounting, the Gross price and Net price of an article are dependent on the selected vat rate. For example if you have selected a 25% vat rate and Net price is 100, Gross price must be 125. The same logic is valid if you enter 125 Gross price, Net price must be 100. In order to preserve data consistency we have added a validation which validates the Net and Gross price based on the selected vat rate.
Changelog
Error code number changed when cost centers not allowed
In order to be more accurate with the error code types thrown, the
4000 - Conflictwas changed to a2000 - DataModelValidationErrorin the cases when a cost center is used in combination with an account that does not allow cost centers.VouchersV2andPaymentVoucherV2endpoints are affected by this change.
We have now implemented support for Dutch companies for creating payment vouchers.
Changelog
We would like to kindly remind you that the last day when we are going to support requests with TLS 1.0 and TLS 1.1 will be 31st December.
If there are any changes required on your side please consider acting on them until the deadline.
Thank you.
Below you can see that latest improvements and updates :
/v2/companysettings now has three new properties called CompanyIdentifier , UsesRotReducedInvoicing and CompanyRotRutSettings .
/v2/supplierinvoicedrafts now has four new properties called CreatedUtc , ModifiedUtc . VatAmount and SkipSendToBank .
/v2/supplierinvoices has been added the property SkipSendToBank .
/v2/articles has been added the property CreatedUtc .
Bugs which have been addressed to and fixed:
/v2/customerledgeritems/customerledgeritemswithvoucher now allows a 0.05 maximum difference between Vat Amount in the header and the one calculated in eAccounting.