Menu
Amazon DevPay
Developer Guide (API Version 2007-12-01)

Revenue Report

The purpose of the revenue report is to help you understand the revenue you've received from each individual customer, across all your DevPay products (if you have multiple ones). You can use this report to determine who your customers are, which customers haven't paid their bills, and the difference between what a customer paid and the corresponding AWS costs you paid.

The report is available in comma-separated value (CSV) format on or around the fifteenth day of each month. We don't generate a revenue report if you don't have any customers yet.

The report covers revenue from all your customers' activity during the previous month. Each row in the report lists the revenue and costs associated with an individual customer's use of a single DevPay product. The report includes subscribed customers even if they didn't use the product during the previous month.

Keep in mind that if your product has a monthly charge, we bill your customers for that on the first day of the month, along with the charges for their usage the previous month. This means that the revenue for the monthly charge appears in the next month's report. For example, the report you receive on January 15 includes revenue for your customers' usage in December. However, the monthly charges to cover January (which we bill customers for on January 1) appear in the February 15 report.

If a customer cancels and then resubscribes to your product in the same month, we present the revenue from each subscription period separately in that month's report. For example, if the customer cancels on January 10 and then resubscribes on January 20, the report you receive in February has one row for the revenue for January 1 to January 10, and a separate row for the revenue for January 20 to January 31. The value in the Customer Since field for the second subscription period will be January 20.

Important

The revenue report includes sensitive customer information such as the customer's name and e-mail address. Make sure to take the necessary precautions to keep the information safe. For more information, go to the Limits on Your Use of Information section in the Amazon Payments User Agreement.

To view the revenue report

  1. Go to your DevPay Activity page at http://aws.amazon.com/devpayactivity.

  2. Click View Customer Reports in the table for any of your products.

    The DevPay Customer Reports page is displayed.

  3. In the Customer Revenue and Usage Reports section of the page, select the time period for the report, click Revenue, and click Download Report.

    You're prompted to save the CSV report to the location of your choice.

The following table describes each of the columns presented in the report in the order they appear. All values in the report (except column names) are enclosed in quotation marks.

Column Name Description

Customer Email

The customer's e-mail address.

Type: String with 64 characters maximum length

Example: john@example.com

Customer Name

The customer's first and last name.

Type: String with 150 characters maximum length

Example: John Smith

Postal Code

The postal code from the customer's billing address. For U.S. ZIP codes, only the five basic digits are included.

Type: String with 32 characters maximum length

Example: 98144

Country Code

The ISO country code for the country in the customer's billing address. For a list of the ISO country codes, go to the ISO web site.

Type: String with 2 characters maximum length

Example: US

Billing Period

The billing month the report covers.

Type: Date with format MMM-YYYY

Example: DEC-2007

Application

The name of the DevPay product (important if you have multiple DevPay products).

Type: String with 80 characters maximum length

Example: My Application

Customer Status

The status of the customer on the day the report is generated. Note that you can programmatically determine at any time whether a customer is active or canceled. For more information, see Verifying the Customer's Subscription Status.

Type: String with 32 characters maximum length

Valid values: Active | Activation Pending | Cancelled

Activation Pending means that the customer's payment at sign-up has not yet cleared. Customers with this status are not actually signed up for the product yet; however, in this report we display the revenue from the sign-up charge that we are attempting to collect.

Customer Since

