Revenue Intelligence Report

v3 model: haiku generated 2026-04-12 17:24
19
Entries Audited
4
Critical Issues
4
Warnings

Invoice Status & Pipeline Summary

INCOMPLETEIntelligence pipeline has not completed — run all agents first.

Timesheet Issues20

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.

📄kimai_timesheets.csv📄normalisation agent (work units)
Showing 20 of 20 issues
SeverityCheck / TypeUserDateProjectIssue
CRITICALCHECK-10 — DEACTIVATED EMPLOYEE BILLINGimran2026-03-09Entain Platformimran | 2026-03-09 | project=Entain Platform
CRITICALCHECK-4 — UNASSIGNED PROJECT BILLINGsushant2026-03-09Entain Platformsushant billed 'Entain Platform' | assigned=['Ballys Portal']
CRITICALCHECK-10 — DEACTIVATED EMPLOYEE BILLINGimran2026-03-10Entain Platformimran | 2026-03-10 | project=Entain Platform
CRITICALCHECK-10 — DEACTIVATED EMPLOYEE BILLINGimran2026-03-11Entain Platformimran | 2026-03-11 | project=Entain Platform
WARNINGCHECK-8 — MISSING DESCRIPTIONsaroj2026-03-09Smarsh Analyticssaroj | 2026-03-09 | project=Smarsh Analytics | activity=Meeting
WARNINGCHECK-7 — MISSING ACTIVITYsaroj2026-03-10Smarsh Analyticssaroj | 2026-03-10 | project=Smarsh Analytics | desc='Implemented feature'
WARNINGCHECK-12 — MISSING TIMESHEET — ACTIVE DAYsushant2026-03-10sushant | 2026-03-10 | 12 Slack msgs
WARNINGCHECK-7 — MISSING ACTIVITYhimanshi2026-03-11Entain Platformhimanshi | 2026-03-11 | project=Entain Platform | desc='Icon set uPdate'
INFOCHECK-13 — HOURS FIELD ACCURACYhimanshi2026-03-09Entain Platformhimanshi | 2026-03-09 | declared=3.54h calculated=3.77h diff=-0.23h
INFOCHECK-13 — HOURS FIELD ACCURACYhimanshi2026-03-09Entain Platformhimanshi | 2026-03-09 | declared=3.54h calculated=3.75h diff=-0.21h
INFOCHECK-13 — HOURS FIELD ACCURACYsaroj2026-03-09Smarsh Analyticssaroj | 2026-03-09 | declared=4.88h calculated=5.28h diff=-0.40h
INFOCHECK-13 — HOURS FIELD ACCURACYsaroj2026-03-09Smarsh Analyticssaroj | 2026-03-09 | declared=4.89h calculated=5.2h diff=-0.31h
INFOCHECK-13 — HOURS FIELD ACCURACYsushant2026-03-09Ballys Portalsushant | 2026-03-09 | declared=2.51h calculated=2.85h diff=-0.34h
INFOCHECK-13 — HOURS FIELD ACCURACYsushant2026-03-09Entain Platformsushant | 2026-03-09 | declared=2.52h calculated=2.97h diff=-0.45h
INFOCHECK-13 — HOURS FIELD ACCURACYhimanshi2026-03-10Entain Platformhimanshi | 2026-03-10 | declared=8.21h calculated=8.55h diff=-0.34h
INFOCHECK-13 — HOURS FIELD ACCURACYsaroj2026-03-10Smarsh Analyticssaroj | 2026-03-10 | declared=4.35h calculated=4.83h diff=-0.48h
INFOCHECK-13 — HOURS FIELD ACCURACYsaroj2026-03-10Smarsh Analyticssaroj | 2026-03-10 | declared=4.35h calculated=4.72h diff=-0.37h
INFOCHECK-13 — HOURS FIELD ACCURACYhimanshi2026-03-11Entain Platformhimanshi | 2026-03-11 | declared=3.9h calculated=4.38h diff=-0.48h
INFOCHECK-13 — HOURS FIELD ACCURACYhimanshi2026-03-11Entain Platformhimanshi | 2026-03-11 | declared=3.9h calculated=4.13h diff=-0.23h
INFOCHECK-13 — HOURS FIELD ACCURACYsaroj2026-03-11Smarsh Analyticssaroj | 2026-03-11 | declared=3.47h calculated=3.92h diff=-0.45h

AI Summary

Structured intelligence panel and natural-language summaries from each agent in the audit pipeline — leakage, compliance, invoice, reconciliation.

⚠️Revenue at Risk

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

Key Findings

|--------|-------|

Leakage by Type

