> ## Documentation Index
> Fetch the complete documentation index at: https://docs.paywise.de/llms.txt
> Use this file to discover all available pages before exploring further.

# sevdesk

> Send open invoices from sevdesk to paywise — including payment term and dunning levels

# paywise for sevdesk

<div style={{width: '64px', height: '64px', background: '#ffffff', borderRadius: '10px', display: 'flex', alignItems: 'center', justifyContent: 'center', padding: '10px', boxSizing: 'border-box'}}>
  <img src="https://mintcdn.com/paywisegmbh/wAdTkukMeudh23V7/images/integrations/sevdesk-icon.png?fit=max&auto=format&n=wAdTkukMeudh23V7&q=85&s=80a7fb4b2a867f69eb046c1871ff56ca" alt="sevdesk" style={{width: '100%', height: '100%', objectFit: 'contain', display: 'block'}} noZoom width="128" height="128" data-path="images/integrations/sevdesk-icon.png" />
</div>

The sevdesk integration hands open invoices from your sevdesk account straight to
paywise for collection. sevdesk supplies unusually much: the **payment term**,
recorded **partial payments**, and your **reminders including dunning level and
dunning fee**.

<Note>
  paywise reads from sevdesk and never writes back. Nothing in your bookkeeping is
  changed, cancelled or marked as paid.
</Note>

## Before you start

* A sevdesk account with API access.
* A paywise account.
* At least one completed, open invoice in sevdesk.
* No active DATEV import may exist for your paywise company. Deactivate it under
  **DATEV Einstellungen → Gefahrenzone → Integration deaktivieren** before
  connecting sevdesk.

### What paywise reads

| Data                    | Why paywise needs it                                   |
| ----------------------- | ------------------------------------------------------ |
| Invoices                | The open receivables you submit                        |
| Invoice positions       | The breakdown behind the amount                        |
| Contacts                | The debtor's name and address                          |
| Payments on the invoice | The amount actually outstanding                        |
| Reminders               | Reminder date, deadline, dunning level and dunning fee |
| Invoice PDF             | The evidence attached to the case                      |

The API token is used read-only.

## Finding your sevdesk API token

Inside paywise this guide is available at any time via **„Was ist das?“** (*what is
this?*) on the sevdesk page.

