Salesforce Field Mapping

Complete field mapping reference for syncing data between MonetizeNow and Salesforce, including Product Catalog, Accounts, Contacts, and Opportunities.

📘

Fields that sync in the MonetizeNow managed package

Product Catalog
Monetize Now FieldSalesforce Field (namespace prefix omitted)Required
id (Offering)monetize__OfferingId__cYes
id (Product)monetize__ProductId__cYes
name (Offering) + " - " + name (Product)NameYes
name (Offering)monetize__OfferingName__cYes
description (Offering)DescriptionNo
status (Offering) && status (Product)IsActive (boolean)Yes
startDate (Offering)monetize__StartDate__cNo
endDate (Offering)monetize__EndDate__cNo
id (Offering) + "-" + id (Product)monetize__ExternalId__cYes
productType (Product)monetize__ProductType__cNo
product.UsageType.Name (Product)monetize__UsageTypeName__cNo
product.UsageType.Description (Product)monetize__UsageTypeDescription__cNo
product.UsageType.Unit (Product)monetize__UsageTypeUnit__cNo
System Generatedmonetize__LastSyncDate__c (DateTime)Yes
Account
Monetize Now FieldSalesforce FieldRequired
Idmonetize__Id__cYes
CustomIdIdYes
companyNameNameYes
isTestAccountNo
localeNo
currencymonetize__BillingCurrency__cNo
statusmonetize__BillingStatus__c (Picklist)No
primaryContactmonetize__PrimaryBillingContact__c (Lookup)No
monetize__EnableSync__cYes
monetize__LastSyncDate__c (DateTime)Yes
monetize__SyncError__c (long text)No
Contact
MN FieldSalesforce FieldRequired
idmonetize__Id__cYes
customIdIdYes
accountIdAccount.Id__c
fullNameFirst Name + LastName
(SFDC → MN will use Name field)Yes
statusmonetize__BillingStatus__cNo
emailEmailNo
phonePhoneNo
address.id
address.line1MailingStreet (concatenate with new line)No
address.line2
address.cityMailingCityNo
address.stateMailingStateNo
address.countryMailingCountryNo
address.postalCodeMailingPostalCodeNo
address.description
monetize__EnableSync__cYes
monetize__LastSyncDate__c (DateTime)Yes
monetize__SyncError__c (long text)No
Opportunity
MN FieldSalesforce FieldRequired
CustomIdIdYes
Idmonetize__Id__cNo
monetize__LifecycleType__cNo
monetize__PrimaryQuote__cNo
OpportunityLineItem
MN FieldSalesforce FieldRequired
QuoteOffering.Id + “-” + QuoteItem.Idmonetize__ExternalId__cYes
monetize__QuoteItem__cNo
Quote
MN FieldSalesforce FieldRequired
CustomIdIdYes
Idmonetize__Id__c
descriptionNameYes
AccountIdmonetize__Account__c
approvalGrantedDatemonetize__ApprovalGrantedDate__c
approvalSubmittedDatemonetize__ApprovalSubmittedDate__c
contacts.billingmonetize__BillingContact__c
contacts.primarymonetize__PrimaryContact__c
contractAmendmentDatemonetize__ContractAmendmentDate__c
contractEndDatemonetize__ContractEndDate__c
contractLengthmonetize__ContractLength__c
contractStartDatemonetize__ContractStartDate__c
contractTermsmonetize__ContractTerms__c
currencymonetize__Currency__c
descriptionmonetize__Description__c
documentUrlmonetize__DocumentUrl__c
expirationDatemonetize__ExpirationDate__c
netTermsmonetize__NetTerms__c
opportunityIdmonetize__Opportunity__r.monetize__Id__c
originalQuoteIdmonetize__OriginalQuote__r.monetize__Id__c
previousQuotemonetize__PreviousQuote__r.monetize__Id__c
primaryQuoteForOpportunitymonetize__Primary__c
statusmonetize__Status__c
totalValuemonetize__TotalValue__c
typemonetize__Type__c
revenueMetrics.arrmonetize__ARR__c
revenueMetrics.mrrmonetize__MRR__c
revenueMetrics.incrementalArrmonetize__IncrementalARR__c
revenueMetrics.incrementalMrrmonetize__IncrementalMRR__c
QuoteItem
MN FieldSalesforce FieldRequired
Id
Idmonetize__Id__cYes
discountmonetize__Discount__c
Id (offering) or quoteOfferingId (quote item)monetize__OfferingId__cYes
monetize__OpportunityProduct__c
monetize__PricebookEntryId__c
productId (quote item)monetize__Product__r.ExternalId
Ratemonetize__Rate__c
quantity (quote item)monetize__Quantity__cYes
quoteId (offering)monetize__Quote__r.monetize__Id__cYes
rateId (offering)monetize__RateId__c
Amount (quote item)monetize__ContractAmount__cYes
unitPrice (quote item)monetize__UnitPrice__cYes
unitPriceAfterDiscount (quote item)monetize__UnitPriceAfterDiscount__cYes
revenueMetrics.arrmonetize__ARR__c
revenueMetrics.mrrmonetize__MRR__c
revenueMetrics.incrementalArrmonetize__IncrementalARR__c
revenueMetrics.incrementalMrrmonetize__IncrementalMRR__c
Contract
MN FieldSalesforce FieldRequired
monetize__CreateRenewalOpportunity__cNo
Idmonetize__Id__cYes
accountIdAccountIdYes
latestQuoteIdmonetize__LatestQuote__cYes
statusmonetize__Status__cYes
statusStatus
startDateStartDate
endDateContractTerm
EndDateYes
endActionmonetize__EndAction__cYes
totalValueTODO
contactContact
lastSyncDatemonetize__LastSyncDate__cYes
previousContractmonetize__PreviousContract__cYes
renewalOpportunitymonetize__RenewalOpportunity__c
Rate
MN FieldSalesforce FieldRequired
idId__cYes
nameNameYes
billingFrequencyBillingFrequency__cYes
currencyCurrency__cYes
descriptionDescription__c
startDateStartDate__c
endDateEndDate__c
lockedLocked__c
offering.idOfferingId__cYes
offering.nameOfferingName__cYes
quotableQuotable__c
rateTypeRateType__cYes
statusStatus__cYes
usageBillingFrequencyUsageBillingFrequency__c
Price (Child of Rate)
MN FieldSalesforce FieldRequired
idId__cYes
fromFrom__cYes
toTo__cNo
amountAmount__cYes
priceModelPriceModel__cYes
product.ProductTypeProductType__cYes
product.idProduct__cYes
rate.IdRate__cYes
product.statusStatus__cYes

