When reviewing charges in Billing Manager, you might notice that a recurring storage charge expected for a specific month does not appear when filtering for that month. Instead, the charge may be listed under the previous month. This is expected system behavior and is related to how timestamps and timezones are handled.

How Recurring Storage charges are recorded

Recurring storage charges are created using a standardized process:

• Charges are generated at 12:00 AM (00:00) on the first day of the month in UTC
• Billing data is displayed and filtered based on your local timezone

Because of this timezone conversion, customers located in timezones behind UTC (such as PST, CST, or UTC‑3) may see the charge reflected on the prior calendar day when viewed locally.

Example Scenario

Charge created: March 1 at 12:00 AM (UTC)
Local time (UTC‑3): February 28 at 9:00 PM

Although the charge is technically created for March, it appears as a February charge when viewed in local time.

Why the charge may not appear in the expected month

When you filter billing data by month:

• The system uses local dates, not UTC
• If the charge falls on the last day of the previous month locally, it will:
  • Be excluded from the current month’s filter
  • Appear when filtering for the previous month instead

Best practices for reviewing monthly charges

To ensure you see all expected recurring storage charges:

• Remember that charges are not missing—they are displayed based on timezone‑adjusted timestamps
• When reviewing a specific month:
  • Include the last day of the previous month in your filters, or
  • Use a broader date range that spans month boundaries