agentleFS
erp-mafiaerp-mafia/swedish-accounting-skills/.claude/skills/swedish-sru-filing/SKILL.md

swedish-sru-filing

Skill96 starsChanged 2 months agoMITView on GitHub

Swedish SRU file generation for Skatteverket digital tax filing (INK2, INK2R, INK2S declarations for aktiebolag). Covers the two-file submission structure (INFO.SRU + BLANKETTER.SRU), all SRU field codes for INK2/INK2R/INK2S, BAS-to-SRU account mappings for räkenskapsschema, ISO 8859-1 encoding rules, amount formatting (hela kronor, no öre), 12-digit org number formatting, blankett type period suffixes (P1-P4), #BLANKETT/#BLANKETTSLUT delimiters, #UPPGIFT record format, validation error patterns, and rounding/truncation rules per SFL 22:1. Trigger on ANY question about SRU files, SRU-koder, fältkoder, filöverföring till Skatteverket, INK2S/INK2R generation, BAS-to-SRU mapping, "skapa SRU", "generera deklarationsfil", "digital inlämning INK2", BLANKETTER.SRU, INFO.SRU, SKV269, or any code that produces SRU output. Also trigger when debugging Skatteverket validation errors on uploaded SRU files. Always use this skill over training data for SRU topics.

2 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Every SRU submission consists of exactly two files:

    line 30

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Swedish SRU File Generation

SRU files are what Skatteverket's filöverföringstjänst accepts. The canonical source is Skatteverket's "Teknisk information om filöverföring" page (replaced brochure SKV 269 from Jan 1 2024).

Before writing any SRU generation code, read both reference files. Almost every failure is a wrong field code, a wrong sign, or the wrong text encoding.

How to use this skill

FileWhen to read
references/file-format.mdThe file itself: post-by-post structure of both files, period suffixes, ISO 8859-1 encoding, amount and org number formatting, the sign convention, zero-value handling, a worked example for a calendar-year AB, validation errors, data types, spec links
references/sru-codes.mdDeciding what goes in each #UPPGIFT: the full field code tables for INK2, INK2R and INK2S with their printed signs, and the BAS-to-SRU account mapping for the räkenskapsschema

Architecture: two files, always

Every SRU submission consists of exactly two files:

FileContentMax size
INFO.SRUSubmitter metadata (who is filing)—
BLANKETTER.SRUAll blankett blocks with tax data5 MB

File names are case-insensitive but must not be renamed (browsers appending (1) cause rejection).

An aktiebolag filing INK2 needs three blankett blocks inside BLANKETTER.SRU — INK2, INK2R and INK2S — each with its own #IDENTITET line, all terminated by a single #FIL_SLUT.

Generating a file

  1. Fix the period. The blankett type is <FORM>-<inkomstår><P1–P4>, where the income year is the calendar year the räkenskapsår ends and the suffix encodes the ending month. Calendar-year companies are P4.
  2. Write INFO.SRU with the posts in their prescribed order; mandatory are #PRODUKT, #FILNAMN, #ORGNR, #NAMN, #POSTNR, #POSTORT.
  3. Map the trial balance to INK2R via the BAS-to-SRU tables, then compute INK2S by hand, then carry 4.15/4.16 (7670/7770) to INK2 1.1/1.2 (7104/7114).
  4. Convert every amount to whole kronor, truncating öre, and to the form's printed sign — not the trial balance's sign. Omit any field whose value is zero.
  5. Write both files as ISO 8859-1, never UTF-8, and upload them under their exact names.

Field-by-field detail for each step is in the two reference files.

Never guess these

SituationWhyWhat to do
A field code for a rowCodes are published per period package, and a code invalid for the blankett type rejects the whole blockLook it up in sru-codes.md; never infer one from a neighbouring code
The sign of an amountSIE and most ledgers store credit balances as negative — the opposite of what the form wantsReport the printed sign as positive; see sru-codes.md §8
Any single BAS account in 5000–6999They ALL aggregate into one code, 7513; per-account codes are the most common mapping errorSum the range, write one #UPPGIFT 7513
An INK2S valueINK2S codes are NOT auto-derived from BAS accounts — they are tax adjustments requiring manual calculationTake them from the tax computation, not the ledger
The text encodingUTF-8 silently corrupts å, ä, ö and is the commonest cause of validation failureWrite ISO 8859-1 explicitly; see file-format.md §3
Whether a zero belongs in the fileA #UPPGIFT for a zero value causes warnings and sometimes errorsOmit the line entirely

Related skills

QuestionSkill
Getting the trial balance out of the accounting systemswedish-sie-import-export
INK2 form logic, skattemässiga justeringar, N9swedish-financial-reporting
Bokslut, closing entries and the result that feeds 4.1swedish-year-end-closing
Periodiseringsfond, koncernbidrag, schablonintäktswedish-tax-planning
Överavskrivningar and värdeminskningsavdrag behind 4.9swedish-asset-accounting

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.