Overview

Kyvento focuses on billing – ongoing accounting (bank reconciliation, document management, annual financial statements) deliberately stays with your accounting software or tax advisor. There is currently no native one-click connection to Lexoffice or sevDesk. This article shows the three ways your billing data reliably reaches your accounting anyway.

Way 1: DATEV export (recommended for tax advisors)

The standard route for working with your tax advisor's office: the DATEV export delivers a posting batch in the EXTF CSV format that DATEV systems read directly. Some accounting programs can also import DATEV posting batches – whether yours is one of them can be found in its documentation. Details in the article "Setting up the DATEV export".

Way 2: CSV exports

On the "Exports" page, you export your data sets as CSV – one tile each for customers, invoices, subscriptions, payments and products. CSV files can be imported into practically any software or processed further in spreadsheets. You download the invoice documents themselves as PDF from the respective invoice detail page; the PDF already contains the embedded e-invoice data (see "E-invoicing: XRechnung and ZUGFeRD").

Way 3: API and webhooks (for developers)

For an automated, ongoing connection, Kyvento provides a REST API and webhooks:

• Under Settings → "API tokens", you create access keys with which your own scripts or middleware services retrieve invoices, customers and payments.
• Under Settings → "Webhooks", you store a URL that Kyvento notifies automatically on events – so your system can react to new invoices, for example, without polling.

This also lets you establish a connection to Lexoffice, sevDesk and the like – both offer their own APIs, so a small intermediary service can transfer invoices from Kyvento to them. The details are described in the "API & Webhooks" category.

Which way suits you?

• Tax advisor does the bookkeeping: monthly DATEV export – no technical effort, established process.
• You do the bookkeeping yourself: CSV exports on a fixed cadence, PDFs as needed.
• Automation desired: API connection with webhooks – a one-time development effort, after which the data flows by itself.

Good to know

• All exports are read-only – they change no data and can be repeated without risk.
• Record the chosen handover path in your procedural documentation (Verfahrensdokumentation) (see "Creating a procedural documentation").

Next steps

• Posting batch for your tax advisor – see "Setting up the DATEV export"
• Set up API access – see the "API & Webhooks" category