Salesforce Billing Custom Objects

The Salesforce Billing data model provides custom objects to manage invoices, payments, and revenue.

The documentation in this developer guide is for the Salesforce Billing managed package. If you’re looking for developer documentation for Revenue Cloud, see Get Started with Revenue Cloud Developer Resources.

Note

  • blng__AccountBalanceSnapshot__c

    Represents a list of outstanding invoice debt within an account, grouped by the number of days past the due date. The account balance snapshot also includes the amounts of unapplied credit notes and payments within the same account.

  • blng__AgingBuckets__c

    Represents the outstanding invoices sorted into various aging periods.

  • blng__BalanceSnapShotRun__c

    Represents the analysis of an account’s invoices on a scheduled basis for past-due balances.

  • blng__BalanceSnapShotScheduler__c

    Represents the Balance Snapshot Scheduler, which creates a Balance Snapshot Run to regularly analyze your account’s invoices for past-due balances.

  • blng__BillingBatchJob__c

    Represents a scheduled processing job that triggers recurring invoice batch runs and payment batch runs.

  • blng__BillingPrefix__c

    Represents a prefix that can be appended to billing-related records for storage purposes.

  • blng__BillingRule__c

    Represents how and when billing must occur for products and services.

  • blng__BillingSchedule__c

    Represents information about the order product that’s invoiced based on the invoice plan billing frequency.

  • blng__BillingTransaction__c

    Represents information about each invoice plan line of a billing schedule. A billing transaction stores the billed amount based on the relationship between the invoice plan line’s commencement date and the order product’s service start and end dates. When a billing transaction is invoiced, Salesforce Billing copies data from the billing transaction to the invoice line.

  • blng__BillingTreatment__c

    Represents information about how Salesforce Billing records billing rule actions in your finance books and general ledgers. Use billing treatments to specify an invoice plan and cancellation invoice plan for dynamic invoice plans. You can also set up the cancellation rule for amendment orders to override the package setting for the default cancel order rule.

  • blng__CreditNote__c

    Represents information about the amount that’s used to reduce the amount that a buyer owes a seller under the terms of an earlier invoice. A credit note always decreases the balance of an invoice. Users can apply positive credit notes to positive invoices, for example, a $10 credit note reduces the balance of a $100 invoice line to $90.

  • blng__CreditNoteAllocation__c

    Represents allocation information about a credit note line that’s been allocated to an invoice line.

  • blng__CreditNoteLine__c

    Represents product, service, adjustment, or tax line items that were included in a credit note.

  • blng__DebitNote__c

    Represents information about the positive balance change that you can allocate to an invoice line or a positive credit note line.

  • blng__DebitNoteLine__c

    Represents information about the amount that’s allocated to increase the balance of an invoice line.

  • blng__FinanceBook__c

    Represents the storage of financial transactions for reporting and recordkeeping.

  • blng__FinancePeriod__c

    Represents a reference object that stores lookups to all accounting or revenue transactions that occur within a specific period.

  • blng__GLAccount__c

    Represents the accounting journal entries in a General Ledger (GL) account. You can define both a credit GL account and a debit GL account as endpoints for these entries. These GL accounts, along with all associated records, can later be exported to an external GL bookkeeping system.

  • blng__GLRule__c

    Represents how transactions are recorded and categorized in the General Ledger (GL).

  • blng__GLTreatment__c

    Represents the lookups to a credit General Ledger (GL) account and a debit GL account. These lookups establish a relationship between your transaction and your GL accounts.

  • blng__Invoice__c

    Represents a financial document describing the total amount a buyer must pay for provided goods or services.

  • blng__InvoiceLine__c

    Represents the amount that a buyer must pay for a product, service, or fee. Invoice lines are created based on the amount of an order line.

  • blng__InvoicePlan__c

    Provides billing schedules with customizable billing frequencies. The invoice plan allows for non-standard billing intervals, skipping traditional monthly or quarterly cycles. For instance, the first payment occurs ten days after the sale, with the second payment two months later.

  • blng__InvoicePlanLine__c

    Represents the custom behavior for a single invoice transaction. An invoice plan contains the invoice plan lines.

  • blng__InvoiceRun__c

    During an invoice batch run, all billing schedules that meet the specified criteria are processed, resulting in the generation of invoices.

  • blng__InvoiceScheduler__c

    Represents whether and when an order product gets invoiced.

  • blng__LegalEntity__c

    Represents the way an organization is structured. An organization can be a single legal entity or it can comprise more than one legal entity.

  • blng__Payment__c

    Represents a single event when a shopper makes a payment. For credit cards, this event is a payment capture or payment sale, but it doesn’t appear on the shopper’s credit card statement.

  • blng__PaymentAllocationDebitNoteLine__c

    Represents an individual line item on a debit note allocated to a payment, used to track and manage payment allocations against debit notes for maintaining accurate financial records.

  • blng__PaymentAllocationInvoice__c

    Represents the allocation of payments to specific invoices. This object is used to track and manage how payments are applied to outstanding invoices, ensuring accurate financial records and reporting.

  • blng__PaymentAllocationInvoiceLine__c

    Represents the allocation of a payment to a specific invoice line. This object helps in tracking how payments are distributed across different invoice lines.

  • blng__PaymentAuthorization__c

    Represents the process of securing authorization from a customer’s bank or credit card issuer to charge a specific amount to their account, verifying the availability of sufficient funds or credit.

  • blng__PaymentGateway__c

    Represents the connection to an external payment gateway.

  • blng__PaymentGatewayConfig__c

    Represents the configuration for integrating Salesforce Billing with a payment gateway.

  • blng__PaymentMapping__c

    Represents the process of associating payment types, methods, or purposes with other information.

  • blng__PaymentMethod__c

    Represents the storage of information about different payment methods used by customers.

  • blng__PaymentRun__c

    Represents a batch processing job in Salesforce Billing. During a payment run, all payment schedules that meet the specified criteria are processed, resulting in the collection of payments.

  • blng__PaymentScheduler__c

    Represents automating payment runs by creating payment schedulers, which process the payment runs on a recurring basis.

  • blng__PaymentTerms__c

    Represents the period customers have to pay for an invoiced order product.

  • blng__PaymentTransaction__c

    Represents the payment transactions associated with a payment.

  • blng__Refund__c

    Represents a refund made against a payment.

  • blng__RefundLineCreditNoteLine__c

    Represents a relationship between a refund line and a credit note line.

  • blng__RefundLinePayment__c

    Represents a portion of a refund that’s applied to or unapplied from a payment. One refund line can represent the full amount of a refund.

  • blng__RevenueAdjustment__c

    Represents the adjustment to increase, decrease, or transfer the available balance between revenue schedules when actual revenue differs from the initial revenue schedule.

  • blng__RevenueAdjustmentLine__c

    Represents a type of revenue schedule balance change. You can have multiple adjustment lines that each target a different revenue schedule.

  • blng__RevenueAgreement__c

    Represents the objects with a revenue schedule related list. The revenue agreement is useful for grouping revenue schedules related to the same transaction, so that you can quickly evaluate revenue amounts for that transaction.

  • blng__RevenueDistributionMethod__c

    Represents how the revenue of a company is spread over a specific period.

  • blng__RevenueRecognitionRule__c

    Represents the creation of a revenue schedule for an invoiced order product or invoice line.

  • blng__RevenueRecognitionTreatment__c

    Represents how and where the revenue of a product is recognized.

  • blng__RevenueSchedule__c

    Represents the fields that you can use to review the amount of revenue already distributed and remaining to be allocated. A revenue schedule is associated with a revenue transaction.

  • blng__RevenueTransaction__c

    Represents the revenue transactions made against an order product.

  • blng__SubInvoiceLine__c

    Represents a detailed line item within an invoice that breaks down the provided charges or services.

  • blng__TaxConfig__c

    Represents the tax configuration associated with a billing schedule.

  • blng__TaxIntegration__c

    Represents the interaction between Salesforce and external tax calculation services or systems.

  • blng__TaxRate__c

    Represents a tax rate for a tax code and country.

  • blng__TaxRule__c

    Represents how Salesforce Billing processes tax for the transactions. All products that must be billed require a lookup to a tax rule.

  • blng__TaxTreatment__c

    Represents how Salesforce and external engines calculate taxes, and the tax engine to use for tax calculation.

  • blng__Usage__c

    Represents the amount of service consumed over a period of time.

  • blng__UsageSummary__c

    Represents the total quantity and value of related usages, and the date ranges for including usage records.