InfraResolution Bench

Case Explorer

Invoice preview mismatch with weak operational noise

Invoice confusion is the clearest customer-facing problem, while a brief operational note adds noise without resolving whether a commercial adjustment is due.

Evidence Packet

CRM Record

Account: Signal Harbor

Tier: enterprise

Plan: Committed-180

Billing Owner: finance@prime.example

SLA Tier: enterprise-standard

Customer is focused on an invoice preview that looks materially higher than expected.; No prior pricing-config mismatch on record.

Billing Record

Plan: Committed-180

Invoice Preview: $15,480

Credits Applied: $0

Burst GPU Hours: 18

Invoice preview shows burst usage above commitment.; Dashboard explanation for the burst line items is incomplete.

Usage & Telemetry

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

GPU Hours: 198

Meter Status: healthy

A short degraded-performance notice overlapped with the billing complaint, but usage stayed largely stable.

Anomalies: Customer-facing invoice explanation did not reconcile to burst line items.

Incident Record

Status: resolved

Service: managed-training-api

Duration: 8m

Customer Visible: Yes

Brief slowdown reported, but customer mainly complained about billing.

Minor capacity pressure was observed but resolved quickly and did not cross breach thresholds.

Customer Note

The invoice preview is much higher than we expected, and we also noticed a brief slowdown earlier that day. Please explain whether either of these changed what we owe.

Policy Snippet

Commercial review should confirm whether pricing explanation gaps reflect a true discrepancy before applying invoice adjustments. Short degradations below SLA thresholds do not automatically trigger credits.

Ground Truth

issue_type: ambiguous_caseroot_cause: unknown_root_causecustomer_impact: invoice_confusioncontractual_applicability: not_an_sla_casediscrepancy_detected: truerecommended_owner: shared_revops_financerecommended_action: hold_for_finance_reviewneeds_human_review: trueconfidence: lowadjudication_notes: ["The billing signal is stronger than the operational signal, but the packet does not justify a final invoice adjustment decision.","The short degradation should not dominate routing."]reference_customer_note: We found an unresolved mismatch between the invoice preview and the explanation available in the current billing records, so we are routing this for finance review before giving you a final answer. At this stage, we are not treating it as an SLA credit case.reference_internal_note: Owner: shared_revops_finance. Action: hold_for_finance_review because the strongest unresolved signal is invoice_confusion, root cause is still unknown, and the brief operational note does not support a breach finding.