👍

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.

👍

CurrencyCode

CurrencyCode 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 currency code for the amount from the source document.

📘

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:

This new property allows better control when creating an invoice draft that contains rows which have the unit price set to 0. The main reason for this change was to have the same behavior in the API as we have in the web application.

When the new field is set to true an unit price of zero will be replaced with the unit price of the article from the article register. When set to false it allows creation of drafts with unit price 0 on one or more rows. Rows with an unit price other than 0 are not affected by this property.

The default value is false.

Release of a highly requested feature by AOs in collaboration with customers.
This will enable end users to save manual journal entries as a draft and then allow the AO to review them and edit if needed before posting them to ledger.
The new endpoints enable the possibility to create, get, update, delete a draft or convert it to a voucher.

Changelog

• added: POST v2/voucherdrafts
• added: GET v2/voucherdrafts
• added: GET v2/voucherdrafts/{voucherDraftId}
• added: PUT v2/voucherdrafts/{voucherDraftId}
• added: DELETE v2/voucherdrafts/{voucherDraftId}
• added: POST v2/voucherdrafts/{voucherDraftId}/convert

New properties on v2/companysettings.

Changelog

• UseAutomaticVatCalculation: optional boolean. When set to true, vat rows are added (when creating a voucher for example), if the account used relates to (SE, NO, FI only)
• ShowCostCenterReminder: read-only boolean. Customer has opted to get reminded about adding a cost center when creating invoices.
• ShowProjectReminder: read-only boolean. Customer has opted to get reminded about adding a cost center when creating invoices.

🚧

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 - DataModelValidationError when using POST /v2/customerinvoices with a set RotPropertyType but empty RotReducedInvoicingPropertyName.