Accounting

Reporting

We require detailed financial reporting by department, sales region, product family, etc.

Modules:

• account_analytic_default
• account_analytic_plans (not in v9)

Reporting Criteria:

• Product Family
  • Can't create analytic defaults on product categories
  • Assign analytic defaults per product template
    • Would all variants then get the same analytic assignment?
• Sales Region
  • Can't create analytic defaults on sales teams
  • Would have to assign analytic rules per customer
  • Can we automate this through our sales_team_region module?

Sales Tax

We need to track and report sales tax by customer location.

• Apply sales tax by city, county, state
  • Import tax data from STC clearinghouse per customer ship-to location
  • Integrate with TaxCloud or STC for calculating sales tax on the fly
• Store tax exemption certs per customer per state

Configuration

Product Costing

In IntuitiveERP, we use LastCost. Odoo doesn't have that. The OCA module purchase_last_price_info will show the last cost. StandardCost is recommended for manufacturing environments where the purchase price of parts is mostly fixed. We were using StandardCost, but we were having a lot of variance. That is partly caused by purchasing in varying quantities with different quantity based price breaks. Maybe we should use StandardCost, and try to account for price breaks with supplier quantity pricing tables.

Chart of Accounts Structure

• TYPE: Operating Expense
  • GROUP: Administration & Finance
    • SUBGROUP: Auto Expense
      • ACCOUNT: Auto Reg/Insurance | CEO
  • GROUP: Sales Travel
    • SUBGROUP: Auto Reg/Insurance
    • ACCOUNT: Auto Reg/Insurance | BU20
  • GROUP: Marketing Exp & Trade Show - Nat'l
    • SUBGROUP: Auto Expense
    • ACCOUNT: Auto Reg/Insurance | Marketing

For v8, I proposed the following structure:

• General Accounts:
  • TYPE: Expense
    • ACCOUNT: Operating Expense (view type)
      • ACCOUNT: Auto Expense (standard type)
• Analytic Accounts:
  • Department
    • Admin
    • Finance
    • CEO
    • Sales
      • Outside
      • Inside
      • Admin
    • Marketing
    • ...
  • Region
    • BU01
    • ...
    • BU20
  • Auto Expense
    • Auto Reg/Insurance
    • Auto Other
    • Auto Repair & Maint

Transactions would then be assigned to a general account, and to a combination of various analytic accounts (using module account_analytic_plans). For example:

Vehicle registration for the outside salesman in sales region BU01 would be recorded as follows:

• general account
  • Auto Expense
• analytic accounts
  • Department -> Sales -> Outside (100%)
  • Region -> BU01 (100%)
  • Auto Expense -> Auto Reg/Insurance (100%)

In v9, there is no hierarchy among accounts (general or analytic). We are to use tags to group accounts.

In v9, there is no module account_analytic_plans. I need to search for a replacement, or upgrade it.

Customization

In v8, we were planning to create a custom report that combines general accounts and analytic accounts.

The v8 Analytic Entries Analysis report counts transactions multiple times, and calculates wrong totals.

For v8, one approach would be to group the report by Analytic Plan (the combination of multiple analytic accounts), rather than grouping by individual analytic accounts. That way, the transactions only get counted once.

Testing and Evaluation

• Import 2 months of financial data from Intuitive
• Create sample P&L and BS statements for review

Anglo-Saxon Accounting

Module account_anglo_saxon is not present in v9. The old account_anglo_saxon module was described as follows:

This module will support the Anglo-Saxons accounting methodology by changing the accounting logic with stock transactions. The difference between the Anglo-Saxon accounting countries and the Rhine or also called Continental accounting countries is the moment of taking the Cost of Goods Sold versus Cost of Sales. Anglo-Saxons accounting does take the cost when sales invoice is created, Continental accounting will take the cost at the moment the goods are shipped. This module will add this functionality by using a interim account, to store the value of shipped goods and will contra book this interim account when the invoice is created to transfer this amount to the debtor or creditor account. Secondly, price differences between actual purchase price and fixed product standard price are booked on a separate account.

A draft roadmap document for v9 accounting states the following:

The Storno module (putting negative values in debit and/or credit when reversing a journal entry) should be integrated by default. Both Storno and AngloSaxon should be in separated module AND they must be activated by company. This would allow to have multicompanies environment, some with storno accounting, others without.

In v9, there is a checkbox setting that affects anglo-saxon accounting, without installing a module. See this issue: https://github.com/odoo/odoo/issues/8576 for additional settings.