LogiSense Billing Configuration

Owned by Tim Neil
Last updated: Sept 24, 2020
5 min read

The following items need to be configured in your EngageIP application. Screenshots are provided to indicate where the settings can be found / provide sample configuration data.

 

  1. Owner Configuration: Owner Currencies which your organization supports
    Must match values in Salesforce (the Salesforce configuration steps can be found under the 'Salesforce (Pre App Installation Process)' section) 

     

     

  2. Regional Settings: Countries (country and state relationships, city is optional)
    Must match values in Salesforce (the Salesforce configuration steps can be found under the 'Salesforce (Pre App Installation Process)' section) 

     

     

  3. Accounts: Contact Types and Contact Points
    Note: if Contact Types and Contact Points are configured as 'Required' in LogiSense Billing then they should also be set as required in Salesforce. The 'Contact Field Mapping' section below explains how to map LogiSense fields to Salesforce fields. Referencing which fields are mapped to Salesforce will tell you which Salesforce fields need to be set as required in order to match the LogiSense Billing configuration

     

     

    1. Add an additional contact point to each contact type

      • Name: sfdcid

      • Data Type: Text

      • Allow Multiple: False

      • Required: False

         

  4. Accounts: Account Status Types

     

     

  5. Accounts: Account Types
    Must match values setup under the Salesforce Account "Type" field (the Salesforce configuration steps can be found under the 'Salesforce (Pre App Installation Process)' section) 

     

     

  6. Billing: Bill Groups

     

     

  7. Dunning Process: AR Terms

     

     

  8. Custom Fields

     

     

    1. Account:

      • Entity: Account

      • Field Type: String(255)

      • Name: sfdcid

      • Column Name: sfdcid

      • Description: Salesforce Account Id

      • Layout: Account Settings (optional)

         

    2. Package Frequency:

      • Entity: Package Frequency Must match values in Salesforce (Product 'Product Family' field)

      • Field Type: String(255)

      • List: True

      • Lookup: False

      • Allow Multiple Selection: False

         

      • Name: Product Family

      • Column Name: family

      • Description: Salesforce Product Family

         

      • List Values: add the values listed in Salesforce (Setup → Object Manager → Product → Fields & Relationships → Product Family Picklist Values)

         

      • Layout: Add Product Family to the Package Frequency Layout

    Note: any additional custom fields setup on package frequencies will not sync to Salesforce by default. To configure syncing of custom fields see the 'Package Field Mapping' section

     

  9. Packages

     

    • Only packages / package frequencies that are "Active" will be synced to Salesforce

      • IMPORTANT! 

        • A product will be created in Salesforce for each Package Frequency

        • The product's name will be constructed by concatenating the following LogiSense fields, "PackageName PackageFrequencyName CurencyCode". For example, "ABC 1m GBP". It is important that all stakeholders are aware of this naming convention so that the names given to packages are user friendly for both Salesforce reps and LogiSense Billing Admins

      • If a package was already synced to Salesforce and then becomes inactive on the LogiSense side and resynced, it will be disabled on the Salesforce side and not available to be added to opportunities

      • Any package services whose Status pricing is NULL will not be synced to Salesforce

      • Rate plans (if applicable) must be attached at the package service level

      • Contracts (if applicable) must be attached to the package frequency

      • There should be a value in the SKU field. This field is mapped to the Product Code native field on the Product object in Salesforce. When a product is added to an opportunity a unique LogiSense Package Product Code will be assign to the opportunity product (SKU-ID). For example, if the SKU was ABC the product code will become, ABC-1. The next product added to any opportunity would be "SKU"-2, and so on. If no SKU is provided in LogiSense Billing and the product catalog is synced with Salesforce, then the product code for each product added to an opportunity would become, -1, -2, -3, ... (no SKU prefix).

      • Select the correct Product Family custom field value on the package frequency

      • The current Salesforce app doesn't support tiered pricing. The package will be synced however the tiered structure will not be displayed in Salesforce

         

  10. Optional Configuration depending on deployment

    • Product Catalog Contracts - these can be attached to package frequencies and will be shown on the Salesforce Product Object. (Custom Field: "Minimum Term", LogiSense_Minimum_Term__c)

    • Usage Buckets - these can be attached to services and populate the Usage Bucket custom object installed with the Salesforce App. The connection between the usage bucket and service will also be established in Salesforce and show as a read-only "allowance" on the custom Opportunity Product Service Visual Force page

    • Rate Plans - standard configuration of Rate Plan/Rate Group/Rates. These must be attached to Package Services and not Package Frequencies in order to allow Salesforce users to override rate amounts

Copyright LogiSense 2020