FAQs - Reporting & Transactions (reconciliation, access, usage)

General

Why doesn't our check amount match the amount reported on the Extranet?
How do we access the Developer Reports on the Extranet?
If we change our company name, will our old reports/stats/usage transfer to the new company name?
How can we determine churn of our subscribers?

Application Usage Reports

What is the purpose of the Application Usage report?
When is the Application Usage report finalized for any given day?
For what date range can the Application Usage report be run?
How long is the Application Usage report data available on the Developer Extranet?
Why do I get different results for the Application Usage report when I run it from 30-jan-2004 00:00:00 to 31-jan-2004 00:00:00 versus 30-jan-2004 00:00:00 to 30-jan-2004 23:59:59?
Why did our subscription event counts on our Application Usage report drop off on the 29th, 30th, 31st?
Why is there a discrepancy in the transaction count between the Invoiced Sales (formerly Carrier Billing) report and the Application Usage report on the Developer Extranet?

Invoiced Sales Report

What is the purpose of the Invoiced Sales (formerly Carrier Billing) report?
When is the Invoiced Sales report data available?
For what date range can the Invoiced Sales report be run?
How long is the Invoiced Sales report data available on the Developer Extranet?
What does "Billable Count" on the Invoiced Sales report represent in terms of subscriptions?
Does the Invoiced Sales report only display NEW subscriptions?
What does "Adjustments" on the Invoiced Sales report represent?
How is the "Net Amount Billed to Operator" amount on the Invoiced Sales report calculated?
Why is there a discrepancy in the transaction count between the Invoiced Sales (formerly Carrier Billing) report and the Application Usage report on the Developer Extranet?

Payment Detail Query

What is the purpose of the Payment Detail Query report?
When is the Payment Detail Query report data available?
For what date range can the Payment Detail Query report be run?
How long is the Payment Detail Query report data available on the Developer Extranet?
Why are there AP Invoice ID numbers listed on our check remittance stub that are not available to view using the Payment Detail Query report?

Developer Extract XML

What is the purpose of the Developer Extract XML report?
When is the Developer Extract XML report data available?
For what date range can the Developer Extract XML report be run?
How long is the Developer Extract XML report data available on the Developer Extranet?
What do we do with the Developer Extract XML report once we download it from the Developer Extranet?
What can we do if we need more information about the Developer Extract XML file and how to use it?

General

1. Q: Why doesn't our check amount match the amount reported on the Extranet?
A: First, please verify that the items you were expecting to be paid for this month were actually part of the check in question by using the Payment Detail Query report. Also, please understand that manual deductions do not show up on any of the Extranet reports; they are only listed as AP Invoice ID codes on your check remittance stub. Manual deductions may be processed for a number of things, such as Foreign Withholding Taxes.

2. Q: How do we access the Developer Reports on the Extranet?
A: Using your internet browser, go to path name https://brewx.qualcomm.com/developer/. You will then be prompted to log in using your username and password. The Developer reports are located in the "Reports" tab on the Extranet.

3. Q: If we change our company name, will our old reports/stats/usage transfer to the new company name?
A: The system currently supports a generic developer name key. If your account was initially set up with a generic name in the name key, then the name of your company can change without impacting reports/stats/usage. However, if your account was set up with a name-specific key then you may need to be set up with a new account. If so, then you will have to run your reports using both the old and new company names until applications associated with the old company name key are no longer coming into the BREW system.

4. Q: How can we determine churn of our subscribers?
A: Unfortunately, there is no way to really determine the specifics of subscriber churn using the available reports. However, the variance or growth seen each month represents the net number of additional billable subscribers. The transaction count that you see in the "Billable Count" column on the Invoiced Sales report represents the total number of Subscription Bill (SB) events that were billed to the operators on your behalf for the current month. This does NOT only represent new subscribers. In other words, your number of current billable subscribers is equal to the number of subscribers from the prior month, less any subscribers that cancelled their subscription since the prior month's billing, plus any new subscribers that have joined since the prior month's billing.

Application Usage Reports

1. Q: What is the purpose of the Application Usage report?
A: This report was created for the purpose of business intelligence. It is only meant to show usage and does not necessarily equal the number that we will end up billing on a developer's behalf, because the data still has to be run through our BREW Billing logic. There may be a case where a duplicate download or some other non-billable event occurred. Also, please note that Adjustments and Value Billing events are not included in this report. The Invoiced Sales report is the only report that provides actual billing data.

2. Q: When is the Application Usage report finalized for any given day?
A: The report data for any given day is not finalized until after 6:00am PST the following day. You should never run this report for <today>.

3. Q: For what date range can the Application Usage report be run?
A: This report can be run for a specified date range, up to a one-month period.

4. Q: How long is the Application Usage report data available on the Developer Extranet?
A: The report data is available on the Extranet for one year. You should be saving your report data to prevent a situation where you need data that is no longer available on the Extranet. This can be done by exporting the data to Excel and saving it as an Excel file.

