Historic usage and adjustments

This topic is about Metered usage V2. Marketplaces use the Metered usage V1 API, Metered usage V2 API, or both, to support metered usage billing. See also: Metered usage V1.

Usage can be submitted retroactively to correct usage for billing periods that are already invoiced except for usage for products configured for volume pricing. Every usage event is submitted with an associated date, so adjustments are allocated to the correct historic billing period and invoiced accordingly. Missed usage can be submitted, and over-reported usage corrected, as illustrated with the following examples:

Missed usage (positive adjustment) example:

• In January, 100 gigabytes (GB) are reported, and an additional 50 are used but not reported.
• An order for 100 GB is generated.
• An invoice is generated for the January billing period.
• In March, you report the additional 50 gigabytes with a January event date to correct the error.
• An order for 100 GB + 50 GB - 100 GB is generated.
• The additional charge for the January billing period is added to the next invoice.

Over-reported usage (negative adjustment) example:

• In January, 200 gigabytes (GB) are reported, which overstated actual usage by 50 GB.
• An order for 200 GB is generated.
• An invoice is generated for the January billing period.
• In March, you report -50 gigabytes with a January event date to correct the error.
• An order for 200 GB - 50 GB - 200 GB is generated.
• The negative charge for the January billing period is added to the next invoice.

When negative-value corrections result in negative-value invoices, the invoices are delegated to the next billing period, as are all negative-value invoices (see Delegated invoices).

Important notes

Avoid usage and invoice adjustments: We recommend that delayed invoicing is enabled for usage products. See Delayed invoicing recommendation.

Volume pricing: You cannot submit historic adjustments for volume pricing usage.

Tiered pricing: Metered usage V2 is currently in Early Availability status and does not yet support tiered pricing. However, note that historic adjustments will not be supported for tiered pricing.