An employee logs three hours on a task, and they appear against the project. Are those hours now eligible for invoicing? Does closing the task mean that the customer accepted its output? A services company may answer these questions differently. Buying an Odoo implementation requires separating these decisions before timesheets become a source of customer disputes.
Ask the implementer to trace a sold service through its project, task, time entry and review, then into what your agreement allows you to invoice. This article scopes that workflow rather than selecting hosting or comparing proposals for the entire system.
Choose work your team recognizes
Imagine a fictional company preparing operating manuals for clients. A researcher and editor work across two projects, undertaking internal research, included revisions or additional requests awaiting approval. These activities differ even when each consumes one hour.
Take one illustrated task and connect it to the right service and customer. Identify the activity description, date, owner and person responsible for correcting a mistaken link. Instead of first browsing dozens of menus, trace one entry's effects and then a second case requiring different treatment.
A workflow card before configuring fields
Complete this card for each main service type. It is a proposed requirements tool rather than guaranteed status names in every Odoo configuration. Ask what configuration, operating procedures or specifically scoped development would deliver it.
| Stage | Buyer's question | Demonstration evidence |
|---|---|---|
| Service and sales order | What invoicing policy was agreed? | Correct service and order-item references before logging time |
| Project and task | Where is activity logged, and for which customer? | A clear task without undifferentiated time for two clients |
| Time entry | Who records it and who may edit it? | Description, date, owner and appropriate permissions |
| Review and delivery | Who reviews effort and accepts the output? | Separate evidence where the agreement separates these decisions |
| Invoice eligibility | What enters the draft, and who checks it? | A test draft matching agreed items and policy |
Odoo 19 documentation describes a time-based invoicing workflow requiring a configured service product, appropriate invoicing policy and project/task links. Timesheets guidance explains the sales-order item for billable projects. This establishes a possible mechanism rather than a commercial entitlement independent of your agreement.
Test three hours with different meanings
In the fictional company, enter internal research, an included client revision and an out-of-agreement request. Decide beforehand which should reach the draft invoice, which should wait or remain nonbillable, and how reviewers can see the reason.
Afterward, request an explanation of differences between total logged time and time selected for invoicing. If the demonstration assumes that everything recorded is automatically invoiced, return to your service policies. Some services may have fixed prices; do not impose time-based billing simply because it appears in the demonstration.
A manager's demonstration does not establish employee permissions
Timesheets documentation distinguishes access to personal entries from viewing, editing and validating everyone's entries, and from administering settings. Logging also requires employee registration and project-level timesheet enablement. Ask how your version and team roles will be configured instead of treating an administrator's account as representative.
Test employee recording, supervisor corrections and reassignment to another order item where policy permits. Agree how corrections discovered after validation or draft preparation are handled: who decides, and how are effects explained to finance? Timesheet validation does not independently establish customer acceptance of an output.
Hand over the operating policy alongside configuration
Request short instructions covering internal activities, extra work, waiting for responses, included revisions and exception ownership. Business and finance owners determine treatment appropriate to their agreements; this article prescribes no accounting or tax rule. Logged hours alone also cannot establish delivery quality or personal productivity.
Start with Odoo discovery workshop deliverables, then use implementation proposal comparisons for broader scope. Send the workflow card and three cases when requesting Odoo implementation from Nextwave so requirements precede screen configuration.
Workflow references
Odoo 19 documentation on time-and-material invoicing and timesheets was opened on 4 November 2026. The example and card are proposals without real transactions or invoices. AI assisted preparation, with information and translation review.
