# paywise Knowledge Center > paywise is a German digital debt-collection platform. The current Case Management API manages collection orders and accepted cases. The current Partner API onboards client companies and memberships and delegates Case traffic through one Partner credential. ## Start here - [API overview](https://docs.paywise.de/api-docs/overview.md): Choose the API for a direct company integration, a Partner integration, or both. - [API changelog](https://docs.paywise.de/api-docs/changelog.md): Initial release baseline for Case Management v2, Partner v2, and Mahnservice, with v1 data continuity and migration guidance. ## API essentials - [Authentication and environments](https://docs.paywise.de/api-docs/essentials/authentication-and-environments.md): Authenticate direct-company and Partner requests, keep sandbox and production credentials separate, and distinguish `case:payments` permissions from order scopes. - [Requests and responses](https://docs.paywise.de/api-docs/essentials/requests-and-responses.md): Use canonical trailing-slash URLs: slashless Case and Partner requests return JSON 404 for every method without redirect; Mahnservice retains GET/HEAD redirects. Apply shared JSON, multipart, identifier, timestamp, money, and partial-update conventions. - [Errors and safe retries](https://docs.paywise.de/api-docs/essentials/errors-and-safe-retries.md): Handle typed errors, idempotency outcomes, rate limits, and transient failures without duplicating effects. - [Pagination and synchronization](https://docs.paywise.de/api-docs/essentials/pagination-and-synchronization.md): Use the shared `ordering` vocabulary, traverse collections, and reconcile inclusive non-snapshot updates with a runnable Python synchronization example. - [Public limits](https://docs.paywise.de/api-docs/essentials/limits.md): Distinguish API rate limits from resource limits for orders, debtors, documents, companies, and webhooks; learn when to wait, correct a request, or free capacity. - [Versioning and deprecation](https://docs.paywise.de/api-docs/essentials/versioning.md): Understand path-based versions, compatible changes, the planned Case and Partner v1 deprecation, and the retirement policy. - [Webhooks](https://docs.paywise.de/api-docs/essentials/webhooks.md): Receive and verify events, handle retries and duplicates, and catch up through event feeds by persisting the always-present `cursor`; `next` only drains a current backlog. ## Case Management API The Case Management and Partner API references both name their unauthenticated liveness endpoint **Health check**. In the Case Management API reference, Orders and Mandates each contain **Messages** and **Requests to client** subgroups. Use the order-scoped endpoints during review before a mandate exists, and the mandate-scoped endpoints for accepted cases. - [Case Management API overview](https://docs.paywise.de/api-docs/case-management-api/introduction.md): Submit claims, track collection progress, and reconcile financial activity. Get started in the sandbox, understand how the Partner API fits in, and download the OpenAPI specification. - [Case Management quickstart](https://docs.paywise.de/api-docs/case-management-api/quickstart.md): Create a debtor and invoice claim, correct and finalize the default order type, accept it in the sandbox, and find the mandate. - [Core resources](https://docs.paywise.de/api-docs/case-management-api/concepts/resource-model.md): Understand resource ownership and shared v1/v2 identity, then follow the detailed concept guides. - [Debtors](https://docs.paywise.de/api-docs/case-management-api/concepts/debtors.md): Reuse debtor resources for new orders and distinguish them from the id-less `MandateDebtor` snapshot owned by an accepted case. - [Orders](https://docs.paywise.de/api-docs/case-management-api/concepts/orders.md): Choose invoice, rental, or titled orders, construct their claims and evidence, and handle terminal expired drafts whose writes return `409 order_expired`. - [Claims](https://docs.paywise.de/api-docs/case-management-api/concepts/claims.md): Understand claim structures, legal-basis codes, and amounts. Create and read metadata/events on claims and charges, preserve duplicate types, and handle complete charge replacement. - [Mandates](https://docs.paywise.de/api-docs/case-management-api/concepts/mandates.md): Understand main and subcases, shared balances, published history, and their id-less case-owned `MandateDebtor` snapshots. - [Documents and communication](https://docs.paywise.de/api-docs/case-management-api/concepts/documents-and-communication.md): Upload multipart or base64 files, follow processing status, replace attachments within their edit windows, and exchange messages and typed request answers. - [Payments](https://docs.paywise.de/api-docs/case-management-api/concepts/payments.md): Report direct receipts with `case:payments:read`/`write`, preserve metadata, and reconcile family-wide duplicate protection; follow money received by paywise through balances, history, and statements. - [Statements](https://docs.paywise.de/api-docs/case-management-api/concepts/statements.md): Reconcile multi-case and single-mandate statements, including case rows whose debtor is the id-less `MandateDebtor` snapshot. - [Webhook events](https://docs.paywise.de/api-docs/case-management-api/concepts/webhook-events.md): Look up Case event triggers and payload families for orders, mandates, payments, and statements, and configure a company subscription. - [Sandbox environment](https://docs.paywise.de/api-docs/case-management-api/concepts/sandbox.md): Build against the sandbox host and its `pw_sbx_` credentials, and test signed webhook delivery with a public HTTPS receiver. - [Submit an order](https://docs.paywise.de/api-docs/case-management-api/workflows/submit-an-order.md): Build and finalize an invoice order with optional metadata/events, safely retry commands, and handle debtor and charge replacement rules. - [Submit a rental order](https://docs.paywise.de/api-docs/case-management-api/workflows/submit-a-rental-order.md): Create the agreement and H17 or H19 claims inline or in stages, manage derived dates, and finalize the rental order. - [Submit a titled order](https://docs.paywise.de/api-docs/case-management-api/workflows/submit-a-titled-order.md): Create titled claims and K014 enforcement costs, attach title evidence, confirm the success fee, and finalize safely. - [Manage documents](https://docs.paywise.de/api-docs/case-management-api/workflows/manage-documents.md): Upload files or base64, poll asynchronous scan status, replace failed attachments, and download ready claim documents. - [Follow a case](https://docs.paywise.de/api-docs/case-management-api/workflows/follow-a-case.md): Read accepted mandate state and consume its published history feed with source tracks, related resources, and authenticated attachments. - [Messages and client requests](https://docs.paywise.de/api-docs/case-management-api/workflows/messages-and-client-requests.md): Send client-authored messages to paywise and answer typed client requests with uploaded attachments. - [Report payments](https://docs.paywise.de/api-docs/case-management-api/workflows/report-payments.md): Report direct receipts with optional metadata at claim or mandate scope and reconcile existing payment UUIDs without duplicate reporting. - [Consume Case webhooks](https://docs.paywise.de/api-docs/case-management-api/workflows/consume-webhooks.md): Subscribe to current company event keys, store the one-time secret, and use 202 test and redelivery command results safely. - [Migrate from Case Management API v1](https://docs.paywise.de/api-docs/case-management-api/migrate-from-v1.md): Continue existing v1 records through v2 with the same UUIDs, read each claim directly to observe its current `order_id`, and preserve historical metadata/events without reimport. - [Use with Postman](https://docs.paywise.de/api-docs/case-management-api/postman.md): Import the ready-made Postman collection and its production and sandbox environments to explore the Case Management API. - [Download the Case Management OpenAPI contract](https://docs.paywise.de/api-docs/case-management-api/openapi.json): Machine-readable contract for the current Case Management API at `/v2/`, including draft deletion, rental agreements, enforceable titles, their documents, and pageable statement cases. ### Claims Claims keep a stable UUID even when paywise review moves them to another order. Create a complete claim in an existing draft, address it and every child resource directly, and use the current `order_id` only as relationship state. - [List claims](https://docs.paywise.de/api-docs/case-management-api/reference/claims/list-claims.md): Reconcile claims directly and filter by current order, status, or update cursor. - [Create claim](https://docs.paywise.de/api-docs/case-management-api/reference/claims/create-claim.md): Add a complete claim to an existing draft order by `order_id`. - [Get claim](https://docs.paywise.de/api-docs/case-management-api/reference/claims/get-claim.md): Read the claim's current order, lifecycle, mandate, debtors, and complete content by stable UUID. - [Update claim](https://docs.paywise.de/api-docs/case-management-api/reference/claims/update-claim.md): Correct an editable draft claim by stable UUID. - [Delete claim](https://docs.paywise.de/api-docs/case-management-api/reference/claims/delete-claim.md): Remove an editable draft claim without addressing it through an order. - [List claim documents](https://docs.paywise.de/api-docs/case-management-api/reference/documents/list-claim-documents.md): List documents attached to one stable claim UUID. - [Create claim document](https://docs.paywise.de/api-docs/case-management-api/reference/documents/create-claim-document.md): Upload a document to one claim by stable UUID. - [Get claim document](https://docs.paywise.de/api-docs/case-management-api/reference/documents/get-claim-document.md): Read claim-document metadata by claim and document UUID. - [Delete claim document](https://docs.paywise.de/api-docs/case-management-api/reference/documents/delete-claim-document.md): Delete an editable claim document by stable claim UUID. - [Download claim document](https://docs.paywise.de/api-docs/case-management-api/reference/documents/download-claim-document.md): Download a ready claim document without an order parameter. - [List claim payments](https://docs.paywise.de/api-docs/case-management-api/reference/claims/list-claim-payments.md): List direct receipts attributed to one claim. - [Create claim payment](https://docs.paywise.de/api-docs/case-management-api/reference/claims/create-claim-payment.md): Report a direct receipt against one exact claim UUID. - [Delete claim payment](https://docs.paywise.de/api-docs/case-management-api/reference/claims/delete-claim-payment.md): Delete an editable claim-scoped payment by its server UUID. - [Get enforceable title](https://docs.paywise.de/api-docs/case-management-api/reference/claims/get-enforceable-title.md): Read the enforceable title owned by one titled claim. - [Replace enforceable title](https://docs.paywise.de/api-docs/case-management-api/reference/claims/replace-enforceable-title.md): Replace the complete draft title on one claim. - [Update enforceable title](https://docs.paywise.de/api-docs/case-management-api/reference/claims/update-enforceable-title.md): Correct individual editable fields of a claim's title. - [Delete enforceable title](https://docs.paywise.de/api-docs/case-management-api/reference/claims/delete-enforceable-title.md): Remove an editable title from one draft claim. - [List enforceable title documents](https://docs.paywise.de/api-docs/case-management-api/reference/claims/list-enforceable-title-documents.md): List evidence attached to one claim's enforceable title. - [Create enforceable title document](https://docs.paywise.de/api-docs/case-management-api/reference/claims/create-enforceable-title-document.md): Upload title evidence through the stable claim URL. - [Get enforceable title document](https://docs.paywise.de/api-docs/case-management-api/reference/claims/get-enforceable-title-document.md): Read one title-document record by claim and document UUID. - [Delete enforceable title document](https://docs.paywise.de/api-docs/case-management-api/reference/claims/delete-enforceable-title-document.md): Delete editable title evidence by stable claim UUID. - [Download enforceable title document](https://docs.paywise.de/api-docs/case-management-api/reference/claims/download-enforceable-title-document.md): Download ready title evidence through the claim resource. ### Order requests to client Answer review questions using the order UUID before a mandate exists. All published questions must be answered before processing resumes; attachments become downloadable when ready. - [List order requests to client](https://docs.paywise.de/api-docs/case-management-api/reference/orders/list-order-requests-to-client.md): Find published questions for an order before acceptance. - [Get order request to client](https://docs.paywise.de/api-docs/case-management-api/reference/orders/get-order-request-to-client.md): Read the question, accepted answer type, attachments, and current answer. - [Answer order request to client](https://docs.paywise.de/api-docs/case-management-api/reference/orders/answer-order-request-to-client.md): Submit one idempotent answer during order review. - [Download order request to client attachment](https://docs.paywise.de/api-docs/case-management-api/reference/orders/download-order-request-to-client-attachment.md): Download a file paywise attached to the question. - [List order request to client answer documents](https://docs.paywise.de/api-docs/case-management-api/reference/orders/list-order-request-to-client-answer-documents.md): Poll answer attachment processing. - [Create order request to client answer document](https://docs.paywise.de/api-docs/case-management-api/reference/orders/create-order-request-to-client-answer-document.md): Upload another attachment before staff review starts. - [Get order request to client answer document](https://docs.paywise.de/api-docs/case-management-api/reference/orders/get-order-request-to-client-answer-document.md): Read answer attachment metadata and availability. - [Delete order request to client answer document](https://docs.paywise.de/api-docs/case-management-api/reference/orders/delete-order-request-to-client-answer-document.md): Remove an attachment while the answer is editable. - [Download order request to client answer document](https://docs.paywise.de/api-docs/case-management-api/reference/orders/download-order-request-to-client-answer-document.md): Download a ready answer attachment through its authenticated route. ## Partner API - [Partner API overview](https://docs.paywise.de/api-docs/partner-api/introduction.md): Embed paywise collection in your platform. Onboard companies and their users through hosted or API-only onboarding, manage their collection cases, and get started as a partner. - [Partner quickstart](https://docs.paywise.de/api-docs/partner-api/quickstart.md): Create a company with an inline admin and submit its first delegated Case draft. - [Companies and users](https://docs.paywise.de/api-docs/partner-api/concepts/resources-and-memberships.md): Connect companies, reuse company UUIDs across API versions, resolve company-scoped memberships, and understand editing rules and notification defaults. - [Readiness and access](https://docs.paywise.de/api-docs/partner-api/concepts/readiness-and-access.md): Understand submission readiness, onboarding options, and disconnecting or reconnecting a company. - [Calling the Case Management API](https://docs.paywise.de/api-docs/partner-api/concepts/calling-the-case-api.md): Use your partner key and the company-selection header to work with a connected company's cases. - [Webhooks](https://docs.paywise.de/api-docs/partner-api/concepts/webhook-ownership.md): Configure Partner-owned subscriptions and their 1–1000 `max_consecutive_failures` threshold, filter connected companies, and handle access and lifecycle events. - [API-only onboarding](https://docs.paywise.de/api-docs/partner-api/workflows/api-only-onboarding.md): Create a complete company aggregate while preserving terms and delegation confirmation. - [Hosted onboarding](https://docs.paywise.de/api-docs/partner-api/workflows/hosted-onboarding.md): Let clients complete hosted setup or authorize a connection to an existing company, then retrieve its current state. - [Manage memberships](https://docs.paywise.de/api-docs/partner-api/workflows/manage-memberships.md): Add, correct, resend, cancel, revoke, and safely re-add company-scoped memberships. - [Resolve readiness](https://docs.paywise.de/api-docs/partner-api/workflows/resolve-readiness.md): Turn readiness issues into targeted company or membership corrections. - [Submit cases for a company](https://docs.paywise.de/api-docs/partner-api/workflows/submit-cases-for-a-company.md): Create and finalize a Case with exact delegated tenant selection and safe retries. - [Handle access changes](https://docs.paywise.de/api-docs/partner-api/workflows/handle-access-changes.md): Gate delegated writes, reconcile Company state, and preserve finalized-case knowledge. - [Release a company](https://docs.paywise.de/api-docs/partner-api/workflows/release-a-company.md): Disconnect a company, revoke all partner access, and handle the final access event. - [Consume Partner webhooks](https://docs.paywise.de/api-docs/partner-api/workflows/consume-webhooks.md): Use wildcard subscriptions, typed one-time secrets, and 202 command results for Partner-owned deliveries. - [Migrate from Partner API v1](https://docs.paywise.de/api-docs/partner-api/migrate-from-v1.md): Reuse existing company UUIDs, resolve memberships separately from old user/invite IDs, and switch delegated Case traffic without recreating business records. - [Download the Partner OpenAPI contract](https://docs.paywise.de/api-docs/partner-api/openapi.json): Machine-readable contract for the current Partner API at the literal `/partner/v2/` route prefix. ## Mahnservice API - [Mahnservice API overview](https://docs.paywise.de/api-docs/mahnservice-api/introduction.md): Automate reminders in your company's name: submit invoices, track reminders, report payments, and hand unpaid invoices over to collection. Start with a sandbox key and a reminder sequence. - [Mahnservice quickstart](https://docs.paywise.de/api-docs/mahnservice-api/quickstart.md): Configure a sandbox Mahnlauf without checkout, look up or create a debtor, upload and scan an invoice PDF, release the invoice, and inspect its dunning state. - [Invoice lifecycle](https://docs.paywise.de/api-docs/mahnservice-api/concepts/invoice-lifecycle.md): Submit, release, settle, and sort invoices with `ordering`; check input rules and all six invoice and dunning webhook event contracts. - [Invoice documents](https://docs.paywise.de/api-docs/mahnservice-api/concepts/documents.md): Upload a PDF, poll pending through ready/rejected/failed, replace while held, and download the scanned document. - [Ownership and access](https://docs.paywise.de/api-docs/mahnservice-api/concepts/ownership-and-access.md): Understand company credentials and API terms, separate API-submitted from bookkeeping-synced invoices, and see what a subscription lapse and a collection handover permit. - [Invoice groups — implementation plan](https://docs.paywise.de/api-docs/mahnservice-api/concepts/invoice-groups.md): Planned grouping of separate monthly invoices, each with its own PDF, into one Mahnlauf; under review and not yet available. - [Download the Mahnservice OpenAPI contract](https://docs.paywise.de/api-docs/mahnservice-api/openapi.json): Machine-readable contract for the Mahnservice API at the literal `/mahnservice/v1/` route prefix. ## Developer integrations paywise can be integrated into automation platforms without writing code. These are developer-facing, in contrast to the ready-made bookkeeping connectors above. - [Introduction](https://docs.paywise.de/integrations/introduction.md): Overview of available paywise automation integrations - [n8n Community Node](https://docs.paywise.de/integrations/n8n-node.md): Integrate paywise APIs into your n8n workflows using the community node - [Zapier](https://docs.paywise.de/integrations/zapier.md): Connect paywise APIs to your Zapier workflows ## Legacy APIs (v1) - [Legacy API snapshot](https://docs.paywise.de/api-docs/legacy/overview.md): Frozen v1: Find snapshot provenance, base paths, current replacements, and migration guides. ### Frozen Case Management API - [Case Management API introduction](https://docs.paywise.de/api-docs/legacy/case-management/introduction.md): Frozen v1: Start with the historical Case Management integration and its claim-release lifecycle. - [Statements overview](https://docs.paywise.de/api-docs/legacy/case-management/statements/overview.md): Frozen v1: Read historical clearing-run statement guidance. - [Single Mandate Statements overview](https://docs.paywise.de/api-docs/legacy/case-management/single-mandate-statements/overview.md): Frozen v1: Read historical per-case Aktenabrechnung guidance. - [Status updates search overview](https://docs.paywise.de/api-docs/legacy/case-management/status-updates/overview.md): Frozen v1: Search and filter published status updates across all cases in one feed. - [Webhook overview](https://docs.paywise.de/api-docs/legacy/case-management/webhooks/overview.md): Frozen v1: Understand the historical Case webhook model. - [Webhook event types](https://docs.paywise.de/api-docs/legacy/case-management/webhooks/event-types.md): Frozen v1: Review historical Case webhook event names and payloads. - [Manage webhook endpoints](https://docs.paywise.de/api-docs/legacy/case-management/webhooks/manage-endpoints.md): Frozen v1: Configure historical Case webhook endpoints. - [Webhook signature verification](https://docs.paywise.de/api-docs/legacy/case-management/webhooks/signature-verification.md): Frozen v1: Verify historical Case webhook signatures. - [Webhook delivery and retries](https://docs.paywise.de/api-docs/legacy/case-management/webhooks/delivery-and-retries.md): Frozen v1: Handle historical webhook delivery attempts and failures. - [Case Management release notes](https://docs.paywise.de/api-docs/legacy/case-management/releasenotes.md): Frozen v1: Review the preserved Case Management release history. - [Download the frozen Case Management OpenAPI contract](https://docs.paywise.de/api-docs/legacy/case-management/openapi.json): Frozen v1: Machine-readable historical Case Management contract. ### Frozen Partner API - [Partner API introduction](https://docs.paywise.de/api-docs/legacy/partner/introduction.md): Frozen v1: Start with the historical Partner integration. - [Partner getting started](https://docs.paywise.de/api-docs/legacy/partner/getstarted.md): Frozen v1: Follow the preserved Partner onboarding entry path. - [Partner entities](https://docs.paywise.de/api-docs/legacy/partner/entities.md): Frozen v1: Review historical company and user entities. - [API-only onboarding](https://docs.paywise.de/api-docs/legacy/partner/onboarding-api-only.md): Frozen v1: Follow the historical API-only onboarding path. - [Hosted web onboarding](https://docs.paywise.de/api-docs/legacy/partner/onboarding-web-flow.md): Frozen v1: Follow the historical hosted onboarding path. - [Partner release notes](https://docs.paywise.de/api-docs/legacy/partner/releasenotes.md): Frozen v1: Review the preserved Partner release history. - [Download the frozen Partner OpenAPI contract](https://docs.paywise.de/api-docs/legacy/partner/openapi.json): Frozen v1: Machine-readable historical Partner contract. ## Bookkeeping integrations Ready-made connectors between paywise and the customer's bookkeeping, invoicing or payment software. The customer connects the system once, then picks open invoices from a live list and hands them to debt collection — invoice number, amount and debtor data are carried over, and an invoice PDF is attached when the provider supplies one. Every connector is read-only: paywise never writes back into the customer's bookkeeping. The invoice picker uses one active import source at a time. Classic bookkeeping imports and DATEV are alternatives, while easyVerein is a separate collection-import source that can coexist with either and takes precedence in the picker. Six connectors — Lexware Office, sevdesk, WISO MeinBuero, orgaMAX, Qonto and Stripe — additionally feed the paywise Mahnservice, the pre-collection dunning service that polls the connected system and sends reminders on the customer's behalf; the rest are handover-only. Disconnecting a Mahnservice source stops status checks and can pause running dunning processes; collection orders already submitted remain unaffected. The connectors differ mainly in how the customer authenticates (API key, OAuth sign-in, or a marketplace grant), whether existing payment reminders (Mahnungen) can be imported or must be typed in by hand, and which invoices are refused. These pages are written for end users; the German pages are the source of truth and quote the German UI labels verbatim. - [Buchhaltungs-Integrationen – Übersicht](https://docs.paywise.de/integrationen/uebersicht.md): Überblick über alle Buchhaltungsanbindungen, der gemeinsame Ablauf vom Verbinden bis zum Auftrag, und was für alle Anbindungen gilt - [Lexware Office](https://docs.paywise.de/integrationen/lexoffice.md): Anbindung per Anmeldung am Lexware-Office-Konto, inklusive Registrierung neuer paywise-Konten ueber Lexware Office mit uebernommenen Unternehmensdaten; importiert bestehende Mahnungen und Teilzahlungen mit; versorgt auch den Mahnservice - [sevdesk](https://docs.paywise.de/integrationen/sevdesk.md): Anbindung per API-Token; Fälligkeit aus dem sevdesk-Zahlungsziel, Mahnungen inklusive Mahnstufe und Mahngebühr; versorgt auch den Mahnservice - [FastBill](https://docs.paywise.de/integrationen/fastbill.md): Anbindung per E-Mail und API-Schlüssel; echtes Fälligkeitsdatum und Teilzahlungen, aber keine Mahnungen über die API - [Xentral](https://docs.paywise.de/integrationen/xentral.md): Anbindung per Anmeldung am Xentral-Konto; echtes Fälligkeitsdatum, keine Teilzahlungen und keine Mahnungen - [Sage Active](https://docs.paywise.de/integrationen/sage-active.md): Anbindung per Anmeldung am Sage-Active-Konto, mit Unternehmensauswahl; keine Teilzahlungen und keine Mahnungen - [Billomat](https://docs.paywise.de/integrationen/billomat.md): Anbindung per Billomat-ID und API-Schlüssel ab Business-Tarif; echtes Fälligkeitsdatum, echte Teilzahlungen, Mahnungen inklusive Mahngebühren - [WISO MeinBüro](https://docs.paywise.de/integrationen/wiso-meinbuero.md): Anbindung über den MeinBüro-Marktplatz; echtes Fälligkeitsdatum, Zahlungen und versendete Mahnungen, Abschlagsrechnungen ausgeschlossen; versorgt auch den Mahnservice, sofern das MeinBüro-Mahnwesen abgeschaltet und bestätigt ist - [orgaMAX Buchhaltung](https://docs.paywise.de/integrationen/orgamax.md): Anbindung über den orgaMAX-Marktplatz; nur orgaMAX Buchhaltung, nicht orgaMAX ERP; Abschlagsrechnungen einreichbar, Stornos ausgeschlossen; versorgt auch den Mahnservice, sofern das orgaMAX-Mahnwesen abgeschaltet und je Konto bestätigt ist - [Qonto](https://docs.paywise.de/integrationen/qonto.md): Anbindung per Qonto-Autorisierung; übernimmt unbezahlte Kundenrechnungen mit Fälligkeit, offenem Betrag, Teilzahlungen und verfügbarem PDF; versorgt auch den Mahnservice, sofern automatische Erinnerungen in Qonto deaktiviert und für das verbundene Unternehmen bestätigt sind - [easyVerein](https://docs.paywise.de/integrationen/easyverein.md): Anbindung per API-Schlüssel für Vereinsforderungen; einreichbar sind Mitgliedsbeitrag, Einnahme, Saldo und Spende, Entwürfe, Angebote und Stornos werden abgelehnt; kann parallel zu Buchhaltung oder DATEV verbunden sein, ein fehlendes PDF muss manuell ergänzt werden - [Stripe](https://docs.paywise.de/integrationen/stripe.md): Anbindung per API-Schlüssel, für ein Konto, mehrere Marken oder eine Organisation; die normale Rechnungsauswahl zeigt Rechnungen mit Status open und verlangt eine Prüfung in paywise, der Mahnservice übernimmt nur überfällige offene Euro-Rechnungen mit vollständigen Kunden- und PDF-Daten; je Stripe-Konto freigegeben - [apaleo](https://docs.paywise.de/integrationen/apaleo.md): Anbindung per apaleo-Autorisierung für offene Debitorenrechnungen aus dem Property-Management-System; nur unbezahlte, auf Debitor ausgecheckte Rechnungen ### DATEV The DATEV integration is the largest bookkeeping connector and is split into two independent features with separate authorisations and separate state: importing open items from DATEV into paywise as claims, and uploading paywise statements and advance invoices into DATEV Unternehmen online (Belege online). Pausing the import and revoking the connection are deliberately different actions with very different consequences. - [DATEV – Übersicht](https://docs.paywise.de/integrationen/datev/uebersicht.md): Die zwei unabhängigen Funktionen im Vergleich, Voraussetzungen und die Exklusivität gegenüber klassischen Buchhaltungsimporten; easyVerein ist ausgenommen - [DATEV verbinden](https://docs.paywise.de/integrationen/datev/verbinden.md): Mandant per DATEV-Anmeldung oder per Berater-/Mandantennummer verknüpfen, DATEV Connect über Cloud Gateway einrichten, Verbindung pausieren oder widerrufen - [Offene Posten importieren](https://docs.paywise.de/integrationen/datev/offene-posten.md): Forderungen von Hand einreichen oder automatisch nach Zeitplan und Regeln importieren; eine Forderung je offenem Posten statt je Buchungssatz - [Belege online](https://docs.paywise.de/integrationen/datev/belege.md): Abrechnungen und Vorschussrechnungen als Belege nach DATEV Unternehmen online übertragen; Mandantenbestand, Belegtyp, Statuswerte, Pausieren - [DATEV – Fehlerbehebung](https://docs.paywise.de/integrationen/datev/fehlerbehebung.md): Abgelaufene Verbindung, doppelte Forderungen, verschwundener Belegtyp, nicht übertragene Abrechnungen ### English versions Full English translations of every bookkeeping integration guide, maintained for partner and marketplace certification reviewers. The product interface itself is German, so these pages quote German button labels alongside their English explanation. - [Bookkeeping integrations – overview](https://docs.paywise.de/en/integrations/overview.md): Overview of all bookkeeping connectors, the shared connect-to-order flow, and what applies to every integration - [Lexware Office](https://docs.paywise.de/en/integrations/lexoffice.md): Connect by signing in to the Lexware Office account, including registering a new paywise account through Lexware Office with company data carried over; imports existing reminders and partial payments; also feeds the Mahnservice - [sevdesk](https://docs.paywise.de/en/integrations/sevdesk.md): Connect with an API token; due date from the sevdesk payment term, reminders including dunning level and fee; also feeds the Mahnservice - [FastBill](https://docs.paywise.de/en/integrations/fastbill.md): Connect with account email and API key; real due date and partial payments, but no reminders over the API - [Xentral](https://docs.paywise.de/en/integrations/xentral.md): Connect by signing in to the Xentral account; real due date, no partial payments and no reminders - [Sage Active](https://docs.paywise.de/en/integrations/sage-active.md): Connect by signing in to the Sage Active account, with a company picker; no partial payments and no reminders - [Billomat](https://docs.paywise.de/en/integrations/billomat.md): Connect with a Billomat ID and API key on the Business plan or above; real due date, real partial payments, reminders including dunning fees - [WISO MeinBüro](https://docs.paywise.de/en/integrations/wiso-meinbuero.md): Connect through the MeinBüro marketplace; real due date, payments and sent reminders, deposit invoices excluded; also feeds the Mahnservice once MeinBüro's own dunning is switched off and confirmed - [orgaMAX Buchhaltung](https://docs.paywise.de/en/integrations/orgamax.md): Connect through the orgaMAX marketplace; orgaMAX Buchhaltung only, not orgaMAX ERP; deposit invoices submittable, cancellations excluded; also feeds the Mahnservice once orgaMAX's own dunning is switched off and confirmed per account - [Qonto](https://docs.paywise.de/en/integrations/qonto.md): Connect through Qonto authorisation; imports unpaid client invoices with due date, open amount, partial payments and an available PDF; also feeds the Mahnservice once automatic reminders in Qonto are disabled and confirmed for the connected organisation - [easyVerein](https://docs.paywise.de/en/integrations/easyverein.md): Connect with an API key for club receivables; membership fee, revenue, balance and donation are submittable, drafts, offers and cancellations are refused; can coexist with bookkeeping or DATEV, and a missing PDF must be uploaded manually - [Stripe](https://docs.paywise.de/en/integrations/stripe.md): Connect with an API key, for one account, several brands or an organisation; the standard picker shows open invoices and requires review in paywise, while the Mahnservice imports only overdue open euro invoices with complete customer and PDF data; opted in per Stripe account - [apaleo](https://docs.paywise.de/en/integrations/apaleo.md): Connect with an apaleo authorisation for open accounts-receivable invoices from the property management system; only unpaid invoices checked out on accounts receivable - [DATEV – overview](https://docs.paywise.de/en/integrations/datev/overview.md): The two independent features compared, prerequisites, and exclusivity against classic bookkeeping imports; easyVerein is exempt - [Connect DATEV](https://docs.paywise.de/en/integrations/datev/connect.md): Link the client by DATEV sign-in or consultant/client number, set up DATEV Connect via Cloud Gateway, pause or revoke the connection - [Import open items](https://docs.paywise.de/en/integrations/datev/open-items.md): Submit claims by hand or import automatically on a schedule with rules; one claim per open item rather than per posting - [Belege online](https://docs.paywise.de/en/integrations/datev/documents.md): Upload statements and advance invoices as documents to DATEV Unternehmen online; client data set, document type, status values, pausing - [DATEV – troubleshooting](https://docs.paywise.de/en/integrations/datev/troubleshooting.md): Expired connection, duplicate claims, missing document type, statements that were not uploaded ## Mahnservice Der paywise Mahnservice ist das vollautomatische Mahnwesen für Unternehmen, die Lexware Office, sevDesk, WISO MeinBüro, Stripe, orgaMAX Buchhaltung oder Qonto nutzen. Überfällige Rechnungen werden automatisch importiert, über bis zu vier Stufen per E-Mail und Brief angemahnt und auf Wunsch ins paywise-Inkasso übergeben. Diese Anwenderdokumentation erklärt Einrichtung und Nutzung des Mahnservice. - [Mahnservice: Überblick](https://docs.paywise.de/user-docs/mahnservice/overview.md): Überblick über den vollautomatischen paywise-Mahnservice: Funktionsweise, Kernablauf, Dashboard und Einstieg. - [Registrierung & Onboarding](https://docs.paywise.de/user-docs/mahnservice/registrierung-onboarding.md): Einstieg in den paywise Mahnservice: Neuregistrierung mit geführtem Onboarding (Unternehmen, Buchhaltung, Einrichtungsassistent) oder Erste-Schritte-Checkliste für bestehende paywise-Kunden. - [Buchhaltung verbinden](https://docs.paywise.de/user-docs/mahnservice/buchhaltung-verbinden.md): Schritt-für-Schritt-Anleitungen für Lexware Office, sevDesk, WISO MeinBüro, Stripe, orgaMAX Buchhaltung und Qonto sowie Hinweise zu Import und Synchronisierung. - [Mahnlauf einrichten](https://docs.paywise.de/user-docs/mahnservice/mahnlauf-einrichten.md): Anleitung zur Konfiguration des automatischen Mahnlaufs: Stufen, Abstände, Kanäle, Mahngebühren, Eskalation, globale Optionen und Speicheroptionen. - [Mahnlauf pausieren & fortsetzen](https://docs.paywise.de/user-docs/mahnservice/mahnlauf-pausieren.md): Unternehmens-, Schuldner- und Rechnungspausen, Regeln zum Fortsetzen, Ausnahmen und Pause-Gründe. - [Schuldner verwalten](https://docs.paywise.de/user-docs/mahnservice/schuldner-verwalten.md): Kontaktdaten und Anschriften pflegen, Einzel-Sync und Vertragsart, plus Hinweise zu Lexware-Office-Sammelkunden und unpassenden E-Mail-Adressen. - [Eigenes Layout & Absenderdomain](https://docs.paywise.de/user-docs/mahnservice/branding.md): Branding ab Professional: Layout-Editor für Mahnschreiben (Logo, Primärfarbe, Stile) und eigene E-Mail-Absenderdomain mit DNS-Einrichtung. - [Inkasso-Übergabe](https://docs.paywise.de/user-docs/mahnservice/inkasso-uebergabe.md): Optionale Übergabe offener Mahnservice-Fälle ans paywise-Inkasso: Modi, Ablauf, Datenprüfung und manuelle Einzelübergabe. - [Tarife](https://docs.paywise.de/user-docs/mahnservice/tarife.md): Übersicht der drei Mahnservice-Tarife (Basis, Professional, Enterprise) mit Preisen und Selbstverwaltung (Wechsel, Rechnungen, Kündigung). - [Häufige Fragen (FAQ)](https://docs.paywise.de/user-docs/mahnservice/faq.md): FAQ zum paywise Mahnservice: Antworten zu Buchhaltungssystemen, Import, Mahngebühren, Versandkanälen, Pausieren, Inkasso, Branding und Tarifwechsel, plus Support-Kontakt. ## User documentation Guidance for working with the paywise platform itself, as opposed to its APIs. Both languages carry the same three top-level sections — user documentation, integrations and technical documentation. German is the default; the technical documentation exists only in English, and the German section links into it. - [Anwenderdokumentation](https://docs.paywise.de/user-docs/overview.md): Fachliche Dokumentation für die Arbeit mit paywise (German user documentation) - [Account- und Nutzerverwaltung](https://docs.paywise.de/user-docs/verwaltung/multi-user.md): Verwalten Sie Benutzer und Accounts in paywise — Teammitglieder einladen, zwischen Unternehmen wechseln, Accounts zusammenführen, getrennte Unternehmen für abweichende Vorsteuer-Einstellungen - [Technische Dokumentation](https://docs.paywise.de/technische-dokumentation.md): Deutschsprachiger Einstieg in die Schnittstellen — welche API wofür gedacht ist, Abgrenzung zu den fertigen Buchhaltungs-Integrationen, Hinweis auf die englische Referenz und die noch nicht ausgerollte Mahnservice API (Developer Preview) - [User documentation](https://docs.paywise.de/en/user-docs/overview.md): English entry point to the user documentation, with pointers to the integrations and the API reference - [Accounts and user management](https://docs.paywise.de/en/user-docs/administration/multi-user.md): Manage users and accounts in paywise — invite team members, switch between companies, merge accounts, separate companies for differing input-tax settings ## OpenAPI specs - [Case Management API OpenAPI specification](https://docs.paywise.de/api-docs/case-management-api/openapi.json): Current Case Management contract at the `/v2/` prefix. - [Partner API OpenAPI specification](https://docs.paywise.de/api-docs/partner-api/openapi.json): Current Partner contract at the `/partner/v2/` prefix. - [Mahnservice API OpenAPI specification](https://docs.paywise.de/api-docs/mahnservice-api/openapi.json): Current Mahnservice contract at the `/mahnservice/v1/` prefix.