[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# Chase overdue sevdesk invoices with payment reminders

> Find overdue sevdesk invoices every week and send each customer a payment reminder, with your OK per send and VIPs left for you.

Source: https://cotlet.dev/integrations/sevdesk-api-mcp-server/chase-overdue-invoices

Open the Fällig tab in sevdesk on a Monday and the overdue invoices are all there, but each reminder is its own click path, so the list gets shorter only on the days someone has an hour for it.

Cotlet does it in your own sevdesk account with list\_invoices, get\_invoice and create\_payment\_reminder, called by your AI agent, an n8n workflow or a script.

[Sign up free](https://cotlet.dev/app/signup?app=sevdesk) [All sevdesk tools](https://cotlet.dev/integrations/sevdesk-api-mcp-server.md)

Hosted · nothing to install or maintain

## Can sevdesk do this on its own?

sevdesk creates every reminder by hand from the invoice (checked 14 Oct 2026). Its help articles describe a click per invoice, and the API offers createInvoiceReminder only on the Buchhaltung Pro plan. Nothing in sevdesk chooses which invoices to chase or asks you before a reminder goes out.

## How you do it in sevdesk today

1. In the main menu, go to Rechnungen and open the tab Fällig. sevdesk shows the overdue invoices.
2. Open the invoice and click the button Mahnung / Zahlungserinnerung. sevdesk fills a mask with the standard text, which you can edit.
3. Choose Versenden / Drucken / Herunterladen to send the reminder. It then sits under Rechnungen > Mahnungen.
4. If the customer still has not paid, use Nächste Mahnung erstellen on the invoice or on the reminder. This needs the Buchhaltung plan, and the Mahnfrist must be set under Einstellungen > System > Aufträge & Rechnungen.
5. Repeat for every overdue invoice. Nothing tells you which invoices already got a reminder except the Mahnungen list.

## How to chase overdue sevdesk invoices with payment reminders

Prompt

```
Every Monday, list my sevdesk invoices that are overdue. For each one with no reminder yet, send a friendly payment reminder. Skip customers I tagged as VIP in the contact description and list them for me.
```

1. 01  
### Pull the overdue list  
list\_invoices runs with status due, the same set as the Fällig tab, and pages through the cursor, so a long backlog is judged as one list and not just the first page.
2. 02  
### Skip who is already chased  
For each invoice the agent opens get\_invoice and checks whether a reminder is linked to it. An invoice that already got a Zahlungserinnerung this month goes to the "left for you" list instead of getting a second letter.
3. 03  
### Apply your own rule  
Your prompt decides who is skipped, for example customers whose contact description says VIP, or invoices above an amount you named. The agent names the rule it used next to each skipped invoice.
4. 04  
### Send one reminder per invoice  
create\_payment\_reminder creates the reminder and emails it to the invoice contact. Each send waits for your OK until you switch confirmation off for that tool, so no customer gets a letter you did not see.
5. 05  
### Report what went out  
The agent returns who got a reminder, who was skipped and why, and the invoices that are overdue but have no email address on the contact, so you can fix the contact in sevdesk.

### What you get back

Example data

```
Overdue invoices: 7
Reminders sent 4:
- RE-1031 Brandt GmbH, 226.10 EUR, due 28 Sep
- RE-1036 Nordlicht Studio, 1,963.50 EUR, due 30 Sep
Left for you 2 (marked VIP):
- RE-1029 Keller & Sohn, 4,760.00 EUR
No email on the contact 1:
- RE-1038 Mara Voss
```

### Other ways to ask

- Every Friday, send the second reminder to invoices that got a Zahlungserinnerung more than 14 days ago, and list them first.
- Show me the overdue invoices sorted by amount and send nothing.
- Remind only customers in the Kunde category with invoices over 500 EUR.
- Draft the reminder text for each overdue invoice in German and wait for my OK on every one.

## What sevdesk allows, and what to know first

- sevdesk starts with a Zahlungserinnerung, and a Mahnung can only be based on an invoice that already got a reminder.
- Sending Mahnungen needs the Buchhaltung plan or higher; the first Zahlungserinnerung is described without a plan limit.
- The Mahnfrist is set once under Einstellungen > System > Aufträge & Rechnungen, in the section Mahnung.
- sevdesk does not limit the number of Mahnstufen, so a third or fourth reminder is possible.
- When an invoice is marked as paid, every linked reminder changes to Bezahlt at the same time.

create\_payment\_reminder asks for your OK by default. To run it weekly without you, switch confirmation off for that tool in your dashboard.

Sources: [sevdesk Help: Zahlungserinnerung schreiben](https://hilfe.sevdesk.de/de/articles/9071059-zahlungserinnerung-schreiben) · [sevdesk Help: Mahnungen](https://hilfe.sevdesk.de/de/articles/9167192-mahnungen) · [sevdesk Help: sevdesk API](https://hilfe.sevdesk.de/de/articles/9374668-sevdesk-api)

## Call create\_payment\_reminder from a script

curl

```
curl -X POST https://cotlet.dev/api/v1/sevdesk/invoices/41872618/payment-reminders \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"message":"Hello Mr. Brandt, invoice RE-1031 was due on 28 September. Could you please transfer the open amount in the next days? Thank you."}'
```

Example response

```
{
"reminder_id": "88100412",
"invoice_id": "41872618",
"kind": "payment_reminder",
"status": "sent",
"sent_to": "billing@brandt-gmbh.example",
"sent_at": "2026-10-14T09:10:00+02:00"
}
```

MCP: add https://cotlet.dev/mcp/v1 with the same key; the call is sevdesk\_write → create\_payment\_reminder. Example data.

[Schedule it in n8n, Make, Zapier or cron](https://cotlet.dev/integrations/sevdesk-api-mcp-server.md#automations)

## sevdesk tools this automation uses

__Cotlet sevdesk tools used to chase overdue sevdesk invoices with payment reminders__
| Tool | Parameters |
| ------------------------- | ------------------------------------------------------------------------- |
| list\_invoices | status, contact\_id, invoice\_number, from\_date, to\_date, limit, cursor |
| get\_invoice | invoice\_id |
| create\_payment\_reminder | invoice\_id, message |

[All 14 sevdesk tools with descriptions](https://cotlet.dev/integrations/sevdesk-api-mcp-server.md#tools)

## Frequently asked questions

### Is it safe to connect sevdesk to Cotlet?

Yes. You sign in to sevdesk yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get sevdesk once you enable it, every background request is listed, and the browser profile is stored encrypted with AES-256-GCM, the cipher 1Password uses for its vaults. The AI model never sees a login, posts and messages wait for your OK, and Disable for agents cuts access in one click. Independent scanners grade cotlet.dev A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory; live results are on https://cotlet.dev/security.

## More sevdesk automations

- [Create and send sevdesk invoices from a short brief](https://cotlet.dev/integrations/sevdesk-api-mcp-server/create-and-send-invoices.md)
- [Digitize receipts in sevdesk and mark them paid](https://cotlet.dev/integrations/sevdesk-api-mcp-server/digitize-receipts.md)
- [sevdesk API and MCP server: every tool](https://cotlet.dev/integrations/sevdesk-api-mcp-server.md)
- [All use cases](https://cotlet.dev/use-cases.md)

## Give your agent access to sevdesk.

Free 7-day trial with 2,000 credits, no card needed. Cotlet is independent and not affiliated with sevdesk.

[Sign up free](https://cotlet.dev/app/signup?app=sevdesk)

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.

## For AI agents: sign your user up

Is your user asking you to sign them up for Cotlet? You can do it for them, no account or key needed.

1. Read the fields and their allowed values: GET https://cotlet.dev/api/v1/access-requests
2. Ask the user for each value: email, apps, what you will do with them. If they leave the password to you, generate a strong one and show it to them.
3. Show the user what you will send, then POST it as JSON to https://cotlet.dev/api/v1/access-requests.

One call creates the account and sends the access request; we email the user when access is granted.