Skip to content
Home / Integrations

Integrations and APIs: what ZepDesk connects to.

ZepDesk fetches account transactions via finAPI or Qonto and payments from your Stripe account, reports events to Make or Zapier and exchanges data with your own systems through a REST API. Your tax firm gets a package with a DATEV posting batch and receipts, and ZepDesk prepares and checks the filings for the German tax office (ELSTER). Which connections are still in preparation or in development is shown on each card.

Integrations at no extra charge, included in every plan, depending on legal form from €29 per company per month incl. VAT. See pricing

Integrations page in ZepDesk, version 0.8.90: migration from Lexware Office, below it Add connection with 4 available and 18 in development; Shopify and Stripe with the Connect button, Amazon Seller Central and Mollie with the banner “In development, not yet possible”

Which interfaces does ZepDesk have?

Data runs in three directions. Account transactions and payments come in; these connections only read, write nothing back into the other system and move no money. What goes out are files and values you pass on yourself: to your tax firm, the tax office and your customers. Only the REST API and MCP run in both directions, and you unlock them with a key or a sign-in.

Which connections are available today?

Today you can connect your bank via finAPI or Qonto, your Stripe account and workflows in Make or Zapier. Every integration is part of the core and has no price of its own. It is set up under Administration, Company, Integrations, the bank connection on the bank page; the company's administration enters the access details. The sentence next to the logo is the one ZepDesk itself uses to describe the integration.

As of: ZepDesk 0.8.90, 14 November 2026. Available means: a new company can connect it by itself.

Banking
finAPIavailable
Fetches account transactions from almost every German bank.
Lands as account transactions on the bank page
Qontoavailable
Fetches account transactions directly from the Qonto business account.
Lands as account transactions on the bank page

Without a connection you upload bank statements as MT940, CAMT or CSV. The bank feed only reads; ZepDesk makes no transfers itself. How payments find their receipt is explained under bank reconciliation.

Payment provider
Stripeavailable
Fetches payments, fees and payouts from your Stripe account.
Lands as bank line, split into invoices and fee
Automation
Makeavailable
A webhook reports events such as a paid invoice to a Make scenario; actions run through the REST API.
Zapieravailable
A webhook reports events such as a paid invoice to a Zap in Zapier; actions run through the REST API.
In preparation

Built in the core, but not yet released for new companies.

Shopifyin preparation
Fetches paid orders from your Shopify store and turns them into invoices.
We will offer Shopify for connecting once it has been tested with a real store.
meetergoin preparation
Fetches booked meetings from your booking page into sales.
Tested with a real account; the sign-in for new companies is not set up yet.
In development

Set up in the core, but not yet tested with a real account. A connection like this can only be connected after that test.

Molliein development
Fetches payments, fees and payouts from your Mollie account.
PayPalin development
Fetches incoming payments, fees and payouts from PayPal.
SumUpin development
Fetches your card payments, the fees and the payouts from your SumUp account.
Ecwidin development
Fetches orders with line items and tax from your Ecwid store.
Billbeein development
Fetches your invoices from Billbee, separated by sales channel.
Das Programmin development
Fetches invoices, customers and items from your trades software.

Amazon Seller Central and Amazon Business are in development as well. What ZepDesk will read there, why and how long it keeps the data is described on the page about the Amazon connection. Your service is not listed? Connect your own systems through the REST API and webhooks.

All logos are trademarks of their owners. Here they only indicate which service a connection exists with or is planned with; no partnership is implied. As in the product, finAPI is shown without a logo.

What happens to the fetched data?

Depending on the integration, data is fetched manually, hourly, daily or instantly when the provider sends a notification. In an integration's Intake tab you choose whether ZepDesk accepts what was fetched by itself or whether you review it first.

IntegrationWhat arrivesWhat it becomes in ZepDesk
finAPI, Qonto, bank statement as a fileaccount transactionsa line on the bank page, for which ZepDesk suggests the matching invoice or receipt, bank reconciliation
Stripeone record per payout with the paid items and the feeonce you click Accept, the bank line of the payout, split into the invoices and the fee account; ZepDesk never splits a payout by itself
Make, Zapiernothing, the direction is reverseda webhook reports events such as a paid invoice to your scenario or Zap; whatever comes back is written by Make or Zapier through the REST API

