The Customer in CloudBilling is the entity to which Invoices are associated, and represents the real customers of your business or organisation. A Customer therefore has Purchases associated to it, and also has several specific attributes that describe how the customer should be treated within the CloudBilling system and operations (for instance, billing frequency, time zone, etc.).
Below, we take a look at the information that is stored for each Customer.
- Primary Customer Information
- identifying information for the CloudBilling customer
- Billing Related Information
- settings and information that describe the specifics of how this customer should be billed
- Emailing Information
- if you make use of the Email module, this section contains the details relevant to this, such as the email addresses of the customer
- Meta Information
- all other data that does not fit explicitly into CloudBilling, but is important for your billing calculations or invoice outputs
- Customer Code: The unique code identifying this customer throughout CloudBilling.
- Customer Name: A name identifying the customer
- Customer Cluster: All customers need to be assigned to a Customer Cluster - this association indicates the group or groups that are relevant for this Customer..
- Bill From Date: The date from which point onward a customer is billed. If Align is set to true, only used to indicate which invoice period is used, otherwise used as the exact start date of the first invoice.
The customer has 4 key settings to drive how Invoices are generated during the Billing Calculation process. Using these, the user is able to configure the frequency of the Invoice, and whether or not to ensure the Invoices are aligned to the start of the periods. The specific fields are:
Invoice Period UOM: Unit of measure for the invoice. Possible values are Day, Month, and Year
Period Size: The size of the invoice period (used in conjunction with above field to specify, for example, “every 1 month”)
Align: True/False value indicating whether the invoice period of the customer should be aligned to the unit of measurement. For instance, if the customer is invoiced monthly, should the invoice period start at the first of the month? If set to false, the start of the invoice period is determined by the exact Bill From Date.
Invoice Separately Per Period: Whether recurring purchases should be invoiced separately per invoices, or all recurrences should be invoiced in the first applicable period.
- Language Code: The language code ID indicates which Invoice Label language to use when generating the Invoice line descriptions. A list of codes can be found in Locale ID (LCID) Table.
- Timezone: A value identifying the timezone the customer resides in. Used to determine whether DST is applicable or not and what offsets to use in terms of time.
- Billing Suspended: You can use this option to temporarily prevent invoicing from taking place on this customer.
A customer can have a list of email addresses associated. These can be used to send invoices to the customer and each of them has the following properties:
- Key – a key to refer to the address
- Email Address – the actual address
- Display Name – the name to be displayed in email clients.
- Addresses: A list of Addresses associated with the customer. Each address must be uniquely named, and can be used during Invoice Transformations.
- Metadata: The Customer Metadata can be used during Billing Calculations, Invoice Transformations, or even just for searching in the management portal. There are 3 types of metadata collections, for Text, Numbers, and Dates. Each of these are defined as a set of name-value pairs.
- Finding Customers in the Management Portal…
- Editing a Customer in the Management Portal…
- Importing Customers via the API…