TL;DR
Swedish reminder fees are capped by Förordning (1981:1057): 60 kronor for a påminnelse and 180 kronor for an inkassokrav. Those are ceilings rather than entitlements, which is why the shipped defaults are 0 kronor at level one, 60 at level two and 180 at level three, and why an organisation can lower them further. A schedule sends levels one and two. Level three is different in kind and is never sent automatically.
Three levels, and the third is not like the other two
Levels one and two are letters. They say the invoice is late, they carry a fee within the statutory cap, and they are the ordinary business of a receivables ledger.
Level three is the notice that the debt is going to collection. Handing a customer to an inkassobolag ends the commercial relationship about as often as it recovers the money, and that is a decision a person makes about a named customer with a history. So the nightly job stops at level two and reports what is waiting, rather than deciding for you.
That distinction is enforced in one place rather than being a matter of discipline. The schedule cannot reach level three; the button can.
The fees, and why the first one is free
The statutory maxima are 60 kronor for a reminder and 180 for a collection notice. The defaults that ship are:
| Level | What it is | Default fee | Statutory ceiling |
|---|---|---|---|
| 1 | Påminnelse | 0,00 kr | 60,00 kr |
| 2 | Påminnelse | 60,00 kr | 60,00 kr |
| 3 | Inkassokrav | 180,00 kr | 180,00 kr |
The first level carries no fee on purpose. A first reminder that arrives with a charge on it reads as a penalty for a delayed bank transfer, and the customer who reads it that way is usually right — most first reminders go to people whose payment crossed the letter in the post.
The ceilings are enforced at the settings screen rather than left as advice. A fee above the cap is not recoverable, it is printed on a document the customer may dispute, and the person typing it into a form has no way of knowing that.
The timeline, to the day
Two settings shape it. A grace period of 3 days on top of the due date, and a gap of 10 days between letters.
The grace period exists because a payment made on the last day takes a day or two to arrive, and a reminder that crosses it in the post is how a customer who paid on time is insulted.
Take an invoice issued 2 March 2026 on 30-day terms:
- 2026-04-01 — due date.
- 2026-04-02 — overdue by one day. Nothing is sent.
- 2026-04-04 — three days overdue, the grace period is satisfied, and level one goes out.
- 2026-04-14 — ten days after the level one letter, level two goes out with its 60,00 kr fee.
- After that — level three is waiting for somebody to press a button. The schedule will not send it.
The gap is measured from the last reminder rather than from the due date. An invoice discovered late — imported, or unblocked after a dispute — would otherwise have three letters fired at it in a single week.
What the level two letter actually says
Continue the example. On 2026-04-14 the invoice is 13 days overdue with 24 500,00 kr outstanding, and the organisation has configured a late-payment rate of 10,00 per cent (an illustration, not a rate this product ships):
Outstanding 24 500,00
Reminder fee, level 2 60,00
Interest, 13 days 87,26
Total 24 647,26
The interest is 24 500,00 × 0,10 × 13 / 365 = 87,26 kr, counted on actual days over 365, with no VAT on it. Payment terms and late-payment interest has the reasoning.
Those three figures are stored on the reminder row as amounts. Not as a rate and a date to be recomputed later — the letter said 87,26 and the record has to say 87,26 tomorrow as well.
The rules that stop a reminder being wrong
Five refusals, each of which returns a sentence somebody can read rather than a code:
A credit note is never chased. It is money owed to the customer, not by them.
An invoice that is not outstanding is never chased. Paid, credited, cancelled or written off — there is nothing there to ask for.
An invoice with nothing outstanding from the customer is never chased, which is the ROT case: the customer has paid their half and the rest is Skatteverket's.
The same level is never sent twice. There is a unique index on the invoice and the level, and the check is also asked in advance — a caught constraint violation is not an explanation, and this one has to be shown to whoever pressed the button.
A reminder cannot go backwards. An invoice already chased at level two cannot be sent a level one, and the refusal says which level it reached.
There is a sixth that matters more than it looks: a reminder needs somewhere to go. If the customer has no address, the action refuses rather than recording the letter. Writing a reminder row for a letter that went nowhere turns the invoice's own history into a lie, and the next person reading it concludes the customer is ignoring them.
The nightly job and the button ask the same questions
Two callers want to know the same things for different reasons. The scheduled job asks "is there anything to do here?" about every outstanding invoice in the system, and has to answer without writing anything. The screen asks "may I do this one?" about a level a person picked.
If each worked it out for itself they would drift, and the drift would surface as an office being told an invoice is not ready while the job quietly chases it anyway. So both ask one policy, and the only difference between them is the level each is allowed to reach.
That policy also answers "what comes next?" without reference to what a schedule may send — deliberately. Conflating the two is how the level three that a person is supposed to decide on becomes invisible instead of pending. The job reports it and moves on.
One more edge worth naming. If an invoice carries a reminder at a higher level with no timestamp recorded — rows written by an import, or by a repair script — it is treated as due rather than as never due. An invoice must not become permanently unchaseable because of a missing date.
Interest, fees and what you are actually owed
A late invoice accrues three things: the amount itself, the reminder fees within the statutory caps, and dröjsmålsränta from the due date. They are three separate figures for a reason — a customer disputing a fee is disputing something different from a customer disputing interest, and a single blended "amount now due" gives neither of you anything to point at.
What this module does not do
It does not hand a debt to a collection agency. Level three is a notice you send, drafted and recorded here, and what happens next is a commercial decision and a relationship with an inkassobolag that is yours rather than ours.
It also does not keep your books. The receivables ledger is here; the general ledger, the year-end close and the VAT return are not. The SIE4 file your accountant opens is how the two meet.