Mapping data from Salesforce to MonetizeNow

Fields from Salesforce may be mapped to Standard and Custom Fields on Quote in MonetizeNow. The following object mappings are available:

  1. Salesforce Account to MonetizeNow Account
  2. Salesforce Contact to MonetizeNow Contact
  3. Salesforce Opportunity to MonetizeNow Quote

The most common use case is to drive approval, validation, and conditional term logic in MonetizeNow using data from Salesforce. Specific examples are provided on Custom Fields page.

You can configure the mapping on the CRM Configuration page in MonetizeNow.


Mapping data from MonetizeNow to Salesforce

MonetizeNow automatically synchronizes most Quote data from MonetizeNow to Salesforce, but we also support mapping custom Quote fields from MonetizeNow to Salesforce.

To configure this, all you need to do is create custom fields in each system that have matching API names.

Additional Considerations:

  1. Case insensitive
  2. Ignores special characters
  3. Ignores the Salesforce suffix of __c
  4. Will never auto-map to a field with the monetize__ managed package prefix
  5. The data types must be compatible (e.g. a number or boolean cannot map to a string field)
  6. We can only map identical objects using this approach. For example, a MonetizeNow quote to a Salesforce Quote. If you need data to flow from a Salesforce Quote to another Salesforce object, your best option would be to utilize Salesforce Flows.
MonetizeNow fieldSalesforce fieldIs Eligible for Auto-Mapping?
my_custom_fieldmy_custom_field__cYes - assuming data types are compatible
my_custom_fieldMyCustomField__cYes - assuming data types are compatible
mycustomfieldMy_Custom_Field__cYes - assuming data types are compatible
amountmonetize__amount__cNo - managed package fields will never get overwritten

FAQs


📘

How can I push invoice payment status from MonetizeNow to Salesforce opportunities?

While Salesforce doesn't natively allow external platforms (like MonetizeNow) to update invoice-related fields inside Opportunities, you can set up custom automations in SFDC to surface invoice payment statuses where your sales teams need them.

What's the Alternate Solution?: Many MonetizeNow customers solve this by building custom flows within Salesforce. These flows typically pull invoice data from MonetizeNow and display key payment status fields directly on the Opportunity record. This gives your Sales team visibility into outstanding invoices tied to deals they've closed, without needing to leave SFDC.

Here's a quick breakdown of how it works:

  1. Sync Invoice Data from MonetizeNow to SFDC: Use our standard Invoice APIs to fetch the invoice details you need.
  2. Map MonetizeNow Invoice Data to Custom Fields in SFDC: You'll want to create custom fields on the Opportunity object to house this data.
    For example:
    • Invoice ID
    • Payment Status (Paid, Unpaid, Overdue, etc.)
    • Due Date
    • Invoice Amount
  3. Automate the Flow Between Invoice and Opportunity: We recommend linking invoices to Opportunities using a shared reference field (e.g., Deal ID or Subscription ID). Once the link is in place, your flow can automatically display the invoice status on the Opportunity page layout, making it easy for reps to spot outstanding payments.