Top Tier Customer Report¶
The Top Tier Customer Report provides valuable insights into the most significant customer organisations within Dsposal's Paperwork system. This report focuses on customer entities rather than individual sites, offering a comprehensive overview of key organisational clients. By highlighting top-tier customers, businesses can efficiently analyze their most significant client relationships, track performance metrics, and make informed strategic decisions to optimise customer engagement and drive business growth.
Before you start¶
Before getting started, there are a couple of helpful things to know:
- Deleted customers are NOT included in the report.
- Dates are not used when generating this report.
Fields in the report¶
| Field Name | Data Type | Description |
|---|---|---|
| customerId | Number | Unique identifier for the customer. |
| customerName | Text | Name of the customer organisation. |
| addressLine1 | Text | First line of the customer's address. |
| addressLine2 | Text | Second line of the customer's address (if applicable). |
| townCity | Text | Town or city where the customer is located. |
| postcode | Text | Postcode of the customer's address. |
| accountNumber | Text | Account number assigned to the customer. |
| vatNumber | Text | VAT number of the customer (if applicable). |
| registrationNumber | Number | Registration number of the customer organisation. |
| customerStatus | Text | Current status of the customer (e.g., Active, Inactive). |
| statusReason | Text | Reason for the customer's status (if applicable). |
| taxRate | Number | Tax rate applied to transactions with the customer. |
| customerSIC | Number | SIC code associated with the customer. |
| customerSICDescription | Text | Description corresponding to the SIC code assigned to the customer. |
| customerSector | Text | Sector to which the customer belongs. |
| Text | Email address of the customer contact. | |
| phoneNumber | Text | Phone number of the customer contact. |
| faxNumber | Text | Fax number of the customer (if available). |
| paymentTermCode | Text | Code indicating the payment terms for the customer. |
| paymentTermQuantity | Number | Quantity associated with the payment term (e.g., number of days). |
| paymentTermPeriod | Text | Period for the payment term (e.g., Days, Months). |
| paymentTermType | Text | Type of payment term (e.g., end of month, day(s) after bill date). |
| creditLimitInternal | Number | Internal credit limit assigned to the customer. |
| invoiceName | Text | Name to be used on invoices for the customer. |
| invAddressLine1 | Text | First line of the invoicing address. |
| invAddressLine2 | Text | Second line of the invoicing address (if applicable). |
| invTownCity | Text | Town or city in the invoicing address. |
| invPostcode | Text | Postcode of the invoicing address. |
| invoiceSIC | Number | SIC code for invoicing purposes. |
| invoiceSICDescription | Text | Description corresponding to the SIC code used for invoicing. |
| createdDate | Date/Time | Date and time when the customer record was created. |
| createdBy | Text | User who created the customer record. |
| updatedDate | Date/Time | Date and time when the customer record was last updated. |
| updatedBy | Text | User who last updated the customer record. |
| notes | Text | Additional notes or comments about the customer. |
| salesNumber | Text | The default agreement linked to this customer. |
| salesTypeName | Text | Type of sales that this default agreement is (e.g., Price List, Agreement). |
| purchaseOrderRequiredForDefaultAgreement | Boolean | Indicates if a purchase order is required for the default agreement with the customer (TRUE/FALSE). |
Frequently asked questions¶
What is a field?
A field refers to a single piece of data within a dataset, also known as a column or attribute. It represents a specific characteristic or attribute of the data being collected or analysed. For example, in a dataset of opportunity information, fields may include "department," "salesType," "customerSite," and "lostReason".
Why do your field names look funny?
We use a computer programming convention called camel case (more accurately lower camel case) where multiple words are combined into a single word, with each word (except the first one) capitalised and no spaces between the words. The name "camel case" comes from the capitalisation's resemblance to the humps of a camel.