SW

swedish-invoice-compliance

Provides regulatory guidance on Swedish invoicing (fakturering), including legal requirements and BAS accounting.

Install

mkdir -p .claude/skills/swedish-invoice-compliance && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/12025" && unzip -o skill.zip -d .claude/skills/swedish-invoice-compliance && rm skill.zip

Installs to .claude/skills/swedish-invoice-compliance

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Swedish invoice compliance (fakturering) reference. Covers mandatory invoice fields per ML 17 kap 24§ (2023:200), förenklad faktura, kreditfaktura/ändringsfaktura, självfakturering, Peppol BIS 3.0 e-faktura for B2G/B2B, ROT/RUT-avdrag invoicing with fakturamodellen and BAS accounts (1513, 3740), reverse charge notation per scenario (byggtjänster, EU, electronics), currency/VAT conversion, OCR/Bankgirot, autogiro, skattetillägg, and BAS mapping for AR/revenue/VAT/bad debts. Trigger on ANY Swedish invoice question, faktura validation, kreditfaktura, självfakturering, Peppol, e-faktura, ROT/RUT fakturering, omvänd betalningsskyldighet, faktureringsvaluta, OCR-nummer, ML 17 kap, fakturamodellen, or creating/validating/booking Swedish invoices. Always use over training data -- ML 2023:200 replaced ML 1994:200 on 1 July 2023, moving invoice rules from old Chapter 11 to Chapter 17.
887 charsno explicit “when” triggerlonger than Claude Code's old 250-char listing cap (fine on current versions)
Intermediate

Key capabilities

  • →Validate mandatory invoice fields per ML 17 kap 24§
  • →Determine if a simplified invoice can be used
  • →Identify applicable reverse charge scenarios
  • →Verify ROT/RUT invoice compliance
  • →Check credit note requirements

How it works

This skill references Swedish tax law (ML 17 kap 24§) and related regulations to validate invoice fields, simplified invoice eligibility, reverse charge scenarios, ROT/RUT invoicing, and credit note requirements.

Inputs & outputs

You give it
Invoice details or specific compliance questions
You get back
Validation of invoice compliance against Swedish law

When to use swedish-invoice-compliance

  • →Validate Swedish invoice compliance
  • →Check Peppol requirements
  • →Account for ROT/RUT deductions

About this skill

<!-- SPDX-License-Identifier: MIT; Copyright (c) Accounted contributors. Generated mirror; edit the Accounted source. -->

Swedish Invoice Compliance (Fakturering)

Invoicing rules moved from Chapter 11 (ML 1994:200) to Chapter 17 (ML 2023:200) on 1 July 2023. Every legacy reference to "ML 11 kap" maps to ML 17 kap in current law. Always cite ML (2023:200). Account numbers follow BAS 2026.

How to use this skill

FileWhen to read
references/decision-trees.mdValidating or building one invoice: the 17-point ML 17:24 check, whether a förenklad faktura is allowed, which reverse charge scenario applies, ROT/RUT requirements, the credit note checklist, and the common error patterns with their fixes
references/invoice-rules.mdThe rules behind those trees, in 16 numbered sections: mandatory fields, förenklad faktura, time limits, kreditfaktura, självfakturering, Peppol BIS 3.0 and the ML→UBL mapping, ROT/RUT, reverse charge, currency, OCR, autogiro, penalties, BAS mapping, law references, time-dependent parameters

Is this invoice valid?

Walk ML 17 kap 24§ in order. Points 1-11 are always required:

