Avoid double-counting cloud network charges

NETWORK CHARGE RECONCILIATION

SCOPE AND INPUTS
[ ] Record the provider, account scope, closed invoice period, currency and tax treatment. Keep a separate review for each provider and currency.
[ ] Obtain read-only billing records and invoice documents from an authorized billing colleague, plus a traffic-path map from a network engineer. Do not change exports or resources.
[ ] Record each input file or table and the period it covers. Preserve original records so review notes can be traced to their source.

1. VERIFY COVERAGE
[ ] Confirm that inputs cover the full selected invoice period. If they do not, label the subtotal partial and request complete records before reconciling it.
[ ] For Google Cloud regional exports, check when export began and whether it was disabled. Data is available from enablement, and disabled intervals might be missing.
[ ] Use the invoice period, not only usage dates. Google Cloud invoice month can differ from usage month.

2. KEEP DOCUMENTED DETAILS INTACT
[ ] AWS: keep product/dataTransfer, product/fromRegionCode and product/usagetype when present. Product columns are dynamic, so an absent column is not proof of zero cost.
[ ] Azure: use CostInBillingCurrency for the charge in the billing currency when that field applies to the account type. Treat every cost-details record as unique.
[ ] Google Cloud: retain sku.id, sku.description, cost, currency and adjustment_info when present. Do not assume a missing field means zero cost.
[ ] Record usage units exactly as reported. Do not treat GB and GiB as equal or add unlike units.

3. SEPARATE IMPORT DUPLICATION FROM SERVICE CHARGES
[ ] Check whether the same source records were included more than once in the working report. Exclude only confirmed repeated imports from the report, not from source data.
[ ] For each network line, record the charged service or function, traffic direction, locations, project or account, reported units and what traffic is measured. Mark unknowns for engineering review.
[ ] Keep distinct service fees even when their traffic volumes match. Google Cloud Armor Enterprise processing and Cloud Load Balancing processing are separate fees.
[ ] Ask the engineer to confirm which charges belong to the same path. Do not infer a duplicate from matching bytes, cost or descriptions alone.

4. RECONCILE WITHOUT HIDING CHANGES
[ ] Keep charges, credits, taxes, corrections and rounding adjustments visible as separate reconciliation components.
[ ] For Google Cloud corrections, retain both the negating line and the replacement line, and retain their adjustment_info values when present. Corrections can appear on a later invoice for earlier usage.
[ ] For Azure, include applicable invoice-level rounding adjustments when reconciling the complete invoice scope. Do not assign the whole adjustment to a network subset.
[ ] Reconcile complete-scope totals to the invoice with credits, taxes and adjustments accounted for. Show the network subtotal separately; do not compare it directly with the whole invoice total.
[ ] Record each unresolved difference, its source records and the colleague responsible for resolving it. Do not force a match by deleting unexplained lines.