Reconcile Compute usage and statements
How to trace a statement line back to the job behind it, and what to do when a billing record is missing or conflicts.
Trace one job through the records
Start with the selected account, the job or batch reference and its signed quote. Follow that work through the commercial records:
confirmed credit purchase → paid purchase invoice
|
job or batch + approved signed quote + credit hold
|
usage observation
|
accepted usage
|
credit consumption + release of unused hold
|
monthly credit and usage statement (amount due: zero)A usage observation records activity. Accepted usage records recognized work under its acceptance policy. Accepted prepaid usage consumes the original credit hold once. The monthly statement summarizes the period with zero further amount due; the paid purchase invoice records the earlier credit purchase. Historical invoices retain their own terms. These are related records, not independent charges to add together.
Open the account's Usage and Billing areas with your assigned permissions; do not borrow a work agent's identity for a billing action.
Compute statements use the same two customer rates throughout the period: USD 0.05 per 1,000,000 input tokens and USD 0.10 per 1,000,000 output tokens. They show accepted token quantities by service or operation; physical attempts and provider token counters are separate measurements.
Physical Mac attempts are not customer billing units. Several attempts may exist for one logical task; a retry, hedge, rejected attempt or duplicate dispatch does not become another accepted customer unit merely because another Mac tried the work.
Review one job first
Find the job and its final or partial outcome. Compare the input and requested outputs with the quote, then identify the accepted quantity, billing unit, price version and any recorded adjustment. Keep useful work separate from failed, missing or disputed outcomes. Download or delivery problems do not by themselves establish that inference must run again.
| Record | Compare | Do not assume |
|---|---|---|
| Quote | Work identity, unit, expected charge, maximum and expiry. | A quote is an invoice or authorization to run. |
| Usage observation | Quantity, unit, period and observation freshness. | Every counter is a customer charge. |
| Accepted usage | Accepted work under the quoted acceptance policy, token quantities, applicable rate and associated evidence. | Every physical attempt creates another accepted customer unit. |
| Statement | Account, period, opening credit, purchases, accepted usage, releases, adjustments and closing credit; prepaid amount due is zero. | The statement creates another payable. |
| Purchase invoice | Purchase reference, invoice number, currency, subtotal, tax, total and confirmed payment. | An accounting-system annotation proves payment or issued credit. |
The Usage view can return only a bounded window. Read any partial or stale indication and use available continuation controls before treating the result as complete. A list with no visible entries can mean no entries in that window; an unavailable read is not evidence of no usage. Do not extrapolate a monthly bill from the latest activity count.
Reconcile a period
Use the same account, currency and period boundaries for every comparison. Match accepted usage to its credit consumption and statement. Match purchases to their paid invoice references, including purchases made in an earlier period whose credit is used now. Keep the original document identity and version in your reconciliation notes. Use an export's declared schema and included formats.
Check that opening credit, purchases, accepted consumption, releases and recorded adjustments explain closing credit. A hold moves credit out of the available amount; releasing it restores availability without creating another purchase. Tax on a purchase invoice remains separate from spendable credit. A pending adjustment is not posted credit, and restored credit is not proof of a cash refund.
Recover a missing or different total
If the statement or invoice cannot be read, keep the job and period references and ask billing support for the authoritative record. Do not create a replacement payable from a screenshot of counters. If two exports differ, compare their versions, periods, included lines and observation times before choosing one; preserve both references while the discrepancy is resolved.
For a suspected duplicate, identify the original logical work and the repeated record. A deliberate new request is different from a transport replay. For cancellation, keep accepted work separate from remaining canceled or unresolved work and compare the terminal record with the charging policy. Do not turn a local timeout into a zero-charge conclusion.
You are finished when the accepted work and credit movements explain the period's statement, and each purchase matches its paid invoice. Record any unexplained difference for review. Use adjustments and disputes for a charge you contest and invoices and payment for purchase and payment recovery.