Generate financial data beyond the default transaction journal record fields with accounting field mappings.
| Available in: Lightning Experience |
| Available in: Enterprise, Performance, Unlimited, and Developer Editions with Accounting Subledger |
| User Permissions Needed | |
|---|---|
| To set up accounting field mappings: | Manage Accounting Subledger |
Before you create accounting field mappings, here are a few things to consider:
- You can create up to 10 accounting field mappings in an accounting set.
- You can’t edit or delete accounting field mappings used in active accounting sets. See Manage Accounting Sets.
- Deleting an accounting set via API or changing its object model also deletes its related accounting field mappings.
- You must create and add the custom fields to use as target fields on the Transaction Journal object. See Create Custom Fields.
To create accounting field mappings:
- From Setup, in the Quick Find box, enter Accounting Sets, and then select Accounting Sets.
- Next to the accounting set to which you want to add an accounting field mapping, click
, and then select View. - Click New Accounting Field Mapping.
- Select the source object to copy data from. The dropdown only lists the source objects that you included in the related accounting set’s object model.
- Select the source field to copy data from.
- Select a transaction journal target field to which you want to copy the data. The target field must meet these requirements:
- Its data type matches the selected source field. See Accounting Field Mappings.
- It’s not used in another accounting field mapping within the same accounting set.
- Click Next.
- Select a mapping behavior.
If you choose Current Value, 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.