Odoo Project: hours logged every day, billing from timesheets, budget under control

What Odoo Project and Timesheets 20 cover, how they are configured and what to check: stages, hours, time-based billing, budget, profitability and when custom development is needed.

ProductOdooprogettitimesheetERP19 November 2026 · 17 min read

Odoo Project manages work by task, both in internal projects and in delivering services to customers. Timesheets are the time-recording layer that feeds project cost control, productivity reporting and customer billing. Together they close the loop between selling services (Sales), delivering them (Project), tracking the effort (Timesheets) and invoicing (Accounting). This article describes what the modules cover, how they are configured, which mistakes recur most often and how to decide between standard, configuration, integration and custom development. It refers to Odoo 20 Enterprise.

When an implementation is healthy

A project and timesheets implementation works when five conditions hold:

  • every active project has tasks with assigned owners, deadlines and stages that mirror real progress;
  • time is logged in Odoo by the people doing the work, and not reconstructed from memory at month end;
  • billable time reaches the invoice from Odoo with no billing spreadsheet;
  • project profitability (budget against actual hours and costs) is visible in real time;
  • managers see the team's workload and resource allocation without having to ask person by person.

The module covers five areas: projects (structure, stages, deadlines, Gantt), tasks (assignments, sub-tasks, dependencies), timesheets (hourly logging per task), resource planning (workload view) and integration with billing (time and materials through Sales).

The basics for people working on projects

People who use Project often move between planning views and execution views.

ViewUse in projects
KanbanTasks by stage within a project: the team's daily working view
ListAll project tasks with deadlines, assignees, status: multiple editing
FormA single task: description, sub-tasks, timesheets, attachments, chatter
GanttProject timeline: task durations, dependencies, critical path
CalendarTasks with a deadline on the calendar: deadline management
PivotHours by employee, project, period: workload and cost analysis
GraphBurn-down, trend of time allocation

The Kanban per project is the team's daily interface. Stages must match the real work process, not be generic labels nobody understands.

On filters: in tasks you filter by assignee, project and deadline (late, this week) with grouping by stage, project and assignee. In timesheets you filter by employee, project and date, grouping by project to see the distribution of hours. My tasks is the personal filter with only those assigned to the logged-in user, the individual to-do list; All tasks is the cross-cutting view for managers, to be filtered by late deadline. Favourites are saved such as "My tasks due this week", "All late tasks by assignee", "Unbilled timesheets this month".

Every task has a chatter, which is the place for project communication: the internal note for technical decisions, blockers and review feedback, the internal history of the work; the message to notify a stakeholder or a customer contact directly from the task, with the thread recorded; the scheduled activity for the next step ("Upload the deliverable", "Customer review", "Set up a meeting"). An example: the task "Develop the integration module" is blocked because the API specification is missing. The developer notes "API documentation not yet received from the customer. Blocked since Monday", schedules an "Email" activity for the project manager, notifies the PM with a mention so that they escalate to the customer, and moves the task to the "Blocked" stage, if it exists. The chatter is the complete trace of what happened, when and why, more reliable than WhatsApp threads or email chains.

The structure of projects mirrors delivery, not the org chart

Every project in Odoo is a container of tasks and its structure must follow how the work is really organised. The good structures are: one project for each customer engagement (tasks equal deliverables or workstreams); one project per product area (tasks equal features, bugs, improvements); one project for each recurring service (tasks equal periodic interventions). The bad ones: a single mega-project for everything, where tasks get mixed and there is no reporting per project; projects only by department, where cross-cutting work has no home; projects never archived, which pollute the views for ever. A project with more than 500 open tasks and no substructure (no milestones, no task types, no stages) is a graveyard of tasks: nothing is ever truly finished or findable.

Stages are configured per project, unlike CRM stages, which are shared by the pipeline. A software development project may have Backlog, To do, In progress, Code review, Testing, Done. A service project for a customer: Received, Under analysis, Waiting for the customer, Delivered, Approved, Invoiced. An internal operations project: Ideas, Planned, In progress, Done. Stages shared across all projects (To do, In progress, Done) are used only if all projects really follow the same flow. Using the same stages for a software project and a consulting one makes both pipelines unreadable.

Time is logged every day

