Document note only. Field Ledger is not a tax firm, cloud reseller, dental office, or insurer. Read your own form and confirm it with the preparer, billing desk, carrier, or another licensed professional.
This side-by-side reference table clarifies log-ingestion and log-storage charge distinctions for regular cloud billing reviews. Both line items appear on most enterprise cloud infrastructure invoices, but they are calculated using separate usage metrics that are often conflated during monthly reconciliation workflows. This page is designed for use with your cloud billing folder, and all figures shown are for illustrative teaching purposes only. Field Ledger does not act as a cloud billing intermediary, and all disputed line items should be escalated directly to your cloud provider’s billing support team.
Field Ledger
Table Column Breakdown of Per-Event Log-Ingestion Charges
The table below maps directly to the line items listed on your monthly cloud observability services invoice, with columns structured to simplify cross-referencing between internal usage tracking and provider billing data. The Line Item ID column matches the 6-digit identifier printed on the first page of your invoice under the “Observability Services” section, allowing for quick lookup of individual charges. The Charge Category column explicitly distinguishes between one-time log-ingestion charges and recurring log-storage charges to eliminate the common confusion of conflating the two metrics. The Usage Metric column defines the unit of measurement used to calculate each charge: log ingestion is measured per GB of uncompressed data transferred to the observability platform at the time of log generation, while log storage is measured per GB of compressed data retained in a specific storage tier per month. The Total Usage Volume column lists the full volume of usage recorded by the provider for the billing period, before any free tier allowances or discounts are applied. The Contracted Per-Unit Rate column reflects the rate agreed to in your signed service agreement, separate from any on-demand pricing listed publicly on the provider’s website. The Pre-Discount Total column shows the calculated charge before free tier credits, committed use discounts, or enterprise agreement adjustments are applied. The Reconciliation Flag column lets you mark line items as matching internal tracking, pending further review, or eligible for dispute. The Annotations column is reserved for notes about discrepancies, overage causes, or support ticket details. All values shown below are for illustrative teaching purposes only and do not represent official cloud provider pricing.
| Line Item ID | Charge Category | Usage Metric | Total Usage Volume | Contracted Per-Unit Rate | Pre-Discount Total | Reconciliation Flag | Annotations |
|---|---|---|---|---|---|---|---|
| 742916 | Log Ingestion | GB uncompressed data ingested | 118.7 GB | $0.50 per GB | $59.35 | Matches Internal Tracking | Regular application log volume, no overages |
| 742917 | Log Storage (Standard Hot) | GB compressed data stored per month | 42.2 GB | $0.023 per GB/month | $0.97 | Matches Internal Tracking | Logs for active application debugging, 30 day retention |
| 742918 | Log Storage (Infrequent Access) | GB compressed data stored per month | 127.9 GB | $0.004 per GB/month | $0.51 | Pending Review | Possible misconfiguration: 40 GB of logs marked for infrequent access appear to be stored in hot tier per internal checks, ticket #CS-12984 submitted 10/12/2024 |
| 742919 | Log Ingestion (Overage) | GB uncompressed data ingested | 22.3 GB | $0.75 per GB | $16.73 | Matches Internal Tracking | Overage from scheduled marketing campaign traffic spike 10/03/2024 to 10/05/2024, pre-approved by devops team |
| 742920 | Log Storage (Cold Archive) | GB compressed data stored per month | 312.4 GB | $0.0007 per GB/month | $0.22 | Matches Internal Tracking | Compliance logs, 7 year retention, no planned access |
Ingestion charges are incurred at the time logs are sent from your cloud resources to the provider’s observability platform, regardless of how long you retain those logs. This means you can incur an ingestion charge even if you delete the logs within 24 hours of ingestion, which is a common point of confusion during reconciliation.
Row Header Box Labels for Log-Storage Tier Pricing Entries
Each row header for log-storage entries explicitly lists the storage tier associated with the charge, allowing for direct cross-referencing with your internal log retention policy. The four standard tier labels included in most enterprise agreements are Standard Hot Storage for logs accessed more than once per week for debugging or performance monitoring, Infrequent Access Storage for logs accessed fewer than once per 30 days for incident post-mortems, Cold Archive Storage for logs retained only for compliance purposes with no regular access expectations, and Deletion Hold Storage for logs subject to legal hold that cannot be deleted even if the contracted retention period has expired. Each row header also includes the retention period associated with that tier, if applicable, so you can cross-check against your policy to ensure you are not retaining logs longer than required. For example, if your internal policy requires 30 day retention for hot storage logs, a row header listing a 90 day retention period for Standard Hot Storage would indicate a misconfiguration that is driving excess storage costs. You can add a custom row to the table for any custom storage tiers you have negotiated as part of your enterprise service agreement, as long as you label the tier clearly in the row header for future reference. Illustrative example: A log group configured for Infrequent Access storage that appears under a Standard Hot Storage row header would be eligible for a billing adjustment request if the misconfiguration is confirmed by your provider.
Monthly Usage Schedule Calculations for Aggregate Charge Totals
To validate the aggregate charge totals listed on your invoice, start by pulling a daily usage schedule export from your provider’s observability console for the full billing period. For log-ingestion charges, sum the daily uncompressed ingestion volume across all log groups to get the total usage volume, subtract any applicable free tier allowances, then multiply by the contracted per-unit rate to get the pre-discount total. For log-storage charges, calculate the average daily compressed storage volume per tier across the billing period to account for logs added or deleted mid-cycle, then multiply by the contracted per-GB per-month rate for that tier to get the pre-discount total. Be sure to account for any free tier allowances included in your service agreement before applying contracted rates, as many providers offer a set amount of free ingestion and storage per month for non-production accounts. After calculating pre-discount totals for all line items, apply any committed use discounts, enterprise agreement credits, or promotional credits to arrive at the final billed total, which should match the total listed on your invoice. Illustrative example: If your service agreement includes 50 GB of free ingestion per month, you would subtract that 50 GB from your total 120 GB ingestion volume before multiplying by the per-unit rate to calculate your charge.
Line Item Note Annotations for Overage Charge Adjustment Entries
Any line items marked as pending review or eligible for dispute should include detailed annotations to support follow-up with your provider or internal finance team. Annotations should include the root cause of any discrepancy (e.g., unexpected traffic spike, misconfigured log verbosity settings, unapproved storage tier change), the date the discrepancy was identified, the full support ticket number submitted to your provider if applicable, the expected adjustment amount, and the name of the team member responsible for resolving the issue. If you receive a billing adjustment from your provider for a disputed line item, add the adjustment amount and the date the adjustment was applied to the annotation for that row, and retain a copy of the adjustment confirmation in your supporting documentation folder. All annotations should be written in clear, specific language that can be understood by team members who were not involved in the initial reconciliation process, to avoid confusion during future audits. Note that Field Ledger does not provide tax advice, and you should consult a licensed tax professional regarding the deductibility of any cloud service charges.
Cross-Reference Folder Links to Supporting Usage Log Documentation
Each line item in the table should include a relative link to supporting documentation stored in your cloud billing folder, to streamline audit reviews and dispute resolution. Required supporting documents include a CSV export of your daily usage metrics from the cloud provider’s observability console for the full billing period, a signed copy of your service agreement showing contracted per-unit rates for all ingestion and storage tiers, a copy of your internal log retention policy to confirm tier assignments are aligned with internal requirements, all support ticket correspondence with your provider regarding disputed charges or adjustments, and your monthly cost allocation report showing how charges are split across departments or business units. You can also add links to your internal cost forecasting spreadsheet and any third-party cloud cost management tool dashboards for the billing period as additional cross-references. All supporting documents should be named using a consistent naming convention that includes the billing period and document type, e.g., “2024-10_cloud_usage_export.csv” or “2024-10_log_retention_policy.pdf”, to make them easy to locate when needed.
Next action: Print a copy of the completed table and attach it to the front of your cloud invoice folder before submitting your monthly billing reconciliation report to your finance team.