The date the customer signed up for the product (and if the product has up-front fees at sign-up, this is the date the customer's sign-up payment succeeded). If the customer's status is Activation Pending, this field is empty. For information about what this field displays if a customer cancels and then resubscribes in the same month, see the paragraphs preceding this table.

Type: Date with format DD-MMM-YY

Example: 12-DEC-07

Cancellation Date

The date the customer canceled use of the product. If the customer hasn't canceled, this field is empty.

Type: Date with format DD-MMM-YY

Example: 15-DEC-07

Revenue Billed

The amount we billed the customer for the product during the previous month (including applicable sign-up and usage charges), regardless of whether the customer has subsequently paid the bill.

For the amount the customer has actually paid as of the report generation date, see the description of the RevenueCollectedCurrBillPeriod column that follows in this table.

Type: Currency rounded to two decimal places

Example: 12345.99

AWS Costs

The cost to you of the underlying AWS service your customer used. Because it is a debit, this value is always negative.

Note that this is the total amount we expect to charge you. The amount we have actually charged you as of the report generation date is listed in the AWSCostsChargedCurrBillPeriod column. To understand why the amount we've actually charged you might be less than the amount we expect to charge you, see If a Customer Doesn't Pay the Monthly Bill. Any additional AWS costs for the current billing period that we collect after the report generation date will appear in next month's report, in the AWSCostsChargedPrevBillPeriod column.

Note that data transfer out is a special case. Because it has a tiered cost structure, the value used to determine its cost is the cost-per-unit across the tiers.

For example, let's say that data transfer out costs $0.10 for the first gigabyte used by all your customers, and $0.20 for the remaining gigabytes used by all your customers. If you have three customers, and they each use 0.5 GB, then the total amount of data transfer out is 1.5 GB. Therefore, the cost-per-unit is: [(0.5 GB * $0.10/GB) + (0.5 GB * $0.10/GB) + (0.5 GB * $0.20/GB)] / 1.5 GB = $0.2 / 1.5 GB = $0.13 per GB.

Type: Currency rounded to two decimal places

Example: -12345.99

DevPay Fee

The DevPay fees you owe for the billing period. Because it is a debit, this value is always negative.

Note that this is the total amount we expect to charge you. The amount we have actually charged you as of the report generation date is listed in the DevPayFeeChargedCurrBillPeriod column. To understand why the amount we've actually charged you might be less than the amount we expect to charge you, see If a Customer Doesn't Pay the Monthly Bill. Any additional DevPay fees for the current billing period that we collect after the report generation date will appear in next month's report, in the DevPayFeeChargedPrevBillPeriod column.

Type: Currency rounded to two decimal places

Example: -12345.99

Refunds Issued

Refunds we've issued to your customer because of a cancellation or a price change to the product. Because it is a debit, this value is always negative.

Type: Currency rounded to two decimal places

Example: -12345.99

RevenueCollectedCurrBillPeriod

Revenue collected for the billing period listed in the report, as of the report generation date. This includes sign-up charges (if the customer signed up during the billing period), monthly charges, and usage charges.

For example, the January 15 report shows sign-up charges we collected in December for customers who signed up in December, monthly charges we collected in December to cover December use, and usage charges we collected in January (up until January 15) for customers who used the product in December. It's possible we'll collect a customer's payment for December usage after January 15 (for example on January 21). That revenue will appear in the February 15 report in the RevenueCollectedPrevBillPeriod column (see the next entry in this table).

Type: Currency rounded to two decimal places

Example: 12345.99

Note

The value reported is the value before AWS subtracts the corresponding DevPay fees.

RevenueCollectedPrevBillPeriod

Revenue collected since the last revenue report for usage during the months prior to the current billing period (see the preceding description for RevenueCollectedCurrBillPeriod).

The value reported is the value before AWS subtracts the corresponding DevPay fees.

Type: Currency rounded to two decimal places

Example: 12345.99

AWSCostsChargedCurrBillPeriod

AWS costs we've actually collected for the billing period listed in the report, as of the report generation date. Compare this to the AWS costs we expect to collect (see the description for the preceding AWS Costs column). Because it is a debit, this value is always negative.

Type: Currency rounded to two decimal places

Example: -12345.99

AWSCostsChargedPrevBillPeriod

AWS costs collected since the last revenue report for usage during the months prior to the current billing period (see the preceding description for AWSCostsChargedCurrBillPeriod). Because it is a debit, this value is always negative.

Type: Currency rounded to two decimal places

Example: -12345.99

DevPayFeeChargedCurrBillPeriod

DevPay fees we've actually collected for the billing period listed in the report, as of the report generation date. Compare this to the DevPay fees we expect to collect (see the description for the preceding DevPay Fee column). Because it is a debit, this value is always negative.

Type: Currency rounded to two decimal places

Example: -12345.99

DevPayFeeChargedPrevBillPeriod

DevPay fees collected since the last revenue report for usage during the months prior to the current billing period (see the preceding description for DevPayFeeChargedCurrBillPeriod). Because it is a debit, this value is always negative.

Type: Currency rounded to two decimal places

Example: -12345.99

Example Revenue Report

Customer Email,Customer Name,Postal Code,Country Code,Billing Period,Application,Customer Status,Customer Since,Cancellation Date,Revenue Billed,AWS Costs,DevPay Fee,Refunds Issued,​RevenueCollectedCurrBillPeriod,​RevenueCollectedPrevBillPeriod,​AWSCostsChargedCurrBillPeriod,​AWSCostsChargedPrevBillPeriod,​DevPayFeeChargedCurrBillPeriod,​DevPayFeeChargedPrevBillPeriod
"joesmith@example.com","Joe Smith","92009","US","FEB-2008","My Product A","Cancelled","27-FEB-08","04-MAR-08",".31","-.14","-.31","0",".31","0","-.14","0","-.31","0"
"janedoe@example.com","Jane Doe","M4E3W7","CA","FEB-2008","My Product B","Active","21-FEB-08","","3.54","-.03","-.71","0","3.54","0","-.03","0","-.71","0"
"markcooper@example.com","Mark Cooper","50014","US","FEB-2008","My Product C","Active","24-FEB-08","","1.1","0","-.62","0","1.1","0","0","0","-.62","0"
"samanthajones@example.com","Samantha Jones","NW1 9XN","GB","FEB-2008","My Product D","Active","27-DEC-07","","62.28","-40.91","-.94","0","20.00","0","-20.00","0","0","0"