Company Timesheet & Performance Intelligence
by Bilsas https://github.com/aykutsp/odoo19-company-timesheet-performance$ 85.70
See the installed product first
Shown with fictional English demonstration data. These are working product views, not design mockups.
Project, Manufacturing and Field Service timesheets under one roof
Bring project and task timesheets, manufacturing order and work order time, and Field Service job timesheets into one governed operational view. Managers can compare employees, departments, customers, projects, production operations and service work without replacing the native Odoo records that remain the source of truth.
Company Timesheet & Performance Intelligence
Turn authoritative Odoo work records into a governed, auditable reporting layer-without creating a competing source of truth.
Built for decisions, not decorative totals
A dependable foundation for operational reporting, approvals and every connector in this suite.
Source-safe architecture
Project and manufacturing records remain authoritative. The reporting layer is refreshed idempotently and can be rebuilt safely.
Approval and locking
Review, approve, reject and lock periods with clear ownership, timestamps and manager controls.
Explainable anomaly engine
Detect missing context, excessive duration, overlaps and workflow exceptions with traceable reasons.
Financial context
Bring cost, revenue, margin and billability into the same governed analytical surface.
Multi-company security
Company-aware access, manager scope and record rules are designed into every reporting path.
Native analytical views
List, form, calendar, pivot and graph views keep advanced reporting inside familiar Odoo workflows.
Observe
Read authoritative Odoo business records.
Reconcile
Synchronize reporting context idempotently.
Explain
Expose traceable KPIs, anomalies and drill-down.
Act
Approve, correct and improve with confidence.
Real operational screens
Premium, multilingual and designed to preserve the context behind every number.
Designed for production Odoo
| Authority | Native project and manufacturing records |
| Synchronization | Idempotent create/update reconciliation |
| Governance | Approval, lock, anomaly and audit controls |
| Isolation | Addon-owned reporting records; source data is never replaced |
Your Odoo data remains yours
The suite is an analytical and workflow layer. Project, task, manufacturing, attendance and leave records remain authoritative in their native Odoo applications. Addon-owned reporting records can be rebuilt, and removing the addon does not require destructive changes to native business data.
Multilingual foundation: translatable interface strings follow the active Odoo language; English is the source language and Turkish translations are included where supplied.
Clear dependencies, governed capabilities
Install only the capabilities you need. Core is the governed foundation; connectors preserve their native domain context; Dashboard turns the combined dataset into the premium management experience.
| Module | Relationship |
|---|---|
| Unified Timesheet Core | Required foundation |
| Unified Timesheet Dashboard | Requires Core + Project + MRP |
| Unified Timesheet Project Connector | Requires Core |
| Unified Timesheet MRP Connector | Requires Core |
| Unified Timesheet Attendance Bridge | Requires Project + MRP |
Turn fragmented operational time into governed, traceable management evidence.
Move beyond totals. Every score is paired with a formula, a valid denominator, a reporting period and a path back to the Odoo records that produced it.
Find exceptions before they become reporting disputes.
Trace cost, revenue, margin and billable hours.
Trust approved metrics with source drill-down.
Know what each number means before acting on it
The sample values below illustrate the product experience. Your results are calculated from your own authorized Odoo records and selected reporting period.
| Score | Example | Calculation basis |
|---|---|---|
| DATA COMPLETENESS | 96.8% | Complete required dimensions / eligible entries |
| APPROVAL HEALTH | 84.2% | Approved hours / recorded hours |
| SYNC CONFIDENCE | 99.7% | Reconciled sources / eligible sources |
| ANOMALY EXPOSURE | 2.4% | Open anomalies / active entries |
| LOCK COVERAGE | 91.0% | Locked approved hours / approved hours |
| BILLABILITY | 73.6% | Billable hours / recorded hours |
| TIME MARGIN | Native financial context | Time revenue - employee time cost |
| SOURCE TRACEABILITY | 100% | Entries with a valid source identity |
See the signal. Understand the formula. Open the evidence. Take action.
Premium presentation is matched by operational depth: multilingual UI, company-aware security, source traceability, period controls and drill-down are part of the product story.
From installation to management action
This guide explains the complete operating model: what must be configured, which native Odoo record remains authoritative, how the reporting layer is refreshed, how managers should interpret metrics and how common data-quality issues are resolved.
Installation and first configuration
Prepare a controlled, auditable rollout before exposing metrics to management.
- Install the Core module first and verify that Project, Manufacturing and employee company assignments are configured in native Odoo.
- Open Unified Timesheets > Configuration and review the synchronization scope, approval managers and company access before the first refresh.
- Run the initial synchronization from the reporting action. Existing source records are projected into the reporting layer; they are not moved or replaced.
- Grant User, Approver or Manager access according to responsibility. Test each role with a non-administrator account before production rollout.
Daily operating workflow
Understand where data originates and how it becomes visible in the suite.
- Employees continue recording work in their native Project or Manufacturing screens.
- The synchronization service creates or updates the matching unified entry using a stable source identity.
- Approvers review pending entries, inspect the source reference and resolve anomalies before approval.
- Approved periods can be locked to prevent uncontrolled reporting changes while source records remain traceable.
Manager review procedure
Use drill-down and comparable periods to turn indicators into defensible decisions.
- Filter entries by company, employee, source type, project, task, manufacturing order, work order, state or date.
- Open an entry to compare normalized duration and commercial values with the authoritative source link.
- Use anomalies as review prompts, not automatic accusations. Every anomaly includes the measurable condition that triggered it.
- Re-run synchronization after correcting the source. Idempotency updates the existing projection instead of creating a duplicate.
How the principal indicators are calculated
Percentages are meaningful only when their denominator is valid. Always confirm calendar, leave, planning, cost and source completeness before comparing employees or departments.
| Metric | Formula | Interpretation |
|---|---|---|
| Approved Rate | Approved Hours / Total Recorded Hours x 100 | Share of captured time that completed governance. |
| Billability | Billable Hours / Total Recorded Hours x 100 | Commercial utilization of recorded work. |
| Margin | Revenue - Cost | Contribution after time-based employee cost. |
| Anomaly Rate | Open Anomalies / Unified Entries x 100 | Review workload, not an employee performance score. |
Resolve the cause at the authoritative source
Recommended production acceptance checklist
1. Reconcile a sample period against native Odoo totals.
2. Test multi-company access with real non-admin roles.
3. Confirm timezone and calendar behavior around day boundaries.
4. Verify every KPI drill-down reaches its contributing records.
5. Test approved leave, holiday and no-schedule scenarios.
6. Start and stop each supported timer path.
7. Upgrade in a staging database before production.
8. Document who owns data correction and period approval.
Make time, capacity and performance explainable
Purpose-built for organizations that need operational clarity across project delivery, manufacturing and workforce capacity inside Odoo.
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Employees (hr) |
| Lines of code | 1531 |
| Technical Name |
unified_timesheet_core |
| License | LGPL-3 |
| Website | https://github.com/aykutsp/odoo19-company-timesheet-performance |
Please log in to comment on this module