fakturadatum (p.1), unique löpnummer from a series (p.2), seller's and buyer's momsreg.nr (p.3-4, the buyer's only when reverse charge or intra-EU), both parties' name and address (p.5-6), quantity and nature of the goods or services (p.7), delivery or prepayment date when it differs from the invoice date (p.8), beskattningsunderlag per skattesats and unit price excl. VAT (p.9), the VAT rate (p.10), the VAT amount and also in SEK (p.11, 17:29).

Point 12 adds the notation the case calls for: "Självfakturering", an exemption reference, "Omvänd betalningsskyldighet", new-means-of-transport details, or a margin scheme statement.

Missing any of 1-11 = non-compliant. Missing 12 when applicable = non-compliant. Prepayments and a conto payments must also be invoiced (ML 17:14).

The full tree, and the simplified-invoice, reverse-charge, ROT/RUT and credit note trees, are in references/decision-trees.md.

Never guess these

SituationWhyWhat to do
The ROT percentage for a job30 % is standard, but 50 % applied 12 May-31 Dec 2025 and the 2024 H2 caps were separatedTake the payment date, then read the rates table in invoice-rules.md §8
Whether the buyer accounts for the VATCharging VAT when reverse charge applies leaves the buyer unable to deduct itSettle the scenario first (decision-trees.md §3), then charge 0 % and add the notation
Which account a reverse charge posts toDomestic and foreign acquisitions use different input VAT accounts (2647 vs 2645)Read the account table in invoice-rules.md §9
Whether a customer has ROT/RUT room leftThe cap is per person per year across all suppliers, and Skatteverket pays shortAsk the customer, and expect part payments
The status of a B2B e-invoicing mandateB2G is mandatory since April 2019; no domestic B2B mandate has been decidedRead the timeline in invoice-rules.md §7 before stating any date
An invoice in foreign currencyThe rate source and the taxable-event date are both prescribedRead invoice-rules.md §10; always show the VAT amount in SEK

Peppol e-invoices in Accounted

Accounted sends Peppol BIS Billing 3 e-invoices from the invoice page in the dashboard (POST /api/invoices/{id}/peppol/send, Access Point: Qvalia). Sending is gated per company: access is requested under Inställningar > Kopplingar > E-faktura via Peppol (Settings > Connections > E-invoicing via Peppol) and enabled by Accounted's operators; a grant may carry a send cap, and when it is used up the dashboard says so and support raises it. Restrictions: senders with an organisationsnummer, which is every legal form except enskild firma (its org number is the owner's personnummer, so it needs a GLN, not yet supported), standard invoices only (no credit notes, no self-billing), Swedish org-number buyers (scheme 0007; a buyer whose org number is a personnummer, i.e. an enskild firma customer, is refused until GLN identifiers are supported), SEK invoices with taxable Swedish VAT at 6, 12 or 25 % only (no reverse charge, no VAT-exempt sales, no ROT/RUT deductions), and Er referens (BuyerReference) set. Agents send with gnubok_send_invoice_peppol (staged, a person approves; check gnubok_get_invoice_peppol_readiness first) or v1 POST /api/v1/companies/{companyId}/invoices/{id}/send-peppol, under the same grant and restrictions. Never describe Peppol sending as absent; it is gated per company. A successful dashboard Peppol send issues the invoice itself, so do not mark it as sent afterwards. If the dashboard reports that the invoice was sent via Peppol but could not be marked as sent, complete the issuance with gnubok_mark_invoice_as_sent on the still-draft invoice (if it already shows as sent, the verifikat exists and only its link to the invoice needs repair: do not mark it as sent again, leave the repair to support). Where access is not granted, or the sender is an enskild firma, use an external e-invoice provider for delivery, then record the delivery with gnubok_mark_invoice_as_sent.

Peppol format, identifiers, SE-R validation rules and the ML to UBL mapping: references/invoice-rules.md §7.

Related skills

QuestionSkill
VAT rates, rutor, reverse charge and EU trade in depthswedish-vat
Byggmoms, ROT in a construction context, ÄTAvertical/bygg-hantverk
Distance selling, OSS/IOSS, marketplacesvertical/e-handel
Verifikationer, archiving, bookkeeping dutyswedish-accounting-compliance
Exporting or importing the invoice ledgerswedish-sie-import-export
Kundfordringar at year end, bad debt provisionsswedish-year-end-closing
Invoicing against project progressswedish-project-accounting

When not to use it

  • →When validating non-Swedish invoices
  • →When the legal framework is not ML 2023:200
  • →When not dealing with fakturamodellen or BAS accounts

Limitations

  • →Only applies to Swedish invoice compliance
  • →Relies on ML 17 kap 24§ (2023:200) and related laws
  • →Does not cover non-Swedish tax regulations

How it compares

This workflow provides specific, up-to-date guidance on Swedish invoice compliance, including recent legal changes and common error patterns, unlike general invoicing advice.

Compared to similar skills

swedish-invoice-compliance side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
swedish-invoice-compliance (this skill)07moNo flagsIntermediate
directed-share-program07moNo flagsAdvanced
coverage-scope-judgment06moNo flagsIntermediate
fintech_inversiones06moNo flagsIntermediate

Try saying

Example prompts that trigger this skill in your AI assistant.

You might also like

directed-share-program

CaseMark

Drafts a Directed Share Program (DSP) agreement governing share allocation and purchase by designated participants in a U.S. public offering or IPO. Covers eligibility, allocation methodology, pricing, settlement, lock-up, indemnification, and SEC/FINRA compliance. Use when preparing DSP documentati

00

coverage-scope-judgment

FDU-INS

当用户需要判断某项损失或疾病是否在保险责任范围内时使用此 skill。适用于理赔责任判定、免责条款解读、保障范围咨询等场景。

00

fintech_inversiones

Walter102202

Activar cuando el usuario describa una inversión, plataforma de crowdfunding, asesoría crediticia o de inversión, custodia digital, exchange de criptoactivos local, rendimientos prometidos por una fintech, sistema de finanzas abiertas (Open Finance), o duda sobre si una plataforma está autorizada po

00

legal-risk-assessment

anthropics

Assess and classify legal risks using a severity-by-likelihood framework with escalation criteria. Use when evaluating contract risk, assessing deal exposure, classifying issues by severity, or determining whether a matter needs senior counsel or outside legal review.

336

fda-consultant-specialist

alirezarezvani

FDA regulatory consultant for medical device companies. Provides 510(k)/PMA/De Novo pathway guidance, QSR (21 CFR 820) compliance, HIPAA assessments, and device cybersecurity. Use when user mentions FDA submission, 510(k), PMA, De Novo, QSR, premarket, predicate device, substantial equivalence, HIPAA medical device, or FDA cybersecurity.

214

mdr-745-specialist

alirezarezvani

EU MDR 2017/745 compliance specialist for medical device classification, technical documentation, clinical evidence, and post-market surveillance. Covers Annex VIII classification rules, Annex II/III technical files, Annex XIV clinical evaluation, and EUDAMED integration.

213

Search skills

Search the agent skills registry