Odoo analytic accounting: measuring profitability by project and activity

In short. Odoo analytic accounting adds a second reading to your entries: every invoice, purchase and logged hour can be attached to an axis (project, department, service line, job site). The general P&L, kept under the Luxembourg PCN 2020 chart of accounts, stays intact and compliant; the analytic layer lives alongside it and answers the question the balance sheet ignores: which activity makes money, and which loses it. The setup comes down to three decisions: which axes, which allocation rules, and who records what.

A Luxembourg SME invoicing €2M knows from its general accounting that it makes, say, 8% profit. What it almost never knows is that this figure blends one activity at 25% margin with another that has been losing money for two years. Analytic accounting exists to separate those realities. In Odoo it is native, requires no third-party module, and is fed automatically by the documents you already create.

What does analytic accounting do in Odoo?

Odoo analytic accounting attaches every revenue and cost line to one or more analytic accounts, grouped into plans (by project, department or activity). It produces a profitability view per axis, independent of the general chart of accounts, and is fed automatically from invoices, purchases, timesheets and expense reports.

The key word is "independent". Your general accounting stays structured by nature of cost (class 6) and revenue (class 7) under the PCN 2020: that is what produces the balance sheet, the VAT return and the annual accounts filed with the RCS. The analytic layer changes none of these obligations. It answers a different question: not "how much did we spend on salaries", but "how much did project A cost us in salaries".

Analytic plans and axes: structuring without drowning

In recent versions (and still the case in Odoo 19), the analytic layer is organised in plans, each containing analytic accounts. You can cross several plans: a "Projects" plan, a "Departments" plan, a "Regions" plan. A single invoice can then be read along all three axes at once.

The classic temptation is to create too many. Three plans that live are worth more than six that die: every extra axis is extra data entry, and neglected entry produces false reports. For a services SME, a single plan per project or per client is often enough to transform steering. For a trading business, one plan per product range. For a multi-activity company, one plan per division, and nothing more, at least in year one.

Analytic distribution: the mechanism that does the work

On each invoice or vendor bill line, Odoo offers an analytic distribution: you assign the line to an analytic account, or split it by percentages (60% project A, 40% project B). Distribution models then automate the gesture: Odoo can apply the split on its own based on the partner, product or account involved. The office rent spreads across the same divisions every month with no human intervention.

Timesheets play the same role for services: an hour logged on a project becomes an analytic line valued at the employee's cost. That is what powers the project profitability view, where hours actually spent are compared with what was invoiced, a mechanism we detail in Odoo for service companies in Luxembourg.

Want to know which analytic axes would make sense for your business? The right breakdown depends on the decisions you need to make, not on a textbook model. Advena provides a free diagnostic of your steering needs.

General vs analytic: who does what?

Both feed on the same entries: there is no double data entry. That is precisely the point of running the analytic layer inside the ERP rather than in a spreadsheet rebuilt every quarter. The prerequisite remains a clean general accounting base on the PCN 2020, whose setup is described in setting up Luxembourg accounting in Odoo.

The setup, in practice

1. Define the axes with management, starting from the decisions at stake: pricing, closing or growing an activity, tracking job sites.
2. Create the analytic plans and accounts in Odoo Accounting, with a stable naming convention.
3. Configure distribution models for recurring costs (rent, insurance, subscriptions) and obvious cases (this vendor, that division).
4. Connect the sources: timesheets, expense reports, purchases. The more the split happens at the source, the less reprocessing remains.
5. Check the first month: the share of entries with no analytic assignment should tend towards zero on the tracked revenue and cost accounts.

Illustrative case (provided as an example; it does not correspond to a real client). A nine-person engineering firm runs about fifteen assignments in parallel. Setup: a single "Assignments" analytic plan, fed by timesheets and subcontracted purchases. By the second month, the profitability view shows that fixed-price assignments for one particular client consume 35% more hours than the standard quote assumes. The quote is recalibrated; the effect on margin shows the following quarter. Without the analytic layer, that gap would have stayed diluted in a respectable overall result.

From analytic data to steering

A P&L filtered by analytic axis is the raw material of margin by activity, one of the five indicators we recommend watching weekly in the financial dashboard in Odoo. And reading those gaps, deciding on repricing, dropping a range, reallocating a team, is financial steering: the work a fractional CFO performs a few days a month, on figures the analytic layer finally makes readable.

This is Advena's particular coupling: the same team configures the analytic plans in Odoo and works with what they reveal, because it holds the tool and the finance dimension under one roof. An analytic breakdown designed without a finance eye produces accurate but useless reports; a finance professional without access to the tool rebuilds everything in a spreadsheet. Together, they produce decisions.

FAQ

Is analytic accounting mandatory in Luxembourg?

No. No legal obligation requires a Luxembourg SME to keep analytic accounts. The obligations (annual accounts, VAT, FAIA on request) rest on the general accounting kept under the PCN 2020. The analytic layer is an internal steering tool, optional but often decisive.

Does it require an extra module in Odoo?

No. Analytic plans, distributions and reports are part of the Accounting app. Timesheets and the project profitability view rely on the Project app, included in the all-in-one offer.

Can one invoice be split across several projects?

Yes. The analytic distribution accepts percentage splits across several accounts, and distribution models memorise these rules to apply them automatically to future entries.

What is the difference between an analytic account and a PCN account?

The PCN 2020 account classifies an entry by nature (salaries, rent, sales) and serves the legal obligations. The analytic account classifies the same entry by destination (which project, which division). The two readings coexist without interfering.

Why Advena?

• Finance and digital under one roof: the analytic axes are designed by the people who will read the margins they produce.
• Luxembourg grounding: the analytic layer sits on top of a clean PCN 2020 base, never in place of it.
• Clear packages, no hourly billing: a defined scope, a price known upfront.
• Direct access to the founders: the partners work with you, not a junior.

Going further: Financial dashboards in Odoo · Fractional CFO in Luxembourg · Odoo for service companies in Luxembourg · Setting up Luxembourg accounting in Odoo · Odoo in Luxembourg: is it the right ERP for your SME?