1. Rate Mismatch (718 findings)

  • Users being over-billed or under-billed relative to SOW contract rates
  • Largest financial exposure

2. Unlogged Work (91 findings)

  • Slack evidence of work performed with no corresponding timesheet entry
  • Revenue completely lost if not captured

3. Contract Hours Underbilling (42 findings)

  • Hours logged beyond monthly contract caps without additional approval
  • Potential discrepancy between contract obligations and actual delivery
Top Issue: Pranav Rate Discrepancy (AI Workshops Project)

The sample data reveals a systemic over-billing problem:

  • User: pranav
  • Project: AI Workshops
  • Problem: Billing at $75/hr vs. SOW contracted rate of $55/hr
  • Impact from sample alone: ~$1,300+ in excessive charges
  • Multiple dates affected: Mar 5–18, 2026

Action required: Audit all pranav entries on AI Workshops for rate correction before invoice.

Recommended Immediate Actions

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

Next Steps

All 851 findings have been saved to agent state with work_unit IDs for traceability. Recommend:

  • Export leakage report for finance review before client communication
  • Schedule reconciliation call with resource managers to validate findings
  • Prepare amendment documentation for any scope-creep items that warrant change orders

The 251 critical findings demand immediate human review—do not invoice with these unresolved.

Unlogged Work from Slack

I'll run the Slack signals extraction to identify hidden work signals and potential revenue leakage.## Slack Context Mining Report

Summary of Findings

Total Signals Extracted: 1,756

|---|---|

Primary Revenue Leakage: Unlogged Work Activity

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):

|---|---|

Notable Work Activity Examples

Sample unlogged activities captured:

  • PR Reviews & Code Feedback — Multiple instances across team members
  • Production Deployments — Unlogged deploy activity from vishnu.nair, vineet.singhal
  • Refactoring Work — Middleware layer and other system improvements
  • Migration Scripts — Testing and completion signals without timesheet records
Escalation Signals

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.

Key Insights

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.

🚫Compliance & Blockers

COMPLIANCE & RISK ASSESSMENT

Status: CRITICAL BLOCKING ISSUES DETECTED

SUMMARY OF FINDINGS

|----------|-------|----------|--------|

CRITICAL BLOCKING ISSUES

#### 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:

  • Client invoice disputes (billing for non-existent work)
  • Audit red flags
  • Potential contract termination

Affected Users: deepak, sankalp, sumit, arjun (and others)

Examples:

  • deepak: 1.98h billed to "AI Workshops" on 2026-03-02 (approved leave)
  • deepak: 4.0h billed to "AI Workshops" on 2026-03-09 (approved leave)
  • sankalp: 8.0h billed to "AI Workshops" on 2026-03-04 (approved leave)

Resolution Steps:

1. Audit all 204 entries — cross-reference with leave approval records

2. Options for each entry:

  • If leave was incorrectly marked: remove from leave calendar and restore billing
  • If work truly occurred: request retroactive leave cancellation + written approval from client
  • If billing is erroneous: remove timesheet entry and adjust hours to non-leave dates

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:

  • Invalid billing (no SOW coverage for this person on this project)
  • Client disputes over unauthorized resource allocation
  • Rate/allocation mismatches

Affected Projects: CRED, Provus, Shippit - Rate Card, and others

Examples:

  • deepak: billed to "CRED" on 2026-03-04 (not assigned per HR system)
  • deepak: billed to "Provus" on 2026-03-25 (not assigned per HR system)
  • sankalp: billed to "Provus" on 2026-03-09 (not assigned per HR system)
  • sumit: billed to "Shippit - Rate Card" on 2026-03-06 (not assigned per HR system)

Resolution Steps:

1. For each of 128 entries:

  • Check if assignment should exist but is missing from HR system → add retroactive assignment
  • Check if employee is covering due to resource shortage → obtain signed SOW amendment
  • If no valid assignment exists → remove timesheet entry (cannot bill without contract coverage)

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:

  • Data integrity issue (ghost entries)
  • Potential fraud risk
  • Ineligible billing

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

WARNING ITEMS ⚠️ (Must be Documented)

#### 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:

  • Which portion of the day was worked
  • Leave hours vs. billable hours are correctly split
  • Client approves mixed leave/work day billing
INVOICE READINESS: BLOCKED 🚫

Before this invoice can be sent to clients, ALL CRITICAL items must be resolved.

|------|-----------------|---------|----------|

RECOMMENDED IMMEDIATE ACTIONS

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.

🧾Invoice & Billing

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)

📊 Project-Level Breakdown

|---------|----------|-------|

Total: $442,592.25 across 17 projects

🚨 Lines Requiring Human Review: 53 flagged items

