Usage – Distributor Portal

Updated: May 11, 2021
Contents

Reviewing Reports from Vendors

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:

Column HeaderDescription
item_nameThe display name of the item as provided by vendor on the product definition, for example “Gold seat”
item_typein this column we can see if an item is PPU (pay-per-use) or reservation
item_unitexposes the unit of measure of the item, for example “licenses”
item_periodexposes 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_idunique identifier of the asset on Connect platform
asset_external_ididentifier of the asset on the commerce system, this value shall be easily identified by a Distributor
customer_account_idcustomer account identifier on the commerce system
customer_company_namecustomer account name as defined on last request sent by commerce system

Following the review, Distributors can accept it or reject the report:

  • In case of rejection, Distributors provide a reason that can be seen by vendors for further processing.
  • In case of acceptance, the report becomes available for propagation to the Distributor systems.

Acceptance Automation

Distributors have 3 ways of accepting reports from Vendors:

  1. Manually using Distributor Portal
  2. Using API by creating some Custom Script
  3. Using Automation Rules of the Distributor Portal

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.

Extracting Data

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.

Reconciling Data

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:

  • external_billing_id – any string value that would allow to reference relevant billing object (invoice, order, etc.)
  • external_billing_note – any additional data that might be useful for the reconciliation

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.

Is this page helpful?
Translate with Google
Copied to clipboard