Before using the TMF666 resource mappings, refer to the following.
Constraints and Limitations
TMF666 v5 currently supports the billingAccount resource. Billing accounts map to the Salesforce BillingAccount object.
Financial accounts are not supported in this release.
Sub-resource sorting is not implemented.
Out-of-the-box implementation is restricted to the core data model.
name and relatedParty are mandatory for POST. Each related party must include role and partyOrPartyRole.id. If contact is provided, each contact must include contactName.
DELETE is a soft delete. The API sets BillingAccount status to Inactive. The record is not physically deleted.
Only a single tax exemption is supported out of the box.
defaultPaymentMethod is not settable through POST or PATCH.
Default payment method. Not settable through POST or PATCH.
No
—
—
No
—
These attributes are patchable: name, state, accountType, bill structure format, presentation media, cycle specification frequency, and tax exemption certificate number, dates, and reason.
These attributes are not patchable: id, href, lastUpdate, relatedParty, contact, contact.contactMedium, and defaultPaymentMethod.
Sub-resources
Related Party
Related parties map through the AccountBillingAccount junction to Account.
TMF Field
Description
Supported
Salesforce Mapping
Mandatory for POST
role
Role played by the related party.
Yes
AccountBillingAccount.RelationshipType
Yes, when relatedParty is provided
@type
Sub-class name.
Yes
Hardcoded: RelatedPartyRefOrRelatedPartyRoleRef
Yes, when relatedParty is provided
partyOrPartyRole.id
Unique identifier of the related party.
Yes
AccountBillingAccount.Account
Yes, when relatedParty is provided
partyOrPartyRole.name
Name of the related party.
Yes
Account.Name
No
partyOrPartyRole.href
Hyperlink reference.
Yes
Derived
No
partyOrPartyRole.@type
Sub-class name.
Yes
Hardcoded: PartyRefOrPartyRoleRef
No
Bill Structure
TMF Field
Description
Supported
Salesforce Mapping
Mandatory for POST
@type
Sub-class name. Always BillStructure.
Yes
Hardcoded
No
format.name
Bill format, such as detailed or summary.
Yes
BillingAccount.ExtlBillFormat
No
format.@type
Always BillFormat.
Yes
Hardcoded
No
presentationMedia.name
Delivery method, such as email or paper.
Yes
BillingAccount.ExtlBillDeliveryMethod
No
presentationMedia.@type
Always BillPresentationMedia.
Yes
Hardcoded
No
cycleSpecification.frequency
Billing frequency, such as monthly.
Yes
BillingAccount.ExtlBillFrequency
No
cycleSpecification.@type
Always BillingCycleSpecification.
Yes
Hardcoded
No
cycleSpecification.DateShift
Offset of a billing date.
No
—
No
Contact
Contacts map through the BillingAccountContact junction to Contact.
TMF Field
Description
Supported
Salesforce Mapping
Mandatory for POST
id
Identifier of the contact.
Yes
Id
No
contactName
Displayable name for the contact.
Yes
Contact.Name
Yes, when contact is provided
contactType
Type of contact, such as primary.
Yes
BillingAccountContact.RelationshipType
No
validFor
Validity period.
Yes
startDateTime and endDateTime
No
@type
Sub-class name. Always Contact.
Yes
Hardcoded
No
contactMedium.emailAddress
Billing email.
Yes
BillingAccount.BillingEmailAddress
No
contactMedium.phoneNumber
Phone.
Yes
Contact.Phone
No
contactMedium.faxNumber
Fax.
Yes
Contact.Fax
No
contactMedium street, city, state, postCode, country
Billing address.
Yes
PrimaryBillAddr fields on BillingAccount
No
contactMedium.@type
Discriminator for email, phone, fax, or geographic address.
Yes
Hardcoded discriminator
No
Tax Exemption
Only a single tax exemption is supported out of the box.