When the vendor submits the usage report and transitions it to the status Pending, Distributors can access and download the spreadsheet for validation.
The file available for Distributors download contains more information than the one provided by Vendors to help the Distributors validate the file. Distributors have access to the following additional columns:
|item_name||The display name of the item as provided by vendor on the product definition, for example “Gold seat”|
|item_type||in this column we can see if an item is PPU (pay-per-use) or reservation|
|item_unit||exposes the unit of measure of the item, for example “licenses”|
|item_period||exposes the billing period for the item, it can be one time, monthly or yearly billing. Please see that this is not commitment time but rather exposes how often vendor bills for this item to the Distributor|
|asset_id||unique identifier of the asset on Connect platform|
|asset_external_id||identifier of the asset on the commerce system, this value shall be easily identified by a Distributor|
|customer_account_id||customer account identifier on the commerce system|
|customer_company_name||customer account name as defined on last request sent by commerce system|
Following the review, Distributors can accept it or reject the report:
Distributors have 3 ways of accepting reports from Vendors:
The latter options allows Distributors to specify simple processing rules that will automatically accept or reject Usage Report from the Vendor:
Usage Rules can be configured at the Product Details > Usage Rules page of the Distributor Portal.
Once a usage report has been accepted, Distributors can extract usage data to their systems per hub:
For systems that are integrated with CloudBlue Connect in an automated way, records are automatically extracted using either record-level API calls or bulk file export.
Once usage data has been used for billing, corresponding records need to be marked as “Closed” in the Usage Report file for the end-to-end reconciliation. This could be achieved either through API or by uploading reconciliation report manually in the Distributor Portal:
Reconciliation file structure is similar to the extraction file with 2 additional columns:
Once Reconciliation file is uploaded and processed, statistics of the Closed records will be updated to reflect how many records were closed:
Once all records are closed, the whole usage file will be marked as closed.