We have released the PATCH verb for our Sandbox environment together with some endpoints which use it. This enables the user to update an entity without providing the whole object in the body.

For further information on how to use the PATCH verb please check out our FAQ at https://developer.vismaonline.com/docs/patch-verb

Changelog

• added: PATCH v2/articles/{articleId}
• added: PATCH v2/companysettings
• added: PATCH v2/customerinvoicedrafts/{customerInvoiceDraftId}
• added: PATCH v2/customers/{customerId}
• added: PATCH v2/supplierinvoicedrafts/{supplierinvoicedraftId}
• added: PATCH v2/suppliers/{supplierId}

Please keep in mind that the endpoints above are currently experimental and subject to change. You can share your thoughts on our API community forum https://community.visma.com/t5/Visma-eAccounting-API/ct-p/IN_MA_eAccountingAPI and provide feedback.

We have now released webhooks for our Sandbox environment. The functionality is still in beta, but make sure to check it out!

Read more about webhooks here

Possibility for fetching either matched or unmatched bank transactions.

Changelog

• added GET /v2/banktransactions/{bankAccountId}/unmatched
• added GET /v2/banktransactions/{bankAccountId}/matched
• added GET v2/banktransactions/{bankAccountId}/{bankTransactionId}

BuyersOrderReference was added for customer invoices and customer invoice drafts that can be used when sending electronic invoices.

Changelog

• improved: GET and POST v2/customerinvoices
• improved: GET v2/customerinvoices/{invoiceId}
• improved: GET and POST v2/customerinvoicedrafts
• improved: GET and PUT v2/customerinvoicedrafts/{customerInvoiceDraftId}

Below you can see the updates from May.

New CompanyStatus property on /v2/companysettings that indicates if the company is Inactive, Active or ReadOnly.

/v2/accountbalances now has two new properties called AccountType and AccountTypeDescription. This is to make it easier to generate reports based on the different account types.

We have also made several bug fixes:

• /v2/customerinvoicedrafts lacked mapping of a few properties
• A few previously uncaught exceptions are now translated correctly to user-friendly errors
• Other minor bugfixes

Changelog

• improved: GET v2/companysettings.
• improved: GET /v2/accountbalances
• improved: POST/PUT /v2/customerinvoicedrafts

The WebshopOrderApi response object values were changed in order to align with the webshop order values in eAccounting web. The TotalAmountBaseCurrency and TotalAmountOrderCurrency will always be including vat.
The properties PricePerUnitInvoiceCurrency and Sum inside the WebshopOrderRowApi sub-object will be including vat and for webshop orders that have customers of type Company. For the webshop orders with customers of type Private individual the properties will be excluding vat if the ShowPricesExclVatPC in company settings is true and including vat otherwise.

The CompanySettingsApi model will now return null on the optional TaxDeclarationDate property when the AccountingLockInterval property in not of type TaxDeclaration.
This impacts the response object for GET /v2/companysettings, PUT /v2/companysettings and PUT /v2/companysettings/accountinglocksettings.

Changelog

• improved: GET v2/companysettings
• improved: PUT v2/companysettings
• improved: PUT v2/companysettings/accountinglocksettings

This impacts the way amount roundings are calculated on sales documents.

For example, lets take the amount 100.45 . Before this amount was rounded to 100.4. After this update, the amount will be rounded to 100.5.

Below you can see a list of all the endpoints in which this update was implemented

Changelog

• fixed: POST v2/customerinvoicedrafts
• fixed: POST v1/customerinvoicedrafts
• fixed: POST v2/customerinvoices
• fixed: POST v2/orders
• fixed: POST v1/orders
• fixed: POST v2/quotes
• added: POST v2/quotedrafts
• added: POST v1/customerinvoicespaidbycreditcard

Below you can see the updates from April.

Changelog

• improved: POST & PUT v2/customerinvoicedrafts. LineNumber is not required anymore on rows. Leave blank for automatic calculation based on row order
• improved: GET v2/statuses. The date for the latest bank statement now return the correct date.
• fixed: GET v2/customers. Now possible to filter on IsActive property
• fixed: GET v2/suppliers. Now possible to filter on IsActive property

The response status was changed from 200 to 201 with response object and location for the endpoints listed below. All affected partners are aware of this change.

Changelog

• improved: POST /v2/messagethreads/{messageThreadId}
• improved: PUT /v2/messagethreads/{messageThreadId}
• improved: POST /v2/messagethreads