> ## 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.

# DATEV – Troubleshooting

> Connection expired, import creating too many claims, document type gone — the most common DATEV cases

## Connection and authorisation

<AccordionGroup>
  <Accordion title="„DATEV-Integration nicht aktiv“">
    The DATEV connection is not active. Authorise it again — either via **DATEV
    Einstellungen** or via the connection card on the dashboard.
  </Accordion>

  <Accordion title="The connection has expired">
    The connection card shows **Verbindung gültig bis …** (connection valid until).
    Once that date passes, import and document upload stop **without** any error
    message appearing in DATEV.

    paywise emails you a reminder in good time beforehand. Set the authorisation up
    again in that case.

    <Warning>
      **A deactivated integration receives no reminder.** If you deactivated the
      integration in the Gefahrenzone, paywise no longer sends expiry warnings for it.
      Check the expiry date yourself before reactivating.
    </Warning>
  </Accordion>

  <Accordion title="„Mandanten-Zuordnung erforderlich“ (client mapping required)">
    The technical client ID could not be determined automatically, so some features —
    creating claims and importing — are unavailable. Contact
    [info@paywise.de](mailto:info@paywise.de) so we can map it manually.
  </Accordion>

  <Accordion title="„DATEV-Mandanten konnten nicht geladen werden“">
    The connection to DATEV failed. Sign in with your DATEV account again — or enter
    the **Beraternummer** and **Mandantennummer** directly via **Manuell eingeben**.
  </Accordion>

  <Accordion title="„Keine Mandanten gefunden“ (no clients found)">
    No clients you are entitled to are visible under your DATEV account. Check the
    rights assignment in DATEV, or enter the consultant and client numbers manually.
  </Accordion>

  <Accordion title="The Cloud Gateway setup is incomplete">
    The status then shows **Warte auf Ihre Autorisierung** (waiting for your
    authorisation). Open the **Cloud Gateway Portal**, authenticate with a DATEV
    SmartCard or identity document, sign the contract and confirm access. Your IT
    partner then installs the software, which takes up to one working day.

    Watch the displayed **deadline**. If it has passed, request the setup again via
    **Erneut einrichten**.
  </Accordion>
</AccordionGroup>

## Pausing, revoking, setting up again

<AccordionGroup>
  <Accordion title="What is the difference between deactivating and revoking?">
    **Deactivating** (Gefahrenzone → *Integration deaktivieren*) pauses only the
    **import**. Settings and tokens are kept, the document upload keeps running, and
    you can reactivate at any time.

    **Revoking** requests token revocation at DATEV, always removes the connection
    from paywise and disconnects **every** DATEV feature — import **and** both upload
    lanes. If DATEV is unavailable during revocation, also revoke the access in
    DATEV's token management. Setting it up again requires the entire authorisation
    process from scratch.
  </Accordion>

  <Accordion title="I only wanted to stop the document upload and revoked the connection">
    The revoke is deliberately comprehensive — there is only one shared authorisation
    for your company. Set the connection up again via **Connect DATEV**; claims
    already handed over and documents already uploaded are unaffected.

    To stop only one lane in future, use **Übertragung pausieren** on the Belege
    online page.
  </Accordion>

  <Accordion title="I want to switch to a different bookkeeping software">
    Deactivate the DATEV import under **DATEV Einstellungen → Gefahrenzone →
    Integration deaktivieren** before connecting a classic bookkeeping integration
    such as Lexware Office, sevdesk or WISO MeinBüro as the new import source. Your
    DATEV connection and claims already handed over remain unaffected.

    easyVerein is an exception and can remain connected as a separate
    collection-import source.
  </Accordion>
</AccordionGroup>

## Import

<AccordionGroup>
  <Accordion title="The import creates the same invoice several times">
    This can affect orders imported before open-item consolidation was introduced.
    Contact [info@paywise.de](mailto:info@paywise.de) — we clean up the affected
    orders and keep the claim from the invoice row.

    Newly imported items are correctly consolidated into **one** claim per open item.
  </Accordion>

  <Accordion title="An invoice appears several times in the manual picker">
    The manual picker shows postings, not consolidated open items. Select the row
    carrying the invoice document. The automatic import does consolidate correctly.
  </Accordion>

  <Accordion title="The auto-import cannot be enabled">
    paywise lists what is missing under **Bitte konfigurieren Sie:** —
    **Geschäftsjahr**, **Zeitplan** or **Import-Regel**. Complete the item named and
    the switch becomes available.
  </Accordion>

  <Accordion title="My overdue rule does not match some items">
    An open item **without a due date** matches no overdue rule. Movement postings in
    DATEV carry no due date. That is deliberate — otherwise they would pass a rule
    such as "30 days overdue" unchecked.
  </Accordion>

  <Accordion title="The rule imports too many or too few items">
    Use **Testen** in the rule editor before saving; paywise then shows how many
    invoices match. Also note that rules are evaluated top to bottom and the **first
    matching** one is applied.
  </Accordion>

  <Accordion title="A website is stored as a phone number on the debtor">
    This affects debtors imported before a correction. Contact
    [info@paywise.de](mailto:info@paywise.de) — we correct the affected contact
    details from the original DATEV data.
  </Accordion>

  <Accordion title="A phone number is flagged as invalid in the order">
    paywise converts DATEV phone numbers into a consistent international form. Where
    that is not unambiguously possible, the number is left as it is and the order
    wizard flags it — deliberately, rather than storing a plausible-looking wrong
    number. Correct it by hand in the order.
  </Accordion>
</AccordionGroup>

## Belege online

<AccordionGroup>
  <Accordion title="„Der gewählte Belegtyp ist in DATEV nicht mehr vorhanden“">
    The document type was renamed or deleted in DATEV. Pick a new one via **Belegtyp
    ändern**. Until then that lane's upload is paused.
  </Accordion>

  <Accordion title="„Es wurden keine berechtigten Mandantenbestände gefunden“">
    Check the rights assignment in DATEV for the account you authorised with, and
    start the setup again.
  </Accordion>

  <Accordion title="Why do I have to authorise at DATEV twice?">
    That is by design. The first authorisation may only read your client list. The
    second is bound to exactly the client you selected, permits filing documents, and
    is valid considerably longer.
  </Accordion>

  <Accordion title="A statement was not uploaded">
    The upload starts once the statement is published **and** its PDF exists. Failed
    uploads are retried automatically several times. If the error persists, paywise
    tells you about it and says what to do — renew the connection, choose a different
    document type, or add rights in DATEV. If the cause is technical, our team takes
    care of it.
  </Accordion>

  <Accordion title="The upload has been „running“ for minutes">
    The list refreshes automatically in the background. After a while paywise notes
    that the transfer continues in the background — you can safely leave the page and
    check again later.
  </Accordion>
</AccordionGroup>

## Still stuck

If you cannot get further, write to [info@paywise.de](mailto:info@paywise.de). Please
include your company, the **Beraternummer** and **Mandantennummer**, and — where
applicable — the time of the affected import run or the affected statement.