5. Q: Why do I get different results for the Application Usage report when I run it from 30-jan-2004 00:00:00 to 31-jan-2004 00:00:00 versus 30-jan-2004 00:00:00 to 30-jan-2004 23:59:59?
A: Please note that the time stamps on the date parameters of the Application Usage report do not matter. Using an end time of 00:00:00 and 23:59:59 will return the same results for any given day. The report only uses the day (DD), month (MMM), and year (YYYY) as date parameters. The only thing to be concerned about is that the data for any given day is not finalized until after 6:00am PST the following day. You should never run this report for <today>.

6. Q: Why did our subscription event counts on our Application Usage report drop off on the 29th, 30th, 31st?
A: Billing automatically occurs on the same date each month following the month in which the end user downloaded the application. One thing to note is that if an end user's original download date falls on the 29th, 30th, or 31st day of the month, all subsequent billing events will occur on the 28th day of the month since not all months have more than 28 days. For example, for a download that occurs on January 10th, the subsequent monthly billing will occur on the 10th of every month until the end user deletes the application. For a download that occurs on January 30th, the subsequent monthly billing will occur on the 28th of every month until the end user deletes the application.

7. Q: Why is there a discrepancy in the transaction count between the Invoiced Sales (formerly Carrier Billing) report and the Application Usage report on the Developer Extranet?
A: The Invoiced Sales report illustrates billable events only. This report assists with revenue recognition by allowing you to retrieve the amounts for which operators have been invoiced for developer revenue related to application usage. The transaction count on this report includes download (DL) and monthly subscription bill (SB) events. Please note that if a subscriber downloads a subscription multiple times during a billing cycle, Qualcomm will invoice the operator for the first event only. This prevents the subscriber from being overcharged for duplicate downloads. Any transaction adjustments (TAs) made by the operator will be captured as a dollar amount under the "Adjustments" column, and will be netted against the amount billed to the operator.

The Application Usage report provides information about the number of application downloads logged by each operator, including the price method, price basis, basis value, and date of download. You may find this data helpful in analyzing statistical trends of application sales by operator. The transaction count on this report includes all transactions associated with each part number.

The transaction count for these two reports will rarely match because the Application Usage report illustrates usage events (including Demos) while the Invoiced Sales report illustrates only billable events.

Invoiced Sales Report

