Marketplace purchases
The Marketplace purchases page lets you review upfront marketplace purchases discovered from your AWS, Google Cloud, and Azure billing data and configure a recognition period for each one. Instead of showing the full purchase amount on a single charge date, the recognized cost is spread across calendar months over the period you specify. The adjusted amounts appear in reports that use the Amortized Cost metric.
This feature is available to selected early access customers. It currently supports AWS, Google Cloud, and Azure Actual Cost marketplace purchases in standard billing reports. Forecasts, FOCUS reports, and partner reports are not supported. Azure FOCUS and DCI billing sources and OCI purchases are excluded.
Required permissions
-
To view purchases: Cloud Analytics User or higher
-
To configure recognition periods, save drafts, apply schedules, or change default settings: Cloud Analytics Admin
-
To refresh purchase discovery: Cloud Analytics Admin
-
To apply a recognition period to reports: access to the Amortized Cost extended metric (requires the Amortized Cost entitlement)
Your account must have access to the full customer billing scope. Users restricted to a subset of billing data cannot use this page.
Open the Marketplace purchases page
Sign in to the DoiT console, select Reporting and analytics from the top navigation bar, and then select Marketplace purchases.
The page displays a table of marketplace purchases imported from your billing data. Each row shows the product name, cloud provider (AWS, Google Cloud, or Azure), charge date, purchase amount, and current recognition status. You can filter by product, provider, or billing account. Loaded purchases are sorted by amount from largest to smallest, with the latest charge date first when amounts match. Select Load more purchases to include additional purchases in the table and its filters.
Automatic purchase discovery
The DoiT platform automatically discovers marketplace purchases from your registered AWS, Google Cloud, and Azure Actual Cost billing exports. Daily discovery checks the current month plus the preceding 12 months and adds new purchases to the table. Previously discovered purchases are also rechecked for billing changes. No additional marketplace API permissions are required.
Opening the page as an administrator starts or resumes discovery when needed. A recent completed discovery is reused, so opening the page does not always start a new scan. Discovery does not apply recognition periods to reports.
A status banner at the top of the page shows the current state of discovery:
-
Checking billing discovery status…: The page is loading the discovery state.
-
Billing discovery has not run yet: Discovery has not started. An administrator can start it from this page.
-
Checking supported billing data: Discovery is in progress. The banner shows how many billing checks have completed out of the total.
-
Supported billing checked: Discovery finished successfully. The banner shows the date range that was scanned.
-
Billing discovery is incomplete: Some billing sources could not be fully scanned. Purchases may be missing. You can retry after a few minutes.
-
Could not check billing discovery: Discovery encountered an error. The purchase list may be incomplete.
-
No supported AWS, Google Cloud or Azure Actual Cost billing tables are registered: No billing exports are available for discovery. Check that your cloud account is connected and supported billing data has been imported.
Refresh purchases
Administrators can manually trigger discovery by selecting Refresh purchases in the status banner. This button is available when discovery is idle, incomplete, or encountered an error. Users with the Cloud Analytics User role can view the discovery status but cannot start or refresh a discovery run.
Eligible purchases
Not all marketplace charges appear on the Marketplace purchases page. The platform uses billing descriptions and charge types to identify potential upfront purchases. Charges with clear evidence of ongoing consumption or monthly billing are excluded. A product appearing in the table still requires your confirmation that it is an upfront purchase.
Examples of excluded charges include:
- Metered usage charges (AWS and Azure Usage line items)
- AI token and CCU-based billing (for example, Anthropic Claude consumption units)
- Time-metered licenses billed per second, minute, or hour
- Monthly subscription fees that are not part of an annual or multi-year contract
- Zero-cost AI model enrollments
Descriptions that indicate an upfront, prepaid, annual, multi-year, or installment commitment are retained for review when supported by the billing data. A vendor name alone does not cause exclusion. Repeated charges with the same amount are not excluded solely because they recur monthly; they may be installments of a longer commitment. Previously configured purchases can remain visible for review or removal even if their billing evidence no longer qualifies.
Recognition statuses
Each purchase shows one of the following statuses in the Recognition column:
-
As billed: No recognition period is applied. Existing billing and reporting behavior is unchanged.
-
Draft: A recognition period has been saved but not yet applied to reports.
-
Applied: A recognition period is active. Amortized Cost reports reflect the spread cost.
-
Needs review: Billing data changed, is missing, or does not provide sufficient evidence for recognition. Review the purchase and resolve the billing issue before generating a new preview. You can still remove an existing schedule.
Configure a recognition period
-
On the Marketplace purchases page, locate the purchase you want to configure.
-
Select Configure (or Edit period if a schedule is already applied).
-
In the Recognition period dialog, set the Start date and End date (inclusive) for the period over which you want to spread the purchase cost.
The period can range from one day to 120 months. Dates are in UTC. For a new purchase, the suggested period starts on the charge date and uses your default number of months. Verify these dates against your contract and recognition policy; the suggestion does not identify the actual contract term.
-
Select the confirmation checkbox to confirm the purchase is an upfront charge and the dates match your intended recognition period.
-
Select Preview monthly costs to see how the charge is allocated across months.
The charge is spread across calendar months, with partial months prorated by the number of days within the period.
-
After reviewing the preview, choose one of the following:
-
Save draft: Saves the recognition period without applying it to reports. You can return later to preview and apply.
-
Apply to reports: Publishes the recognition period for Amortized Cost reports. Refresh or rerun your report to see the updated amounts without waiting for billing recalculation.
-
During early access, you can have up to 20 applied recognition periods per customer. You must generate a fresh preview before you can select Apply to reports. If you change the start or end date after previewing, select Preview monthly costs again before applying.
Azure baseline behavior
When you configure an Azure marketplace purchase, the editor displays an informational note about how amortization works for Azure. While an Azure schedule is active, the Amortized Cost metric starts from the Azure Cost baseline and spreads your configured purchases over the recognition period. Azure reservation and savings-plan amortization is not available on this billing source. Removing all Azure schedules restores the previous reporting behavior.
Remove a recognition period
To remove an active recognition period and restore the purchase to its original billing recognition:
-
On the Marketplace purchases page, select Edit period next to the purchase.
-
In the Recognition period dialog, select the checkbox to confirm that you want to restore the original recognition.
-
Select Remove amortization.
Refresh or rerun your reports to see the original metric behavior for this purchase.
Set a default recognition period
The default recognition period determines the initial end date suggested when you configure a new purchase. Changing it does not affect existing schedules or drafts.
-
On the Marketplace purchases page, select the Default recognition period button in the page header.
-
In the dialog, enter the number of months in the Months field.
-
Select Save default.
You can set a value between 1 and 120 months. The default is 12 months.
How marketplace recognition affects reports
Applied recognition periods affect supported reports and dashboard widgets using Amortized Cost the next time they refresh or run. Publishing a period does not require billing recalculation; report queries still take their normal time to complete. Discovery, previews, drafts, and default settings do not change report values. The Cost metric and the original billed charges remain unchanged.
Applying a recognition period also creates a report annotation at the start date, at 00:00 UTC, labeled marketplace-amortization. Its message identifies the purchase and the year recognition starts. Select View purchase on the annotation to open its recognition period. Editing an applied period updates the same annotation; removing amortization removes it. Existing applied purchases receive annotations when discovery next starts.
To show these markers, open Manage annotations display on a report and choose Show annotations with specific labels, then select marketplace-amortization. Alternatively, assign the label to your report and choose Show annotations matching report labels. These display settings select annotations; they do not filter billing costs. Generated annotations are customer-wide and also appear when Show all annotations is selected.
For AWS, marketplace recognition adjusts the existing Amortized Cost baseline, preserving native reservation and savings-plan amortization. For Google Cloud, Amortized Cost starts from the reporting Cost baseline and applies your marketplace recognition periods. This feature does not add amortization for Google Cloud committed use discounts. Azure Actual Cost uses the Azure baseline behavior described above.
If billing data changes after a period is applied, reports can return an error until the purchase is reviewed, rather than use an outdated allocation. Refresh purchase discovery and review affected purchases before applying a new preview or removing the period.
Removing a recognition period restores the original metric behavior. Applied periods persist if early access is later disabled, so remove any periods you no longer want before access is withdrawn.