· 

Reporting Module (BETA)

The Reporting module provides insightful reports based on your own usage data. The Reporting Module will initially be released with five standard reports:

 

1. Top Revenue Report

This report presents a clear and concise list of customers and the revenue they generate. When available, costs too will be displayed, and as a result the margin per customer. The report can be applied to all customers or a subset there of when desired. The report can be sorted on a number of different criteria such as the Period, Revenue, Cost and Margin.

 

2. Revenue Differences Report 

This report gives insight into revenue growth. It calculates both the absolute growth and the relative growth. These calculations will be performed per customer and over the total revenue. It is possible to sort the report based on each column.

 

3. GL Report 

This report provides more insight into the General Ledger. It immediately displays the Global Balance of the General Ledger. It specifies the totals per account and if an imbalance is found it immediately displays the customers and their invoices that are responsible for the imbalance. Per customer it is possible to reveal the different accounts. If no imbalances are found, no customers will be displayed. It is possible that due to rounding differences a number of customers will be listed. To cater for these differences a button is added in the top right of the report. This button automatically filters all imbalances that can be explained by rounding differences. Furthermore, if one or more price rules with incorrect tags are detected it immediately displays these rules including a link to edit them, allowing to immediately fix the problem.


4. Purchase Report 

This report displays 100 random purchases. For each purchase it presents the Customer code, Quantity, Product, Purchase Date and Purchase Reference. It also provides a count of the total number of purchase, unmapped purchase and uninvoiced purchase. Unmapped and uninvoiced purchase counters are clickable and will immediately display the affected purchases. Each displayed purchase has an edit button to support in making any needed changes.

 

5. Average Invoice value

This report generates a graph that displays the average invoice value over time. It is possible to display the average invoice cost, the total invoice value and total invoice cost over time to the graph. It is possible to generate the graph using a subset of the underlying data, such as the customer clusters or over a different time period.

 

 

· Purchase Processing Stats Widget

This new widget has been developed as part of an effort to make the CloudBilling process more transparent. The widget displays per hour how many purchases have been imported and or processed. It provides immediate insight in the current activities CloudBilling is undertaking and can act as a warning sign of potential issues.

 

 

Improvements

· Added "Completed" flag to Purchase model in API – GetPurchase

There was no way to know (from the API) whether a purchase is completed or not. If an update was made to a purchase using the API on a completed purchase the API would return 200 OK. It gave no additional information on whether or not the update succeeded. This could be problematic on the customer side. The API response for the UploadPurchase call has been updated to contain a completed flag to indicate whether the purchase in question has been completed or not.

  

Bug Fixes

· Fixed incorrect grouping on grouped invoices

Previously transformations that operate on all invoices (like GL export) would generate multiple results. 1 for every 500 invoices. For customers that have large amounts of invoices this could lead to unmanageable large amounts of results. This has been fixed; Grouped Transformations generates only 1 result.

 

· Fixed 500 error upon login when users groups have overlapping rights

When a user has multiple groups and those groups have overlapping rights, a 500 error was generated when the user tried to log in. This has been fixed; a user can be part of multiple user groups that can potentially have overlapping rights.

 

· Fixed broken Purchase - Bulk Edit button

Previously when bulk editing purchases only the customer name would change and not the customer code. This has been fixed; all fields that have been edited will be stored correct.

 

· Fixed broken UploadPurchase Call

When specifically uploading a bundle purchase using the API call UploadPurchase the BundleInfo part would get lost during processing. This would lead to missing customer bundles. This has been fixed; customer bundles are created as expected.

 

· Fixed broken GetInvoiceHeaders call when no billingPeriodDate is specified

The GetInvoiceHeaders call indicated the billingperiodDate as optional when this was not the case. Returning an error when the billingperiodDate was left out. This has been fixed; the billingperiodDate is optional. When leaving the billingperiod out, the call returns all invoice headers.