#### 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:

  • AI Workshops: deepak ($10,640 @ $80/hr), sidharth ($9,416 @ $80/hr), sumit ($8,591), sankalp ($7,930) — all using fallback rates
  • Entain - CRM: pranjal ($10,966 @ $75/hr), rajat.tomar ($8,347 @ $65/hr), neel.chavan ($8,289 @ $75/hr)
  • Economist - Ads: sagar.yadav ($10,762 @ $75/hr), rahul.dhuri ($9,832 @ $75/hr)
  • Universal Ether: All 5 team members using fallback rates (70–80/hr)

#### Role Mismatch (5 items) — Users not in contract team

These require explicit approval to bill:

  • CRED: riyaz.kagzi (118.88 hrs @ $80), manish.lath (80.18 hrs @ $80), gaurav.shewale (85.47 hrs @ $75)
  • Home Health Notify: priyanka.pakhale (missing from contract roster)
  • Provus: saunak.adhikari (missing from contract roster)

#### Name Ambiguity (4 items)

  • sagar.yadav (Economist - Ads)
  • gaurav.shewale (CRED)
  • sagar.sahasrabuddhe (Economist - Ads)
📋 Recommendations Before Sending

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.

Reconciliation

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:

Billable vs Non-Billable Hours
  • Billable: 1,540 units / 6,258.91 hours (80.5%)
  • Non-billable: 470 units / 1,519.31 hours (19.5%)
  • Total: 2,010 units / 7,778.22 hours

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.

Duplicate Detection
  • Duplicates Found: 0 ✓
  • No duplicate timesheet entries detected—data quality is clean on this dimension.
Role Mismatches
  • Mismatches Flagged: 287 ⚠️
  • Risk Level: HIGH—significant dispute risk
  • Pattern: Users billing to projects without being listed in the contract team roster
  • Example: `deepak` billing to CRED and Provus but not contracted for those projects
  • Example: `sankalp` billing to CRED and Provus but not contracted
  • Impact: Invoices containing these hours may be disputed by clients who verify team composition against SOWs.
Projects with Highest Non-Billable Hour Ratios

|---------|-------------------|-------|-------|

Next Steps

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

Contract Model

I'll extract the structured billing rules from all SOW and guideline documents by calling the contract model builder.## Contract Model Summary

Documents Parsed:

  • 17 SOW (Statement of Work) documents
  • 5 Guideline documents
  • 17 Active Projects
Projects Overview

All projects are configured as Time & Material (T&M) billing. Here's the complete project inventory:

|---------|-------------------|-----------|---------------------|

Global Rules & Compliance Framework

⚠️ Critical Finding:

  • Overtime Approval Required: NO global requirement across all contracts
  • Leave Types Defined: None in global rules (to be cross-referenced with HR guidelines)
  • Billing Exclusions: None specified in contracts
  • Billing Caps: All defined at project level (no global override)
Data Quality Notes

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:

  • Normalize timesheet data (build_work_units)
  • Reconcile work against contracts (reconcile_work)
  • Detect revenue leakage and compliance violations

🔍Data Quality

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.

Data Processing Overview

|--------|-------|

Top 3 Data Quality Issues (by count)

1. hours_mismatch — 1,411 issues (87.8%)

  • Declared hours differ from calculated hours (begin/end timestamps) by >0.15h
  • Impact: High risk for billing disputes; direct revenue accuracy threat
  • Example: `deepak` on 2026-03-02 to AI Workshops has mismatched declared vs. calculated hours

2. missing_description — 96 issues (6.0%)

  • Timesheet entries lack description field
  • Impact: Reduces transparency on work performed; harder to cross-reference with project scope

3. missing_activity — 61 issues (3.8%)

  • No activity field specified
  • Impact: Cannot categorize work type; makes downstream billing categorization ambiguous
High-Risk Users (Multiple Quality Flags)

User: `deepak` — Multiple concurrent quality issues detected

  • Flagged entries: hours_mismatch (consistent across multiple projects/dates)
  • Also flagged: missing_activity on some entries
  • Action Required: Manual review of `deepak`'s timesheet methodology and timestamp entry practices
Additional Quality Concerns
  • missing_project — 37 entries (2.3%): Work logged without project assignment
  • invalid_timestamp — 1 entry: Malformed or impossible begin/end time
  • weekend_entry — 1 entry: Work logged on weekend (may indicate override or error)
Next Steps

✅ WorkUnit records now ready for downstream agents:

  • Reconcile Agent will align units with project assignments and contract rates
  • Compliance Agent will cross-check against leave, holiday, and authorization policies
  • Revenue Leakage Agent will identify billing gaps and rate mismatches

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.