1. Q: What is the purpose of the Invoiced Sales (formerly Carrier Billing) report?
A: This report represents the amount of revenue that we bill each operator/carrier on behalf of developers (i.e. the Developer's Share of Revenue, typically 80%). The report can be retrieved for a specified operator, part number, and/or monthly billing period. The report is subtotaled by AR invoice.

2. Q: When is the Invoiced Sales report data available?
A: We state that our invoices will be finalized and posted by close of business on the 10th calendar day of every month, which means that the Invoiced Sales report data will be available on the Developer Extranet by the morning of the 11th each month. Please understand that we have to process invoice data for all operators, audit the data, and get every invoice approved which is why we allow 10 days on our end before they can be finalized and posted. The report may be available earlier than the 11th day, as you may see the data posted sooner, but we only promise it by the 11th.

3. Q: For what date range can the Invoiced Sales report be run?
A: The report is produced based on monthly billing periods, and can be run for up to three consecutive months at once. Please note that the system uses only the month and year. It does not use the day or time as part of the date parameters.

4. Q: How long is the Invoiced Sales report data available on the Developer Extranet?
A: The report data is available on the Extranet for one year. You should be saving your report data to prevent a situation where you need data that is no longer available on the Extranet. This can be done by exporting the data to Excel and saving it as an Excel file.

5. Q: What does "Billable Count" on the Invoiced Sales report represent in terms of subscriptions?
A: The "Billable Count" on the Invoiced Sales report noted as Subscriptions represents the number of events that we billed the operators on your behalf. This number includes recurring bill events for end users that are still active in subsequent months. Billing automatically occurs on the same date each month following the month in which the end user downloaded the application.

6. Q: Does the Invoiced Sales report only display NEW subscriptions?
A: The number of subscription events on your Invoiced Sales report represents the number of events that we billed the operators on your behalf. This number includes both new subscriptions and recurring bill events for end users that are still active in subsequent months. Billing automatically occurs on the same date each month following the month in which the end user downloaded the application.

7. Q: What does "Adjustments" on the Invoiced Sales report represent?
A: The "Adjustments" column represents the dollar amount associated with the "Adj Count" column for the Transaction Adjustment (TA) events that were processed in the current month. These can occur at any time throughout the month as operators process credits for end users when they accidentally download an application, inadvertently download an application twice, or are not satisfied with the application they purchased. Operators may elect to do a partial or full credit for the transaction, at their discretion. Qualcomm processes these adjustments every day, just as purchase and subscription events are processed on a daily basis.

8. Q: How is the "Net Amount Billed to Operator" amount on the Invoiced Sales report calculated?
A: The Net Amount Billed to Operator is calculated by taking the Gross Developer Revenue (= 80% of DAP multiplied by Billable transaction count) and subtracting from it any Extension Revenue Share (owed if using an Extension application) and any Adjustments (processed by the operator for end user returns, etc).

Example:
If the DAP for a part was $4.15, and there were 115 billable downloads and one end user requested a full refund for their download, then the Net Amount Billed to Operator would be equal to $378.48:

Gross Developer Revenue = 0.80 x $4.15 x 115 = $381.80
Extensions = 0
Adjustments = 0.80 x $4.15 x 1 = $3.32
Net Amount Billed to Operator = $381.80 - 3.32 = $378.48

9. Q: Why is there a discrepancy in the transaction count between the Invoiced Sales (formerly Carrier Billing) report and the Application Usage report on the Developer Extranet?
A: The Invoiced Sales report illustrates billable events only. This report assists with revenue recognition by allowing you to retrieve the amounts for which operators have been invoiced for developer revenue related to application usage. The transaction count on this report includes download (DL) and monthly subscription bill (SB) events. Please note that if a subscriber downloads a subscription multiple times during a billing cycle, Qualcomm will invoice the operator for the first event only. This prevents the subscriber from being overcharged for duplicate downloads. Any transaction adjustments (TAs) made by the operator will be captured as a dollar amount under the "Adjustments" column, and will be netted against the amount billed to the operator.

Payment Detail Query

1. Q: What is the purpose of the Payment Detail Query report?
A: This report should be used to determine what each payment represents. It can be run by selecting the AP Invoice ID number "BB00xxxx" that is noted on a given check remittance stub, and will provide detail explaining which operator invoices and billing periods are included in the check. Please note that there may be several AP Invoice ID numbers listed on one check, meaning that it includes payment for more than one operator invoice. You have the option to run this report for "ALL" AP Invoice ID numbers. The "Net Payment" amount represents a developer's payment amount including deductions for withholding taxes, Low-DAP fees, and currency gain/loss (if applicable).

2. Q: When is the Payment Detail Query report data available?
A: The report data is available after your vouchers have been processed by Qualcomm, which is prior to when you will receive a check.

3. Q: For what date range can the Payment Detail Query report be run?
A: The report is not run by a date range, but rather by the AP Invoice ID number associated with a specific check. These numbers will be listed on your check remittance stub. You may also choose to run the report for "ALL" AP Invoice ID numbers which will provide details on all invoices for payments that you have received within the past year.

4. Q: How long is the Payment Detail Query report data available on the Developer Extranet?
A: The report data is available on the Extranet for one year. You should be saving your report data to prevent a situation where you need data that is no longer available on the Extranet. This can be done by exporting the data to Excel and saving it as an Excel file.

5. Q: Why are there AP Invoice ID numbers listed on our check remittance stub that are not available to view using the Payment Detail Query report?
A: Invoice numbers that do not begin with "BB" represent exceptions to normal invoice processing and are currently not included for viewing detail on the Developer Extranet. An example of this is Foreign Withholding Taxes (FWT) which are typically coded as "FWT-XXXX-xxxxxx" on your check remittance stub.

Developer Extract XML

1. Q: What is the purpose of the Developer Extract XML report?
A: This report provides access to transaction data in the form of an XML file. It can be used for business intelligence and financial reconciliation. It is generated as a .zip file, a common binary compression format. Once the file has been downloaded, it should be saved locally for processing. Please refer to the Developer Extract XML and the Best Practices documents located on the Developer Extranet for more information about this report.

2. Q: When is the Developer Extract XML report data available?
A: We state that our invoices will be finalized and posted by close of business on the 10th calendar day of every month, which means that the Developer Extranet XML report data will be available on the Developer Extranet by the morning of the 11th each month. Please understand that we have to process invoice data for all operators, audit the data, and get every invoice approved which is why we allow 10 days on our end before they can be finalized and posted. The report may be available earlier than the 11th day, as you may see the data posted sooner, but we only promise it by the 11th.

3. Q: For what date range can the Developer Extract XML report be run?
A: The report is produced based on monthly billing periods, and can be run for a one-month period within the past three months. The first month of availability for this report is April 2004.

4. Q: How long is the Developer Extract XML report data available on the Developer Extranet?
A: The report data is available on the Extranet for up to three months.

5. Q: What do we do with the Developer Extract XML report once we download it from the Developer Extranet?
A: You should save the two files to a local disk, and then process the XML file using an XML parser. Once you have properly parsed the data you will be able to use the report data to generate analytical reports and answer specific business questions.

6. Q: What can we do if we need more information about the Developer Extract XML file and how to use it?
A: Using your internet browser, go to path name https://brewx.qualcomm.com/developer/. You will then be prompted to log in using your username and password. The Developer reports are located in the "Documents" tab on the Extranet. There are three documents that relate to this report. The Developer Extract XML Specification document provides a detailed explanation of the report. The Business Intelligence Best Practices for ISVs document and the Reconciliation Best Practices for ISVs document each provide sample SQL statements and suggested uses of the report.