LogiSense Billing for Salesforce empowers your sales and customer representatives with the tools to simplify on-boarding of new clients, promote upsell opportunities and provide end-to-end visibility into customer account details all without ever having to leave the Salesforce platform or interface with your company's billing department.
The app is designed to work with native Salesforce objects which include, Accounts, Contacts, Price Books, Products and Opportunities. The product object in Salesforce will be extended with a custom child object (Product Services) which will house the individual line items and their respective pricing that has been defined in LogiSense Billing.
Both LogiSense Billing and Salesforce have the concept of parent/child relationships between accounts. This relationship will be honored when accounts are pushed to LogiSense Billing. As part of an account sync any contacts which are marked to sync will also be push to LogiSense Billing as part of that request.
Shared contacts are also supported within the LogiSense Billing for Salesforce app. Any mapped or required fields that change on either an account or contact that has been synced previously with LogiSense Billing will initiate an update request to ensure that both systems have the latest detail.
Only changes made to accounts or contacts within Salesforce will be pushed to LogiSense Billing. There is no syncing of account or contact detail from LogiSense Billing to Salesforce. However billing administrators can at anytime create additional accounts or contacts within LogiSense billing that are not related to those within Salesforce.
Any accounts that will be synced with LogiSense must contain the following settings on the Salesforce end:
Account Currency - the currency cannot be changed once synced. Parent and child accounts must have the same currency.
Subscription and Usage Invoice Recipients - (self or another Account).
Account Status - the status of the account
Bill Group and Accounts Receivable Term - these are defined in LogiSense Billing and made available within Salesforce
The master product catalog, which contains all list pricing for each product, is defined within LogiSense Billing. This information is synced to Salesforce in turn creating a specific LogiSense Price Book which can be used on standard Opportunities.
LogiSense Billing will always be the system of record for any product definitions and pricing to ensure that when an opportunity is Closed:Won and pushed to LogiSense that the system can associate the correct products/pricing to an account price plan. Account Price Plans within LogiSense Billing represent the negotiated/contracted pricing for each product to ensure that that pricing is honored when future purchases/orders are made against those products.
Only opportunities that use an integrated LogiSense price book can be synced with LogiSense for billing purposes when the opportunity is Closed:Won. Syncing of opportunities will occur via a custom button that must either be manually clicked (native) or triggered via a custom Salesforce business process (developed by customer). This will ensure that any predefined approval processes will not be interfered with when an opportunity stage changes to Closed:Won.
Custom pricing of the opportunity line item within Salesforce is done via a custom child object (Opportunity Product Services). Each service within a opportunity product can be priced individually and the sum of the pricing will set the opportunity product’s sales price. This allows the rep to drill down into the services to change quantities, recurring, one-time and/or state based pricing, and overage charges per service.
The account must first be synced with LogiSense Billing prior to any opportunities being synced. When an opportunity is pushed to LogiSense Billing it will create an Account Price Plan.
This means that the opportunity push is not creating an order in LogiSense Billing but instead recording the custom pricing set for each product within the opportunity for this account.
Orders would need to be processed outside of the app via the LogiSense Order object or using the customers current ordering system.