agentleFS
tuanle96tuanle96/mcp-odoo/skills/odoo-month-end-close/SKILL.md

odoo-month-end-close

Skill421 starsChanged 4 months agoMITView on GitHub

Drive a month-end accounting close on Odoo through odoo-mcp — AR/AP aging, open-item and draft-invoice review, reconciliation checklists, and chatter documentation — with human sign-off at every posting step. Use when the user asks to "close the month", "review receivables/payables", "check aging", or prepare finance reports from Odoo.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

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

    Unreconciled sweep: search account.move.line for open items on receivable/payable accounts older than the period.

    line 31
  2. Very specific:

    Anomaly pass: run data_quality_report(model="account.move") — missing required values and format anomalies on invoices are close blockers.

    line 35
  3. Distinctive:

    Never post, reconcile, or delete without a fresh per-batch approval.

    line 54
  4. Very specific:

    If multi-company is active, confirm the company scope first (diagnose_access explains company-based invisibility).

    line 57

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

Odoo month-end close

You are running a month-end close review against a live Odoo database through odoo-mcp. Finance data is the last place an agent should guess: every number you present must come from a tool result, and every posting action needs the human's explicit approval.

Prerequisites

  • odoo-mcp connected; account module installed (verify via business_pack_report(pack="accounting") or get_odoo_profile).
  • The accounting_close_checklist MCP prompt is the compact in-server version of this playbook; this skill adds pacing and judgment.

Playbook

  1. Baseline: accounting_health_summary — open AR/AP item counts and the draft-invoice backlog. This is your before-photo; show it.
  2. Aging deep-dive: receivable_payable_aging(direction="receivable") then "payable". Present the bucket table (not due / 1-30 / 31-60 / 61-90 / 90+) with per-partner totals; flag partners with >60d balances.
  3. Draft backlog: search_records(model="account.move", domain=[["state","=","draft"],["move_type","in",["out_invoice","in_invoice"]]]) — list drafts with amounts and dates; ask which should be posted, which deleted (deletion = human decision, never yours).
  4. Unreconciled sweep: search account.move.line for open items on receivable/payable accounts older than the period; summarize by account. Use aggregate_records (groupby account_id) instead of paging raw lines.
  5. Anomaly pass: run data_quality_report(model="account.move") — missing required values and format anomalies on invoices are close blockers.
  6. Actions through the gate. Posting a draft, correcting a field, or any state change: preview_write → human reviews the diff → validate_write → execute_approved_write(confirm=true). One document batch at a time.
  7. Document the close: with approval, chatter_post a close summary on the relevant records (or the human's designated close journal entry) — what was reviewed, what was posted, what is carried over.
  8. After-photo: re-run accounting_health_summary; report the delta.

Output format

Close report with: baseline vs final summary, aging tables, actions taken (each with its approval token event), and a carried-over list with owners.

Hard rules

  • Never post, reconcile, or delete without a fresh per-batch approval.
  • as_of on aging shifts the bucketing reference only — say so if the human asks for a "historical snapshot"; do not fake one.
  • If multi-company is active, confirm the company scope first (diagnose_access explains company-based invisibility).

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.