agentleFS
norman-financenorman-finance/norman-mcp-server/skills/tax-report/SKILL.md

tax-report

Skill65 starsChanged 13 days agoMITView on GitHub

Review and manage tax reports. German companies: VAT (UStVA, ZM, Umsatzsteuer), income tax prepayments and Finanzamt submissions via ELSTER. Polish companies: the JPK_V7 and VAT-UE, PIT or CIT advances, ZUS DRA, the annual PIT and the CIT-8, which Norman prepares and the owner files in the Norman app or outside it. Use when the user asks about taxes, Steuern, podatki, VAT, USt, JPK, Finanzamt, urząd skarbowy, or tax filing.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 0 are distinctive, and 6 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 6

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Overview: Call list_tax_reports to see all tax reports and their statuses (draft, validated, submitted)

    line 18
  2. Very specific:

    Specific report: If the user asks about a specific period, call get_tax_report with the report ID to see details including:

    line 22
  3. Very specific:

    Call generate_finanzamt_preview to show the user exactly what will be sent to the Finanzamt.

    line 36
  4. Very specific:

    Only when the user explicitly confirms, call submit_tax_report to file with the Finanzamt via ELSTER.

    line 39
  5. Very specific:

    Read a JPK_V7's sales, purchases, totals and exclusions with get_polish_jpk_register, and its filing state (methods, MF status, UPO) with …

    line 42
  6. Very specific:

    If a German tax number (Steuernummer) needs validation, use validate_tax_number (Germany only)

    line 55

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

Help the user with their tax obligations. Read the company's country first (company://current or get_company_details) and use its own terms: a German company has a UStVA and the Finanzamt, a Polish company the JPK_V7 and the urząd skarbowy, never the other one's.

  1. Overview: Call list_tax_reports to see all tax reports and their statuses (draft, validated, submitted)
  2. Next deadline: Call get_vat_next_report for the next VAT return: the UStVA of a German company (a Kleinunternehmer or a company with VAT-exempt sales under § 4 UStG files one only for a month or quarter with reverse-charge purchases), the JPK_V7 of a Polish VAT payer (a Polish company exempt from VAT files none). A Polish company's PIT or CIT advance and ZUS DRA, due on the 20th, are in list_tax_reports.
  3. Specific report: If the user asks about a specific period, call get_tax_report with the report ID to see details including:
    • Reporting period
    • Revenue and VAT amounts
    • Status (draft, ready, submitted)
    • Submission status (the Finanzamt for a German report; the Ministry of Finance and its UPO for a Polish JPK_V7)
  4. Why this number (Polish companies; a German company has no explanation, read its report with get_tax_report): When the user asks why a report shows its amount or where a figure comes from, call explain_tax_report with the report ID and answer from it, never from memory:
    • Lead with the answer in two or three sentences, then the formula with the report's own figures as a short list.
    • Name the source rows behind the base (document numbers, dates, counterparties, amounts), split by rate where rates differ, and the deductions and carry-overs: contributions paid and the part deducted, earlier advances deducted, the excess carried from the previous return, losses, rounding.
    • A Polish PIT or CIT advance is year-to-date: compare this period's step with the previous one to say what changed. A Polish ZUS DRA: the scheme, the social base and the health base and tier.
    • Say what is missing or blocking and what the owner can change and where. Quote only figures the tool returned; if it cannot work the report out, explain why instead of giving a number.
    • The tool's total is the report's amount now, the one its page shows. If the user or a list names another amount, the books changed since: explain the tool's total and never talk about stored, saved or recalculated totals.
  5. German companies, preview and submit:
    • Call generate_finanzamt_preview to show the user exactly what will be sent to the Finanzamt. Let them review all figures.
    • If the preview names tax_number, tax_state, steuernummer or bundesland, quote its message and ask for the number from the Finanzamt's letter (slashes and the 13-digit ELSTER form are fine) or for the right federal state. The field names where the return reads it. Save tax_number and tax_state with update_company_details (tax_id is the Steuernummer, tax_state the state). steuernummer and bundesland are the number and state saved in the income tax return: no tool changes them, so the user corrects them in Norman, in the return's personal details. Then preview again.
    • If it names tax_liability_entry_date, that is ELSTER's KSt 1 F check: the date unlimited tax liability began must equal the first day of the annual close's fiscal year. Quote its message and never pick a date: no tool changes either value, so the user corrects the date in the KSt wizard's first step or the close period in the Jahresabschluss, then previews again.
    • Only when the user explicitly confirms, call submit_tax_report to file with the Finanzamt via ELSTER. If it answers Email not confirmed, call resend_email_confirmation and ask the user to open the link in that email; a paid plan confirms the address without it.
  6. Polish companies, check and then file in the app:
    • Read a JPK_V7's sales, purchases, totals and exclusions with get_polish_jpk_register, and its filing state (methods, MF status, UPO) with get_polish_jpk_filing_status; a PIT return's with get_polish_pit_filing_status. get_polish_tax_estimates gives PIT/ZUS or CIT estimates, which are not filed returns.
    • There is no Polish signing or submission tool here. Norman files the JPK_V7 (the monthly JPK_V7M, or each monthly file of a quarterly JPK_V7K) from the Norman app only after the owner approves and signs it, on the JDG Pro and Sp. z o.o. Max plans. Norman prepares the PIT returns, the CIT-8 draft and the VAT-UE and calculates ZUS; the user or their accountant files them.
    • Give facts and next steps, never an individual tax opinion.
  7. Tax settings: Call list_tax_settings to review VAT registration, filing frequency, and other tax configuration. A German Kleinunternehmer or a company with VAT-exempt sales under § 4 UStG files a UStVA only for a period with VAT it owes as recipient (§ 13b, § 1a UStG), quarterly by default. To file monthly, call update_tax_setting with reporting_frequency "monthly". A German Kleinunternehmer files no ZM (§ 18a Abs. 4 UStG), also for EU B2B sales. Filed ZMs stay in the reports. For a German Kleinunternehmer, call get_kleinunternehmer_limit to say where this year's revenue stands against 100,000 € (25,000 € in the founding year) and next year's 25,000 €; at near_limit, crossed or not_eligible, tell the user the invoice that crosses the limit already needs VAT and suggest updating the VAT status in the tax settings. Never change the VAT status for them.

Important warnings:

  • German companies: ALWAYS show the Finanzamt preview before submitting
  • Tax submissions are IRREVERSIBLE - make sure the user explicitly confirms
  • Remind the user of filing deadlines:
    • DE: monthly: 10th of following month, quarterly: 10th of following quarter month
    • PL: JPK_V7M or JPK_V7K and VAT-UE: 25th of the following month; PIT and CIT advances and ZUS DRA: 20th of the following month; each moved to the next working day
  • Reminders: for a German company Norman emails a reminder a week before and on the morning of each UStVA and ZM due date. For a Polish company Norman reminds of the JPK_V7, VAT-UE, PIT and CIT advances, ZUS DRA, annual PIT and CIT-8 a few days ahead and on the day, in the app, by push and by e-mail. To turn the reminders off or on again, set notify_tax_deadlines with update_company_details.
  • If a German tax number (Steuernummer) needs validation, use validate_tax_number (Germany only)

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.