Objects

turboboost is based on the salesforce platform, and as such has much underlying functionality however, all of the turboboost data is contained in objects that are not standard to the salesforce platform customers, subscriptions and invoices at the heart of turboboost is the subscription record, which represents an ongoing subscription with a customer , and the invoice record, which represents a discrete billing transaction with the customer at a point in time not all billing systems that you connect to will necessarily have the concept of a subscription, so where your billing system only has invoices, such as quickbooks, turboboost will create virtual subscriptions to represent the effective subscription you have with a customer line items and items items represent the products you sell, whereas a line items is a specific sale of that item a certain price, on an invoice line items are (to use the language of salesforce) a junction object between an invoice and an item transactions transactions represent a payment against an invoice this may or may not be an actual payment, and may also represent a credit note or refund change and revenue change records are used internally to represent a change from one amount to another (expansion or contraction), or the start of a subscription or customer, or the cancellation or churn of a customer the change records determine the per customer mrr chart, which is visible on a customer record revenue records allow for both mrr and recognized revenue over various time periods the most typical configuration is to have a revenue record per invoice, per month of that invoice it is unlikely you will diretly use revenue records as they represent internal concepts however, you may see them on the customer or subscription they represent the mrr for a given customer for the last day of that month please note, revenue records do not represent recognized revenue connection a connection represents a data connection to a third party system, such as stripe billing, or quickbooks online you can think about it as a data source it allows you to save settings or configuration on a per source basis entity entity records are only used if you are using turboboost to manage multiple legal entities an investor might want all of the portfolio companies in the same instance of turboboost, and thus each entity record would represent a portfolio company entity records are only available on advanced plans