The e-invoice is a new feature in sevdesk, which allows you to send invoices to your customers in a digital way.

Announcement

Due to maintenance work, the sevdesk application will be unavailable on Thursday, 24.10.2024 from 21:00 for approx. 60 minutes.

We are introducing new endpoints for the creation of check accounts, they are now tailored better to their specific use cases.

Enshrined objects should not be modifiable.

Status Quo:
In sevDesk system version 1.0 it is possible to directly set and unset / change the value of the property enshrined for Invoice, Voucher, CreditNote and CheckAccountTransaction. This is already not possible in sevDesk-Update 2.0.

Future:
The property enshrined must be set via the dedicated endpoint. It can no longer be set directly.

We have noticed that some of our validations for orders, invoices, vouchers and credit notes are returning a HTTP status code of 500 instead of 422. This is a bug that will be addressed.

To better distinguish between open, partially paid and paid invoices we, will introduce a new status.

In the future, we will provide our customers with more guidance and help them to avoid error in their accounting. To this end, we are introducing fundamental changes to our software, which will take the form of a major update. In addition, new functions will be made available that offer our customers even more insights & therefore opportunities for their company. In the documents linked below we will focus on the changes of the sevDesk-Update 2.0 for our public API. The PDF is also including a detailed timeline for the roll-out of all changes and the migration of users.

Handbook sevDesk-Update 2.0:

It will no longer be possible to change the status of invoices and credit notes manually. Instead, the respective endpoints must be used.

Saving proposals (aka estimates) / orders / delivery notes with a negative total will result in a validation exception. This is necessary so that the resulting invoices can be booked correctly.

Status Quo:
The invoice date of a final invoice can be earlier than the date of an associated partial invoice.

Future:
The invoice date of a final invoice must be on the same day or later than the highest date of the associated partial invoices.

Affected endpoints: