Quick answer

A streaming bandwidth billing audit matches each invoice line to the same resource, usage type, geography, unit, period and contracted price. Reconstruct transfer, processing, storage and connected-session usage separately. Approve explained charges, investigate material unexplained differences and assign technical and finance owners. Missing logs qualify the conclusion; they do not prove overbilling or change payment terms.

Start the streaming bandwidth billing audit with a decision

The invoice shows more delivery than the platform dashboard, yet appointments and receipts look normal. Before approving it, trace each charge from recorded activity through the contracted billable unit to the amount due. A dashboard mismatch is a reason to reconcile; it is not a verdict.

Bandwidth here means billed transfer, rather than network speed. Check it separately from processing, storage and connected-session usage. A graph in Mbps cannot validate GB. Origin transfer and viewer delivery can be distinct services, even when both support the same broadcast.

Collect the invoice, effective agreement, usage exports, production/test resource map and existing application, request, job and storage records. Finance supplies payment and dispute deadlines; engineering assigns resource owners. This verifies consumption. How Much It Costs to Start a Streaming Service instead addresses future workload costs.

Two thick, separately clipped document stacks with colored page tabs rest on a finance counter in natural light, with all printed text out of focus.

Build the usage-to-invoice worksheet

Use one worksheet row per invoice line and matched consumption group. Split calculations when geography, rates or usage types differ. The following six grouped fields keep the decision reproducible without turning a founder into a cloud billing specialist.

  1. Matched scope: invoice and line reference, supplier/account, service and usage type, resource/environment, geography, charge start inclusive and end exclusive, and timezone.
  2. Contract basis: agreement version and effective dates, rate or tier calculation, unit and conversion divisor, rounding, minimums, discounts and credits applicable to that line.
  3. Quantity comparison: billed quantity, reconstructed quantity, signed difference and percentage against reconstructed quantity. When reconstruction is zero, record the absolute difference instead.
  4. Amount comparison: invoiced charge, expected contracted charge after documented adjustments, and signed unexplained difference. Keep taxes and unrelated fees separate.
  5. Evidence: original export and calculation locations, extraction time, independent application corroboration, coverage gaps and any estimates. Preserve originals and calculate in a separate copy.
  6. Decision and ownership: technical owner, finance approver, payment and dispute deadlines, supplier case reference, status, dated rationale and matched correction or credit reference.

Consider an illustrative coaching platform; all example quantities, rates, dates, thresholds and outcomes are hypothetical. The period runs from November 1, 2026 at 00:00 to December 1 at 00:00 UTC, end exclusive. Delivery has one geography and matched production resource. The agreement uses decimal GB without rounding or minimums. Taxes, unrelated services and initial adjustments are excluded. Normal appointments tempt the operator to approve.

Invoice lineBilled quantityReconstructed quantityContract rateInvoicedInitially supported
Delivery12,000 GB11,000 GB$0.05/GB$600$550
Transcoding4,000 normalized minutes4,000 normalized minutes$0.02/minute$80$80
Storage500 GB-months500 GB-months$0.02/GB-month$10$10
Video20,000 participant-minutes20,000 participant-minutes$0.004/minute$80$80
TotalSeparate unitsSeparate unitsLine-specific$770$720
Illustrative invoice and initially supported consumption, before tax

Quantity difference is billed minus reconstructed; divide by reconstructed quantity and multiply by 100 for percentage variance. Unexplained money is invoiced minus expected charge after adjustments. Preserve signs: negative differences also need explanation. Only money shares a unit across these lines; never total GB and minutes.

Delivery differs by +1,000 GB, approximately +9.09%, leaving +$50 unexplained. Other lines reconcile. This is a supplier question, not savings yet. Assign the engineering lead and finance approver, with illustrative December 10 dispute and December 15 payment deadlines. Record locations and extraction times for invoice.csv, usage.csv and transfer-calculation.csv; request-log completeness remains unestablished.

An operations lead sorts usage printouts into four open folders at a counter, with archive boxes on metal shelves behind her.

Reconstruct each meter on its own terms

Start by matching what the supplier measured, rather than forcing every charge to agree with viewer counts. Transfer, output processing, storage held over time and connected participants have different evidence trails. A rising invoice can accurately describe extra work that the customer dashboard never counted.

For CloudFront, obtain billing CSV through Bills: select the period, expand CloudFront under Charges by service, then Download all to CSV. For usage, use Cost Explorer: set dates and granularity, filter Service to CloudFront and download CSV under Cost and usage breakdown. Match distribution, direction, geography, usage type and interval. Reconcile origin transfer separately, including attribution where the origin serves other workloads.

Confirm the contractual divisor: decimal GB is 1,000,000,000 bytes; GiB is 1,073,741,824. A GB label alone does not settle the rule. The example’s decimal divisor converts 11,000,000,000,000 bytes into 11,000 GB. Compare both quantities in that contractual unit.

CloudFront logs record response bytes including headers, separately from incoming bytes. Use bytes sent, not nominal object size. Compare usage exports and logs with independent application activity. Agreement between provider reports is corroboration, not independent confirmation. Best-effort logs can be delayed or missing; a shortfall cannot prove overbilling. If matched traffic and pricing explain a spike, approve the higher invoice and pass efficiency questions to engineering.

Deduplicate evidence copies, retaining genuine attempts. Illustratively, 2 MB sent before abandonment plus a distinct 6 MB retry means 8 MB observed. Importing the retry twice creates no extra consumption. Preserve event and attempt identity, quantity and timestamps; a shared path or user cannot establish duplication. Failed requests may have delivered bytes.

Normalize timezones, search adjacent periods and prevent double inclusion. Apply the supplier’s boundary rule. CloudFront timestamps mark response completion or WebSocket closure; they cannot justify dividing connection bytes between months by elapsed time. Missing attribution rules leave a named exception requiring supplier explanation.

Reconcile job attempts and outputs by duration, settings, region and failure status using contractual factors and rounding. MediaConvert normalized minutes combine output duration and features. Illustratively, a 60-minute source with two 60-minute outputs, factors 1 and 2, yields 60 × 1 + 60 × 2 = 180 normalized minutes. Extra outputs or separately submitted jobs explain growth despite stable viewers. Distinguish real repeat work from proven double charging. Missing factors or failed-job rules require an account-specific explanation.

Reconstruct storage held over time by resource and class from dated creation, deletion, version and transition records. Illustratively, under a 720-hour convention, 1,000 GB for 360 hours and 2,000 GB for 360 hours yield (1,000 × 360 + 2,000 × 360) / 720 = 1,500 GB-months. Closing inventory misstates this basis; snapshots remain estimates. Separate requests, retrieval, transfer and applicable minimum-duration or early-deletion charges from ordinary storage.

Session minutes can mean appointments, paid time, room duration or participant time. Twilio Video bills connected participant-minutes, including partial minutes, with recordings and compositions separate. Illustratively, two participants connected for 30 whole minutes produce 60 participant-minutes. Compare application events with provider connection times and final duration after disconnection. Include disconnected participants, all result pages and rooms overlapping the period. Track still-connected participants separately; preserve distinct connections and obtain actual reconnect and fractional-minute rules.

Paid minutes describe what the customer bought, not each participant’s connected time. For receipts or settlement mismatches, streaming payment reconciliation follows the money separately from this consumption audit.

Clipped stacks of job records and inventory sheets sit beside a plain calculator on a worn archive worktop in strong daylight.

Resolve exceptions before the deadline

Set investigation thresholds before seeing the results. For this illustrative operator policy, investigate an absolute unexplained amount above $25 or an absolute quantity variance above 2%. Always investigate suspected duplicates, unknown resources, wrong rates and missing consumption categories, regardless of size.

Thresholds prioritize investigation; they do not certify smaller differences. Percentages use reconstructed quantity; zero reconstruction requires an absolute difference. Compare service, consumption, interval and quantity before declaring duplication, excluding legitimate corrections. Repeated resource names prove little.

  1. Preserve original invoices and exports, then map every line to a resource, environment and technical owner.
  2. Normalize units and charge boundaries, reconstruct each meter and calculate charges under the effective agreement and adjustments.
  3. Open exceptions with the matched evidence and its limitations. Engineering owns consumption reconstruction; finance owns rates, adjustments, deadlines and payment. Operations coordinates unresolved cross-team cases.
  4. Obtain the supplier’s response, test its breakdown against the worksheet, and record approval or a matched correction. Keep unresolved cases open with an explicit finance payment decision.

