Maintenance work
AnnouncementDue to maintenance work, the sevdesk application will be unavailable on Wednesday, 04.12.2024 from 22:30 for approx. three hours.
NEW feature: file an e-Invoice as a receipt (voucher) via API
The adapted functionality allows you to file the machine readable/processable e-Invoice formats into the sevdesk platform.
Enabling voucher/receipt creation with eInvoice document
We are enabling XML as a valid file type for voucher creation. The endpoint /api/v1/Voucher/Factory/uploadTempFile will accept files in XML format as well as a PDF with embedded XML (i.e. in the ZUGFeRD format). The voucher creation process does not change.
Note that eInvoice files can not be merged with other documents in a single voucher object, to ensure that all data is stored in its original form.
Documentation:
https://api.sevdesk.de/#tag/Voucher/How-e-invoice-works
Affected customers:
The described functionality is only available to customers on system version 2.0
Release: Changes to the endpoint /api/v1/Voucher/Factory/uploadTempFile are already live since 05.11.2024.
NEW feature: create an e-Invoice via API
The e-invoice is a new feature in sevdesk, which allows you to send invoices to your customers in a digital way.
Maintenance work
AnnouncementDue to maintenance work, the sevdesk application will be unavailable on Thursday, 24.10.2024 from 21:00 for approx. 60 minutes.
Change in creation of check accounts
We are introducing new endpoints for the creation of check accounts, they are now tailored better to their specific use cases.
Setting or changing the property ‘enshrined’
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.
Changing some 500 HTTP status codes to 422
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.
New invoice status: Partially paid
To better distinguish between open, partially paid and paid invoices we, will introduce a new status.
sevDesk-Update 2.0 - API Changes
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:
Changing the status for invoices and credit notes
It will no longer be possible to change the status of invoices and credit notes manually. Instead, the respective endpoints must be used.