How does data reach the tax office, your tax firm and your own systems?

  1. Taxes and ELSTER
  2. What the DATEV package contains
  3. E-invoicing
  4. API reference
  5. Webhooks A webhook reports events such as a paid invoice to an https address of your choice, for example to Make or Zapier, signed with HMAC-SHA256. The administration creates them, tests them with a probe, switches them off or deletes them under Help, Interface, Webhooks.
    API reference
  6. AI assistant and MCP
API reference of ZepDesk with the routes for invoices
MCP view in ZepDesk: the MCP server address to copy, the OAuth access “Claude im Büro” with status active and below it the access key for programs without OAuth

Does ZepDesk have a DATEV interface?

Yes, as an export. Under DATEV export, ZepDesk creates the posting batch for a period and, at the push of a button, a package for your tax advisor: one ZIP file with everything your tax firm needs to import it into DATEV. The firm uploads the receipts through DATEV's receipt transfer, imports the batch and then sees the receipt for every booking.

  • DATEV posting batch with one receipt link per booking
  • Account labels for the accounts that appear in the batch
  • Master data of customers and suppliers with their own personal account, without bank details
  • Receipt files of receipts and invoices, with the index for DATEV's receipt transfer
  • Lists of incoming receipts, outgoing invoices and bank transactions
  • Cover sheet with totals, gaps and checksums

Payroll data is not included. You can also invite your tax firm into your company as users with the Tax role, with no per-seat price. If you come from another program, you take over its DATEV posting batch in the booking import, up to 1,000 lines per file; the whole switch is described on the migration page. How the bookings themselves come about is shown on the accounting page.

Questions about integrations and APIs

All questions and answers
Which banks can I connect to ZepDesk?

Via finAPI, accounts at almost any German bank, plus the Qonto business account directly. The bank feed only reads account transactions. Without a connection you upload bank statements as MT940, CAMT or CSV. This is set up on the bank page; how payments find their receipt is explained under bank reconciliation.

Can ZepDesk initiate transfers at my bank?

No. The bank connection only reads account transactions; ZepDesk makes no transfers itself. You approve transfers in your online banking as usual. The approval of every payment stays with you and your bank.

Does ZepDesk work with PayPal, Mollie or SumUp?

Not yet. All three are set up in the core but have not been tested with a real account, so they cannot be connected. Stripe is available: ZepDesk fetches payments, fees and payouts and, once you click, splits a payout into the invoices and the fee account. Until then you see payouts from the other services as a transaction on your bank account.

Is there an API for my own software?

Yes. The REST API reads and writes with an API key of your company. The key has the rights of the administration, only the administration may create and revoke it, and the secret is shown exactly once. Webhooks report events such as a paid invoice to an https address of your choice, signed with HMAC-SHA256. All routes are in the API reference.

Can an AI program like Claude work with ZepDesk?

Yes, via MCP. Each company has its own address through which Claude and other AI programs read and make changes with your permissions. Before sensitive steps such as a cancellation there is a warning first, and nothing goes to the tax office without your approval. More under AI assistant and MCP.

What do the integrations cost?

Nothing extra. Every integration is part of the core and included in every plan. Plans depend on the legal form and start at €29 per company per month incl. VAT. All plans are listed under Pricing.

What ZepDesk does not take on

No way back. ZepDesk writes nothing back into your payment account or your store and moves no money there.
No payments through the bank connection. You approve transfers in your online banking.
No payroll data in the DATEV package. The package for your tax advisor leaves out bookings from payroll; the cover sheet states how many there were.
No key with fewer rights. An API key may do as much as the administration. Only give it to systems you trust with that.
No app of our own at Make or Zapier. You connect both through their webhook module and an API key; ZepDesk shows the steps under Help, Interface, Webhooks.

Set up an integration.

Create your company, connect your business account on the bank page, enter your Stripe account under Administration, Company, Integrations and look in the intake at what has arrived. Connect your own systems using the API reference.