[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 Fiken invoices with payment reminders

> Find overdue Fiken invoices and send reminders or dunning letters by days past due, leaving old cases to you. Runs weekly from Claude Code or n8n.

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

Invoices pass their due date quietly, and someone has to open each one in Fiken, work out whether a reminder is allowed yet and send it.

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

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

Hosted · nothing to install or maintain

## Can Fiken do this on its own?

Fiken can chase automatically (checked 14 Oct 2026), but only with a KID agreement with your bank, KID/OCR ordered under Foretak → Tilleggstjenester and an agreement with Kravia, its partner for external follow-up; it applies only to invoices created after you switch it on. The Fiken API has no endpoint for reminders or dunning letters. Nothing in Fiken chases older invoices by a rule of your own.

## How you do it in Fiken today

1. Open Salg → Faktura-/salgsoversikt and look for invoices past their due date; the small arrow at the right of an invoice shows the options Fiken allows for it.
2. Click the invoice and, once the due date has passed, click Veiviser for forfalt faktura.
3. Click Lag en påminnelse eller purring, choose Følg opp på egenhånd, pick the type and create it, then send it to the customer.
4. Fiken allows a reminder once the invoice is due, but no fee and no collection until 14 days after the due date.
5. Repeat per invoice every week, and check before each one that the customer has not paid, because payments are registered by hand unless you have a KID agreement.

## How to chase overdue Fiken invoices with payment reminders

Prompt

```
Every Monday, find overdue invoices in Fiken. Send a reminder by email to those up to 13 days overdue and a dunning letter to those 14 to 44 days overdue. List anything older for me and do not touch it.
```

1. 01  
### Find what is overdue  
list\_invoices runs with status overdue and returns the invoices unpaid and past their due date, oldest first. Drafts and settled invoices are never in the list.
2. 02  
### Re-read each invoice  
get\_invoice shows the balance and the payments registered so far. An invoice that got a payment after the list was read is skipped, so nobody is chased for money that arrived this morning.
3. 03  
### Pick the step by days past due  
The agent applies the rule from your prompt: a reminder in the first 13 days, a dunning letter from day 14, and nothing automatic beyond the limit you set. Fiken itself refuses a fee before day 14, so the agent never asks for one earlier.
4. 04  
### Send by email  
create\_reminder goes out by email by default. Fiken does not send reminders as EHF, even when the invoice went out that way, so the agent does not try it. Each reminder waits for your OK by default.
5. 05  
### Leave collection to you  
Invoices past your limit are listed with days overdue and amount. Sending a case to external follow-up (inkasso) through Kravia stays your decision, and no Cotlet tool does it.

### What you get back

Example data

```
Overdue invoices: 7
Reminders sent by email: 4, e.g. 10031 Havbris Maritim AS, 8,750 NOK, 14 days overdue
Dunning letters sent: 1 (invoice 9984, 31 days overdue)
Skipped 1: payment registered since the list was read
Left for you 1: invoice 9950 is 52 days overdue, your call on external follow-up
```

### Other ways to ask

- List overdue invoices by customer with total owed per customer, and send nothing.
- Send a reminder only to customers whose invoice is between 1 and 7 days overdue and tell me who is left.
- Every Friday, show invoices that will fall due next week so I can warn the big customers myself.
- For invoices more than 30 days overdue, draft the follow-up message and wait for my OK before sending.

## What Fiken allows, and what to know first

- Fiken offers a reminder once the invoice is due, but no fee and no external collection until 14 days after the due date.
- A dunning letter (purring) can carry a fee of at most kr 38 and must give the customer at least 14 days to pay, according to the Fiken help center.
- Fiken does not send reminders or dunning letters as EHF; it suggests email even if the invoice went out by EHF.
- If a customer pays without the dunning fee, register the amount actually paid first and then delete the fee, and the invoice stands as settled.
- Changing the due date in Fiken does not change the invoice itself; it only records, for example, an oral agreement with the customer.

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

Sources: [Fiken Help: Faktura - oversikt og oppfølging](https://hjelp.fiken.no/faktura---oversikt-og-oppfoelging) · [Fiken Help: Hvordan opprette en purring manuelt i Fiken](https://hjelp.fiken.no/kunde-har-ikke-betalt-jeg-vil-starte-purring-selv-foer-inkasso) · [Fiken Help: Automatisk purring av ubetalt faktura](https://hjelp.fiken.no/automatisk-purring-av-ubetalt-faktura) · [Fiken API v2 documentation](https://api.fiken.no/api/v2/docs/)

## Call create\_reminder from a script

curl

```
curl -X POST https://cotlet.dev/api/v1/fiken/invoices/5120288/reminders \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"type":"reminder","method":"email"}'
```

Example response

```
{
"invoice_id": 5120288,
"invoice_number": 10031,
"type": "reminder",
"method": "email",
"to": "okonomi@havbris.example",
"days_overdue": 14
}
```

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

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

## Fiken tools this automation uses

__Cotlet Fiken tools used to chase overdue Fiken invoices with payment reminders__
| Tool | Parameters |
| ---------------- | ------------------------------------------------ |
| list\_invoices | status, customer\_id, due\_before, limit, cursor |
| get\_invoice | invoice\_id |
| create\_reminder | invoice\_id, type, method |

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

## Frequently asked questions

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

Yes. You sign in to Fiken yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get Fiken 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 Fiken automations

- [Create and send Fiken invoices from a list](https://cotlet.dev/integrations/fiken-api-mcp-server/create-and-send-invoices.md)
- [Book Fiken receipts and supplier invoices as purchases](https://cotlet.dev/integrations/fiken-api-mcp-server/book-receipts-as-purchases.md)
- [Fiken API and MCP server: every tool](https://cotlet.dev/integrations/fiken-api-mcp-server.md)
- [All use cases](https://cotlet.dev/use-cases.md)

## Give your agent access to Fiken.

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

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

---

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.