Odoo Accounting Setup

Overview

This public intake copy packages

plugins/antigravity-awesome-skills-claude/skills/odoo-accounting-setup

https://github.com/sickn33/antigravity-awesome-skills

Use it when the operator needs the upstream workflow, support files, and repository context to stay intact while the public validator and private enhancer continue their normal downstream flow.

This intake keeps the copied upstream files intact and uses

metadata.json

ORIGIN.md

Odoo Accounting Setup

Imported source sections that did not map cleanly to the public headings are still preserved below or in the support files. Notable imported sections: How It Works, Limitations.

When to Use This Skill

Use this section as the trigger filter. It should make the activation boundary explicit before the operator loads files, runs commands, or opens a pull request.

• Setting up a new Odoo instance for a company for the first time.
• Configuring multi-currency or multi-company accounting.
• Troubleshooting tax calculation or fiscal position mapping errors.
• Creating payment terms for installment billing (e.g., Net 30, 50% upfront).
• Use when the request clearly matches the imported source intent: Expert guide for configuring Odoo Accounting: chart of accounts, journals, fiscal positions, taxes, payment terms, and bank reconciliation.
• Use when the operator should preserve upstream workflow detail instead of rewriting the process from scratch.

Operating Table

metadata.json

ORIGIN.md

SKILL.md

SKILL.md

## Related Skills

Workflow

This workflow is intentionally editorial and operational at the same time. It keeps the imported source useful to the operator while still satisfying the public intake standards that feed the downstream enhancer flow.

1. Confirm the user goal, the scope of the imported workflow, and whether this skill is still the right router for the task.
2. Read the overview and provenance files before loading any copied upstream support files.
3. Load only the references, examples, prompts, or scripts that materially change the outcome for the current request.
4. Execute the upstream workflow while keeping provenance and source boundaries explicit in the working notes.
5. Validate the result against the upstream expectations and the evidence you can point to in the copied files.
6. Escalate or hand off to a related skill when the work moves out of this imported workflow's center of gravity.
7. Before merge or closure, record what was used, what changed, and what the reviewer still needs to verify.

Imported Workflow Notes

Imported: Overview

This skill guides functional consultants and business owners through setting up Odoo Accounting correctly from scratch. It covers chart of accounts configuration, journal setup, tax rules, fiscal positions, payment terms, and the bank statement reconciliation workflow.

Imported: How It Works

1. Activate: Mention

   @odoo-accounting-setup

   and describe your accounting scenario.
2. Configure: Receive step-by-step Odoo menu navigation with exact field values.
3. Validate: Get a checklist to verify your setup is complete and correct.

Examples

Example 1: Ask for the upstream workflow directly

Use @odoo-accounting-setup to handle <task>. Start from the copied upstream workflow, load only the files that change the outcome, and keep provenance visible in the answer.

Explanation: This is the safest starting point when the operator needs the imported workflow, but not the entire repository.

Example 2: Ask for a provenance-grounded review

Review @odoo-accounting-setup against metadata.json and ORIGIN.md, then explain which copied upstream files you would load first and why.

Explanation: Use this before review or troubleshooting when you need a precise, auditable explanation of origin and file selection.

Example 3: Narrow the copied support files before execution

Use @odoo-accounting-setup for <task>. Load only the copied references, examples, or scripts that change the outcome, and name the files explicitly before proceeding.

Explanation: This keeps the skill aligned with progressive disclosure instead of loading the whole copied package by default.

Example 4: Build a reviewer packet

Review @odoo-accounting-setup using the copied upstream files plus provenance, then summarize any gaps before merge.

Explanation: This is useful when the PR is waiting for human review and you want a repeatable audit packet.

Imported Usage Notes

Imported: Examples

Example 1: Create a Payment Term (Net 30 with 2% Early Pay Discount)

Menu: Accounting → Configuration → Payment Terms → New

Name: Net 30 / 2% Early Pay Discount
Company: [Your Company]

Lines:
  Line 1:
    - Due Type: Percent
    - Value: 100%
    - Due: 30 days (full balance due in 30 days)

Early Payment Discount (Odoo 16+):
  Discount %: 2
  Discount Days: 10
  Balance Sheet Accounts:
    - Gain: 4900 Early Payment Discounts Granted
    - Loss: 5900 Early Payment Discounts Received

Note (v16+): Use the built-in Early Payment Discount field instead of the old split-line workaround. Odoo now posts the discount automatically when the customer pays within the discount window and generates correct accounting entries.

Example 2: Fiscal Position for EU VAT (B2B Intra-Community)

