You are here:
Accounting Field Mappings
Create accounting field mappings to bring your data to custom fields on transaction journal records.
| Available in: Lightning Experience |
| Available in: Enterprise, Performance, Unlimited, and Developer Editions with Accounting Subledger |
Transaction journal records include default fields populated from eligible source objects. If your accounting system requires data beyond the default fields, create custom fields and accounting field mappings in accounting sets to copy your data to those custom fields. For example, your GAU Allocation object has custom fields that represent different donor categories in your organization. To reflect this breakdown on the generated cash flows, create matching custom fields on the Transaction Journal object.
- Mapping Behavior
The mapping behavior controls whether Salesforce creates transaction journal records when the source data changes. - Compatible Data Types
Mapped fields must be of compatible data types.
Mapping Behavior
The mapping behavior controls whether Salesforce creates transaction journal records when the source data changes.
- Point-in-time: Copies the source field value to the transaction journal record target field when Accounting Subledger creates the record. Salesforce ignores any subsequent updates to the source field, and doesn't create more transaction journal records.
- Current value: Copies the source field value to the transaction journal record target field when Accounting Subledger creates the record. Salesforce evaluates subsequent source value updates, and creates reversals and other records accordingly. Don't add automation that updates transaction journal record values. If you do, Accounting Subledger sometimes creates unnecessary reversals and transaction journal records. Instead, create a second field outside of any accounting field mapping to store the transaction journal record value, and add automation to that second field. Use the source value on the transaction journal record only for mapping and comparison. Some objects such as the Fund object don't support the current value behavior.
Compatible Data Types
Mapped fields must be of compatible data types.
| Source Field Data Type | Custom Field Data Type |
|---|---|
| Checkbox | Checkbox |
| Currency | Currency, number |
| Date | Date |
| Date/Time | Date/Time |
| Email, text, text area | |
| Number | Currency, number |
| Percent | Number, percent |
| Phone | Phone, text, text area |
| Picklist | Picklist, picklist (multi-select), text, text area |
| Picklist (combo box) | Picklist, string, text area |
| Picklist (multi-select) | Picklist (multi-select), text, text area |
| Reference | Email, phone, reference, text, text area |
| Text area | Text, text area |
See Create Custom Fields and Create Accounting Field Mappings.