Finance sends: “For the November delivery line, 12,000 GB were billed and our matched reconstruction supports 11,000 GB at $0.05/GB, leaving $50 unexplained. Attached are the resource, region, UTC period, rate reference and calculation. Request-log completeness is not established. Please provide the metering breakdown or correct the charge.” Include invoice/line references, billed and expected amounts, event evidence and the dispute deadline.

Before the illustrative December 10 deadline, the supplier confirms 1,000 GB duplicated and posts a $50 credit against this invoice. Finance matches it once and approves $720 before December 15. Legitimate omitted traffic would support $770 instead. Without resolution, keep the exception open with an explicit finance payment decision. A case or withheld accuracy sign-off does not suspend payment or authorize deduction.

With incomplete history, reconcile available usage and agreement, flag unsupported attribution and request supplier evidence. Do not manufacture records. Assign engineering to retain request, connection, job and storage-change evidence from next period’s start, with resource references and timestamps. Finance reruns the worksheet; the current decision remains qualified.

Illustratively, two engineering hours at loaded $60/hour plus one finance hour at $40/hour allocate $160 of staff cost. A $50 credit alone does not prove positive return. Salaried time need not create cash expense; contractor work can. Credit against this invoice reduces this payment; later credit and cash refund have different timing.

Close frontal photograph of a monitor showing an indistinct spreadsheet beside a document preview, with one row selected and paperclip icons.

Carry the evidence requirement into your platform inquiry

An audit becomes repeatable when application activity can be matched to supplier usage. Before accepting a platform’s suitability, ask for a sample record set that supports those matches or a written scope identifying the missing records and required development.

Bring the completed worksheet to the platform discussion, together with a redacted invoice and usage export. Test whether the sample links the billed resource, consumption type and interval to the relevant application activity. A claim that reporting is available is too broad to answer this question. Check coverage and retention as well as whether records can be matched; a usable sample makes the next decision concrete.

Wide consultation studio with two chairs, a wired microphone, tripod camera, compact equipment rack, and a technician tracing a floor cable.

Ask for evidence you can actually match

Scrile Stream offers branded private and group streaming with customization and hosting support. Use the Scrile Stream project inquiry to share a redacted invoice, usage export and worksheet. Ask the team to demonstrate or scope the application-to-provider records, timestamps and retention needed for reconciliation. Request a joinable sample or written customization scope; native invoice auditing and particular export fields should not be assumed.

Frequently asked questions

Is a bandwidth audit the same as payment reconciliation?

No. It checks supplier consumption and contracted charges. Payment reconciliation checks customer receipts, settlements and related money movements.

Can matching provider reports prove usage is correct?

They corroborate the provider’s account of usage. Independent application records add a separate comparison; agreement between provider reports is not independent confirmation.

Should I delete failed requests from the transfer calculation?

No. A failed or abandoned response may already have sent bytes. Retain measured consumption and apply the supplier’s charging rule.

Does a repeated resource name prove a duplicate charge?

No. The same resource can incur distinct service charges or genuine retries. Establish repeated charging for the same consumption before calling it a billing error.

What if reconstructed usage is zero?

Record the absolute quantity and monetary difference instead of a percentage. Check missing evidence and unknown resources before deciding what caused it.

Can I use closing storage inventory to validate the month?

Closing inventory does not capture how much was stored throughout the period. Use dated changes and the contracted time convention; snapshots provide an estimate.

Does opening a dispute let finance reduce payment?

A dispute does not itself change payment terms. Finance must record payment handling under the applicable agreement while the accuracy exception remains open.

What should close an invoice exception?

Matched supporting evidence, a corrected invoice or a posted credit linked to the original exception. An unanswered supplier ticket is not closure.