How I Won a SaaS Billing Dispute in 10 Days Using Swedish Contract Law
April 2026
A Swedish cloud accounting platform took my subscription payment, blocked my account, and refused to deliver service or issue a refund. Ten days after I sent a formal complaint, the debt was waived and access was restored — in writing, no legal fees.
Here is exactly what happened and what worked.
The Setup
In August 2024, a payment to Bokio failed. Bokio cancelled the subscription and recorded an outstanding debt on my account. Fine — that happens.
In April 2026, I decided to start fresh. I signed up again, paid for a 3-month subscription (April 3 – July 2, 2026), and expected to get to work. Instead, Bokio locked the account again immediately, citing the unpaid 2024 debt. They had taken a new payment — for a new subscription period — and provided nothing in return.
I cancelled the subscription in frustration on April 6. But money had changed hands, and I wasn’t going to let that stand.
The Complaint
On April 10, I sent a formal reklamation — a written legal complaint — via email. Bokio’s first response arrived on April 14. Their position: I was a näringsidkare (business operator, not a consumer), consumer protection law didn’t apply, and their general terms gave them the contractual right to block access when an outstanding debt existed.
This is where most disputes end. People accept the company’s framing, give up, or accept a partial resolution. I didn’t — because their response, while partially correct, answered the wrong question.
The Arguments That Won
1. Concede the weak point, lead with the strong one
Bokio was right that consumer protection law didn’t apply to me as a sole trader (enskild firma). I conceded this immediately in my counter-response. There’s no value in defending a losing argument — it wastes everyone’s time and undermines credibility.
But conceding that point had no effect on the actual legal issue.
2. Unjust Enrichment: The Right They Didn’t Have
Bokio’s general terms gave them the right to block access when a debt exists. That’s a contractual right. What their terms do not — and cannot — grant is the right to retain a separate, fully paid subscription fee while delivering nothing in return.
This distinction between the right to block access and the right to keep payment is the crux of the entire dispute, and it’s the one their initial response completely glossed over.
The applicable legal principle is unjust enrichment (obehörig vinst / condictio indebiti) — a foundational doctrine in Swedish contract law. When one party receives payment and delivers no performance, the receiving party is unjustly enriched at the payer’s expense, regardless of any other debts or disputes between them. This applies equally between businesses.
My counter-response stated this directly:
“En part kan inte behålla betalning utan att leverera avtalad motprestation, oavsett om det föreligger andra oreglerade fordringar mellan parterna.”
(“A party cannot retain payment without delivering the agreed performance, regardless of whether there are other unsettled claims between the parties.”)
3. A Disputed Debt Cannot Unilaterally Offset a Separate Transaction
Bokio’s implicit argument was that the 2024 debt justified withholding the 2026 subscription service — a form of informal setoff. But a disputed B2B debt doesn’t grant the creditor the right to unilaterally offset it against a completely separate, fully paid transaction.
If Bokio believed the 2024 debt was valid, the correct legal remedies were:
- Filing for a betalningsföreläggande (payment order) at Kronofogdemyndigheten
- Initiating civil proceedings at the District Court (tingsrätten)
Not: accepting a new payment for a new subscription and then providing nothing.
I named this explicitly, along with the escalation path I intended to follow if demands weren’t met (Kronofogden, IMY, tingsrätten). This isn’t a threat — it’s a roadmap. It shows you understand the process and are prepared to follow it.
4. GDPR Article 20 as Independent Leverage
In parallel with the billing dispute, I submitted a formal request under GDPR Article 20 (right to data portability) for a complete export of my accounting data in SIE4 format, with a 30-day deadline (May 11, 2026).
GDPR is mandatory law. It cannot be waived or overridden by contractual terms. And critically — a payment dispute is not a valid legal basis for refusing a data portability request. The two obligations are independent.
This created a second track that Bokio had to address regardless of how the billing dispute resolved. Non-compliance with a GDPR data portability request exposes a company to regulatory enforcement by IMY (Sweden’s data protection authority) under Article 83.
The Resolution
Bokio’s response came on April 16 — six days after my formal complaint, two days after my counter-response. Their email acknowledged the principle directly:
“Bokio ansvarar för att leverera i enlighet med ingånget avtal - förutsatt att kunden har gjort sin del av prestationen. Trots att så inte är fallet […] väljer Bokio att i detta fall ta bort skulden från augusti 2024 och därmed ge dig tillgång till tjänsterna för den period som du nu har erlagt betalning för (3 april - 2 juli 2026).”
Translation: Bokio agreed to waive the entire 2024 debt and restore access for the April 3 – July 2 subscription period — exactly what was demanded.
Written confirmation of account restoration arrived on April 20 from Bokio Customer Support:
“Vi har nu tagit bort skulden, och du har återfått tillgång till ditt konto.”
(“We have now removed the debt, and you have regained access to your account.”)
Total time from formal complaint to written confirmation: 10 days.
A Note on the GDPR Question
Bokio’s position on the data portability request was that accounting records (SIE files) are data I created in their system, not data I provided to them, and therefore Article 20 portability rights don’t apply. They argued the distinction lies between Article 15 (right of access, broader) and Article 20 (portability, narrower — limited to data “provided” by the data subject).
This is a reasonable interpretation of the current regulatory landscape. The boundary between Article 15 and Article 20 for user-generated content in SaaS platforms is genuinely unsettled in EU case law.
Since account access was restored and I could self-export my SIE files directly, the GDPR claim became moot as a separate enforcement track. But for someone in a situation where access was permanently revoked, this would be worth pursuing with IMY — the argument that a user’s own accounting entries constitute data they “provided” to the controller has genuine legal merit.
What Actually Works in These Disputes
Concede precisely, then redirect. If the company makes a correct point, acknowledge it and move on. Using your credibility on the points that matter.
Separate the rights they have from the rights they claim. “We can block your access” and “we can keep your money” are legally distinct. Companies often conflate them. Naming the distinction clearly forces them to engage with it.
Lead with a principle, not a complaint. Unjust enrichment is a principle. “This isn’t fair” is a complaint. Principles are harder to dismiss.
Create parallel tracks. A GDPR data portability request runs independently of a billing dispute. Two compliance obligations are harder to ignore than one.
Name your escalation path and deadline explicitly. Not as a bluff — as information. If you know you’d actually file at Kronofogden, saying so is simply accurate. Companies weigh the cost of continued resistance against the cost of resolution.
Write everything down. Every exchange via email. No phone calls. No ambiguity about what was said or agreed.
The Numbers
| Subscription paid | April 3, 2026 |
| Account blocked | Immediately |
| Formal complaint sent | April 10, 2026 |
| Bokio’s concession | April 16, 2026 |
| Written confirmation | April 20, 2026 |
| Total time | 10 days |
| Legal fees | 0 kr |
| 2024 debt waived | Yes |
| Account restored | Yes |
Dennis Dyall is a developer and sole trader (enskild firma) based in Sweden.