agentleFS
actinon-comactinon-com/brass-monkey/skills/odoo-finance/SKILL.md

odoo-finance

Skill2 starsChanged 3 months agoMITView on GitHub

MANDATORY for Customer Invoices (out_invoice), Vendor Bills (in_invoice), and Payments (account.payment). High-level expertise in Odoo's unified ledger and banking.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

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

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

    Verification: If a task requires absolute technical precision or if the user references fields not in your resource, you MUST call …

    line 13
  2. Very specific:

    Mandate: NEVER attempt to modify a posted entry.

    line 23
  3. Very specific:

    Flow: Import Bank Statements (account.bank.statement) -> Run Reconciliation Models -> Match with Invoices/Bills or post to Expense/Income …

    line 26
  4. Very specific:

    Analytic Distribution: Use the analytic_distribution (JSON) field on lines to allocate costs/revenues across analytic accounts without …

    line 34

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

Skill: Odoo Finance & Accounting

This skill provides the agent with high-level business expertise in Odoo's unified accounting engine, covering Invoicing, Billing, Banking, Consolidation, and Analytics.

Core Mandates

1. Snapshot Awareness (Dynamic Discovery)

  • Mandate: The finance-fields.json resource is a snapshot of core accounting fields. It is NOT exhaustive.
  • Verification: If a task requires absolute technical precision or if the user references fields not in your resource, you MUST call inspect_model to retrieve the "Live Truth" from the target Odoo instance.

2. The Unified Ledger (account.move)

Odoo uses a single model for Invoices, Bills, and Journal Entries.

  • Move Type: Dictates behavior (out_invoice = Customer Invoice, in_invoice = Vendor Bill, entry = Journal Entry).
  • Double-Entry Mandate: For pure journal entries (entry), the sum of Debits must equal the sum of Credits across all account.move.line records.

2. Invoicing Lifecycle

  • States: draft (Editable) -> posted (Locked, valid in ledger) -> cancel.
  • Payment States: not_paid, in_payment (Matched with statement line), paid (Reconciled).
  • Mandate: NEVER attempt to modify a posted entry. You must reset to draft first (if permitted) or create a Reversal/Credit Note.

3. Banking & Reconciliation

  • Flow: Import Bank Statements (account.bank.statement) -> Run Reconciliation Models -> Match with Invoices/Bills or post to Expense/Income accounts.
  • Suspense Account: Transactions sit here until they are reconciled.

4. Advanced Configuration

  • Fiscal Positions: Automatically map Taxes and Accounts based on the partner's country/VAT.
  • Journals: Categorize transactions (Sales, Purchase, Bank, Cash, General). Each journal has its own sequence.

5. Analytics & Budgets

  • Analytic Distribution: Use the analytic_distribution (JSON) field on lines to allocate costs/revenues across analytic accounts without creating new ledger entries.
  • Budgets: Compare planned_amount vs. practical_amount (actuals) to track financial health.

Available Resources

  • finance-advanced-logic.md: Deep-dive into Tax Reporting, Consolidation, Currency handling, and Online Payments.
  • finance-fields.json: Dense technical map of fields for Move, Line, Account, Journal, Tax, and Analytic models.

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.