What is being tested
Were image requests charged at the requested and delivered quality tier? The boundary for this investigation is ai image-generation quality-tier billing. Begin with the disputed transaction or population, then identify which request parameter log establishes the observed position and which output-count record supports the comparison. A difference in totals should not replace this question.
Evidence: request parameter log
For ai image-generation quality-tier billing, request parameter log must be linked to output-count record. Preserve the authorized sender, accepted scope and event timestamp. Distinguish a request from its acceptance and check whether the approver had authority for this change. Later approval should remain visible as a separate event rather than rewrite the original sequence.
Evidence: output-count record
For ai image-generation quality-tier billing, output-count record must be linked to quality price schedule. Document the observation window, units, inclusion criteria and export version. Identify gaps and corrected events before using the total. Keep raw observations separate from derived quantities so a reviewer can reproduce the population without assuming every logged event is independently chargeable.
Evidence: quality price schedule
For ai image-generation quality-tier billing, quality price schedule must be linked to image invoice. Keep the dated calculation basis, eligible units and any limits or exclusions. Record the sequence of conversion, threshold selection and rounding. An arithmetic result is only supportable after its inputs and applicable version are independently confirmed for the transaction being reviewed.
Evidence: image invoice
For ai image-generation quality-tier billing, image invoice must be linked to request parameter log. Keep the issued document version and line-level quantity, currency and service period. A header total cannot establish which component is being tested. Retain later corrections as linked versions, so a replacement does not create a second liability.
Reconciliation logic
Match size, quality and output counts to effective pricing and separate retries that produced usable outputs. Build the comparison at the level identified by request parameter log and retain the governing version from output-count record. Show intermediate classifications and excluded items separately; a net total can hide an unsupported component or a correctly offset correction.
Exception conditions
A request can intentionally return multiple paid images. Treat the item as an unresolved exception only when the comparison described here cannot be supported by the linked request parameter log, output-count record, quality price schedule, image invoice. Document the conflicting input or rule. A plausible operational explanation requires validation, but it should not be discarded to maximize an apparent financial difference.
Human review and outcome
The application owner validates request options and output acceptance. Return a request-tier bridge for finance review. Keep the reviewer's reason and source references with that disposition. A supported correction should be followed to the revised record or settlement; an accepted explanation can close the question with no adjustment. Missing authority or evidence should remain an open task rather than a confirmed recovery.
Limitations and processing boundary
Do not infer license removability from activity alone or describe a proposed configuration change as confirmed savings. The authoritative spend, license and contract producer is not complete; customer evidence and processing validation are prerequisites to production conclusions. In this scenario, absence of request parameter log or output-count record limits whether the comparison can be completed. The review method describes what people should validate, not a promise that AuditRes automatically detects or executes this specific outcome.
AuditRes pathway
Discuss ai image-generation quality-tier billing in the Technology Spend workspace. Review current plans, the shared platform and secure evidence requirements; use the existing contact path to confirm the sources and validation this scope requires.
AuditRes Technology Spend: Available for onboarding. Public previews use synthetic demonstration data; production processing remains gated until applicable customer sources and authoritative processors are connected and validated.
Neighboring financial questions
- Review billed API calls across pagination and export requests
- CI job parallelism concurrency tier
- AI cached-input price classification
- AI embedding refresh versus incremental indexing costs
Technology Spend resource hub · All guides in this evidence collection