Timesheets are worth something only if logged close to the moment the work happens. With daily discipline the employee works two hours on task A and logs them on task A before the end of the day; goes to a meeting and logs one hour on the task of the project concerned; works three hours on task B and logs them on B. With monthly reconstruction they try to remember what they did three weeks earlier: estimates are wrong by 20 to 40 per cent, project cost analysis is useless and billing disputes cannot be settled. With weekly or monthly logging the data gives a rough indication but is not reliable for billing and profitability analysis.

In Odoo 20 there are two levers for daily logging. The timer in the top bar lets you log hours from any screen by starting and stopping the timer; with Attendances the timer is tied to the employee's check-in. The timesheet assistant suggests entries from activity on the computer and in the browser (ActivityWatch app and browser extension), from calendar events and from planning, matched to projects and tasks through assistant rules; the suggestions are reviewed and converted into timesheets. Activity data is processed locally on the user's device. Because the assistant monitors activity on the device, it is advisable to discuss it with HR and the privacy officer before rollout, even though the processing is local.

From timesheets to the invoice, without going through a spreadsheet

For time-and-materials projects the whole billing chain must stay in Odoo. The sales order is created with a service product with invoicing policy "Timesheets"; the project is created automatically or linked by hand; the team logs timesheets on the tasks; the hours are marked as "Billable"; from the order you use Create invoice and the lines are filled from the billable hours; the invoice goes to the customer, who pays, and the payment is reconciled in Accounting. If the billing sheet is filled in by hand by the PM at month end and then entered into Odoo to create the invoice, the timesheet integration gives no value.

The product for billable services has type Service, invoicing policy Based on timesheets (not delivered or ordered quantities) and, as sales price, the hourly rate charged to the customer. An example: the order line "Consulting services", quantity 1, price 150 euro an hour; on Confirm the project is created (or linked to an existing one), timesheets are logged, the Timesheets button on the order shows the logged hours, and Create invoice produces lines of the type hours logged times 150 euro an hour, to be sent to the customer.

Budget is the profitability control

