InfraResolution Bench

Case Explorer

Usage dashboard lags invoice preview

Usage dashboard and invoice preview disagree because meter ingestion is lagging even though compute service health is normal.

Evidence Packet

CRM Record

Account: Lattice Foundry

Tier: enterprise

Plan: Committed-200

Billing Owner: finance@prime.example

SLA Tier: standard-covered-service

Customer often watches the self-serve usage dashboard closely.

Billing Record

Plan: Committed-200

Invoice Preview: $14,750

Credits Applied: $0

Burst GPU Hours: 12

Invoice preview includes 212 GPU-hours of billable usage.; No pricing config drift detected.

Usage & Telemetry

Window: 2026-03-01 to 2026-03-31

GPU Hours: 186

Meter Status: lagging

Compute path is healthy, but the meter ingestion pipeline is delayed by several hours.

Anomalies: Usage dashboard currently trails internal billable meter by approximately 26 GPU-hours.

Incident Record

Status: no_known_incident

Service: billing-meter-pipeline

Customer Visible: No

Compute services are healthy; only the meter ingestion pipeline is lagging.

Customer Note

The usage dashboard does not match our invoice preview and we cannot reconcile the difference.

Policy Snippet

If usage evidence is incomplete or delayed, hold invoicing changes for finance review and correct the final invoice if needed.

Ground Truth

issue_type: metering_discrepancyroot_cause: usage_metering_errorcustomer_impact: usage_visibility_gapcontractual_applicability: invoice_adjustment_duediscrepancy_detected: truerecommended_owner: shared_revops_financerecommended_action: hold_for_finance_reviewneeds_human_review: trueconfidence: mediumadjudication_notes: ["The customer-facing problem is visibility and invoice reconciliation, not service downtime.","Finance review is needed because the invoice may need adjustment after meter catch-up."]reference_customer_note: We found a lag in the usage meter pipeline, which is why the dashboard and invoice preview do not line up right now. We are holding this for finance review and will correct the final invoice if the adjustment is confirmed.reference_internal_note: Owner: shared_revops_finance. Action: hold_for_finance_review because metering is lagging, compute path is healthy, discrepancy_detected is true, and invoice adjustment may be due.