Norman: Accounting Monthly Reconciliation

v1.0.0

Perform a complete monthly financial reconciliation - review all transactions, match invoices, check outstanding payments, and prepare for tax filing. Use wh...

0· 664·2 current·2 all-time
byStan Kharlap@stanlee000
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The name and description describe bookkeeping and reconciliation work, and the SKILL.md only calls finance-related RPCs (search_transactions, categorize_transaction, list_invoices, etc.) via an MCP named norman-finance. There are no unrelated environment variables, binaries, or config paths requested. Note: the registry top-level homepage is empty but the skill metadata lists https://norman.finance — verify that domain and the MCP provider before trusting the skill.
Instruction Scope
The instructions are narrowly scoped to transaction review, invoice matching, attachment management, and tax preview/submit. They do not ask the agent to read arbitrary files, environment variables, or external endpoints beyond the finance MCP. Critical actions (submit_tax_report) are gated by explicit user confirmation per the instructions.
Install Mechanism
No install spec and no code files (instruction-only). This minimizes on-disk execution and supply-chain risk; the skill depends on platform-provided MCP methods rather than installing external packages.
Credentials
The skill declares no required environment variables, credentials, or config paths. That is proportionate for an instruction-only bookkeeping assistant that uses platform RPCs.
Persistence & Privilege
The skill is not always-enabled (always: false) and has disable-model-invocation set true, so it cannot be autonomously invoked by the model — this reduces risk. It does not request changes to other skills or system-wide settings.
Assessment
This skill appears coherent and low-risk: it only uses accounting-specific MCP calls and requests no credentials or installs. Before enabling, verify the MCP/provider (norman-finance) and the listed homepage (https://norman.finance) are legitimate and under an expected trust boundary. Confirm what platform permissions the skill will have (which company accounts or ledgers it can read/modify), require interactive confirmations for any tax submissions or external communications, and monitor access logs after first runs. If you do not trust the MCP provider or cannot confirm the domain, do not grant the skill access to live financial data.

Like a lobster shell, security has layers — review code before you run it.

Runtime requirements

📅 Clawdis
bookkeepingvk970nb18sjv604f999a8atxxmx81fyspfinancevk970nb18sjv604f999a8atxxmx81fysplatestvk970nb18sjv604f999a8atxxmx81fyspmcpvk970nb18sjv604f999a8atxxmx81fyspnormanvk970nb18sjv604f999a8atxxmx81fyspreconciliationvk970nb18sjv604f999a8atxxmx81fysp
664downloads
0stars
1versions
Updated 1mo ago
v1.0.0
MIT-0

Guide the user through a complete monthly reconciliation:

Step 1: Transaction Review

  • Call search_transactions for the specified month (or last month if not specified)
  • Identify uncategorized transactions
  • For each batch, suggest categories and let the user confirm
  • Use categorize_transaction to assign the correct bookkeeping category

Step 2: Finalize Transactions

  • After all transactions are categorized, verify each one using change_transaction_verification
  • Mark every transaction for the period as verified so the month can be closed
  • If any transaction has missing information (no receipt, unclear category), flag it for the user before verifying
  • Present a count: "X of Y transactions verified for [month]"

Step 3: Invoice Reconciliation

  • Call list_invoices to find invoices from the period
  • Cross-reference with incoming payments in transactions
  • Use link_transaction to match payments to invoices
  • Flag any overdue unpaid invoices and suggest sending reminders via send_invoice_overdue_reminder

Step 4: Document Check

  • Call list_attachments for the period
  • Identify transactions without attached receipts (especially expenses)
  • Remind the user to upload missing receipts with upload_bulk_attachments
  • Use link_attachment_transaction to connect any newly uploaded receipts

Step 5: Tax Preparation

  • Call get_company_tax_statistics for the period overview
  • Call get_vat_next_report to check if a VAT report is due
  • If due, call generate_finanzamt_preview to show the draft
  • Only submit with explicit user confirmation via submit_tax_report

Step 6: Summary

Present a closing summary:

  • Total income and expenses for the month
  • Number of invoices sent vs. paid
  • Outstanding receivables
  • VAT liability
  • Any action items remaining

Be thorough but keep each step interactive - wait for user confirmation before proceeding.

Comments

Loading comments...