Menu: Accounting → Configuration → Fiscal Positions → New

Name: EU Intra-Community B2B
Auto-detection: ON
  - Country Group: Europe
  - VAT Required: YES (customer must have EU VAT number)

Tax Mapping:
  Tax on Sales (21% VAT) → 0% Intra-Community VAT
  Tax on Purchases      → 0% Reverse Charge

Account Mapping:
  (Leave empty unless your localization requires account remapping)

Example 3: Reconciliation Model for Bank Fees

Menu: Accounting → Configuration → Reconciliation Models → New

Name: Bank Fee Auto-Match
Type: Write-off
Matching Order: 1

Conditions:
  - Label Contains: "BANK FEE" OR "SERVICE CHARGE"
  - Amount Type: Amount is lower than: $50.00

Action:
  - Account: 6200 Bank Charges
  - Tax: None
  - Analytic: Administrative

Best Practices

Treat the generated public skill as a reviewable packaging layer around the upstream repository. The goal is to keep provenance explicit and load only the copied source material that materially improves execution.

• ✅ Do: Install your country's localization module first (l10nus, l10nmx, etc.) before manually creating accounts — it sets up the correct chart of accounts.
• ✅ Do: Use Fiscal Positions to automate B2B vs B2C tax switching — never change taxes manually on individual invoices.
• ✅ Do: Lock accounting periods (Accounting → Actions → Lock Dates) after month-end closing to prevent retroactive edits.
• ✅ Do: Use the Early Payment Discount feature (v16+) instead of splitting payment term lines for discount modelling.
• ❌ Don't: Delete journal entries — always reverse them with a credit note or the built-in reversal function.
• ❌ Don't: Mix personal and business transactions in the same journal.
• ❌ Don't: Create manual journal entries to fix bank reconciliation mismatches — use the reconciliation model workflow instead.

Imported Operating Notes

Imported: Best Practices

• ✅ Do: Install your country's localization module first (

  l10n_us

  ,

  l10n_mx

  , etc.) before manually creating accounts — it sets up the correct chart of accounts.
• ✅ Do: Use Fiscal Positions to automate B2B vs B2C tax switching — never change taxes manually on individual invoices.
• ✅ Do: Lock accounting periods (Accounting → Actions → Lock Dates) after month-end closing to prevent retroactive edits.
• ✅ Do: Use the Early Payment Discount feature (v16+) instead of splitting payment term lines for discount modelling.
• ❌ Don't: Delete journal entries — always reverse them with a credit note or the built-in reversal function.
• ❌ Don't: Mix personal and business transactions in the same journal.
• ❌ Don't: Create manual journal entries to fix bank reconciliation mismatches — use the reconciliation model workflow instead.

Troubleshooting

Problem: The operator skipped the imported context and answered too generically

Symptoms: The result ignores the upstream workflow in

plugins/antigravity-awesome-skills-claude/skills/odoo-accounting-setup

metadata.json

ORIGIN.md

Problem: The imported workflow feels incomplete during review

Symptoms: Reviewers can see the generated

SKILL.md

Problem: The task drifted into a different specialization

Symptoms: The imported skill starts in the right place, but the work turns into debugging, architecture, design, security, or release orchestration that a native skill handles better. Solution: Use the related skills section to hand off deliberately. Keep the imported provenance visible so the next skill inherits the right context instead of starting blind.

Related Skills

• @monte-carlo-monitor-creation

  - Use when the work is better handled by that native specialization after this imported skill establishes context.

• @monte-carlo-prevent

  - Use when the work is better handled by that native specialization after this imported skill establishes context.

• @monte-carlo-push-ingestion

  - Use when the work is better handled by that native specialization after this imported skill establishes context.

• @monte-carlo-validation-notebook

  - Use when the work is better handled by that native specialization after this imported skill establishes context.

Additional Resources

Use this support matrix and the linked files below as the operator packet for this imported skill. They should reflect real copied source material, not generic scaffolding.

references

references/n/a

examples

examples/n/a

scripts

scripts/n/a

agents

agents/n/a

assets

assets/n/a

Imported Reference Notes

Imported: Limitations

• Does not cover multi-currency revaluation or foreign exchange gain/loss accounting in depth.
• Country-specific e-invoicing (CFDI, FatturaPA, SAF-T) requires additional localization modules — use

  @odoo-l10n-compliance

  for those.
• Payroll accounting integration (salary journals, deduction accounts) is not covered here — use

  @odoo-hr-payroll-setup

  .
• Odoo Community Edition does not include the full lock dates feature; some controls are Enterprise-only.