Agree the opening status of each active engagement by deliverable, fee phase, approved change and outstanding customer input. Reconcile previously billed amounts, recorded effort and the firm's reviewed unbilled position without assuming they are interchangeable. Preserve document references so imported project records still point to the operative technical evidence.
Understand the decision
An engagement can be technically advanced while commercial acceptance or invoicing remains incomplete. Historical timesheets may use phase codes that changed during delivery. The migration must explain those mappings and retain source records so finance and project managers can investigate differences without rewriting the underlying history.
Work through the requirements
- Map deliverables and legacy phase codes.
- Reconcile billed and reviewed unbilled positions.
- Preserve current document and decision references.
| Record or decision | Why it matters |
|---|---|
| Engagement opening sheet | Explains remaining deliverables and commercial status. |
| Phase cross-reference | Connects old and new effort categories. |
| Financial reconciliation | Documents prior billing and opening differences. |
What would a passing test show?
Use these hypothetical cases in a demonstration. Mark the evidence you have reviewed, then download the checklist. Selections stay in this tab.
Watch for this failure
Treating all recorded time as opening revenue can misstate the project position. Have finance approve the accounting treatment separately and reconcile the operational evidence before imported balances become the basis for management reporting.
Continue the evaluation
This example defines what to verify, rather than promising a particular Odoo feature. Keep a record of the demonstrated result, configuration, unresolved gaps and person who accepts it.
Read the wider implementation guideBring your workflow to the conversation.
Discuss requirements for Engineering consultancies in a business needs review. Start with your current systems, the handoff that fails and the result you need to prove.
Sources & scope
The linked product documentation is a starting point for validating your chosen version, edition, apps and hosting. The scenarios and acceptance criteria are editorial planning guidance, not customer case studies or a guarantee of built-in functionality. See how this library is prepared.
Odoo 19: project management ↗Odoo 19: project milestones ↗Odoo 19: timesheet configuration and recording ↗