<Steps>
  <Step title="Sign in to sevdesk">
    Sign in to your sevdesk account at [my.sevdesk.de](https://my.sevdesk.de/).
  </Step>

  <Step title="Open the API section">
    In the menu, go to **Erweiterungen → API** (*Extensions → API*).
  </Step>

  <Step title="Reveal the token">
    Click **Einblenden** (*show*) to display the API token.
  </Step>

  <Step title="Copy the token">
    Copy the key to your clipboard.
  </Step>
</Steps>

<Warning>
  The API token covers your entire sevdesk account. Never share it by email or chat.
</Warning>

## 1. Connect sevdesk

<Steps>
  <Step title="Open the connection page">
    Go to [app.paywise.de/connect/sevdesk/](https://app.paywise.de/connect/sevdesk/).
  </Step>

  <Step title="Paste the token">
    Paste the key into the **API-Token** field. The **API Basis-URL** is pre-filled
    with `https://my.sevdesk.de/api/v1` and normally needs no change.
  </Step>

  <Step title="Accept the terms and test">
    Tick **Ich akzeptiere die Nutzungsbedingungen** (*I accept the terms of use*) and
    choose **API-Token testen** (*test API token*).

    paywise verifies the token directly with sevdesk. If the check succeeds, the
    connection is saved immediately.
  </Step>
</Steps>

## 2. Submit invoices for collection

<Steps>
  <Step title="Open the invoice picker">
    On the sevdesk page in paywise, choose **Rechnungen einreichen**.
  </Step>

  <Step title="Pick the invoices">
    paywise lists your open invoices live from sevdesk — with invoice number,
    customer, invoice date, due date, total and open amount.

    paywise derives the **due date** from the invoice date plus the payment term
    stored in sevdesk. Nothing needs to be configured in paywise for this.
  </Step>

  <Step title="Check the debtor data">
    Name and address come from the sevdesk contact, the invoice PDF is attached
    automatically. Review and correct anything missing.
  </Step>

  <Step title="Review the reminders">
    Reminders you created in sevdesk for the invoice are imported automatically —
    with reminder date, payment deadline and, where charged, the **dunning fee of the
    respective dunning level**. If you dunned outside sevdesk, add that by hand here.
  </Step>

  <Step title="Send the order">
    Confirm how collection should start, answer the legal questions, accept the terms
    and choose **Auftrag absenden**.
  </Step>
</Steps>

### Invoices that cannot be submitted

* **Drafts and unfinished invoices.** paywise reads only completed sevdesk invoices.
* **Incomplete recipient details.** paywise imports the invoice as an editable
  draft. Complete the name and address in paywise before submitting the order.
* **Already submitted** invoices are shown as *Eingereicht*.

## Mahnservice: importing invoices continuously

This integration feeds more than the one-off collection handover — it can also supply
the **paywise Mahnservice**, the pre-collection dunning service. paywise then fetches
your open invoices regularly and sends payment reminders on your behalf, before a case
becomes a collection matter. You set the Mahnservice up at
[app.paywise.de/mahnservice/](https://app.paywise.de/mahnservice/).

### Prerequisites

All of the following must be in place before the recurring sync starts:

* An **active sevdesk connection** with a valid API token.
* A **Mahnservice subscription** and the **accepted Mahnservice terms**.
* A decided **import scope** — you determine once which invoices should be taken over.

### What paywise checks before every reminder

<Steps>
  <Step title="Regular sync">
    paywise fetches your open invoices from sevdesk at fixed intervals. Newly opened
    invoices are picked up automatically.
  </Step>

  <Step title="Status check immediately before sending">
    Right before a reminder goes out, paywise queries the current invoice status in
    sevdesk once more. If the invoice has been paid or cancelled in the meantime, no
    reminder is sent.
  </Step>

  <Step title="When in doubt, nothing is sent">
    If the status cannot be established beyond doubt — because sevdesk is temporarily
    unreachable, for instance — paywise holds the reminder back. That is deliberate: a
    reminder sent late is better than one sent to somebody who has already paid.
  </Step>
</Steps>

Payments paywise finds in sevdesk during a sync end the dunning process
automatically.

## 3. Disconnect

On the sevdesk page, choose **Verbindung löschen** (*delete connection*) and confirm
with **Löschen**.

paywise removes the stored token and stops reading invoices. Orders you already
submitted are unaffected. paywise pauses running dunning processes that depend on
this connection. You can resume them after reconnecting.

<Warning>
  The token itself stays valid in sevdesk. To invalidate it completely, reset it in
  sevdesk under **Erweiterungen → API** as well.
</Warning>

## Troubleshooting

<AccordionGroup>
  <Accordion title="„Der API-Token konnte nicht verifiziert werden“">
    Check that you copied the full token (no leading or trailing spaces) and that the
    API base URL is unchanged.
  </Accordion>

  <Accordion title="„Ihr API-Token ist nicht mehr gültig“">
    The token was reset or revoked in sevdesk. Fetch a current token under
    **Erweiterungen → API** and store it again.
  </Accordion>

  <Accordion title="The invoice list is empty">
    paywise shows only completed, open invoices. Drafts do not appear. Check the
    invoice status in sevdesk.
  </Accordion>

  <Accordion title="The open amount is wrong">
    paywise subtracts payments recorded in sevdesk from the gross amount. A payment
    not yet assigned to the invoice in sevdesk does not show up here. Assign it in
    sevdesk and reload the list.
  </Accordion>

  <Accordion title="Another integration is already active">
    Another import source conflicts with sevdesk. If the message names a DATEV
    import, deactivate it; disconnect any other integration named there. Then try
    again.
  </Accordion>
</AccordionGroup>

## Questions

Write to [info@paywise.de](mailto:info@paywise.de).