Add automatic invoices and DATEV bookings to Qonto

No. Qonto stays your business account with cards, receipt forwarding and the bank transaction feed to your tax advisor. Rechnungskit takes over invoicing for your shop and Stripe, the GoBD archive of those documents and the DATEV bookings. You then no longer need Qonto's invoicing feature for these sales; you can keep using it for quotes or individual service invoices.

Yes, and that's the usual way to switch. You run both systems in parallel for one billing period and compare documents and bookings before you switch over.

They stay where they are. Rechnungskit doesn't import or archive invoices created elsewhere; you keep meeting your retention duty for old documents (eight years under § 14b (1) UStG and § 147 (3) AO) in your previous system. What Rechnungskit can pull in are past orders and payments from your connected shops and payment providers, which then become new, validated invoices. For the number sequence, you set the number Rechnungskit continues from, so nothing overlaps with your old documents.

Documents are stored tamper-proof and unchangeable for eight years for as long as your account exists (WORM archive with checksums). Eight years is the retention period for invoices and accounting records (§ 14b (1) UStG, § 147 (3) AO); the requirements for the archive are set out in the GoBD. You can export them at any time, and for 90 days free of charge after you cancel. The final assessment of your process documentation (Verfahrensdokumentation) is up to your tax advisor.

For everything that happens by hand between order and booking. In Qonto you create every invoice yourself; Rechnungskit creates it from the shop order or the Stripe payment, with the date of supply from shipping, the right tax rate and its own cancellation invoice when you refund. With a few invoices a month, that's no argument. With a few hundred orders, it's the difference between an afternoon of manual work and none at all.

It depends on what arrives. Qonto passes bank transactions via the DATEV bank data service and, once a day, the document images to Unternehmen online. Qonto itself says that no transaction data is transferred, only the document image. So every booking, such as revenue at 19%, revenue at 7%, Stripe fee, money in transit, is created at your tax firm. Rechnungskit delivers exactly these booking records ready-made as an EXTF file, each invoice booking with a Beleglink to its document image. Ask your tax advisor how they book a Stripe payout today; the answer shows whether this is worth it for you.

At Qonto, as one bank transaction with the Stripe receipt attached. But it contains many payments, the Stripe fees and possibly refunds. Rechnungskit breaks the payout down into its parts and books revenue by tax rate, fees and money in transit separately, so the entry on the bank account in DATEV is cleanly offset against money in transit.

Yes, and that's the normal case. Rechnungskit is not a bank and doesn't need access to your account. Qonto stays your account, cards and receipt collector; the bank transaction feed to your tax advisor keeps running as before. Rechnungskit only takes over invoicing for your shop and Stripe, the archive of those documents and the matching DATEV bookings.

Qonto talks about GoBD-compliant storage and certifies uploaded receipts with a timestamp. For the invoices you keep writing in Qonto, that remains your archive. Invoices created by Rechnungskit sit in the Rechnungskit archive, locked from creation with a SHA-256 checksum, and can be exported free of charge for 90 days after you cancel. Rechnungskit doesn't import documents from Qonto.

From the providers' publicly available sources, checked on July 28, 2026, with footnotes for each row. Where we found no reliable source, the table says "Not documented". If you spot a mistake, write to support@rechnungskit.de and we'll correct it and re-date the page.