Every project should have a budget (in hours or in cost) to compare with the actuals. In Odoo Project there are three types: the hours budget (planned hours against timesheet hours), the cost budget (planned cost, hours times the employee's hourly cost, against the actual cost) and the revenue budget (the contract value from the order against the invoiced amount). The profitability view (Project, Reporting, Profitability) shows: revenue (invoiced plus to invoice, that is billable hours not yet invoiced), costs (timesheets by cost, plus expenses, plus purchase orders linked to the project) and margin (revenue less costs). A project without a budget cannot be governed: it overruns and nobody notices in time.

Configuration

In the project settings what matters are the customer (links the project to the customer for billing); Invoice from, which can be none, project rate, employee rate or task rate; the type Fixed price (invoiced by milestone) or Time and materials (invoiced by the hour); the invoicing of timesheets (only timesheets or all, billable versus internal hours); the analytic account (the link with Accounting for cost centres, created automatically or assigned by hand); privacy (employees, invited employees, portal users, for customer visibility). An internal-only project is seen by the team, and by the manager, not by the customer. With the portal the customer has read-only access to the tasks and progress of their own project.

The fields of a task that matter for management: assignee (one main owner, other followers for visibility), deadline (commitment date, shows in the calendar and in the late filters), planned hours (the estimated effort: feeds the workload view and the burn-down), stage (the state of the flow, which drives the Kanban column), tags (Bug, Feature, Administration, Urgent), star priority (one star equals urgent, to filter priority tasks), sub-tasks (to break complex tasks into trackable items) and milestones (group the tasks by deliverable and give the completion percentage).

A timesheet entry has: date (the day the work was done, not the day of logging), employee, project, task (mandatory if the project has tasks), description (at least one sentence), time (hours in decimal: 1 hour 30 minutes is 1.5) and billing type (billable or non-billable, determines whether it appears on the invoice). For profitability the employees' hourly costs are also needed, set in HR Settings, Timesheets, and they feed the "Cost" column of the reports.

The flows

Starting a project. The opportunity is won, the order is confirmed (service product with invoicing policy on timesheets) and the project is created automatically, linked to order and customer. The PM configures the stages for that type of project, the analytic account (for cost centres), the budget (planned hours or fixed revenue) and portal access, if the customer must see progress. The first tasks are created (workstreams or deliverables), members are assigned and the deadline of each task and of the project is set.

Weekly timesheet discipline. On Monday morning the team reviews the assigned tasks, updates the stages in the Kanban and logs any weekend work (with the assistant active, the suggestions are reviewed and converted). During the week the work done is logged the same day, or at the latest the next morning: for example two hours on the task "API integration" with the description "Implemented the authentication endpoint". On Friday the team compares the logged hours with the week's planned ones; the PM checks for tasks overrunning or unreported blockers and reviews the unbilled timesheets for accuracy before month end.

Monthly time-and-materials billing. In the last week of the month the PM reviews all billable timesheets: are the descriptions correct and presentable to the customer? Are all the hours billable or should some be marked internal? If needed they correct the billing type line by line. At month end, from Sales, Orders, the order is selected and Create invoice is used: the invoice is filled with all the billable timesheets of the period; the PM reviews the draft and approves it, Accounting posts and sends it. The customer receives the invoice with the timesheet detail (configurable: summary or line by line).

What changes with Odoo 20

Odoo 20 Enterprise is the reference. Before classifying a need as development (Studio or custom), it pays to test it against these functions.

  • Field service. In the Odoo 20 documentation it is no longer an app based on Project. The Odoo 19 documentation (field service tasks, task worksheets, product management on tasks, itinerary) has been removed and interventions are planned as Planning shifts (see the article on Planning). Field service processes are assessed on Planning, not on Project. Field service remains documented under Planning.
  • Timesheet assistant: suggests entries from activity on the computer and in the browser, calendar events and planning, matched to projects and tasks by assistant rules.
  • Timer in the top bar: hours are logged from anywhere in Odoo; with Attendances the timer is tied to the employee's check-in.

The Project documentation is otherwise unchanged compared with the previous realignment.

For development requests the guidance is this: custom project portals, capacity plans on spreadsheets, time-tracking plug-ins and separate profitability reports are tested first against the standard and the configuration of Project, Timesheets, Planning (including field service), Sales and Accounting in Odoo 20.

The justifications you hear

In the company they sayIn reality
"Our team has no time to fill in timesheets"Filled in every day they take five minutes. Reconstructing them at month end takes two hours and is imprecise. The resistance is to the habit, not to the tool.
"We invoice from a spreadsheet because it's easier to customise"The sheet is rebuilt every month from memory. Odoo's billing integration is permanent, verifiable and is configured once in ten minutes.
"Project tasks are in Jira or Trello, Odoo is only for invoicing"With tasks separated from billing, every invoice needs a manual reconciliation between two systems.
"We have one big 'Internal work' project for everything that is not billable"Non-billable time by employee and task is invisible. Resource allocation, capacity planning and indirect cost analysis become impossible.
"We don't set planned hours because estimates are always wrong"The wrong estimates are the data. The gap between planned and actual is what improves estimates. Without a budget there is no visibility and overruns repeat.
"The PM keeps the project status with a weekly email"A weekly email is not searchable, is not tied to the tasks and cannot be seen by whoever missed it. The task Kanban and the chatter replace it.
"Portal access for the customer is not needed, we call when there are updates"The customer portal reduces update calls by 60 per cent. Customers see the progress of the tasks, and calls are for deciding, not for finding out the status.

Warning signs

  • Projects without tasks: the project exists in Odoo but the work is tracked elsewhere (Jira, spreadsheet, WhatsApp).
  • Tasks with no assignee or no deadline: no accountability, no scheduling signal.
  • Timesheets logged weekly or monthly: poor accuracy and unresolvable billing disputes.
  • Billable time filled in on Excel to invoice: the timesheet integration gives no value.
  • No employee hourly costs configured: the profitability report shows revenue and zero costs.
  • All timesheets set as non-billable, whatever the project type: billable time is not captured.
  • Project budget (planned hours) never set: the overrun is invisible until the PM flags it.
  • Completed projects not archived: polluted active views and longer dashboard loading times.
  • No milestone on projects lasting several months: no intermediate checkpoint of deliveries.
  • The customer has no portal access to their own projects: a phone call is needed for every update.
  • Task stages not customised by project type: software and consulting projects share generic stages.
  • The PM tracks project status outside Odoo (email, presentation): chatter and activity history unused.
  • Sub-tasks not used for complex deliverables: large tasks without substructure that never come out as "done".

How to check a configuration

After configuring or assessing Project and Timesheets, the check goes through these controls:

  • every active project has a customer (if billable), analytic account, budget (planned hours or revenue) and an assigned PM;
  • the task stages are configured by project type, and not all projects use the default ones;
  • all tasks have an assignee, deadline, planned hours and current stage;
  • the Timesheets module is active and employees log time every day or at least every week;
  • the employees' hourly costs are set in HR Settings, Timesheets, for all members of the project teams;
  • the billable or non-billable distinction is applied per timesheet line or per project;
  • the profitability view is available per project: revenue (order value) against costs (timesheets and expenses);
  • for time-and-materials projects the service product is configured with the policy "Based on timesheets";
  • the time-and-materials billing flow is tried: timesheets, order, Create invoice, billable hours on the invoice;
  • customer portal access is enabled on customer-facing projects and customers see task progress;
  • milestone tracking is configured for projects lasting more than a month;
  • completed projects are archived at once and the list of active projects is up to date;
  • the PM's weekly review routine is established: late tasks, unbilled timesheets, budget against actuals;
  • the integration with Attendances is reviewed, if timesheets are used to validate hours worked.

Standard, configuration, integration or custom development

To compare the current process with what Odoo covers without customisation, the starting point is knowing what is standard: project and task management with Kanban, list, Gantt and calendar views; dependencies between tasks and milestones; logging timesheets on tasks with an optional approval flow; budget monitoring per project (planned against actual hours and costs); billing customers from timesheets, at fixed price, time and materials or by milestone; the project profitability report (margin per project); recurring tasks and project templates; the integration with sales orders to start a project from a confirmed order; the timesheet timer in the top bar and the assistant's suggestions from the user's activity.

Six questions help classify every gap before asking for a development:

  1. How are projects tracked today? Spreadsheet, a PM tool (Asana, Jira, MS Project), email chains? A spreadsheet is standard. Jira with a deep development flow leads to an integration, and whether to replace or link it must be assessed.
  2. How are timesheets captured today? Who logs them, how often, in which tool? Are they used for billing, payroll or project control? If they are not captured, it is understood why before the start. Paper or Excel is standard. An external HR system is an integration.
  3. How are projects invoiced? Fixed price, time and materials, by milestone, or not invoiced externally? Every billing model is configuration, solved by Odoo's invoicing policy. Complex multi-currency project billing remains configuration.
  4. How is project profitability tracked? Is there a margin-per-project view? If it is missing, it is a configuration gap solved by the profitability report and analytic accounts.
  5. How are milestones and deadlines communicated to the customer? Portal, email, PDF report? Email is solved with Odoo's customer portal and the sharing of milestones.
  6. Are there project templates for recurring types of work? If they are missing it is standard plus a process change. Complex templates with tasks created automatically by product require Studio.

The typical classification of the most common cases is this:

Frequent gapTypical pathSigns that push towards custom
Projects on a spreadsheetStandardJira or ADO with complex development flows and hundreds of integrations
No timesheet captureProcess change and configuration (timer, timesheet assistant)None
Field interventions managed as project tasksConfiguration (Planning's field service)None
Fixed-price billing onlyConfigurationComplex billing with several rates, currencies and contract types
No profitability viewConfiguration (analytic accounts)A multi-entity project P&L with complex intercompany allocation
No project templatesStandard and process changeA heavily parameterised project setup that requires a guided creation
This article is an OIAR skill

What you have just read is the content of a skill from the OIAR catalogue, written for people. Knowledge like this, but richer and deeper, written for the agents, drives the interviews, the analysis and the report inside the platform. Skills are used in OIAR: to try this one on a project of yours you need an account.

odoo-projectA guide to designing and checking the Odoo 20 Enterprise Project and Timesheets modules: project structure, stages per project, tasks and milestones, daily time logging, timer and timesheet assistant, time-and-materials billing from timesheets, budget and profitability. It contains the warning signs, the justifications heard in companies and the questions for deciding between standard, configuration, integration and custom development. It is needed when setting up or checking service project management in Odoo, with or without interviews with project managers and service heads.