All timesheet findings in one place — rule-based check violations and data quality problems, sorted by severity. Use the breakdown below for grouped detail by issue type.
| CRITICAL | CHECK-10 — DEACTIVATED EMPLOYEE BILLING | imran | 2026-03-09 | Entain Platform | imran | 2026-03-09 | project=Entain Platform |
| CRITICAL | CHECK-4 — UNASSIGNED PROJECT BILLING | sushant | 2026-03-09 | Entain Platform | sushant billed 'Entain Platform' | assigned=['Ballys Portal'] |
| CRITICAL | CHECK-10 — DEACTIVATED EMPLOYEE BILLING | imran | 2026-03-10 | Entain Platform | imran | 2026-03-10 | project=Entain Platform |
| CRITICAL | CHECK-10 — DEACTIVATED EMPLOYEE BILLING | imran | 2026-03-11 | Entain Platform | imran | 2026-03-11 | project=Entain Platform |
| WARNING | CHECK-8 — MISSING DESCRIPTION | saroj | 2026-03-09 | Smarsh Analytics | saroj | 2026-03-09 | project=Smarsh Analytics | activity=Meeting |
| WARNING | CHECK-7 — MISSING ACTIVITY | saroj | 2026-03-10 | Smarsh Analytics | saroj | 2026-03-10 | project=Smarsh Analytics | desc='Implemented feature' |
| WARNING | CHECK-12 — MISSING TIMESHEET — ACTIVE DAY | sushant | 2026-03-10 | sushant | 2026-03-10 | 12 Slack msgs | |
| WARNING | CHECK-7 — MISSING ACTIVITY | himanshi | 2026-03-11 | Entain Platform | himanshi | 2026-03-11 | project=Entain Platform | desc='Icon set uPdate' |
| INFO | CHECK-13 — HOURS FIELD ACCURACY | himanshi | 2026-03-09 | Entain Platform | himanshi | 2026-03-09 | declared=3.54h calculated=3.77h diff=-0.23h |
| INFO | CHECK-13 — HOURS FIELD ACCURACY | himanshi | 2026-03-09 | Entain Platform | himanshi | 2026-03-09 | declared=3.54h calculated=3.75h diff=-0.21h |
| INFO | CHECK-13 — HOURS FIELD ACCURACY | saroj | 2026-03-09 | Smarsh Analytics | saroj | 2026-03-09 | declared=4.88h calculated=5.28h diff=-0.40h |
| INFO | CHECK-13 — HOURS FIELD ACCURACY | saroj | 2026-03-09 | Smarsh Analytics | saroj | 2026-03-09 | declared=4.89h calculated=5.2h diff=-0.31h |
| INFO | CHECK-13 — HOURS FIELD ACCURACY | sushant | 2026-03-09 | Ballys Portal | sushant | 2026-03-09 | declared=2.51h calculated=2.85h diff=-0.34h |
| INFO | CHECK-13 — HOURS FIELD ACCURACY | sushant | 2026-03-09 | Entain Platform | sushant | 2026-03-09 | declared=2.52h calculated=2.97h diff=-0.45h |
| INFO | CHECK-13 — HOURS FIELD ACCURACY | himanshi | 2026-03-10 | Entain Platform | himanshi | 2026-03-10 | declared=8.21h calculated=8.55h diff=-0.34h |
| INFO | CHECK-13 — HOURS FIELD ACCURACY | saroj | 2026-03-10 | Smarsh Analytics | saroj | 2026-03-10 | declared=4.35h calculated=4.83h diff=-0.48h |
| INFO | CHECK-13 — HOURS FIELD ACCURACY | saroj | 2026-03-10 | Smarsh Analytics | saroj | 2026-03-10 | declared=4.35h calculated=4.72h diff=-0.37h |
| INFO | CHECK-13 — HOURS FIELD ACCURACY | himanshi | 2026-03-11 | Entain Platform | himanshi | 2026-03-11 | declared=3.9h calculated=4.38h diff=-0.48h |
| INFO | CHECK-13 — HOURS FIELD ACCURACY | himanshi | 2026-03-11 | Entain Platform | himanshi | 2026-03-11 | declared=3.9h calculated=4.13h diff=-0.23h |
| INFO | CHECK-13 — HOURS FIELD ACCURACY | saroj | 2026-03-11 | Smarsh Analytics | saroj | 2026-03-11 | declared=3.47h calculated=3.92h diff=-0.45h |
Structured intelligence panel and natural-language summaries from each agent in the audit pipeline — leakage, compliance, invoice, reconciliation.
I'll now detect all revenue leakage signals across your timesheet data.## Revenue Leakage Detection Summary
🚨 CRITICAL ALERT: $301,058.65 in Revenue at Risk
|--------|-------|
1. Rate Mismatch (718 findings)
2. Unlogged Work (91 findings)
3. Contract Hours Underbilling (42 findings)
The sample data reveals a systemic over-billing problem:
Action required: Audit all pranav entries on AI Workshops for rate correction before invoice.
Priority 1 (Before Invoicing):
1. ✋ Halt invoice generation — 251 critical findings require triage
2. 📋 Rate audit — Reconcile all 718 rate_mismatch findings against SOW contracts; identify systematic over/under-billing by user-project pair
3. 📝 Unlogged work recovery — Cross-reference 91 unlogged_work findings with Slack signals; request retroactive timesheet entries or formal scope amendments
Priority 2 (Concurrent):
4. 🎯 Cap overage analysis — Review 42 contract_hours_underbilling entries; determine if these require change orders or are within scope variances
5. 👥 High-impact user review — Flag users appearing in multiple leakage categories (likely data quality or assignment issues)
Priority 3 (Post-Fix):
6. 🔄 Regenerate invoice draft — After corrections, rerun invoice builder to reflect accurate rates and hours
All 851 findings have been saved to agent state with work_unit IDs for traceability. Recommend:
The 251 critical findings demand immediate human review—do not invoice with these unresolved.
I'll run the Slack signals extraction to identify hidden work signals and potential revenue leakage.## Slack Context Mining Report
Total Signals Extracted: 1,756
|---|---|
Total Unlogged Work Signals: 91
These represent Slack messages indicating work completed (code reviews, deployments, refactoring, testing) without corresponding timesheet entries — direct revenue leakage opportunities.
#### Top Users with Unlogged Work Activity (by count):
|---|---|
Sample unlogged activities captured:
18 escalation signals detected (urgent production issues requiring immediate attention). These often correlate with unlogged overtime work and should be cross-referenced with approval records.
✅ Strong signal volume: 1,738 work activity messages indicate high documentation of activity in Slack.
⚠️ Revenue at risk: 91 unlogged work signals (5.2% of total activity) represent billable hours not yet captured in timesheets.
🔴 No scope change signals detected — Informal extra-work requests are either not visible in these channels or documented via other means.
Output saved to agent state for downstream revenue leakage and invoice reconciliation analysis.
Status: CRITICAL BLOCKING ISSUES DETECTED
|----------|-------|----------|--------|
#### 1. LEAVE-DAY BILLING (204 findings)
Violated Contract Clause: `leave_policy`
Impact: Employees have logged billable hours on dates marked as approved leave in the HR system. This violates the fundamental leave policy and will cause:
Affected Users: deepak, sankalp, sumit, arjun (and others)
Examples:
Resolution Steps:
1. Audit all 204 entries — cross-reference with leave approval records
2. Options for each entry:
3. Required Documentation: Obtain signed leave cancellation or client work approval memo before invoicing
#### 2. UNASSIGNED PROJECT BILLING (128 findings)
Violated Contract Clause: Implicit (assignment policy)
Impact: Employees billed to projects they have no contract assignment for. This causes:
Affected Projects: CRED, Provus, Shippit - Rate Card, and others
Examples:
Resolution Steps:
1. For each of 128 entries:
2. Required Documentation: SOW amendment, assignment record, or authorized change order
#### 3. DEACTIVATED EMPLOYEE BILLING (4 findings)
Violated Contract Clause: Employee onboarding/status policy
Impact: Inactive employees have timesheet entries. This indicates:
Resolution Steps:
1. Identify the 4 deactivated employees with entries
2. Determine termination/deactivation dates
3. Remove all entries dated after deactivation
4. Verify no duplicate billing by active replacements
#### PARTIAL DAY LEAVE BILLING (2 findings)
Severity: WARNING
Impact: 2 entries show partial day leave with associated hours. Less severe than full-day violations but still requires documentation.
Resolution: Obtain written approval from employee manager and client confirming:
Before this invoice can be sent to clients, ALL CRITICAL items must be resolved.
|------|-----------------|---------|----------|
1. HOLD invoice release pending resolution
2. Escalate to Finance Director — 336 critical violations require executive review
3. Request leave calendar reconciliation from HR — validate all 204 leave-day entries against official leave system
4. Request project assignment audit from HR — verify or add the 128 missing assignments
5. Generate compliance remediation report — document resolution for each finding
6. Schedule client communication — prepare explanations for any billing adjustments
Findings saved to agent state. Awaiting resolution actions before proceeding to invoice draft stage.
I'll generate the invoice draft by calling the Invoice Drafting Agent. This will compile billable work units into line items, apply contract rates, and flag any items requiring human review.## Invoice Draft Summary
✅ Invoice generated successfully — 62 billable line items totaling $442,592.25 (6,258.91 hours)
|---------|----------|-------|
Total: $442,592.25 across 17 projects
#### Rate Fallback (53 items) — Contract rates not found
These lines use timesheet rates as fallback. Action needed: Verify rates are correct before invoicing.
High-priority users/projects:
#### Role Mismatch (5 items) — Users not in contract team
These require explicit approval to bill:
#### Name Ambiguity (4 items)
1. Verify AI Workshops team rates — 6 core team members all on fallback rates (no SOW contract rates available). Confirm $75–80/hr is correct.
2. Approve CRED roster addition — Three users (riyaz.kagzi, manish.lath, gaurav.shewale) billing to CRED but not in SOW contract. Either amend SOW or exclude from invoice.
3. Review ambiguous names — Resolve duplicate/alternate name references (e.g., "sagar.yadav" vs "sagar.sahasrabuddhe") to prevent duplicate billing.
4. Validate Provus & Home Health Notify staffing — saunak.adhikari and priyanka.pakhale need to be added to contract rosters or removed from billing.
5. Cross-check with compliance findings — Before sending, ensure all lines pass revenue leakage, cap overage, and scope-creep checks.
Invoice draft is saved and ready for review. Once flagged items are approved/corrected, the invoice can be finalized for client submission.
I'll help you reconcile the work units with project assignments and the contract model. Let me start by calling the reconciliation agent.## Work Reconciliation Summary
The reconciliation is complete. Here are the key findings:
Analysis: About 20% of logged hours are classified as non-billable. Primary reasons are likely missing project assignments (empty project) and unassigned staff. The "empty project" entry alone accounts for 142.15 non-billable hours across 25 users, indicating assignment data gaps.
|---------|-------------------|-------|-------|
The reconciled work has been saved. Downstream agents should now run:
1. detect_revenue_leakage — identify missed billing, scope creep, and rate mismatches
2. run_compliance_checks — catch unauthorized overtime, leave-day billing, and deactivated user entries
3. build_invoice_draft — aggregate billable line items for client invoicing
I'll extract the structured billing rules from all SOW and guideline documents by calling the contract model builder.## Contract Model Summary
Documents Parsed:
All projects are configured as Time & Material (T&M) billing. Here's the complete project inventory:
|---------|-------------------|-----------|---------------------|
⚠️ Critical Finding:
✅ Strengths:
1. All 17 projects have explicit monthly_cap_hours defined (no None values)
2. Clear team size specification for each project enables headcount validation
3. Consistent T&M billing model across all engagements
⚠️ Items to Monitor:
1. No global overtime approval requirements — validate against HR guidelines to ensure compliance with labor laws
2. No leave types or billing exclusions defined in contracts — must cross-reference with HR policies and public holiday calendars
3. Team rosters are project-specific (team_map available per project) — ensure all timesheet entries match assigned roster members
4. The "Caizin (Smarsh K8s Migration)" project has an unusually low cap (16 hours) — verify this is intentional and not a data entry error
Status: ✅ Contract model extracted and saved. Ready for downstream agents to:
I'll help you normalize and enrich the timesheet data into WorkUnit records. Let me start by discovering what data files are available, then build the enriched work units.Great! I found 9 data files. Now let me normalize all the timesheet data into enriched WorkUnit records:## 📊 Normalization & Linking Agent — Summary Report
Status: ✅ All timesheet data successfully normalized into enriched WorkUnit records and saved to agent state.
|--------|-------|
1. hours_mismatch — 1,411 issues (87.8%)
2. missing_description — 96 issues (6.0%)
3. missing_activity — 61 issues (3.8%)
User: `deepak` — Multiple concurrent quality issues detected
✅ WorkUnit records now ready for downstream agents:
All enriched work units (including assignment status, leave status, employee status, project status, and quality flags) are saved to agent state and ready for analysis.