To optimize platform functionality use Google Chrome.
Overview: The billing module contains cloud provider-specific Billing Reports. These reports are meant for analysis and reconciliation of monthly billing data, as well as the primary method to generate customer and 'partner level' invoices. This article demonstrates how to create customer usage statements in the platform. Billing statements are generated monthly and typically based on usage in the prior month. The settlement period of cloud provider fees is typically completed several days after a month closes.
Tech Data recommends waiting approximately five business days after a calendar month ends to generate customer Billing Statements/Invoices, EXCEPT for AWS resellers. Tech Data sends a formal notification to platform administrators when the AWS billing is finalized. The notifications are sent between the 5th and the 15th of the following month. If you did receive the distribution email notification, please contact Support to be added to the email distribution list.
You can create Customer Billing Statements/Invoices at any time during the month. As long as it remains in 'draft' format, it will not display to your customers via the end Customer Portal.
The platform billing reports consolidate all billable services for all of the end customer cloud accounts. As a reseller, you will receive one invoice from AVT (Tech Data). Use the platform to generate billing reports and break out the billing information by customer and account numbers. The Reports is where the detailed information is found.
To generate Customer Billing Statements/Invoices , follow these steps:
1) Select the Reports module
Select one or more customers by clicking the checkboxes.
- You may need to expand the groupings to see the customers.
- To select all customers, click Options in the top-right corner and select Select All.
- To clear your selections, click Options and select Select None.
In Options, select Generate Invoices. In an invoice, you can:
- Apply any credits
- Include tax
- Include marketplace fees
- Use credits for marketplace fees
*Billing Note Specific to AWS Marketplace Fees
1. AWS Marketplace fees are specific to the AWS Customer Billing report. AWS Marketplace fees will only generate in your billing statement if the fees apply to your customer
(whether or not this feature is marked active). These fees are not associated with AVT Marketplace Program(s) and offerings.
2. Taxes, support plans, and global discounts are calculated exclusive of AWS Marketplace fees which are a pass-through under the AWS Reseller Program.
3. AWS Marketplace fees may display as $0 line-items in the report and on the customer billing statement. In general, there can be two reasons for this:
a. The usage is actually covered by some kind of free tier offering from the AWS Marketplace vendor. (For example, in March, the usage for Alert Logic Threat Manager for AWS lists "AWS Marketplace Free Trial..." in the description.)
b. The usage is small enough that a charge hasn't yet been generated. (For example, the usage for Foxit Reader lists only "0.806 Months", which could be under the threshold to generate a charge)
Perform actions on an invoice
Click Preview Invoices. You can perform the following actions:
- Approve all
When you click View, the report is displayed in draft status, meaning that if you are using the Customer Portal to allow customers to log in, the report would not be visible to the customer. This allows you to review invoice data before sending it to your customers.
Invoices include customer contact information and also your public profile data—your logo and contact information configured in Settings > Account information.
You can also download a CSV or PDF of the invoice.
*Note: Invoices are organized by product type.
Change the invoice status
You can change the invoice status to the following states:
- Past Due
If you View the invoice, you can change the currency by scrolling to the top of the document and click the drop down arrow.
The platform supports a billing API. You enable the API under Settings > Account Information screen.
To view the system integration options, we have an API set defined in Swagger.
Rounding in the Billing Reports
- The usage report has to do rounding and it's done to the 2 decimal points. The rounding is off of 9 + decimal points deep.
- DBR rounding occurs at the service level. DBR does all the fractional hours and fees.
- The Reseller billing report could be higher than the values received on your invoice from AVT
- The billing represents the billing with rounded included.
- If you want to go to the penny you go to DBR view of the billing data.
- Usage report rounds and is dynamic. It could change at any time.
- The report that is post-billing statement generation maintains the view of billing at a specific month against the pricing at the time of the billing. When you run the same report for a past month, you are likely to see changes to the billing report.
More Information Regarding Rounding
The usage report that you view your usage detail from in SES takes data directly from the billing DBR however given that the billing detail goes in some cases to 9 and beyond decimal points we have to round the data when you view it in the report. The rounding for this view is occurring at the individual line item level and then rolled up. The reason for this is that you have drill down capabilities in the usage report to go into for example ec2-box usage-instance type. Because of this and the two decimal points that get displayed it forces rounding. The bill itself, however, is not rounded. It is calculated with all decimal points then totaled and at the service category total is then rounded to the nearest penny. To summarize the usage report view represents a rounded view of the bill because you have the ability to drill Deeper into the detail and because it is always displayed to 2 decimals points. The only way to reconcile your charge to "the penny" is to use the detailed billing file we provide with the bill aka the DBR. The usage report will always show a "rounded" view of the data.