👍

CreditedByApi

CreditedByApi has been added to the CustomerInvoiceApi object, an object that contains information about the invoice that the current invoice is credited by.

👍

CurrencyCode

CurrencyCode has been added to the AttachmentResultApi object, representing the currency used on the supplier for the attachment.

👍

PUT /v2/fiscalyears/{fiscalYearId}

This endpoint provides the possibility to lock and unlock a given fiscal year using the property IsLockedForAccounting.

👍

Id

Id was previously missing as a navigation property for each QuoteRowApi object. As all other navigation properties, it's read-only and generated by eAccounting.

👍

OssCodeType

OssCodeType is a readonly property added to the response object of the endpoint GET /v2/vatcodes. The values are 0 = None, 1 = Sales, 2 = Vat with 0 = None as default value. Values 1 = Sales and 2 = Vat are only returned if the company has the setting Apply rules for One Stop Shop (OSS) activated.

👍

TransactionDate

TransactionDate is a readonly property added to the response object of the endpoint GET /v2/attachments and GET /v2/attachment/{id}. The value is set if the source image has been interpreted. It represents the date of the transaction for the source document; eg invoice date for a supplier invoice, payment date for a receipt.

📘

Use prompt=select_account to always prompt the selection of company

Up until now acr_values=service:44643EB1-3F76-4C1C-A672-402AE8085934+forceselectcompany:true in combination with prompt=login was used to ignore the standard company setting in Visma Online and always prompt the user with the selection of company.
Now you can use prompt=select_account to achieve that. Both options for prompt can be used to force login as well: prompt=login+select_account.

The recommandation is to use prompt=select_account&acr_values=service:44643EB1-3F76-4C1C-A672-402AE8085934.
Please check the authentication page for more information.

Disclaimer: prompt=select_account does not work in Sandbox. Since that is a test environment there are differences compared to Production in regards to the Identity Server implementation. We are working on aligning them in the near future.

🚧

Payments endpoints will not allow future payment date

In order to align to the behaviour inside eAccounting the API will not allow payment dates in the future when using POST /v2/customerinvoices/{invoiceId}/payments and POST /v2/supplierinvoices/{invoiceId}/payments endpoints. A validation exception will be returned in that case.

🚧

New mapping on empty InvoiceAddress1 and InvoiceAddress2 for POST /v2/customerinvoicedrafts

In order to fix a bug and align to the behaviour inside eAccounting when doing a POST on /v2/customerinvoicedrafts and not providing a value for InvoiceAddress1 and InvoiceAddress2 the values will be taken from the customer.

ReplaceUnitPriceWhenZero: