Mapping Custom Salesforce Billing Fields Between Objects
Certain pairs of Salesforce Billing objects pass custom field values from the first
object to the second object when the second object is created. The values pass if the custom
fields are editable, have matching field types, and have matching API names. We call these field
pairs “twin fields.” (Salesforce Billing Managed Package)
Required Editions
Available in: All Salesforce Billing Editions
Important
To map one field to another, you need Read access on the source field and Edit access on the
target field.
Standard fields and package fields can't map to or from any other fields.
Salesforce Billing can't map values from a formula field that returns text to a text
field.
Objects in Column 1 pass field values to custom fields with matching types and API names from
the objects in Column 2.
Column 1
Column 2
Credit Note Line
Revenue Schedule
Debit Note Line
Revenue Schedule
Invoice
Credit Note
Note Invoice fields map to credit note fields automatically when you click
Cancel and Rebill. To manually create a credit note on your invoice
and map the invoice fields, provide a lookup to the invoice record on the credit note’s
Source Invoice field.
Invoice Line
Credit Note Line
Invoice Line
Payment Allocation Invoice Line
Payment Allocation Invoice Line (Custom Field Type: Allocation)
Payment Allocation Invoice Line (Custom Field Type: Unallocation)
Note When a payment
is unallocated from an invoice line, the custom fields on the payment allocation invoice
line of type Allocation are transferred to a payment allocation invoice line of type
Unallocation.
Invoice Line
Revenue Schedule
Order Product
Invoice Line
Order Product
Revenue Schedule
Did this article solve your issue?
Let us know so we can improve!
Loading
Salesforce Help | Article
Cookie Consent Manager
General Information
Required Cookies
Functional Cookies
Advertising Cookies
General Information
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required Cookies
Always Active
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional Cookies
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising Cookies
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.