The general ledger tells you what happened: rent, salaries, sales, cost of goods. Analytic accounting tells you where and for whom: which branch, which department, which project, which product line. Owners in the region almost always ask the second question, especially as companies grow from one shop or office to several. Odoo answers it without a chart of accounts with thousands of lines.
FlexCode Middle East is part of FlexCode Systems GmbH, an Odoo Silver Partner. We implement Odoo, so Odoo is the system we describe, next to an honest look at the topic itself.
Key points
- Plans are dimensions. Each analytic plan, such as branch or project, is an independent way of slicing the same transactions.
- Split by percentage. A line can be distributed across several analytic accounts, for example a shared expense across branches.
- Automate with models. Distribution models fill analytics from the product, partner or account, so users rarely choose by hand.
- Make it mandatory. Applicability rules force analytics on the accounts where you need them.
What analytic accounting adds
Every journal item in Odoo has an account, which describes the nature of the transaction. It can also carry an analytic distribution, which describes its purpose or location. A rent bill for the Alexandria branch posts to the rent account and to the Alexandria analytic account. The profit and loss shows total rent; the analytic report shows rent, and profit, by branch.
| Question | Answered by |
|---|---|
| What did we spend on rent? | Account |
| How profitable is the Riyadh branch? | Analytic plan: branch |
| What did the marketing department cost? | Analytic plan: department |
| Did project X make money? | Analytic plan: project |
| Which product line has the best margin? | Analytic plan: product line |
This is why we recommend keeping the chart of accounts lean; see building the right chart of accounts in Odoo.
Analytic plans
Recent versions of Odoo organise analytics into plans. Each plan is a dimension with its own analytic accounts: a branch plan with one account per branch, a department plan with one per department, a project plan created automatically by the Project app. A single transaction can carry one value from each plan at the same time.
2 to 4
Plans most companies need
100%
Distribution per plan on each line
Automatic
Projects create their own analytic account
Mandatory
Can be enforced per account
- Branch or location, for companies with several sites.
- Department or cost centre, for overhead control.
- Project or contract, for contracting, services and construction.
- Product line or business unit, for groups with distinct activities.
More plans are not better. Every plan is another field users must fill or models must maintain. Start with the two or three dimensions management actually reviews.
Filling analytics automatically
Analytics that depend on users choosing the right value are analytics that will be wrong. Odoo offers several ways to fill them automatically.
- Distribution models: rules that apply an analytic distribution based on the account, product, product category or partner.
- Sales teams and warehouses: sales and stock moves can carry the branch of the team or warehouse.
- Projects: timesheets, expenses and vendor bills linked to a project inherit its analytic account.
- Employees: payroll can post salaries to each employee's department.
Shared costs, such as head office rent or a group-wide software subscription, can be split by percentage across branches with a distribution model, so each branch carries a fair share without manual journal entries.
- Bill or invoice created
- Distribution model applies
- Analytics filled per plan
- Mandatory check on posting
- Profit by branch and project

Making analytics mandatory
Applicability settings on each plan define where analytics are optional, mandatory or unavailable. A common setup makes the branch plan mandatory on all income and expense accounts, and the project plan mandatory on cost of sales for a contracting company. Odoo then refuses to post an entry without the required analytics, which is far better than discovering gaps at month end.
- Create the plans and their analytic accounts.
- Set applicability: mandatory on income and expenses, optional on balance sheet accounts.
- Create distribution models for the common cases.
- Test with real bills and invoices from each branch.
- Review the analytic report monthly with branch managers.
Reporting and budgets
Odoo's analytic reports and the profit and loss filtered or grouped by analytic plan give branch and project profitability directly. Budgets can also be set per analytic account, so each branch or department sees its actual spending against its budget during the month, not after the year closes.
Budgets are covered in budgets in Odoo, project margins in projects, timesheets and billing, and management views in dashboards and spreadsheet reports.
FlexCode designs analytics that management uses
We define the right analytic plans, automate them with distribution models and build branch and project profitability reports.
Frequently asked questions
What is an analytic plan in Odoo?
A dimension for analysing transactions, such as branch, department or project, with its own analytic accounts.
Can one transaction belong to several branches?
Yes. An analytic distribution can split a line by percentage across several analytic accounts in the same plan.
Should branches be accounts or analytics?
Analytics. It keeps the chart of accounts readable and gives the same information in reports.
Can analytics be mandatory?
Yes. Applicability rules make a plan mandatory on chosen accounts, and Odoo blocks posting without it.
How do I allocate head office costs?
With a distribution model that splits the cost across branches by agreed percentages.
Talk to us about how Odoo fits your business. Book a free call
Run invoicing, stock and accounts from one system.
FlexCode Middle East implements Odoo in Arabic and English for companies in Egypt, Saudi Arabia and the UAE.