agentleFS
Sign inStart free
norman-financenorman-finance/norman-mcp-server/skills/ta-missing-receipts/SKILL.md

ta-missing-receipts

Skill65 starsChanged 11 days agoMITView on GitHub

Find and collect missing receipts for a client company. Identify high-priority items, suggest a ping strategy, and bulk-notify the client. Use when a tax advisor asks about missing documents, Belege, or requests receipts from a client.

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_missing_documents_summary with the active company ID

    line 17
  2. Distinctive:

    Ask the tax advisor to confirm before sending

    line 40
  3. Very specific:

    Call ping_client_for_documents with the selected transaction IDs

    line 41
  4. Distinctive:

    Consider requesting receipts monthly to avoid large backlogs

    line 52

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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 tax advisor identify and collect missing receipts from a client:

Step 1: Get the missing documents summary

  • Call get_missing_documents_summary with the active company ID
  • This returns all transactions without receipts grouped by month with amounts
  • Its documentsWithoutBooking counts the opposite gap by month: receipts and invoices the client uploaded that no booking holds yet, so the books miss them

Step 2: Analyze and prioritize

Present the results in a structured format:

By priority:

  1. Critical (>250 [currency]) — required for VAT deduction (DE: Vorsteuerabzug)
  2. High (100–250 [currency]) — significant business expenses
  3. Medium (<100 [currency]) — should be collected for compliance
  4. Informational — small amounts that may be bundled

By month: Show which months have the most gaps, and name each month with documents without a booking: the client books or deletes them under Documents → Review documents

By category: Group by category to help the client understand what types of documents are needed

Step 3: Suggest a ping strategy

  • Recommend which transactions to ping the client about first (highest amount, oldest first)
  • Suggest grouping pings by vendor or category to make it easier for the client
  • Warn if the total missing count is very high (suggest batching requests)

Step 4: Send reminders

  • Ask the tax advisor to confirm before sending
  • Call ping_client_for_documents with the selected transaction IDs
  • Report how many reminders were sent successfully

Step 5: Summary

  • Show total missing documents before and after action
  • Recommend a follow-up date to check again
  • Remind about the retention requirement (DE: 10 years Aufbewahrungspflicht / PL: 5 years)

Tips for the advisor:

  • DE: Receipts are mandatory for Vorsteuerabzug on expenses >250 EUR. Digital copies are GoBD-compliant when stored properly in Norman.
  • PL: Receipts are mandatory for VAT deduction on expenses >450 PLN. Documents must comply with JPK requirements.
  • Consider requesting receipts monthly to avoid large backlogs

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.

Check your setup, free