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

ta-tax-compliance

Skill65 starsChanged 14 days agoMITView on GitHub

Tax compliance check for a German or Polish client company. Checks all tax periods (UStVA, ZM and EÜR in Germany; JPK_V7, VAT-UE, PIT or CIT advances and ZUS DRA in Poland), identifies unfiled or overdue reports, verifies tax registration, and generates a compliance summary. Use when a tax advisor asks about tax deadlines, compliance status, or filing obligations.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

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

    Call get_tax_compliance_status with the active company ID

    line 17
  2. Very specific:

    Call list_tax_settings to verify the reporting frequency and VAT configuration

    line 21
  3. Distinctive:

    Check if the settings match the company type (DE: VAT subject, Kleinunternehmer (§ 19 UStG) or VAT-exempt sales (§ 4 UStG, e.g.

    line 22
  4. Distinctive:

    Check the following registration details:

    line 25

≈ “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

Perform a thorough tax compliance check for the tax advisor:

Step 1: Check compliance status

  • Call get_tax_compliance_status with the active company ID
  • This returns tax reports status, tax settings, and registration info

Step 2: Review tax settings

  • Call list_tax_settings to verify the reporting frequency and VAT configuration
  • Check if the settings match the company type (DE: VAT subject, Kleinunternehmer (§ 19 UStG) or VAT-exempt sales (§ 4 UStG, e.g. Heilberufe or Versicherungsvermittler: no input VAT deduction, annual VAT return); PL: VAT-exempt vs. VAT payer, monthly JPK_V7M vs. quarterly JPK_V7K)

Step 3: Verify registration

Check the following registration details:

  • Germany:
    • Steuernummer (tax ID): Is it set? Is it in the correct format for the tax state?
    • USt-IdNr. (VAT ID): Is it set? Is it needed based on EU trade activity?
    • Tax state (Bundesland): Is it correctly assigned?
  • Poland (no tax state):
    • NIP (tax ID): Is it set?
    • EU VAT number (PL + NIP, VAT-UE registration): Is it set? It is needed only for EU trade.

Step 4: Analyze report filing status

For each unfiled report:

  • Identify the report type (DE: USt-VA, ZM, EÜR, annual VAT, trade tax; PL: JPK_V7M or JPK_V7K, VAT-UE, PIT or CIT advance, ZUS DRA, annual PIT, CIT-8)
  • Note the period and due date
  • Flag if it is overdue

Step 5: Present the compliance report

Registration Status

  • Tax ID: ✅/❌ with value if present
  • VAT ID: ✅/❌ with value if present
  • Tax state (German companies): ✅/❌ with name

Filing Status

Report TypePeriodStatusDue Date
............

Upcoming Deadlines

  • List the next 3 filing deadlines with dates
  • Note the standard deadlines:
    • DE:
      • Monthly USt-VA: 10th of the following month (+ Dauerfristverlängerung = 10th of the month after)
      • Quarterly USt-VA: 10th of the month after the quarter ends
      • Annual USt: July 31 of the following year (with advisor extension: end of February of the year after)
    • PL, each moved to the next working day:
      • 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
      • Annual PIT (and a JDG's JPK_PKPIR or JPK_EWP): April 30 of the following year
      • CIT-8: end of the third month after the tax year (March 31 for a calendar year)

Action Items

Prioritized list:

  1. Overdue reports that must be filed immediately
  2. Reports due within the next 30 days
  3. Registration issues that need attention
  4. Settings that may need adjustment

Be precise with dates and report periods. Use the tax terminology of the company's country (DE or PL).

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.