{"id":57767,"plugin_id":"plugin_asdk_app_6981ec32565481919b1c5a1627b1e330","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-10-27T00:14:50.256Z","digest":"2399da58ba04499dae5a9781ec38a0b2e3b4382f6f2a2f652e6fe246211380dd","against":null,"payload":{"description":"Analyze and migrate opening balances or prior DATEV books into Norman's SME Ledger. Germany only, for a GmbH or UG on SKR03/SKR04. Use when a GmbH or UG is starting its books, changing accounting systems, importing DATEV opening balances, or performing an accounting cutover.","included_files":[],"name":"accounting-cutover","skill_md_contents":"---\nname: accounting-cutover\ndescription: Analyze and migrate opening balances or prior DATEV books into Norman's SME Ledger. Germany only, for a GmbH or UG on SKR03/SKR04. Use when a GmbH or UG is starting its books, changing accounting systems, importing DATEV opening balances, or performing an accounting cutover.\nmetadata:\n  openclaw:\n    emoji: \"\\U0001F4DA\"\n    homepage: https://norman.finance\n    requires:\n      mcp:\n        - norman-finance\n---\n\nGuide a company through an accounting migration without changing its Ledger until the user has reviewed the preview and explicitly confirmed the import.\n\n## 1. Inspect the current setup\n\n- Call `get_accounting_setup` for the relevant fiscal year.\n- Note the current SKR framework, existing cutover state and any previously imported entries.\n- Do not switch SKR03 or SKR04 automatically. A framework switch has broader accounting consequences and requires its own explicit confirmation.\n\n## 2. Collect and analyze source files\n\n- Upload the available DATEV files or supporting documents and retain their short-lived `file_ref` values.\n- Call `analyze_accounting_cutover_documents` with all related files together.\n- Present the detected file roles, fiscal periods, likely SKR framework and any ambiguity to the user.\n- Ask for a replacement file when a reference has expired.\n\nFile limits enforced by the Accounting API:\n\n- 1 to 20 files per analysis\n- 20 MB per file and 100 MB in total\n- PDFs may be analyzed as supporting evidence, but opening-balance and booking-stack inputs for Preview and Apply must be machine-readable DATEV or CSV files\n\n## 3. Choose the migration scenario\n\n- `formation`: a newly formed GmbH or UG with legal opening entries\n- `year_start`: prior-year closing balances become this year's opening balances\n- `mid_year`: opening balances plus all bookings through the cutover date\n\nChoose `opening_method=datev` when an opening-balance file exists. Choose `opening_method=manual` only when the user wants to enter non-zero account balances directly. Manual rows require `account_code`, `side` (`debit` or `credit`), `amount`, and may include `memo`.\n\n## 4. Preview before writing\n\n- Call `preview_accounting_cutover` with the complete set of dates, files and manual rows.\n- Explain reconciliation totals, detected periods, blockers and warnings in plain language.\n- Treat Preview as read-only. It does not write Ledger entries.\n- Resolve every blocking finding before proceeding.\n\n## 5. Prepare reviewed accounts (GmbH/UG)\n\nPreview returns `accountReview` for GmbH/UG on SKR03/SKR04 (fiscal years 2024-2026). Its rows are source accounts that must exist and have an E-Bilanz position before import; they cause the \"Review and prepare accounts\" and \"no E-Bilanz taxonomy mapping\" blockers.\n\n- Present each row with its state: `NEW` (will be created Ledger-only), `MAPPING_REQUIRED` (exists, needs a position), `CONFLICT` or `HIDDEN` (fix in the chart of accounts first; they cannot be prepared).\n- Use `mode=AUTOMATIC` only where the row has `automatic=true`. Otherwise pick a `MANUAL` position from `accountReview.positions` matching the account type, or `DEFERRED` to decide later (the account then stays a blocker).\n- Keep the name and type of existing accounts.\n- After the user confirms, call `prepare_accounting_cutover_accounts` with `review_token`, the chosen rows and `confirmed=true`. The token expires after 30 minutes; if the API reports a changed or expired review, run Preview again.\n- A single custom account can also be assigned directly: `update_chart_of_accounts_account` (or `create_chart_of_accounts_account`) with `ebilanz_assignment`; `get_ebilanz_positions` lists the allowed positions and `list_chart_of_accounts(fiscal_year=...)` shows each account's status.\n- Run Preview again with the same inputs and confirm the blockers are gone.\n\n## 6. Apply only after explicit confirmation\n\n- Ask the user to confirm the exact successful Preview.\n- Call `apply_accounting_cutover` with the same inputs and `confirmed=true` only after that confirmation.\n- If any date, file, balance row or migration mode changes, run Preview again before Apply.\n- Apply writes opening/cutover postings and establishes the boundary before which transaction-derived postings must not be duplicated.\n\n## 7. Verify the result\n\n- Call `get_accounting_setup` again and inspect the returned import status and counts.\n- Use the Ledger tools to verify the affected accounts and dates.\n- Report any remaining warnings without attempting tax submission or annual-close locking.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}