AWS: Assigned Credits

As part of our June 18, 2019 deployment, payees can now see the list price value of an AWS credit assigned to them.

These Frequently Asked Questions (FAQs) will attempt to answer the most likely questions you may have about this change.

Question: Will this change impact how CloudCheckr shows my list cost?


Yes. If an AWS credit is assigned to a payee, CloudCheckr will:

  1. Set the list price for the original line to zero.
  2. Write a new line that:
    • converts the AWS credit to a negative custom charge with the same description, service category, and related parameters from AWS.
    • shows a value of $0.00 for unblended costs.
    • sets the list price to value of the assigned credit.

Question: Where will assigned credits appear?


Assigned credits will appear anywhere in the application where list cost is applied. This includes the following reports or functions:

  • Billing dashboard
  • Any custom dashboard where list cost is used
  • Summary reports including consolidated, monthly, daily, and historical
  • Invoicing
  • Advanced Grouping
  • Saved Filters
  • Profit Analysis
  • List Cost Analysis

Question: If an assigned credit is hidden, where can I expect not to see it?


Assigned credits that are hidden will not appear anywhere in the application where list cost is applied.

This includes all of the reports and functions identified in the previous question.

Question: What customers are impacted by this change?


Both payers and payees will see the same results in any report or function that contains list cost.

Question: What billing methods are impacted by this change?


Both the Detailed Billing Report (DBR) and the Cost and Usage Report (CUR) will generate list cost in the manner described in the first FAQ.

Question: Will the Exclude Credits option be available to payees?



Since assigned credits must be visible to payees in the Advanced Grouping report and the payees may have available credits, the option will be available to them.

How did we do?